Recent Posts

1

EDRV / Does GS-EDRV100 support GS4-4040

« Last post by Saturn_Europa1 on May 11, 2025, 09:31:01 AM »

The EDRV100 manual says that it supports GS4:  The GS-EDRV100 is designed to work with legacy GS1, GS2, GS3, and GS4
series drives.

But Automation Direct has this answer:

The GS-EDRV100 uses predefined Modbus addresses for the Command Word and Status Addresses which match those for the legacy GS1, GS2 and GS3 series.

There is some overlap with the modbus addresses of GS4 but they are not the same.  Therefore, we do not recommend attempted use of the GS-EDRV100 with the GS4.

The GS4 series offers the following ethernet communication cards:

GS4-CM-MODTCP
GS4-CM-ENETIP


Who is right?

2

NetEdit / Can you use NetEdit3 with a GS4-4040 and a GS4-CM-MODTCP?

« Last post by Saturn_Europa1 on May 11, 2025, 09:25:37 AM »

Currently I can ping my GS4-4040 drive with a GS4-CM-MODTCP but I cannot see it on NetEdit3

3

Do-more CPUs and Do-more Designer Software / Re: Read MHR Memory thru H2-ECOM100

« Last post by rockhead 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".    I know I'll get it working that way.

4

Do-more CPUs and Do-more Designer Software / Re: Read MHR Memory thru H2-ECOM100

« Last post by franji1 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".

5

Do-more CPUs and Do-more Designer Software / Read MHR Memory thru H2-ECOM100

« Last post by rockhead 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?

6

Do-more CPUs and Do-more Designer Software / Re: BX-08AD-3 pulsating input signals

« Last post by Kristjan on May 06, 2025, 04:43:30 AM »

Thank you Bolt. There is a couple of pulses after I set the PLC to PROGRAM mode, then upon RUN mode transition I have a spike - zero - reading.

The input has now been stable for about 20 hours, I am crossing my fingers that it's OK now but somewhat uncomfortable not knowing why. If it fails again, I'll try moving to a different AI input and as a last resort changing to a submersible level sensor.

7

Do-more CPUs and Do-more Designer Software / Re: nickname

« Last post by BobO on May 05, 2025, 06:01:18 PM »

Thanks Bob. I didn't know that option was available. 
I don't think that will help with the problem that I am having. I have used some debounce logic to no avail. The induced voltage is helped by installing a drain resistor. The harmonics can be tamed by adding a filter at the drive or inductance in series with the input.
I don't understand why this problem is more prevalent with the BRX. The H2 and the old 260 platforms are not affected as much.

I can't speak to the debounce logic, but the filters on BRX built-in inputs are entirely software. If the inputs are glitching, increase the filter time, it'll help. If you are talking about modules, that's a different problem.

8

Do-more CPUs and Do-more Designer Software / Re: BX-08AD-3 pulsating input signals

« Last post by Bolt on May 05, 2025, 01:11:08 PM »

Can you move the channel in question to the other AD-3? What confuses me about your trend, is that the line spikes to past 16mA, drops to 4mA for a while, then jumps to before jumping back up to 16mA. When toggling to PROGRAM mode, it keeps reading/logging the input while not in RUN (at least for onboard AI/DI?) When did you toggle it? You could add DST10 to the graph other axis for a more complete overview or RUN/PROGRAM mode.

It's been years since I messed with it, but I had a DL14 once that I could not get stable reading out of either, it would be fine for a while, and then not. I don't remember the timing/details, and it was not in an ideal application either. I gave up and went to a submerged pressure transducer. Radar is also an option.

9

Do-more CPUs and Do-more Designer Software / BX-08AD-3 pulsating input signals

« Last post by Kristjan on May 05, 2025, 05:11:58 AM »

PLC: BX-DM1E-M-D
I/O: BX-16ND3 / BX-16TR / BX-08UT / 2 x BX-08AD-3 / BX-08DA-3

All BX-08AD-3 inputs are configured for 4-20mA. One of the analog signals on the second BX-08AD-3 is stable and correct at ca. 16mA for a while (8-24 hours) and then the signal falls to 6mA (incorrect reading) and shows short 12mA pulses every 4 seconds. Cycling the PLC to PROGRAM mode and back to RUN mode fixes the issue and we get correct readings for a while but then the signal fails again. See attached trend logs.

The input is reading from a DL24-00 level sensor and we are pretty confident about its configuration and installation. Based on the fact that RUN-PROGRAM-RUN transition fixes the issue, I suspect there is something wrong on the BX-08AD-3.

Is this a known issue with BX-08AD-3? Any hints about what could be going on?

10

Do-more CPUs and Do-more Designer Software / Re: Best way to space MQTT publish instructions

« Last post by BobO on May 03, 2025, 06:55:39 PM »

ohhh..Wait do you think it would have anything to do with the success bit being the same for multiple MQTTPUBs ....maybe I try to remedy that.

The instruction cannot be re-run with new data until it has signaled completion by asserting the success/error bit or stage, so if you are not accounting for that with unique bits, or preferably, sequencing with stage logic, you are gonna lose states. If the data you are reporting is changing faster than the instruction can run, then you will need to cache pending values in a FIFO.