I have mach4hobby running (licensed) and a Miller. On the jogging tab the "Jog Rate%" input text-box will not accept any manual input e.g. it if set at 40.0 and I type in 50 and press enter it reverts back to 40.0.

The event is firing as I put a message for screen in it and it shows.

I am using Mach4 Hobby version 4.2.0.4809 with ESS 278.1*  (as recommended by the Warp9td site) see here -> https://warp9td.com/index.php/gettingstarted/setting-up-the-smoothstepper-and-mach4   

I aslo tried this on another machine that was was fiddling with mach4hobby on before purchase, Version 4.2.0.4612 and this works fine, although it is just the simulator as I don't have a machine hooked up to it and that version isn't registered for a license.

I have checked the code and all the settings fo the input box on both machines and they are identical.

Anyone? Developers??

thanks (pics attached)

its problem this forum ,if steve will not back ,this forum value only for very minor simple question ,no real support

Oh - I thought it was their "Support Forum", it even says it in the title "Machsupport.com" and "Machsupport Forum/Mach Discussion/Mach4 General Discussion"

Is theere a way to report bugs officially as a licenced user?

thanks

The default mach screens have some code in the 'On Modify Script'. Replace it with the following:

local inst = mc.mcGetInstance()
local val = select(1,...)
mc.mcProfileWriteString(inst, "PersistentDROs", "droJogRate", string.format(val))
return val


Hi,
the default behavior of Mach4 as it ships is for the DRO to display the  current applied jog speed, the number internal to Mach4.
Just because you edit the DRO DOES NOT Change the applied jog speed. If you want the DRO to display a different value then address the issue of changing
the applied jog speed, and the DRO will display it.

There are a number of DROs where if you manually edit the value  that value will be 'pushed' onto that property within Mach, this is not one of them.

Craig

If the Jog DRO is edited it should update the jog speed. It's just that the default code in the 'On Modify Script' is preventing this from happening. I believe there were some changes internally to do with how the On Modify/On Update scripts work and capturing the changed value but the code in the On Modify Script was not updated inline with these changes.

The code in the script can be modified as to what I posted above, or removed completely (not even commented out, you have to delete it). If you remove it you'll just lose the persistent functionality after restarting Mach.

EDIT: looks like even if you remove it, the persistent functionality remains... so it can just be removed completely.

SwiftyJ - absolutely spot on - thank you very much. It was one of those little anooying thing.

Thanks again