If you run a long program with a different feedrate at the end, (I use a modified 3dchips.ngc) then watch the f code say on AXIS, you'll see it changes to the last feed rate way too soon. It's because it's status of the interpreter state, which is not synced with motion.
Gmoccapy does something fancy (I briefly looked at the code), probably to work around this issue somewhat. I'm not sure they will show the correct feedrate while threading either. My work make a new NML message to specifically to send a feed message to motion. then I told motion when it gets the message to update it's (new) Fcode variable and send the new status back to task to send it out to the uis. oh and there is a new HAL pin in motion cause that was easier to do and the plasma guys may want to use it. Because the message is send to motion through the motion command Queue, it is in sync with actual machine motion. Chris ________________________________ From: Reinhard <reinha...@schwarzrot-design.de> Sent: March 28, 2020 2:57 PM To: EMC developers <emc-developers@lists.sourceforge.net> Subject: Re: [Emc-developers] ask for help Hi Chris, On Donnerstag, 26. März 2020, 16:12:32 CET Chris Morley wrote: > In my branch's case I send an fcode message to motion and motion does > nothing but send it back as status. It's a ton of code to do this one > little status. don't know, whether I got you right: Just tested my app together with axis, as I thought, that F-Code was already included in status messages. ... and yes: F-Code is already handled by status feedback channel. If you run the file "gmoccapy_2_tools_with_cutter_radius_compensation.ngc" - then the feed in UI is adjusted to the coded F-Words. Well in my app. Axis UI elements do not reflect the feed changes. And of cause, the F-Words are alone on a single line. But as my app changes feed elements from status messages only, I can state, that status already contains the right feed value. But the feed value is only non-zero if a real motion is executed. That means, feed is zero after Pause or at tool-change. Cheers Reinhard _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
