Recent Posts

1

Do-more CPUs and Do-more Designer Software / Re: BRX PacketIn Unable to Read

« Last post by BobO on August 27, 2026, 08:09:31 AM »

The IP is configured for both ports and UDP is correctly configured for the BRX device (deleted and remade several times to make sure). Both ports on are on a network switch but I unplugged the POM and read the UDP packets from the cable (put my computer in place of POM). All devices also have correct sub-masks configured for the networks they are on.

Please screenshot the IP and device configs.

2

Do-more CPUs and Do-more Designer Software / Re: BRX PacketIn Unable to Read

« Last post by cc101 on August 26, 2026, 05:46:45 PM »

The IP is configured for both ports and UDP is correctly configured for the BRX device (deleted and remade several times to make sure). Both ports on are on a network switch but I unplugged the POM and read the UDP packets from the cable (put my computer in place of POM). All devices also have correct sub-masks configured for the networks they are on.

3

Do-more CPUs and Do-more Designer Software / Re: BRX PacketIn Unable to Read

« Last post by MikeS on August 26, 2026, 04:17:34 PM »

My setup had the BRX Eth. port directly connected to the POM Eth. port with a Cat6 cable. Do you have a switch or some other network device between them that could be blocking the broadcast traffic ?

4

Do-more CPUs and Do-more Designer Software / Re: BRX PacketIn Unable to Read

« Last post by BobO on August 26, 2026, 03:45:54 PM »

UDP device config? IP config for both ports?

5

Do-more CPUs and Do-more Designer Software / Re: BRX PacketIn Unable to Read

« Last post by cc101 on August 26, 2026, 10:17:55 AM »

It's good to know that this definitely should be working. The confusing part of mine is that I can see the traffic on the network and confirmed that the ethernet connected to the POM has access but the UDP device cannot see any packets from that port.

6

Do-more CPUs and Do-more Designer Software / Re: BRX PacketIn Unable to Read

« Last post by MikeS on August 26, 2026, 09:18:13 AM »

What you're trying to do should work. I have a BRX CPU's internal port with a PACKEOUT sending to a second BRX CPU with an ECOMEX using a PACKETIN to send SL10.

7

Do-more CPUs and Do-more Designer Software / BRX PacketIn Unable to Read

« Last post by cc101 on August 25, 2026, 06:05:55 PM »

I am attempting to have a BRX read in UDP Packets from a POM Ethernet Port using PacketIN. I have swapped the PLC and factory reset it along with trying different POM's (both EX and LT). The Internal ethernet and the POM ethernet are on separate subnets and the UDP packets (port 50222) can only be seen on the subnet attached to the POM. The device sending the packets is broadcasting them the local subnet which is the one attached to the POM. I am completely stumped since the POM should have the capability to bridge subnets. Any suggestions for fixes would be appreciated!

8

Do-more CPUs and Do-more Designer Software / Re: Variable velocity jogging with AXJOG?

« Last post by JasonO on August 18, 2026, 10:47:33 AM »

In case it's ever of use to anyone else, the way I ended up achieving variable velocity jogging with servo motors from an analog joystick input, was by using an AXSCRIPT, with a WHILE loop, with a Ramp to Velocity step inside the WHILE. The Ramp to Velocity is set to immediately continue on to the next step.
So as long as the axis permissive (referenced by the WHILE step) is ON, it keeps looping and updating the axis velocity based on the analog input. Meanwhile, I have it calculating on every scan how many pulses will be needed to ramp to a stop from the axis current velocity, using a trapezoid ramp.
When the joystick is released OR the axis reaches the soft limit minus the number of pulses needed to stop, the AXSCRIPT leaves the WHILE loop and switches to an Absolute Position Move step to bring the axis to a stop. That way, if the stop is caused by reaching a soft limit, it can ramp to a stop exactly at the soft limit position, from whatever its initial velocity had been.

9

Do-more CPUs and Do-more Designer Software / Re: H2-DM1E Communication Issue

« Last post by MikeS on August 18, 2026, 09:00:12 AM »

There's no inherent problem with having both the onboard Ethernet port and the H2-ECOM100 both connected to the same switch as long as their IP addresses are different (which they are).

10

Do-more CPUs and Do-more Designer Software / Re: H2-DM1E Communication Issue

« Last post by Saturn_Europa1 on August 18, 2026, 01:18:05 AM »

I sent them an email, thanks. 

An interesting detail that I didnt mention.  The H2-DM1E is plugged into a D2-09BDC1-1.  On the last slot there is an H2-ECOM100.  Both the H2-DM1E and the H2-ECOM100 are plugged into the unmanaged switches.  The IP addresses in my records show that the CPU is 10.0.1.152 and the ECOM is 10.0.1.119. 

Its my understanding that a H2-DM1E doesnt need a H2-ECOM100. Could this be causing an issue?