Predator Integrated Into JACE 600? - Page 2
Page 2 of 2 FirstFirst 12
Results 14 to 19 of 19
  1. #14
    Join Date
    Nov 2007
    Location
    Phoenix, AZ
    Posts
    256

    Predators

    NINAX

    Not that, the lmnl files in 3.0 and up are not right. Staefa says that it is a Tridium problem, its not, Staefa did not keep up with the Lon world so there is a real problem with this line. If you commission a new Four Loop on AX 3.0 and up it will most likely eat the app. Making the controller no good. The best way for the Four Loop is to commission in R2 first. Once it has been commissioned the problem goes away. The rest of the line (Except for VAV104s) is another can of worms and requires a real understanding of Tridium/Lon. All of this can be worked around.

    Greg

  2. #15
    Join Date
    Nov 2007
    Location
    Phoenix, AZ
    Posts
    256

    Predators

    Let me add that if you upgrade from R2 to AX 3.0 and up, the lnml files won't match up with the controllers. This dose not hold true with the new controllers, just the older ones. There is a way to fix this, but you have to be careful or you are going to reflash the controllers with the old image files to the new one.

    G

  3. #16
    Join Date
    Jun 2005
    Location
    Ohio
    Posts
    1,720
    Quote Originally Posted by GregF View Post
    Let me add that if you upgrade from R2 to AX 3.0 and up, the lnml files won't match up with the controllers. This dose not hold true with the new controllers, just the older ones. There is a way to fix this, but you have to be careful or you are going to reflash the controllers with the old image files to the new one.

    G
    Could you please expand on your reply.
    My intent is to use the AX V3.3.22 LON Device/Point Managers to discover the existing Predator points and bring them into the AX JACE via Lon driver. I do not want to change anything in the Predators.
    Will AX cause the INML file problems you describe?
    Thanks.
    jogas
    Jogas
    Four wheel therapy, my 1968 Camaro is gone and will be missed

  4. #17
    Join Date
    Nov 2007
    Location
    Phoenix, AZ
    Posts
    256

    Predators

    jogas

    Its not the AX or the lmnl file its the Predator. From what you posted th four loop controllers have been commissioned in R2, this makes the problem go away. You should not have any problems at this point and this works with most of the line, unless its version one. However the vav102s are a real problem if you upgrade from R2 to AX (AX version 3.0 and up). It can be fixed without reflashing the controllers (102s).
    Just did not want you to go through what I have.

    G

  5. #18
    Join Date
    Jun 2005
    Location
    Ohio
    Posts
    1,720
    Quote Originally Posted by GregF View Post
    jogas

    Its not the AX or the lmnl file its the Predator. From what you posted th four loop controllers have been commissioned in R2, this makes the problem go away. You should not have any problems at this point and this works with most of the line, unless its version one. However the vav102s are a real problem if you upgrade from R2 to AX (AX version 3.0 and up). It can be fixed without reflashing the controllers (102s).
    Just did not want you to go through what I have.

    G
    Greg,
    Thanks for the clarification. I'm feeling a lot better about this part of the job now.
    The next interesting part of the job will be the JCI N2 integration, but that's another topic.
    again, many thanks.
    jogas
    Jogas
    Four wheel therapy, my 1968 Camaro is gone and will be missed

  6. #19
    Actually it is a problem with both the Predator Controller and the way Tridium does their LON commisioning within AX and R2. The Predator issue has been resovled, all of them have been re-worked and now the problem won't occur. Just look for the V4 on the UPC symbol.
    But if you are using another manufacturer this problem may occur. The reason for this is because Tridium writes to the Lon nodes to fast and doesn't allow the device to reset. Depending on what version of the Echelon library the application was built on would determine if the problem may occur. Anything that has been built on Echelon library 10 or greater, would have this problem.
    In R2 there was a work around for this that resolved the issue, but this work around didn't work within AX. This is why it seems that it works in R2, but the reality of it is it will work until the user commisions the device and then the problem may occur.
    Tridium has fixed alot of LON issue within 3.3.22, which was previously blamed on Lon wiring.

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Comfortech Show Promo Image

Related Forums

Plumbing Talks | Contractor Magazine
Forums | Electrical Construction & Maintenance (EC&M) Magazine
Comfortech365 Virtual Event