Results 1 to 2 of 2

Thread: Carrier DOAS units issues

  1. #1
    Join Date
    May 2018
    Location
    VA/DC
    Posts
    452
    Post Likes

    Carrier DOAS units issues

    Here recently we have 2 doas units on a job that have been acting funny when controlled by bacnet. Carrier installed a new clipping file in the unit and bam communications was gone!
    I received the original and new clipping files ( big difference in the driver number ) App loading all 3 only the original one worked. Now most people are just using this with the equipment touch and will never know.

    Those who may try to bacnet to them and cant discover ( after setting the comm and router settings and dip switches) it may very well not be you.

    There is a permission key for those using field assistant or ivu.

  2. #2
    Join Date
    May 2009
    Location
    SC
    Posts
    2,868
    Post Likes
    They were reset to factory defaults, blew away any setpoints you had too. Far as I'm concerned if I have to go back and "fix" this by putting the BACnet info again that's billable cleanup work. Reasonably certain you don't need FA to do it, just a terminal emulator. If you have a label on the unit door saying what the device instance addressing and speed it lends credibility to the PO request.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •