Сustomization QTvcp

More
28 Jan 2021 01:14 #196870 by cmorley
Replied by cmorley on topic С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)

Please Log in or Create an account to join the conversation.

More
28 Jan 2021 02:44 #196880 by cmorley
Replied by cmorley on topic Сustomization QTvcp
I pushed the status_label changes for Fcode and blend tolerance to master.

Please Log in or Create an account to join the conversation.

More
28 Jan 2021 02:50 #196881 by rodw
Replied by rodw on topic Сustomization QTvcp
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.

Please Log in or Create an account to join the conversation.

More
28 Jan 2021 02:55 #196882 by cmorley
Replied by cmorley on topic Сustomization QTvcp
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.

Please Log in or Create an account to join the conversation.

More
28 Jan 2021 03:30 #196887 by tommieh
Replied by tommieh on topic Сustomization QTvcp
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.
Attachments:

Please Log in or Create an account to join the conversation.

More
28 Jan 2021 04:52 #196894 by rodw
Replied by rodw on topic Сustomization QTvcp
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.

Please Log in or Create an account to join the conversation.

More
28 Jan 2021 05:00 #196895 by tommieh
Replied by tommieh on topic Сustomization QTvcp
Hmm, interesting idea. I have a look at that.

Please Log in or Create an account to join the conversation.

More
28 Jan 2021 05:42 #196896 by cmorley
Replied by cmorley on topic Сustomization QTvcp
Maybe I'm missing something - what are you trying to do that the new code doesn't cover?

As long as you don't 'stack' multiple MDI commands with different F codes it displays fine.
Is that something you often do?

Please Log in or Create an account to join the conversation.

More
28 Jan 2021 06:01 #196899 by tommieh
Replied by tommieh on topic Сustomization QTvcp
When you say new code, do you mean: "I pushed the status_label changes for Fcode..." ?
If that's the case, I haven't had a chance to look at any update in master.
Let me find out on how to get the update...
Thanks

Please Log in or Create an account to join the conversation.

More
28 Jan 2021 06:03 #196900 by cmorley
Replied by cmorley on topic Сustomization QTvcp
yes thats what i meant.
Yes please try it out and let me know. You don;' really want to deal with remap code etc unless absolutely necessary.

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.359 seconds
Powered by Kunena Forum