Recent Posts

71

Do-more CPUs and Do-more Designer Software / Re: Incomplete Status Display

« Last post by Controls Guy on April 06, 2026, 07:18:18 PM »

Well, I was definitely online and not in Edit mode (these two I knew about), but might not have had status on in that window.   Bopped over to the other program window, and may have done an All Status while there, which was why it worked there and also once I returned to the original program window.

I still have that weird thing where Ctrl-Down doesn't insert a row and vertical line.   Used to be somewhat intermittent, but now seems more consistent.   Different PC and different keyboard than when I originally posted about it.

72

Do-more CPUs and Do-more Designer Software / Re: Incomplete Status Display

« Last post by franji1 on April 06, 2026, 09:10:50 AM »

Also, I'm used to double clicking on an instruction or address and getting the Change Value dialog when online.   Now I'm getting the Element Browser instead even though the checkbox is cleared in Global options. (Also, why is that option in Global?  Is there some place other than ladder where this would normally work?)

UPDATE:  Checked this (alternating between behavior and checkbox status) probably 10 times.   Went into a different logic block (a program), worked exactly as expected.  Back to the original, and now it's working.   

Double-click behavior on a contact (instruction) is different based on different "modes" or "states" of your Designer session (explains some reasons why we have an Edit Mode vs. Display Mode):

• Edit Mode (online or offline - doesn't matter), double click brings up the editor.  2.11 lets you specify that you want to start editing on the specific parameter you double-clicked on (see Ladder Options)
• Display Mode, Offline - brings up Element Browser (to assign a NN or enhance any other field for that element)
• Display Mode, Online, Status Off - same as Display Mode/Offline, brings up Element Browser
• Display Mode, Online, Status ON - brings up the Change Value dialog.  Note that this is the default mode when connecting to a PLC Comm Link in RUN mode, typical scenario for a maintenance person 3 years after deployment.

73

General Discussion / Re: Level Winding

« Last post by Garyhlucas on April 03, 2026, 06:48:55 PM »

No this is just a straight screw and the reels are different sizes. So we are doing a scan with a distance laser to locate the flanges then reading two encoders to get the size of of one or more wires and calculating the appropriate pitch and range of motion, with NO input from the operator!

74

Do-more CPUs and Do-more Designer Software / Re: Incomplete Status Display

« Last post by Controls Guy on April 02, 2026, 05:00:24 PM »

Sorry, didn't have time to check back on that, I assume you're correct.   Still having the weird thing where Ctrl-Down doesn't work as I think I remember it should

Also, I'm used to double clicking on an instruction or address and getting the Change Value dialog when online.   Now I'm getting the Element Browser instead even though the checkbox is cleared in Global options. (Also, why is that option in Global?  Is there some place other than ladder where this would normally work?)

UPDATE:  Checked this (alternating between behavior and checkbox status) probably 10 times.   Went into a different logic block (a program), worked exactly as expected.  Back to the original, and now it's working.   

75

General Discussion / Re: Level Winding

« Last post by Controls Guy on April 02, 2026, 03:54:02 PM »

Use electronic gearing instead of dual PID loops slave the level winder to the spindle encoder with a position ratio (pitch/rev) and reverse direction at limits. Cleaner, more precise, and easier to tune.

Does the shaft for the winding guide not look like the guts out of a Stanley push-push screwdriver and auto-reverse at the ends?

76

General Discussion / Re: Level Winding

« Last post by jackmarvia689 on April 02, 2026, 04:52:40 AM »

Use electronic gearing instead of dual PID loops slave the level winder to the spindle encoder with a position ratio (pitch/rev) and reverse direction at limits. Cleaner, more precise, and easier to tune.

77

Do-more CPUs and Do-more Designer Software / Re: OPCUA Client Option

« Last post by JT on March 30, 2026, 04:47:22 PM »

Cool, as OPC-UA is becoming more and more available, having the ability to pull data from other OPC-UA devices directly into the brx would be great, and would add another use case even as a protocol translator/gateway.

78

Do-more CPUs and Do-more Designer Software / Re: OPCUA Client Option

« Last post by BobO on March 27, 2026, 09:46:39 PM »

Are there any plans to implement OPC-UA client functionalities that will allow a BRX PLC to poll other OPC-UA servers?
If yes, would this require more hardware or is it possible with the existing OPC-UA pom alone?

Cheers!

The POM lacks the necessary resources. We are building a full module which will be significantly more capable that the POM. Not sure what it would take to add client capability but we can look into it.

79

Do-more CPUs and Do-more Designer Software / OPCUA Client Option

« Last post by JT on March 27, 2026, 06:37:44 AM »

Are there any plans to implement OPC-UA client functionalities that will allow a BRX PLC to poll other OPC-UA servers?
If yes, would this require more hardware or is it possible with the existing OPC-UA pom alone?

Cheers!

80

Do-more CPUs and Do-more Designer Software / Re: Ring buffer for fault logging

« Last post by BobO on March 26, 2026, 01:51:07 PM »

A ring buffer is just a simple fast implementation of a FIFO that allows addition of records without copying/shifting the data. A FIFO isn't always implemented as a ring buffer, but a ring is generally considered to be a FIFO.

If you are intending the FIFO to store the last N records, losing the oldest as you add a new record, just call FIFOUNLOAD before FIFOLOAD when MyFifo.Full is true. A ring buffer implementation would need to bump the tail to accomplish the same thing.

If you would prefer to implement this as ring buffer, it's really quite simple. Make your buffer size a power of 2. Use one V location as the head pointer and another as the tail pointer. Create a bit mask of the buffer size - 1. If the buffer is 256 elements, the mask is 0x00FF. For 1024, it would be 0x03FF.

Empty = Head == Tail
Full = (Head+1)&Mask == Tail

Add a record (if !Full):
Buffer[Head] = NewVal
Head = (Head+1)&Mask

Remove a record (if !Empty):
OldVal = Buffer[Tail]
Tail = (Tail+1)&Mask

But honestly, just use the FIFO.