News:

  • June 28, 2026, 11:14:23 AM

Login with username, password and session length

Author Topic: Do-More and KepServerEx  (Read 7307 times)

davidbgtx

  • Hero Member
  • *****
  • Posts: 215
  • Host be the Most
Do-More and KepServerEx
« on: November 07, 2014, 11:02:39 AM »
I am trying to get KepServerEX to read Real values from the the h2-DM1E. I am using kepware Modbus TCP/IP Ethernet driver. I am using MOVE instruction
for example R0 to MHR4:RD (the D pops in on it's own). Kepware set to 400004 Float. This works, but is it the best method? The drivers available for me in Kepware are AutomationDirect DirectNet, AutomationDirect EBC, AutomationDirect ECOM, AutomationDirect KSequence. I am using multiple racks EBC 100's. I will also need to write data from kepeware down to Do-More (mostly bit level), if that affects the best driver to use.

franji1

  • Bit Weenie
  • Host Moderator
  • Hero Member
  • *****
  • Posts: 3827
    • Host Engineering
Re: Do-More and KepServerEx
« Reply #1 on: November 07, 2014, 11:34:38 AM »
Does Kepware have a native Do-more driver (that's a Kepware question)?  If so, THAT is best.  If not, your Modbus implementation is correct.

If you end up sticking with the Modbus/TCP driver, you might look at the PUBLISH and SUBSCRIB instructions for doing block transfers into/out of Do-more Modbus data-blocks from/to native "Do-more" data-blocks (like R).  Also, look at utilizing "byte casts" on bits on byte boundaries to move blocks of 8 bits at a time, e.g. X24:UB to/from MI40:UB would move X24-X31 as an UNSIGNED BYTE into MI40-MI47 as an UNSIGNED BYTE.  Moving a bunch of bits individually is "slow" relative to moving blocks of BYTEs on BYTE boundaries.

mhw

  • Hero Member
  • *****
  • Posts: 250
Re: Do-More and KepServerEx
« Reply #2 on: November 10, 2014, 11:01:28 AM »
Your other option is to use the AD ECOM driver and then use DLX, DLY, and DLV addresses.