Top Camera view Updates only after 0.5mm of movemement

[Greg Toman]

I have looked everywhere, but I can't figure this one out. 

I did not update software. I don't think I made any changes to the configuration of the software, but one day my top down camera stopped updating its view when i jogged left or right less with the "buttons" in 0.1mm increments until the total movement reached 0.5mm (5 steps).

It works normally in the other axis.

Anyone have an idea?

Thanks

Greg

[Mohsen Esmaili]

Hello, what are the specifications of your camera? 

--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/openpnp/5f082cf0-cdd5-4298-b2c0-b9d6a32d3268n%40googlegroups.com.

[tonyl...@gmail.com]

Is the machine actually moving with each of the smaller jogs or does it wait until 0.5mm has accumulated before moving? If you've inadvertently set the X axis resolution to 0.5mm then OpenPnP won't send any commands to the controller to make a movement until at least that amount of commanded change has accumulated.  You'll find the Resolution [Millimeters] setting by opening the Machine Setup tab, selecting your controller x-axis, and on its Configuration tab, the setting will be at the bottom of the Controller Settings section.

[Greg Toman]

Yes, the machine is moving 0.1 mm increments as commanded by the job button, but the camera view does not update.

[Greg Toman]

Camera is a standard ELF. It was working just fine, and then one day it started having this problem. I figured I must have changed a setting somewhere, especially with the top camera, but I tested all the settings and it made no difference.

[tonyl...@gmail.com]

I can't think of any camera settings that would make it behave that way. Can you post your machine.xml file?

[Toby Dickenson]

Can you share an openpnp log and kernel log too please.

To view this discussion visit https://groups.google.com/d/msgid/openpnp/d62fbb4c-c231-45a0-89c5-4d8d26e7c471n%40googlegroups.com.

[Greg Toman]

I'm so sorry. I was wrong. The head is only moving every 5th jog to the left or right! It is not a problem with the camera.

[Greg Toman]

I also noticed that it sometimes is every 5th  jog of 0.1mm left or right, and other times every 6th jog. The resolution of the X axis is 0.01 mm as set in the ReferenceControllerAxis resolution setting. I am using a ReferenceLinearTransform axis that I set manually. If it turn this on or off with its "Compensation?" checkbox, it makes no difference.

[Greg Toman]

I also notice this problem only occurs when using the jog buttons. If I use the mouse on the image and drag the crosshairs slightly left or right, the head moves as expected. I believe it is also working correctly when it places parts. It seems to be only the jog function, as far as I can tell so far.

[vespaman]

Hi Greg,

What kind of machine do you have? To me this sounds like the motor is not strong enough to do small steps. 

Did it ever work?

 - Micael

[Mike Menci]

Or settings for motor current are to low!? 

M

Dne 9. dec. 2025 ob 08:05 je oseba vespaman <micael....@gmail.com> zapisala:



To view this discussion visit https://groups.google.com/d/msgid/openpnp/5ea2c863-7523-4992-87dc-1d80cf0b5bf6n%40googlegroups.com.

[tonyl...@gmail.com]

Please post your machine.xml file and a log file (with logging level set at TRACE) that exhibits the problem. That's the only way we can tell if it is an OpenPnP problem or if it is a problem with your physical machine (as others have suggested).

[Greg Toman]

Here is the log file. Thanks for the help. I am always impressed with how responsive everyone is to my questions.

My machine is my own design it uses a Duet 3 Mini 5+ controller board.

Thanks

Greg

[Greg Toman]

The log file is of me commanding jogs to the right in 0.1mm increments, about 15-20 times.

[tonyl...@gmail.com]

The log file clearly shows your problem. Many of your small moves have the feed rate set to NaN (not a number) and your controller is flagging that as an error and is therefore not moving during those commands. See below for two examples of where the jog didn't work followed by one that did work (at least the controller accepted it as valid although it is an extremely large value for the feed rate):

2025-12-09 11:31:17.337 GcodeAsyncDriver$WriterThread TRACE: [GcodeDriver:COM7] >> M204 S1215 G1 X236.13 FNaN ; move to target 2025-12-09 11:31:17.338 GcodeDriver$ReaderThread TRACE: [GcodeDriver:COM7] << Error: at column 30: G1: expected number after 'a' 2025-12-09 11:31:17.339 GcodeDriver$ReaderThread TRACE: [GcodeDriver:COM7] << ok

2025-12-09 11:31:18.080 GcodeAsyncDriver$WriterThread TRACE: [GcodeDriver:COM7] >> M204 S1215 G1 X236.23 FNaN ; move to target 2025-12-09 11:31:18.081 GcodeDriver$ReaderThread TRACE: [GcodeDriver:COM7] << Error: at column 30: G1: expected number after 'a' 2025-12-09 11:31:18.082 GcodeDriver$ReaderThread TRACE: [GcodeDriver:COM7] << ok

2025-12-09 11:31:18.982 GcodeAsyncDriver$WriterThread TRACE: [GcodeDriver:COM7] >> M204 S1215 G1 X236.33 Y118.55 F2551963 ; move to target 2025-12-09 11:31:18.983 GcodeDriver$ReaderThread TRACE: [GcodeDriver:COM7] << ok
You still haven't posted your machine.xml file so I can only guess you have something messed up with your x-axis Feed Rate, Acceleration, or Jerk settings. That feed rate on that last one is equivalent to over 42 meters per second! Pretty hard for any machine to move that fast when only moving 0.1mm.

[Greg Toman]

Interesting. Here is the machine.xml file.

[Greg Toman]

FYI...my machine is physically set up as coreXY. The Duet board handles the conversion of X/Y movement to A/B motors used to drive the coreXY. It works great in spite of this problem. 

[tonyl...@gmail.com]

Yep, on your X-axis, you have your feed rate set to zero (you should set that something reasonable for your machine):

<feedrate-per-second value="0.0" units="Millimeters"/>

<acceleration-per-second-2 value="1500.0" units="Millimeters"/>

<jerk-per-second-3 value="0.0" units="Millimeters"/>

On your Y-axis you have:

<feedrate-per-second value="900.0" units="Millimeters"/>

<acceleration-per-second-2 value="1500.0" units="Millimeters"/>

<jerk-per-second-3 value="0.0" units="Millimeters"/>

And, on your Z-axis you have:

<feedrate-per-second value="1000.0" units="Millimeters"/>

<acceleration-per-second-2 value="1250.0" units="Millimeters"/>

<jerk-per-second-3 value="0.0" units="Millimeters"/>

[Greg Toman]

Excellent work. This would have been very difficult for me to find. I Changed the feedrate to 900 and it instantly fixed the problem. I appreciate the help very much.

I am a little concerned though. I tend to doubt that I accidentally changed this, especially to zero. Maybe, but it seem unlikely. I will keep my eye open for something like this happening in the future. 

I am also impressed with how Openpnp has such great features built in (such as the logging) that allows you to troubleshoot problems like this so efficiently. 

Thanks again!

Greg