Program goes IDLE after a long HOLD

[poplawa]

I paused the program (using physical button connected to Arduino) somewhere in the middle because I had to leave my workshop for about 2 hrs.
When I came back, the program was no longer in HOLD state but turned into IDLE. The physical RESUME button didn't work. Neither did the jog controls.
Luckily pressing SEND button resumed the program from current line.

I didn't switch off any power supply and my computer didn't go to sleep

[winder]

What version of GRBL are you using?

[poplawa]

grbl-1.1f.20170801

[poplawa]

Windows 7.

[winder]

It's possible that UGS was somehow confused by the physical pause button being pressed instead of the in-app pause button... but I think a lot of people are using environments like that and I've never heard of this problem.

When using the pause/resume buttons is it possible to pause with the physical button and resume from UGS?

[poplawa]

Yes. Usually it all works as expected, this was the only time that I saw such behaviour.
I'll let you know if it happens again

[winder]

@chamnit have you seen anything like this? I'm pulling the state right out of GRBLs feedback, is there any way it could go from HOLD to IDLE? I would have thought perhaps something about the USB connection reset, but UGS doesn't have an auto-reconnect and I don't see the version information in the console.