MRX/MWX through ECOMM100

[davidbgtx]

ADC/Koyo did address it in their implementation of the DirectLOGIC MRX/MWX instructions for the 260 and 06 CPUs built-in serial ports.  The 06 even supports MRX/MWX in its DCM module.  However, DirectSOFT's MRX/MWX instructions do not work for ECOMs in DL world.

Do-more's native Modbus MRX/MWX instructions work for built-in serial, built-in Ethernet, and SERIO modules, but not ECOM100 module.  At least you can do the DL Hack of the Modbus Hack when using Modbus via ECOM100 in Do-more .

Can I get this on the wish list, Do-more's native Modbus MRX/MWX instructions to work with ECOM100

[Scot]

The client will only be able to access M-memory in your server Do-more. It cannot access C60. To access C60 you will have to use the PUBLISH in your server to move C60 to somewhere in M-memory and then correspondingly, use the map as shown in the above PDF document and enter the correct Type & Offset in your DLRX instruction in your client to get it.

Hope this helps!

Can't publish a "C", however I was able to use MOVER (C60 to MHRxx) and then in the client DLRX the V(MHRxx) to a V, and it worked. So with a bottle of aspirin and your help, I can make this work, Thanks.

The whole reason for this was to segregate some of my traffic by putting the ECOM100 in the DO-More Client rack, beginning to wonder if it's worth the effort, maybe I'll investigate a managed switch/s with vlan.
 Thanks again

I've tried the managed switch route. I was unable to get it to work. A switch manufacturer thought that setting up a 1-1 NAT between the Do-More IP and the external network would work. But it didn't. I bought an expensive industrial switch but even the switch manufacturer couldn't get it to work. The only way it would have worked was if there was only 1 Do-More on the network, but then you wouldn't need the managed switch anyway (or an ECOM card).
The only thing I've been able to get to work with multiple Do-More CPUs on the same network is to use the ECOM100 card for network access and the Do-More port for the isolated expansion network. Then you have the issues with the ECOM100 limitations, but it's the only option that I've found that works.

[BobO]

When y'all are talking about segregating traffic and certain system configurations not working, can you be more specific and what doesn't work? There are a few things we use broadcasts for, but for the most part we avoid them, and as such I would expect a normal switch to keep things pretty clean. If you are using the onboard port for I/O, and wanting to keep HMI traffic off that port, then yeah, the ECOM is the only way around that (at the present time ).

[Mike Nash]

I know what you mean; I'm so much happier with today's hardware (from all PLC manufacturers) than 1985 era stuff.  Life is good now!

I just last week ran into a failed SLC-500 DC output card that had OCTAL stenciled on the front and the terminal layout card in the door was octal. It was in a remote rack on a VMEbus PLC5. That's all that was different and a standard part number worked just fine.

[Controls Guy]

Yup.  SLC modules came with both octal and decimal door labels (and clear adhesive labels for the module status LEDs) so you'd have whichever you needed depending on whether the processor was a SLC or a PLC.  IIRC, PLC modules did too, in case you used them as SLC RIO.  I just slapped an old SLC module with an octal door label into a SLC system a couple months ago, and the program didn't mind a bit! 

[BobO]

I wouldn't recommend that with the BCD model.

[Scot]

When y'all are talking about segregating traffic and certain system configurations not working, can you be more specific and what doesn't work? There are a few things we use broadcasts for, but for the most part we avoid them, and as such I would expect a normal switch to keep things pretty clean. If you are using the onboard port for I/O, and wanting to keep HMI traffic off that port, then yeah, the ECOM is the only way around that (at the present time ).

Yes, that's what I meant by isolated expansion networks. The network for the expansion bases is physically separated from the HMI/programming network. So each PLC is connected to only it's own expansion bases and through a different connection (the ECOM100) to the HMI network. That way each expansion base is visible to only it's master CPU. No other Do-More can see it.