I am trying to use the override +/- buttons in Edge 1.2.5. (I have mapped them to shortcuts, but that is not relevant to the problem.)
In gSender 1.1.7, when I click on the override buttons, the percentage number changes immediately, the actual feed rate indicator changes immediately and the Mill speeds up or slows down immediately. When I click more than once, all these things respond immediately.
In Edge 1.2 5, when I click on the + or -, there is a delay before anything happens. When I click more than once, things get weird. (Sorry for the technical talk.) For example, I just started a file which is nothing more than a large circle. No Z moves and a consistent XY move. The run starts at 100%. When I click 4 times on the - button, after a pause, the read out changes to 70%. If I click 4 more times on -, it does not reduce the speed, it increases to 108%.
While writing this, I went back to try again. Each time I ran the same file, the numbers were different. They were always weird, just different.
In Main 1.2.0 when using the GUI buttons to raise and lower the feed rate, the feed rate value changes and the percentage of the base rate indicator changes. All is well.
When using keyboard shortcuts to raise and lower the feed rates, the feed rate value changes, BUT the percentage of the base rate indicator does not.
@gwilki how is this looking now in 1.5.2? We recently made some much nicer changes to overrides that should now finally make them feel very responsive and aligned
Grant, just checking in here as well. We recently released v1.5.3, but it should contain the overrides improvements from v1.5.2, as Chris pointed out. Once you get the chance, let me know if this issue has been solved for you on the latest version.
@walid_kayhan Thanks much for following up, W. I have not had the time to install 1.5.2 on my test Uno. I should be able to get to installing 1.5.3 on it later today or tomorrow and will report back asap.
I was curious to see if the time remaining function wrt rotary was improved. I loaded a rotary file and started it running. Since it showed that it would take a few days to cut, I stopped the job. I wanted to explore the new display of eeprom settings. I opened up config and scrolled around. When it was time to go back to the carve window, gSender was again frozen.
Hmmm, I just finished upgrading to 1.5.3. One of the reasons for finally upgrading was because 1.4.12 would freeze up intermittently and there was some hope that this was fixed in 1.5.x. What would happen is that the gSender screen is still there but mouse ‘click’ input was no longer accepted. The cursor travelled like it should showing the mouse movement. When you got to a clickable input field, the cursor did not indicate it was clickable and clicking did not result in any action. If you moved the cursor to an area outside of the gSender screen then mouse click input registered again.
The only fix was to close gSender ad start it back up.
BTW, gSender itself seemed to not be affected (only input was affected) because I never had a situation where the running program was interrupted as the result of a screen/mouse input failure.
@Jens That’s not what I saw, Jens. The freezing that I was getting was always after leaving the carve menu and going into one of the others. I have no issues with 1.4.12 at all.