Sorry to bear bad news on the new beta release but here goes. I start the program and connect to my test arduino running GRBL 1.1 and all is fine. I load some gcode and again all is fine.
I hit test run button and the only thing that happens is the status block changes to âChecking Gcode Fileâ. No activity on the visualizer and the bottom of the screen no longer shows the feed & speed controls. After a few minutes the status block changes back to IDLE. Iâm guessing it has completed the checking with no errors.
I then hit start job and nothing happens. No tool movement, status block says IDLE, buttons change to Load File, Resume Job and Stop Job, no Pause Job. If I hit Resume Job then I get tool movement and viaualizer movement with the Pause Job and Stop Job buttons active. If I pause the job the tool and visualizer freeze and the status block shows HOLD as it should. However when I hit Resume Job it continues for a few seconds and stops again. This time showing IDLE status. I hit Resume Job again and it continues as normal showing RUNNING (Too many screens to show).
One last issue. If I start the program, connect successfully, load my gcode and hit Start Job nothing happens. I have to hit Resume Job to actually start the gcode.
I am running Windows 10 Pro 64bit OS.
I do have one other issue. Itâs not specifically a gSender issue but when I start the program it loads in a normal window size. I can go into properties and changed it to maximized but it still loads in a normal window size. Is this maybe a Windows problem or the way gSender is configured?
Me again. An addendum to my initial post. I switched over to the console display while I went through the issues I found. For the Test Run problem with not showing any activity on the visualizer the console does show the code being processed and it completes normally.
For the straight to Start Job issue after starting the gcode it pauses and the console shows it stopping onn a âT1â command. I guess I didnât realize the T1 was in the gcode. It is not gcode I developed so donât know what post processor was used. The other issue with the pause after Resume Job the console is showing Error:24 and it pauses again. If I hit Resume Job again it continues normally. It will throw this error each time I hit Pause Job and Resume Job. It seems like the resume loses part of the command and just skips it on the second Resume Job. Hope this helps.
Hi Heyward, good to hear your reports on this though Iâm sad to hear that a bug has already emerged in the newest version . Iâve recently broadened the scope of file formats available on the forum, so the only other thing that comes to mind is if you could attach the gcode file for us to try on our end
I am sure something significant changed with the check gcode functionality. A job I have been having trouble with took roughly 3 1/2 minutes to check under versions prior to 0.7.0 When I checked it under 0.7.0 it took 17 minutes. I checked it a second time to actually time it, as I couldnât believe it had slowed down so much. It is also throwing âerror 2â (âbad number formatâ) problems again, although at least the resume function is OK so I could finish the job. I have already submitted a feed back form about these problems.
@chrismakesstuff - Thanks for the quick response Chris. Keep in mind I am using a test arduino thatâs not hooked to any machine but that shouldnât matter I donât think. I have attached the gcode file for you to check. Obviously when I hit Pause Job it is totally random locations. As Frank said I did get error:2 once but the remainder were error:24.
@Heyward43 and @falviani many thanks to the feedback from both of you I think weâve managed to set straight these issues you reported. New version 0.7.1 is now released if youâd be able to take a look and let me know
Frank, originally we were so confused since we hadnât modified anything for the check mode but then we tested and sure enough it had gone AWOL. I believe the bug was tracked down
@chrismakesstuff - Ok, tested Check Gcode and all appears to be working again. However, the random pauses are still generating the error: 24 but it seems more random. In other words sometimes it works ok and sometimes generates the error.
As to the other issue Iâm having with running in a window or maximized itâs still not working. I can go in and change the programs properties to âMaximizedâ and apply but gSender still loads in a âNormal Windowâ. Itâs not a big deal since I can maximize it after it starts but to me it should be able to start âMaximizedâ. Something for the back burner anyway since itâs not an operational issue. Thanks to you and your team getting all of this straightened out. Oh, and it does this on both Win10 Pro/64 and Win10 Home/64.
Chris: If you plan to reply to messages via email from the forum, make sure itâs configured for that. The current error email is: " The recipient server did not accept our requests to connect. Learn more at Fix bounced or rejected emails - Gmail Help [forum.sienci.com142.93.68.9: timed out]" Thereâs probably 1 checkbox unchecked, or something silly like that
I suppose Iâll have to look into it Frank. Itâs possible that I donât have the functionality enabled somewhere so if itâs ok for now itâs probably the best bet to reply on the forum itself
. Iâve recently broadened the scope of file formats available on the forum, so the only other thing that comes to mind is if you could attach the gcode file for us to try on our end 
Retried the large file and the check time is back to normal.