Connecting with Wireless Control Halts Job

Altmill 4x4
gControl Panel Computer
gSender V 1.6,2

Hello,

Since I’m new to my Altmill and gSender, I’m not sure if this existed in previous versions. Whenever I connect to gSender using the Wireless Control option (looks like it’s simply enabling a local web server) when I’m running a job and connected remotely, either with my cell phone or in the browser of another computer, the running job will halt. I have to unlock it so that it will continue for a few seconds to a few minutes before it halts again. As soon as I disconnect any remote client that I was trying to connect with, the locking stops and the job runs normally.

This has been happening to me too, and to make it worse when I’ve resumed the job the last couple of times it’s turned out it’s lost its place and the piece gets ruined upon re-start…

I am (still) using an ancient version of g-sender (1.2.2) and seem toremember that this issue made me stop connecting my tablet at home to have a looksie at the progress timer. I have a security camera hanging above the machine bed to be able to follow progress on laser projects. I tend to start those on site and move home. No need to hover around laser jobs as much as carvings.

I now only reconnect the tablet remote to restart an etch or move to a new xyzero after the machine has finnished an etch, when I have a batch running. I don’t like to walk 300 yards if there is no need for it.

It seems this problem is still around after.. say.. at least 3 years.

I always have a remote running in my office a door away from the machine, to load files into the machine directly from my design pc. That one never stalls the machine, but it also is never started during a job because it is always my path of uploading the file.

Phones and tablets seem to be the problem in 1.2.2.

Hey, actually this has been fixed in 1.7.0-Edge as part of the auto-connect on remote if you’re connected on desktop - the path that caused the job to stop no longer occurs when you auto join the correct event channel on a remote client now.

So it’s both convenient (opening remote already has you connected to the correct device) and fixes this issue.