Even with an account in the administrator group I still had to run ‘_Add Context Menu.bat’ with elevated privileges. That said, worked perfectly. Thanks!
1 Like
I updated Windows to build 2004 yesterday. After that the connection via the context menu worked, but transfer does not. I removed the context menu and set it up again. Since that, no connection anymore. The printer is reachable via ping. Running the batch file I get the message that the IP is not reachable.
Remark: Problem is not the batch file rather the WiFi connection seems to be the issue. Batch file is working fine, even with built 2004.
After solving the WiFi issue by setting up another AP another strange thing came up. When transferring a file over Wi-Fi to the snapmaker, the Progress status on the touchscreen is gone?! It just says connected, after finishing I get the question if I would like to start the print now…
Anybody experienced that too?
I am not getting a progress bar with the laser .nc files I’m currently sending…Not enough data for a conclusion yet. Interesting. The file is small, only about 85kB, maybe transferring too fast for a progress bar?
In my case the file has been sent before, with progress bar. So this is a new issue for me.
Last time I saw the progress bar, ist was flickering with showing alternating numbers 0% and the value that was counting up?!
Another alternative is OctoPrint. I have been successfully using OctoPrint with my A350. OctoPrint also lets me use a web camera to monitor my prints.
1 Like
I‘m using OctoPrint too. Really nice features. Only thing is I don‘t know if the Z-offset, that is usually stored, and can be confirmed over the touchpanel, is set when using OctoPrint. I don‘t know how to confirm that?!
Also using octoprint removes the “recover” and filament run-out features. It would also remove any other feature that is strictly provided by the CAN interface as octoprint does not interface with CAN.
I have been setting the Z offset by hand and using OctoPrint for loading gcode files and printing. Note: I do not use Luban. My software tools of choice are FreeCAD and Cura. OctoPrint does have a filament run-out module but it does not interface with the SnapMaker.
1 Like
Today the progress bar is back again, without changing anything, weird…
1 Like
Also seeing inconsistency in uploads. I’ve had larger files fail to finish upload via Luban. I need to test over API.
@geburges Could you give me a hint how you set the Z offset?
Within OctoPI in the control windows the smallest number for the Z offset I see is 0.1, which is too much for my setting. I thought about changing the GCode of the file like this:
Before it has been Z0. I thought setting that to my desired 0.13 would work?!
Or is there an easier way, as I generally need that offset?!
@FlyByWire: When I say I set the Z offset by hand, I mean with the SnapMaker bed leveling software. The last step in bebd leveling is setting the Z offset. I have found that 2 sheets of note paper that drag against the print nozzle works best for me. ( I usually need to lower the offset by 1.2 -1.3mm.)
The g-code command “G1 Z0.13 F1800” simply move the toolhead up 0.13mm. (The shown rate of 1800 is much too fast BTW.)
If you want to change where the SnapMaker thinks Z=0 use the G92 command.
2 Likes
Today I put G92 Z0.05 into the staring script of Simplify 3D. The result was that the Z axis just moved 0.05 down (or maybe tried to move up from the home position. I think I got this wrong. Where would I have to insert the command?? I guess it should right be executed before the print start.
I’ also not happy with S3D concerning nozzle priming (which Cura does). I guess I have to insert a command for that in the script too?!
Yea, you’re on the right track but you have the behavior of G92 backwards. When you ran G92 Z0.05 you told the machine that right now, you are at Z=0.05. You would want like geburges said, Z0, to tell it that it is at Z0, because the first line of gcode will probably be referenced off of what the machine thinks 0 is.
Hi Brent, good to see you again 
I modified the S3D star tscript in the following way:
I would like to:
- Move to front position X-10 Y-10
- Prime extruder with 20 mm
- Offset Z by +0.05 for the print
…and then hopefully start printing without crashing into the bed…
Right so far??
Hey, I guess you got it right.
You preheat, move to xy-10 front left corner, move z 0, prime, set your z0 to z-0,05.
Maybe you should move to your new z0 as last command, to avoid crashing (because of warped bed?).
Will the script work with *.nc files too? And if so, would it be possible to modify the context menu to support those files?
The above script is updated, check the version number.
4 Likes
perfect, thank‘s Brent!
1 Like