News:

  • May 31, 2026, 02:41:36 PM

Login with username, password and session length

Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31
Do-more CPUs and Do-more Designer Software / Bug in PID View?
« Last post by Kristjan on May 18, 2026, 12:18:40 PM »
I noticed the following today in DMD 2.11.1:

When opening PID View for a certain PID Loop, the viewer actually displays another loop and its parameters (see attachment). I am unable to view two of my loops. Is this a known bug?

32
Do-more CPUs and Do-more Designer Software / Re: MQTTPUB Gets Stuck
« Last post by BobO on May 12, 2026, 11:56:09 AM »
In most cases that is a SYSERR_XXX value and 22 is SYSERR_CONNECTION_FAILED.
33
Do-more CPUs and Do-more Designer Software / Re: MQTTPUB Gets Stuck
« Last post by franji1 on May 12, 2026, 09:23:45 AM »
So what does code 22 mean?

I do not know.  The Help topic does not list it out.  Let me try to find out...
34
Do-more CPUs and Do-more Designer Software / Re: MQTTPUB Gets Stuck
« Last post by Bolt on May 12, 2026, 09:09:12 AM »
I've never been able to get DmLogger to work via a VPN connection.

I believe it.  You may need to ask your IT or VPN people how to enable broadcasts on a specific UDP port (29298 or 0x7272).

That would be me...

So what does code 22 mean?
35
Do-more CPUs and Do-more Designer Software / Re: MQTTPUB Gets Stuck
« Last post by franji1 on May 12, 2026, 09:02:58 AM »
I've never been able to get DmLogger to work via a VPN connection.

I believe it.  You may need to ask your IT or VPN people how to enable broadcasts on a specific UDP port (29298 or 0x7272).  Or get someone to set up a PC at the remote location and run DmLogger (you could enable it remotely, but then have them monitor it locally and send you the log text via email).
36
Do-more CPUs and Do-more Designer Software / Re: MQTTPUB Gets Stuck
« Last post by Bolt on May 12, 2026, 08:58:38 AM »
I've never been able to get DmLogger to work via a VPN connection.
37
Do-more CPUs and Do-more Designer Software / Re: MQTTPUB Gets Stuck
« Last post by franji1 on May 12, 2026, 08:52:08 AM »
Have you enabled Message Dump debug?  That tells the MQTTPUB to broadcast log entries so that DmLogger windows application can monitor it.  Remember to turn it off once you are done using it.

Debug->Do-more Logger brings up a dialog box that lets you enable this in the PLC.  You probably want to raise the logging filter to Level 2 to provide the most detail.  See if that helps you figure out what is going on.

When done, remember to return to this dialog and return to Level 1 and disable message dump in the PLC.
38
Do-more CPUs and Do-more Designer Software / Re: MQTTPUB Gets Stuck
« Last post by Bolt on May 11, 2026, 10:45:43 PM »
I've been commissioning a different system using the same MQTTPUB logic, and this one has a much longer scan time (~14ms) and have had to bump up the timeout with a DEVWRITE to get it be able to publish data on time. It takes over 50 seconds. That's not a huge problem per-say, but it keeps returning a lower word in the error code of 22, but the data is going through. What does 22 mean? How can I further diagnose these issues?
39
ECOMs and ECOM100s / Re: ECOM100 blocking the bus
« Last post by BobO on May 10, 2026, 03:34:16 PM »
The FPGA doesn't directly connect to the bus. All bus connections are through buffers. It is certainly possible a buffer is damaged, but 405s are notorious for bent pins.

We're happy to look at the unit.
40
ECOMs and ECOM100s / Re: ECOM100 blocking the bus
« Last post by rlp122 on May 09, 2026, 06:50:01 PM »
<pushes chips into center of table>

I'm all in on it being a bent or retracted pin.  This is the most common issue with this PLC.  I wouldn't place much faith in ChaptGPT, it hallucinates a lot of stuff.

Retracted pins are very hard to spot.  I couldn't even begin to count the number that I have seen in my career.  It doesn't take much, even 0.5 mm is enough to cause it to not connect fully.  Get out a magnifying glass and look very closley.
Pages: 1 2 3 [4] 5 6 ... 10