Oh wait, that bug is apparently still there. The snapmaker controller can’t parse comments correctly, whereas Lightburn can. That’s why it works in Lightburn, but not sent to the machine. Simply remove all the ; from your header gcode (or copy below).
I tested and verified that was the problem by using your file (modifying in my own focus height and material) running it and noticed the wonk, then noticed the semicolons and removed them and it ran fine afterwards.
Found this bug way back in March on firmware 1.15.x
I love the work you’re doing! The instructions were super simple, and BOOM I’m already able to send commands to the snapmaker wirelessly. It’s great!
I’ve got two questions:
Do you know how I can send files to the snapmaker without starting the job so that I can start it on the machine?
I tried simply deleting the “start job” command line, but the file will not appear in the local storage of the Snapmaker. (I could always use sm2uploader, but it would be cool to do it this way)
Where are you finding the API codes in order to figure out all this stuff?
If you’ve got a spare moment, a list of all the API codes for Snapmaker you’ve gathered over the years would be really handy if you have such a thing kicking around.
Where do I find the token stored on a Mac? Or is there another way to find the token? I have looked for machine.json on the Mac, but I don’t find it. I did also look inside of the Contents of the SnapMaker Luban Application. I don’t find it in there either. Or if it was in there, I didn’t see it. Any guidance would be appreciated.
Sadly, I don’t know where a mac stores the settings files for Luban. However, quickly looking up the equivalent seems to be ~/Library/Application Support/ and the snapmaker luban folder should be in there.