Recent Posts

1

Do-more CPUs and Do-more Designer Software / Sort Code-Blocks By > Sort by Execution Order V2.10.4 and 2.11.1

« Last post by Mike Nash on November 15, 2025, 08:35:48 PM »

I've noticed recently that the Programs in the Project Browser keep reverting to Sort By Type, Then Name.

I know this happens when opening the program, but I'm not sure it isn't happening during some edits.
The View > Options > Project Browser is showing Sort By Execution Order, but it doesn't appear to make it happen
unless I first apply to all open views. or change it via right click. Next time opening it reverts and I can see this
in the right click menu or sort icon.

I know it works properly in v2.9 and before.

2

Do-more CPUs and Do-more Designer Software / Re: BX-DMIO Error Slot 255

« Last post by BobO on November 12, 2025, 03:32:56 PM »

I've been communicating with JeffS off the forum, but to complete the public record, we found a bug in the Ethernet Master where in certain conditions (rare, I think), the master sent a malformed request that resulted in this symptom. The fix will be in the next OS to be released shortly.

3

Do-more CPUs and Do-more Designer Software / Re: BX-DMIO Error Slot 255

« Last post by JeffS on November 10, 2025, 06:29:32 PM »

So I sent them a new PLC and they got the same error.  I had them factory reset the PLC (Dips and RUN/TERM/STOP dance) and I remotely reloaded the program and got the same error.   I am only getting this error at this one site luckily, but so far not able to rectify it.  This setup ran fine last year and nothing has changed on the system (no changed code/sensors/wiring).  They were running 2.9.6 firmware so I did update to 2.10.3 but the error persists.

So at this point we replaced the BX-DMIO and the BX-DM1E-M-D, initially restored the new PLC from a backup of the old PLC, then since the problem persisted, factory reset that PLC using run/stop dance, reloaded from a clean copy, and the problem persists.

Any thoughts on what to check next?

4

Do-more CPUs and Do-more Designer Software / Re: DoMore Designer 2.11.1 Crashing

« Last post by franji1 on November 10, 2025, 02:48:40 PM »

There were issues dealing with "modality" and "z-order" of status windows/message boxes when connecting to a PLC or writing a project to the PLC.

Are your PLC network connections typically all good?  We do see strangeness when dealing with "not-so-good" connections via VPNs (lots of layers and hops that aren't the best).

5

Do-more CPUs and Do-more Designer Software / Re: DoMore Designer 2.11.1 Crashing

« Last post by AC on November 10, 2025, 02:10:19 PM »

Although I am not adding or removing devices, that is not to say that you are not on the right track. Once I start designer, then connect to the PLC, (or sometimes I just try to connect) and the program can hang on connect, during download, or even after disconnect. Its rarely inbetween.

6

Do-more CPUs and Do-more Designer Software / Re: BX-DMIO Error Slot 255

« Last post by BobO on November 08, 2025, 12:51:01 AM »

So the customer replaced the BX-DMIO and it is still showing an error light on the DMIO and when I log into the BRX PLC I see the same Slot 255 error. 

So at this point I guess the BRX Master is the bad component here, just very misleading as the error points toward the DMIO device?

Slot 255 actually points to the onboard I/O, which there isn't any. It isn't a hardware problem, it's probably garbage in the config. I've been out on vacation, but I'll look into it when I'm back in the office.

7

Do-more CPUs and Do-more Designer Software / Re: BX-DMIO Error Slot 255

« Last post by JeffS on November 07, 2025, 12:43:51 PM »

So the customer replaced the BX-DMIO and it is still showing an error light on the DMIO and when I log into the BRX PLC I see the same Slot 255 error. 

So at this point I guess the BRX Master is the bad component here, just very misleading as the error points toward the DMIO device?

8

Do-more CPUs and Do-more Designer Software / BX-DMIO Error Slot 255

« Last post by JeffS on November 06, 2025, 04:38:47 PM »

I have a remote IO module reporting a configuration mismatch on Slot 255.  I tried re-writing booter/firmware, reset defaults, rewrote booter/firmware to the BRX Master with no luck.  I am assuming this remote IO module is dead, but wanted to report the odd message.

9

Do-more CPUs and Do-more Designer Software / Re: MODBUS TCP with H2-D1ME CPU

« Last post by franji1 on November 05, 2025, 05:24:26 PM »

Instead of using R as your setpoint, use casts of Modbus 16 bit Holding Register block (MHR).  Two gotchas in Do-more is that REAL casts of a memory location must be aligned on DWORD boundaries (so even MHR addresses), and the 2nd gotcha is there is no Modbus address 0 (everything starts at offset 1 with Modbus, e.g. Modbus Holding Register 40001 maps to MHR1, so you can't use MHR0, but you can use MHR2 or MHR10 for the cast).

To help out, let's use Nicknames.  Instead of assigning the Nickname MySetpoint to R0, assign it to MHR10:RD (the : is a "cast operator"), which means look at Holding Register 40010 and 40011 (MHR10 and MHR11) as a DWORD REAL.

To learn about casts, there's a video that helps with that:
https://www.youtube.com/watch?v=BvTuz6H3sD4

The easiest way to assign a nickname to a cast is from within the Doc Editor (Ctrl+D), hit the Add button and enter MHR10:RD in the Element field (see screen shot).

Then just use and enter MySetpoint in your logic, data view, trend view, everywhere (or enter MHR10:RD).  The Auto-Complete should make entering the Nickname easy.

The behavior for the relay is simpler, just use MC (Modbus Coil) instead of a C bit for everything that is read/write via Modbus.  No casts needed for bit memory (bit is a bit).

The purpose of these reserved memory areas is to protect the memory locations that are NOT accessible via Modbus.  In a 260, ANYTHING can write to I/O since EVERYTHING is mapped to Modbus memory (you just need that spreadsheet).  In Do-more, ONLY put the Modbus accessible data in your MHR, MIR, MC, MI data blocks.  Nothing else is accessible via Modbus (not X, not Y).

There are similar blocks for legacy DirectLOGIC data types: DLX, DLY, DLC, DLV that are octal.  So a 260 could read/write using RX/WX to Do-more to those memory blocks.  There is also DLRX, DLWX instructions for Do-more program performing the legacy DL protocol to those legacy PLCs.  Similar reasoning for the DL blocks as for the Modbus blocks.

10

Do-more CPUs and Do-more Designer Software / MODBUS TCP with H2-D1ME CPU

« Last post by jktucker92 on November 05, 2025, 04:00:44 PM »

I am working with the Do-More PLC's for the first time and have a question about using Modbus TCP with these PLC's.  For the old DL260 CPU, Modbus was straight-forward and a PLC memory address could be read and written to after you used the excel spreadsheet to map a PLC address to a Modbus holding register.  For the H2-D1ME CPU, what I'm reading is the only memory addresses available via Modbus TCP are the MHR, MIR, MC and MI addresses.  I use Ignition to interface with my PLC's, and I want Ignition to be able to read a setpoint from the PLC memory and be able to change that setpoint.  I don't see how I can do this.  For example, the setpoint is a real number, say R0, while I can copy that memory to the MHR address space to read via Modbus, I can't change that value in Ignition.
What am I missing?  Is there another way to handle this.  I also want to be able to read the position of a relay that controls a valve and also operate that valve.  I have some concepts using multiple values to read and write these values, but that gets very complicated.  Is there a way to mirror the R address space to the MHR address space for read-write capability?  Is there another method I should be using to connect Ignition to these PLCs?