Сustomization QTvcp

If you are using 2.8, you are kinda out of luck.
You can get the feedrate from settings but it will be often wrong because of readahead.

In Master this has been improved.
I will add a feed rate option to status label (thanks for the reminder)

I pushed the status_label changes for Fcode and blend tolerance to master.

if you are using motion.feed-upm that implies you are using master branch as this pin from state-tags is not in 2.8.
motion.feed-upm is a real time variable that holds the feed rate as its set by an F code in the gcode file. But it then displays that value in real time when the motion segments are actually being executed in real time, not when the gcode is parsed and sent to the buffer pending execution by motion.

But if in the MDI and there is no motion I don't think feed_upm has a value.

The GUI is in user space so it is not real time so there will be a delay in displaying the pin value.

But if you want to see the actual velocity at a given point in time, motion.current-vel will display this. (in units per second)

To capture the feedrate from an F command, you probably need to use a remap command. Simplest way would be to set one of the analog pins in the remap and display that in your GUI.

Fcode is available in MDI now. but it still has the old problem it seems.
If you set F100 do a long feed move and while waiting issue f200, the Fcode displayed will be f200 before it should.

But running a program doesn't do this.

Thanks for your help and explanation.

I can confirm that motion.feed-upm has no value in MDI

I'll try the remap and also the new changes from Chris.
Using 2.9.0-pre0-3387 currently.

Attached the display I'm working on. I find QtVCP really great.

I wonder if you could make motion.feed-upm "sticky" with some GUI trickery? What I mean is use it to toggle another variable and leave it displayed until feed-upm changes to a non zero value.