News:

  • May 15, 2025, 02:53:56 PM

Login with username, password and session length

Author Topic: Read MHR Memory thru H2-ECOM100  (Read 218 times)

rockhead

  • Newbie
  • *
  • Posts: 5
Read MHR Memory thru H2-ECOM100
« on: May 08, 2025, 02:31:38 PM »
I have a H2-DM1E CPU in a 205 9-slot rack with a H2-ECOM100 in the last slot. I am using the CPU ethernet port to communicate with several pneumatic valve banks using the Modbus protocol on an isolated network. The H2-ECOM100 has been used for programming access up to this point.

My company would like to read data from the machine into the company data collection software. We will be using ModbusTCP protocol and have made it work with several other machines using H2-ECOM100's and D2-260 CPUs. This is the first with a H2-DM1E.

I've copied all the data that needs to be read into MHR memory but I can't get this data to appear on the ECOM100 ethernet port. I am able to test read the data using Modscan on the CPU ethernet port but not on the H2-ECOM100 port. I'd like to use the ECOM100 as it's already on the company network. What am I missing or is it not possible to use the ECOM100 for this?

franji1

  • Bit Weenie
  • Host Moderator
  • Hero Member
  • *****
  • Posts: 3745
    • Host Engineering
Re: Read MHR Memory thru H2-ECOM100
« Reply #1 on: May 08, 2025, 02:48:00 PM »
The ECOM100 is a LEGACY product.  When used with Do-more CPU, external clients can read/write to DLC, DLV, DLX, DLY (legacy DirectLOGIC data types that are supported in a Do-more PLC).  H2-ECOM100 does NOT know about Do-more's MHR memory (or R or D or even X, Y, C, but ECOM100 DOES know DLV, DLC, DLX, DLY but as the old DL octal V, C, X, Y).  The ONBOARD Ethernet port of the H2-DM1E (controlled by the Do-more firmware) DOES know about MHR (and R, D, X, Y, C).

You are actually close to making it work for your "company data collection" network.  Basically, in your 260 CPUs, you are copying your "modbus" data into 260 octal V memory addresses that map to Modbus Holding Register addresses.  DO THE SAME WITH DO-MORE, except instead of copying it to MHR, put it to the proper octal DLV memory in Do-more.

Since you know about the "spreadsheet from heck" that maps the Modbus addressing to the octal V memory of a 260 - USE THE SAME SPREADSHEET MAP for DLV (e.g. a Modbus Holding Register that maps to V2377 in a 260 would map to DLV2377 in Do-more).

If your "company network" has access to the PLC via the control network on the ONBOARD Ethernet port (not a good idea), you COULD use MHR, but using the Onboard IP Address, not the ECOM100's IP Address.  But you probably ISOLATE your CONTROL network for your pneumatic controls, and use the ECOM100 for the "company network".  Hence, you need to stick with my first answer and use DLV and the "spreadsheet from heck".

rockhead

  • Newbie
  • *
  • Posts: 5
Re: Read MHR Memory thru H2-ECOM100
« Reply #2 on: May 08, 2025, 05:29:57 PM »
Thanks franji, I appreciate the detailed response. It never dawned on me to use the DLV memory. Makes total sense. I'll use that method and the "spreadsheet from heck".  ;D  I know I'll get it working that way.