News:

  • June 16, 2026, 01:16:55 AM

Login with username, password and session length

Recent Posts

Pages: [1] 2 3 ... 10
1
Do-more CPUs and Do-more Designer Software / Re: DM2 CPU?
« Last post by JT on June 15, 2026, 12:27:14 AM »
Are you able to share any information on any new features/abilities? or even a timeline?

There are several schools of thought on this and we are back and forth on which we are going to do. What things would you like to see?

The things I would like to see in no particular order would be,

  • DNP3-SA support
  • Profinet support
  • More memory for larger UDT types > 64DWords
  • Double length tag/nicknames
  • More than 1 level of nesting in a UDT
  • Structured Text support

We are based in Australia and our work is mostly with Water Authorities and these are the protocols that they use including Ethernet/IP but that is already supported.
We have already started using a few of the OPCUA poms and so far they have been a great addition but DNP3 is our biggest hindrance in using more BRX.

I understand everyone has different use cases and ours might be the minority but that’s my 2 cents.
2
Would have to dig in a bit to see what might be happening. There certainly isn't any intentional move to the rail, but we'll need to study the reset state and see what's gong on.
3
Do-more CPUs and Do-more Designer Software / Re: DM2 CPU?
« Last post by BobO on June 13, 2026, 01:01:02 PM »
Are you able to share any information on any new features/abilities? or even a timeline?

There are several schools of thought on this and we are back and forth on which we are going to do. What things would you like to see?
4
Looks like maybe I need to use AXVEL to achieve this, with the .TargetVelocity dynamically update from the scaled analog value, as log as the instruction is active?

Yes, AXVEL will do what you want.
5
Hi,
Having an issue with the BRX analog output configured for +-10vdc during an initial power on sequence.
The analog output controls a hydraulic proportional valve to move a cylinder into position. We are using the BX-DM1E-10ED23-D plc with local onboard analog
input and outputs. I have a 4-20ma LVDT connected to the analog input and a +-10vdc proportional valve connected to the analog output with 0vdc being no motion. Everything works properly
after unit is in run mode with LED run light solid. If the Run/Term/Prog switch is placed in program mode prior to removing plc power, the cylinder will not move during the initial startup sequence.
After the PLC goes through its startup sequence and the PWR light is illuminated solid, the switch can be placed into run and the hydraulic cylinder will not move. If the mode switch is left in run
or terminal position and power is cycled to plc then when power is re-applied and prior to the PLC going into run mode with the PWR light flashing the proportional valve will receive a -10vdc signal from the onboard analog
output, moving the cylinder in a negative direction until the plc fully boots up into run mode and run light is illuminated. Is there any way to disable the analog output during initial startup? I looked
within the Do-more software and online tech support without success. Could this be hardware/firmware related? Thanks for help or direction!
 
6
Looks like maybe I need to use AXVEL to achieve this, with the .TargetVelocity dynamically update from the scaled analog value, as log as the instruction is active?
7
Do-more CPUs and Do-more Designer Software / Variable velocity jogging with AXJOG?
« Last post by JasonO on June 11, 2026, 12:45:35 PM »
I'm retrofitting a control that includes 2 servo axes, which I will control with step and direction outputs from a BRX. I need to be able to move the axes to preset positions, which is easy enough. I also need to be able to jog them manually with analog joystick, with the target velocity scaled from the analog input. In other words, the axis velocity needs to be dynamically updated based on the analog input signal, while the jog is in process. I don't think I've ever done this particular sort of thing before, so I wanted to see if someone can verify that this can work, and how.

Thanks!
8
General Discussion / Re: New features wanted!! Apply here!
« Last post by AC on June 05, 2026, 06:27:36 PM »
Yes, the password field would be sufficient, and I understand leaving the username as it is trivial.
Thank you for the consideration!
9
General Discussion / Re: New features wanted!! Apply here!
« Last post by franji1 on June 05, 2026, 02:22:04 PM »
MQTT Username/Password Obfuscation
I would like to see the obfuscation of the password field in the MQTT broker password field.

We can do this for all the password fields in the System Configuration dialog boxes.  Not sure if it is helpful to do it for the user name?  That could create a lot of frustration for most customers when it's not working.  People understand hiding the password field contents - that's probably enough?
10
General Discussion / Re: New features wanted!! Apply here!
« Last post by AC on June 05, 2026, 01:26:35 PM »
I mentioned this in another thread, but thought it would be appropriate to put it here. 

MQTT Username/Password Obfuscation
I would like to see the obfuscation of the password field in the MQTT broker password field.  In the scenario where multiple techs have access to a plc configuration, it is not always the case that the techs that set up the PLC should be able to see the password for the MQTT broker that is not a part of the PLC, but is another system all together.  Attached is an image of what I would prefer to see.
Pages: [1] 2 3 ... 10