Jump to content

Barry

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Barry

  • Rank
    Newbie

Recent Profile Visitors

93 profile views
  1. Deja vous, Ausman? I'm interested because someone else is looking for info on what seems to be a seldom used module, but concerned because we were never able to get the 232 port on the 02RSC to work. Either in serial or modbus configurations. At this point you ought to get a special commendation for dealing with this hardware.
  2. That's a brilliant point. The Vision series aren't too expensive, and would allow us to really expand almost infinitely one modbus (borrowing from IP terminology for lack of better word) subnet at a time. Create a backbone that's effectively... Unistream ---> Vision ---> Vision ---> Vision ---> ad infinitum ... and split off from the Visions for our smaller I/O heavy devices. In a related point I did get a response from Unitronics about the ports on the 02RSC... "...You absolutely will have the ability to have them both be masters. The RS232 port will be one to one where the RS485 port can be the master to multiple slaves in a daisy chain network...." But that's still at odds with what Unilogic will allow me to configure. I'll respond to them in the AM, and maybe after some coffee I'll be able to communicate a little more clearly than I usually do. Thank you for your help and guidance!
  3. You're right, I had an old spec sheet for the 02RSC that says 32 devices, but Unilogic doesn't seem to have a problem with me adding and compiling with triple that number (although it does enforce the 1-247 addressing limit, while the built-in master lets you assign 1-255). I'm making a stupidly-dangerous assumption that if it compiles it might allow me to operate that way... I have a feeling I'm missing a lot of details on these ports. Wish there was better documentation on them.
  4. You're absolutely correct, I missed the mark in the original post. We're likely to end up with more addresses than the built-in can handle eventually, but the critical issue is the operations limit on the modules. Ah, use one as a hub for expanding the network. That or a gateway. Good call; that's likely our best bet. ((Edit: you're actually more right than you realize. It might be time for us to find a stronger side kick than the existing little PLCs)) If we could use those serial ports we'd be able to pull it off with just existing hardware. Our last install (half this size) was already a massive system... If we can stick to snap-on or built in systems it would be nice for a change. The last thing we need is ANOTHER panel when we can squeeze what we need out of what's there.
  5. We would only end up with 2 or three devices on each of the expansion module masters, so the 32 address limit isn't a big deal. Because those devices have almost 200 operations each we'd max out that limit almost immediately. Hence the need for using the serial ports as additional masters. The idea is to gain another 512 operations; not necessarily more addresses. Unfortunately the small PLCs we use aren't capable of upstream and downstream networks, otherwise they would make for a perfect bridge. But for their cost I can't complain. We might need to consider switching to ones that allow us that method of expansion. For now utilizing the 232 ports as modbus would solve our problem. Presuming we can get them to work.
  6. Yes, Modbus spec is limited to 247 addresses but Unilogic will let you use the full binary 1-255. I've never actually connected more than 247 devices so I don't know what would happen. Those shoes you're talking about are mine, and I've never had a problem walking in them. You're only going to end up with conflicts if you screw up the addressing. So far I've managed to count into the mid 200's without hurting myself. Uniapps alone would clue you in to which devices are in conflict if there is one, let alone any basic in-program diagnostics. The built-in master is running about 200 small sensors (Dwyer temp/humidity/co2 devices). Each only has 4-6 operations. It's lightweight data-wise; just a long string of devices. Low polling rates, updates only once every few seconds. We've set these networks up many times before with no problems. Surprisingly durable even when the network topology is abused. The reason we need such a heavy operations load is our I/O network is comprised of a fleet of Click PLCs (small, cheap, durable, modular devices from Automation Direct). Unfortunately dollar-per-I/O it's a better deal than the local or remote expansion kits, or even the EX-RC1. ((EDIT: We use the Click PLCs because if they lost communications to the Unistream they can act autonomously)) Each one handles a ton of environmental and facility control systems. Easily 200 operations each. The max for the 02RSC is 512 operations. While it means we're burning off an entire modbus master on effectively two or three slaves I don't know another way around it. Also, many of these devices would end up in completely different parts of the facility and having seperate networks would simplify the wiring. There are no gateways, so far everything has been a direct connection back to the unistream. So the original question: How are the 232 ports, when configured in Unilogic as Modbus masters, different from the 485 port? I'm guessing the hardware inside the module isn't strictly speaking a serial comm port (5v-15v logic, single ended, etc) but rather it's emulating those characteristics.
  7. Good morning everyone! We are about to begin work on a Modbus deployment that will need far more than just the 255 addresses available on the built in CPU master. I know we can add up to three of the UAC-02RSC UniComm modules for three more masters. Unfortunately, the masters on the 02RSC have a limit of 512 operations each, so we’re going to need all three modules and then some. I’m interested in using the serial port on the top of those modules as well. Unilogic and the built-in help file shows that we can turn them into Modbus masters, but we’re not having any success getting it to communicate with our sensors and devices. We’re using a small header-to-terminal block plug to give us access to pins two and three (TX and RX) but I’m not sure that’s correct for what we’re doing here. Thank you in advance for any help you can give us on the serial connection!
×
×
  • Create New...