Results 1 to 5 of 5

Hybrid View

  1. #1
    Join Date
    Aug 2011
    Posts
    75

    Trouble w Mammoth RTU I/O Pro 812U Bacnet

    I am trying to connect an FX60 to a mammoth RTU with a I/O Pro 812u. I am connecting with a 3' piece of wire from the internal RS485 card to the port2a (net+, net-). I have setup bacnet correctly and have tested with known good controllers. I cannot add this 812U manually or with discover.

    My wiring is @ 812u red net+ // blk net- @ FX60 red+// blk - (no ground)

    I have tried various speeds without luck. This controller allows you to choose N2 which I did, and was able to discover the device without issue when I added a N2 network. My job spec'd Bacnet MSTP though.

    I have selected MS/TP MASTER and selected 2 wire/ 485 on the units jumpers.


    I know the JACE is setup without issue because I can talk to a PCT controller when connected. My device network is 2001 and 812u is using 12 as the address.

    Any help is appreciated.

  2. #2
    Join Date
    Aug 2011
    Posts
    75
    Fixed. Tech support had me hardcode the JACES bacnet network # into the 812u via BacView. BacView Password was 09876

  3. #3
    Join Date
    Jun 2009
    Location
    StL, MO
    Posts
    572
    Thanks for letting us know how you resolved the issue.
    UA LU 562

  4. #4
    Join Date
    Mar 2005
    Location
    Pacific Time Zone
    Posts
    4,151
    Ditto
    "How it can be considered "Open" is beyond me. Calling it "voyeur-ed" would be more accurate." pka LeroyMac, SkyIsBlue, fka Freddy-B, Mongo, IndyBlue
    BIG Government = More Dependents
    "Any 'standard' would be great if it didn't get bastardised by corporate self interest." MatrixTransform
    http://threedevilskennel.com/ - not my website.
    Versatile Hunting Dog Federation - www.vhdf.org/


  5. #5
    Join Date
    Dec 2006
    Location
    What? Who? Where?
    Posts
    1,650
    I have heard rumors off this. Basically controller will not communicate unless it's network matches the one it is connected to.
    It was indicated that this is part of the future "BACnet security". Basically another way to lock down your system, not sure this is a good thing.
    I see more and more vendors jumping on this "BACnet security" before a standard has been set. Welcome to the WWW (Wild Wild West). And remember the West Coast is the best coast.

    kontrol out
    "Open is as open does." - Forrest Gump
    "Can't we all just get a Lon?" - Garry Jack
    "BACnet: integration or interrogation?" - The Janitor
    "Open protocols? You can't handle open protocols!" - Nathan R. Jessup
    “What’s that? Aaa… open protocols? Don’t talk about…. open protocols? Are you kidding me? Open protocols? I just hope we can hardwire an interface!” - Jim Mora http://www.youtube.com/watch?v=U7fjDS0jKiE

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