Recent Posts

51

Do-more CPUs and Do-more Designer Software / Re: Bug Repot: Cannot copy paste tasks or import from text file possible, need help

« Last post by Bobby Tables on May 05, 2026, 06:24:19 PM »

Oddly enough, the copy paste from the clipboard into notepad adding one line
like

original clipboard contents:

Code: [Select]

// Ver(103) PCU(3) Do-more Designer Clip   Source Project: Format: Do-more Designer 2.00+  DO-MORE Ladder
PLC BX-DM1E-18ED23-D

// Do not modify SYS_CONFIG block!

#BEGIN SYS_CONFIG2<sys config block here>#END



STR C5
OUT C6



new line, simply adding "AND C7":

Code: [Select]

// Ver(103) PCU(3) Do-more Designer Clip   Source Project: Format: Do-more Designer 2.00+  DO-MORE Ladder
PLC BX-DM1E-18ED23-D

// Do not modify SYS_CONFIG block!

#BEGIN SYS_CONFIG2<exact same unaltered sys config block>#END



STR C5AND C7
OUT C6




Then selecting the whole text in notepad with control+A and copying it with control+C does not allow pasting into do more designer, with edit mode on in ladder view with control+V. Yet selecting the whole line or a contact and using copy-paste with control+C and control+V works. But saving the file then using Tools>Insert Instructions from File does work as you mentioned. Why does insert instructions from file differ from the clipboard?

Originally I was intending to duplicate eventlogger2, applying a bunch of changes while keeping the original in case those changes don't work out, then inserting instructions from file.
It seems that to do that I have to add the name of the new control block, eventlogger2_copy, to the MEM_CONFIG section by itself and find and replace each instance of eventlogger2 with eventlogger2_copy. Then the $TSK P1 Task: Invalid element type and $TSKEND P1 Task: Invalid element type errors don't show up and it imports.

Code: [Select]

#BEGIN MEM_CONFIG
 eventlogger2_copy TASK  0 -1
#END
// Beginning of Code Block eventlogger2_copy
$TSK eventlogger2_copy

// Rung eventlogger2_copy#1
// Offset 0
STR ST1
OUT C222

$TSKEND eventlogger2_copy

52

Do-more CPUs and Do-more Designer Software / Re: MQTTPUB Gets Stuck

« Last post by Bolt on April 29, 2026, 06:50:40 PM »

That is an illegal operation system error. In the case of MQTT it means that the driver is in a state it shouldn't be, namely, it should be idle but isn't. My comment to this result says "This really shouldn't happen unless software is broken." Indeed.

This happened again this week, (MQTTPUB's Extended Error Information's lower word is returning 27) on a completely different (newer) system. It's running V2.11.1, and it stopped sending data a few days ago. I can't reboot the device just yet, and I suspect that will fix it, but can't find anything else that will jog the instruction back to working.

53

Do-more CPUs and Do-more Designer Software / Re: BX-P-Ecomex Communications Issues

« Last post by BTimpson on April 29, 2026, 01:06:43 PM »

As it would turn out. the cabling was the issue. it was not routed directly from PLC to PLC. there was a network switch between the 2. Once that was corrected all is well.
Thank you for your input.

54

Do-more CPUs and Do-more Designer Software / Re: First Stage is Active All the Time H2-DM1E V2.10.4

« Last post by Scooter on April 29, 2026, 11:13:46 AM »

I am using a SGSET instruction to Enable S1 of a program.  When a pump turns on it actives NO bit that turns SGSET Enable Stage 1 to true.  Even when the pump is off an NO stays open, S1 will be on the entire time.  Any ideas?

Once you turn on the stage using SGSET it will stay on even if your NO switch turns back off. You need to use the SGRST instruction to turn off S1 once the pump turns off.

55

Do-more CPUs and Do-more Designer Software / Re: BX-P-Ecomex Communications Issues

« Last post by BTimpson on April 29, 2026, 11:05:40 AM »

RX Instruction is set to continuous on interval. Also when does work i get all requested elements.

56

Do-more CPUs and Do-more Designer Software / First Stage is Active All the Time H2-DM1E V2.10.4

« Last post by Saturn_Europa1 on April 29, 2026, 10:40:09 AM »

I am using a SGSET instruction to Enable S1 of a program.  When a pump turns on it actives NO bit that turns SGSET Enable Stage 1 to true.  Even when the pump is off an NO stays open, S1 will be on the entire time.  Any ideas? 

57

Do-more CPUs and Do-more Designer Software / Re: BX-P-Ecomex Communications Issues

« Last post by MikeS on April 29, 2026, 08:46:10 AM »

the RX instruction itself has three optional parameters that can help diagnose what's happening: On Success Counter, On Error Counter, and most importantly Extended Error Information which will tell you which row in the RX instruction is the issue and why.

You might also add a PING instruction before the RX instruction just to confirm the remote ECOMEX is available when you want to execute the RX.

Is your RX's Enable parameter set to 'Once on Leading Edge' or 'Continuous ... at interval' ? If the later, the instruction must stay enabled - I mention this because some customers in the past have placed the RX using 'at Interval' in a code block or Stage that does not remain enabled, so the RX's internal timer doesn't run.

58

Do-more CPUs and Do-more Designer Software / BX-P-Ecomex Communications Issues

« Last post by BTimpson on April 28, 2026, 05:28:33 PM »

Hello
I am of need some assistance with issues I am having with 2 BRX PLCs communicating using BX-P-Ecomex Modules.
The first PLC is a Bx-DM1E-18ED-D with the On Board IP Address 192.168.1.70 Subnet Mask 255.255.255.0 and the POM module IP address set to 10.10.10.1 Subnet Mask 255.255.255.0
The second PLC is a Bx-DM1E-18AR3 with the On Board IP Address 192.168.1.200 Subnet Mask 255.255.255.0 and the POM Module IP set to 10.10.10.2 and a Subnet Mask 255.255.255.0
I am using an RX (Do-More Network Read) from the first PLC to acquire the desired Elements from the second PLC.
The RX is set to target the 10.10.10.2 IP address and the interval is set to 10 seconds. I have adjusted the ACK Timout up to 1000 ms with no result change.
The problem i am having is it only acquires the information a few times an hour inconsistently.
All cabling has been confirmed good.
I have not wire sharked it yet.
I have pinged both POM Module IP addresses with the same result of 4 sent an only one success and 3 failed.
Any assistance would be greatly appreciated

59

Do-more CPUs and Do-more Designer Software / Re: Bug Repot: Cannot copy paste tasks or import from text file possible, need help

« Last post by franji1 on April 23, 2026, 03:25:27 PM »

I should mention that Window's clipboard COPY/PASTE format for Designer
code blocks
rungs
individual instructions
includes the TEXT form of the code that can be pasted into a different project.  So rather than use the EXPORT mechanism, use Ctrl+C, then paste it in NOTEPAD, then edit out the pieces/parts you don't need by hand (basically what you did).  Then use the IMPORT mechanism with THAT text file.

(The clipboard content is optimized compared to the general Export dialog).

60

Do-more CPUs and Do-more Designer Software / Re: Bug Repot: Cannot copy paste tasks or import from text file possible, need help

« Last post by franji1 on April 23, 2026, 03:20:18 PM »

Sadly, no.  Those details are left to the import/export mechanism itself.  There are so many things that COULD be documented - it would probably fill up a book.

The EXPORT mechanism and its output is the only documentation.

The IMPORT error messages could be more specific on how to address those errors (like mentioning options to choose during export, or specific sections to look at in the import file).

When exporting, it does not know what the specific items you are needing later on when you import, hence it includes a "superset".  Element Documentation - you get all of it.  Memory Configuration - you get all of it (with the option of including the built-ins).

The error message on the IMPORT could have known that there was no Mem Config section in the import, and reported that as part of the second attempt where there was the "$TSK P1 Task: Invalid element type" error message.

So something like
$TSK P1 Task: Invalid element type; import does not contain a MEM_CONFIG section that needs to define that invalid element
???

I think that may have helped point you to the Export "Memory Config" option???

You went the other route and did not need it as a code-block, but only as a rung "snippet", and just eliminated the $TSK start/end delimiter instructions, then imported as rungs (ha!).

Posting here is probably the best thing you can do to get some good answers (or on AD's Community forum).