
Visit our shop for nerds in control lifestyle products.
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
rearranging their prejudices.
-- William James
www.control.com/rss/
To get a personalized feed, become a member at no cost.
While it has never been tested with 200 devices the PeakHMI RLL program has MODBUS TCP master and slave included. It does not have a limit on the number of connections.
And at the moment it is free.
http://www.hmisys.com
Regards,
Mark
You will also find a link to it from the Modbus.org web site (look on the "technical resources" page).
You would use the mbserver (release 2) package. There is introductory web based documentation at http://mblogic.sourceforge.net/ The package itself has more detailed web based documentation available through a built in web server which is accessable when you install it. I will be adding the content of those additional pages to the Sourceforge web site within the next couple of days, so you will be able to read them without installing MBServer.
The software runs on a PC. There are no limits to the number of client (master) connections, but if you have a lot of connections and are polling at a fast rate you will want a fast PC to handle the communications load. Check the CPU load on your PC as you add connections. If need be, you could split the load between several PCs. The software itself won't cost you anything, so it's just a matter of how many PCs you want to set up.
The size of the messages themselves is relatively unimportant. What matters is how many messages per second are being sent and received. This means the load on the slave (server) portion of the software will be relatively unimportant, as you will be reading and writing fewer larger messages.
If you want to load test the PC, there is another package at the same location called mbasyncserver which can be used to act as just a slave (or you could just set up a second instance of MBServer with no clients active). Set up MBServer on one PC, and mbasyncserver on another. Then set the MBServer configuration to open up 200 connections to mbasyncserver and do the same polling commands you would use for the drives. The reason for using two different PCs is so that the second server isn't adding its processing load to the same PC.
If you are interested and have further questions, let me know and I will be happy to answer them.
I am more interested in a standalone industrial grade device, preferrably din rail mounted that can act as a server.
We do not want to have all 200 devices on the same server, about 10 ~15 devices would be preffered per server as this will reduce the risk of single point failure.
Can you recommand a device that can serve this purpose.
Regards
Syed Hussain
As for an out of the box solution, I don't know of a system that is exactly what you want. You may want to consider using some small PLCs as data concentrators. Quite a few support Modbus/TCP with master and slave modules. You would have to program the communications for them however, so it isn't entirely "out of the box" either. Whether you are configuring MBServer or programming a PLC, I don't see how you could avoid telling a system what addresses to read from what drives.
I would be careful about loading any system (including the Honeywell) to its rated limit though. Often, the limit on the number of connections allowed is a crude form of load limiting. The processors in many PLCs (and other proprietary controllers) are relatively slow, and they can get bogged down with communications quite easily. Whether or not this would be a problem for you depends on how fast you are polling.
Typically, it is more efficient to transfer one large message than several small ones. I would suggest trying to group the messages from different drives close together in the memory of each data concentrator so you can read them all with one function call from the Honeywell.
We will be interfacing ABB LV and AB MV VSD drives with the Experion C300 controllers.
I have found information on an off the shelf ABB LV VSD module called NETA module that can talk Modbus TCP and can connect up to 9 drive on an ABB proprietary protocol called DDCS. Which is what we are considering. So the DCS would be talking to the NETA card and NETA would be talking to 9 drives using DDCS protocol on a fibre optic ring or star fibre optic topology.
Does anyone have any idea about the DDCS protocol? I could not find any decent documentation on the Net.
We are still looking for a solution for the Allen-Bradley MV VSDs, we are considering an option like Controlnet and then probably a Controlnet to Modbus TCP gateway. Any thoughts on that? Any thoughts on a solution that does not involve a PLC in the middle would be very appreciated.
Regards,
Syed Hussain
I'd have a look at Prosoft Technology's Prolinx line of products.
http://www.prosoft-technology.com
If you don't find what you're looking for, I recommend calling their technical support to point you in the right direction.
If someone needs more details they can contact either myself @ syed. hussain at wapl. com. au or the vendor directly.
Cheers.
We have used Sixnet concentrators and RTUs for years with excellent results.
- ABCs of SBCs: Single board computers for embedded control; Lego learning
- Less, more: NEMA cites less confidence; NAM sees more exports of manufactured goods
- Free webinar on Zigbee for embedded systems
- Better together? Ametek, Dresser-Rand, IntervalZero, Rexroth make acquisitions
- You need 2 monitors: This Website will prove it
- Preview: Mitsubishi iQ controls sequence, motion, process, CNC, robotics; has connectivity
- 30 new Rockwell Automation products integrate hardware, software
- Digital manufacturing: Autodesk Inventor shows component interactions
- Software certified by AT&T: Runs on PDAs, cellphones, enables mobile applications
- Research: HMI supervisory software use increases with service needs
Patronize our advertisers!




