DRO issue

[Randyl84]

Version

2.1.15

Hardware / Firmware

FluidNC

What happened

The dro readout randomly stops reporting updates onscreen. I have tried other g code senders and they work fine and report coordinates as expected. I have found that jogging still works but the dro will not update and if I say probe a point and then try to go use a g1 to move to zero it thinks i'm already thereo

How to reproduce

No response

Operating System

No response

Anything else

No response

[breiler]

I am not able to reproduce this. What version of FluidNC are you using?
Is there any scenario that you are doing that could give a hint on when this happens?
What is your operating system?
How are you connecting to the controller, via USB serial or TCP/IP?

[Randyl84]

Hi Joacim, Thanks for getting in touch. I'm running the latest version, 3.9.9 I think it is. Running on the latest pibot 4.9 board. No particular scenario triggers it and appears to be random. It stopped a few days ago and I changed over to tcp and it started working again, went back to my usual usb serial connection and it's been ok for about a week. I did notice the dro went from green to blue when it stopped working.. I just installed gsender and it's working fine with that. Went back to ugs and it's still not working. I also noticed that the feed override oscillates up and down in speed. Which also doesn't happen on other g code senders. I'm running windows 11 pro. I can record a short video of the situation when I get home tomorrow. I will also try another laptop to see if the issue persists. I have tried other versions of ugs to see if that made any difference but no change. The oled on the controller is showing the position changes when jogging but that isn't being updated in ugs. I really like ugs and have had a great run with it until I upgraded my controller to the ESP 32 based one with fluidnc. Another question too, I love the probing routines you guys have done. Will you be adding a boss type probing routine in the near future? Kind regards, Randyl

…

________________________________ From: Joacim Breiler ***@***.***> Sent: Thursday, November 6, 2025 6:51:24 PM To: winder/Universal-G-Code-Sender ***@***.***> Cc: Randyl84 ***@***.***>; Author ***@***.***> Subject: Re: [winder/Universal-G-Code-Sender] DRO issue (Issue #2924) [https://avatars.githubusercontent.com/u/8962024?s=20&v=4]breiler left a comment (winder/Universal-G-Code-Sender#2924)<#2924 (comment)> I am not able to reproduce this. What version of FluidNC are you using? Is there any scenario that you are doing that could give a hint on when this happens? What is your operating system? How are you connecting to the controller, via USB serial or TCP/IP? — Reply to this email directly, view it on GitHub<#2924 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHVK4ZIRTQOOHAALHM5SUIT33LOVZAVCNFSM6AAAAACLI2AHMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOJVGIYDKNBVGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>