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.
I hope that this is not what you are seeing ā¦ā¦
@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.
@walid_kayhan I just installed 1.5.7 and ran it on my test Uno. I followed the first 11 steps in my previous post. I was able to return to the carve menu both after the first 5 steps and the first 10 steps. However, in each test, it took between 15 and 20 seconds to return to the carve menu.
I must admit that when I first reported this, I did not wait that long before closing gSender. So, for all I know, had I waited between 15 and 20 seconds in 1.5.3, it would eventually have returned to the carve menu.
@gwilki have you tried a shot at this recently on Edge? Today I tried to re-create both reports on the latest Edge:
The delay to the on-screen override when using the shortcuts is still a bit slow, by my count about 2 seconds, but this is likely just a polling rate that we set and could look into changing
I tried testing the screen freezing issue on both 1.5.6 and newer Edge versions following your steps and wasnāt able to recreate it, but it might be perhaps because my computer has more processing power than yours
@chrismakesstuff I ran the steps that I listed in my first report in Edge 5.
In step 6, when I clicked on the carve icon to return from the keyboard shortcuts menu, it did return, but took 8 seconds.
In step 11, when I clicked on the carve icon to return from the keyboard shortcuts menu - this time without running the loaded file - it did return, but took 5 seconds.
The PC is an oldie. It has an AMD 8-core processor running at 3.11 Ghz. 8Gb of system memory. Graphics is weak. It is an AMD Radeon HD5700 with only 1Gb of onboard ram
This test was done using the early version, black board of the SLB. I just thought to look. It was still running 5.0.3. So, I figured that I would try the flash feature in Edge. Part way through, it froze. I had to close it out. The process had disconnected the USB connection and Edge no longer saw that port. I power cycled the SLB and was able to connect. Console is still showing 5.0.3.