You are not logged in. Please login or register.
SoliForum - 3D Printing Community → XYZ Printing Hacks & Mods → print gcode files to miniMaker
You may also be able to pause the print using the buttons on the face of the printer (the green button on the mini pauses and resumes a print, probably something similar works for the jr).
From there you can manually pull the old filament out and manually load new filament but you have to be careful when loading or you will get a void or a blob in your print.
Also you probably need to leave the old spool installed or the printer may get confused.
I can pause from the lcd buttons, but i need to be near the print at the right time and right layer.
I've wanted to make that from gcode, but can't find the right Pause command that the printer supports 
(
Thanks for all your support!
There are several Cura plugins that will help you unload and load filament at a certain z height. I don’t know if any of these work with the davinci printers but in theory they should.
Your script needs to save the head position, move to a safe spot, unload the filament, pause for a moment while you swap filament, load the filament manually, possibly home, then return to the starting position. That all has to be done with straight gcode commands that don’t require user input (no pause till user hits a button commands).
The issue is that the XYZ controller and it's firmware does not allow for that. There is no way to read the current position and store it. The resume from pause and power fail functions works because the head stays where it was and does not get moved.
If it gets moved then then it will not line up on the previous layer correctly.
The hardware on this machine just does not support what is wanting to be done here. It sounds very simple to him. But to accomplish it through hardware and coding will require in depth knowledge of gcode commands and how to read the sliced gcode file. Even then it is near impossible with this hardware as there is no facility for storing coordinates so the best that can be done is raise the head a few mm then move it to the left or right a few mm. Pause for X time while keeping the hotend at full temp. Allow the operator to manually and forcefully remove the filament by hand and then load a another color by hand all the while keeping from moving the head even one step and any direction. If the head moves even if you use the reverse directions you used to make the initial move it will not return to the exact position and there will be a slight layer shift.
"The resume from pause and power fail functions works because the head stays where it was and does not get moved."
Actually when I pause from lcd, the extruder goes to home axes an waits for 3 minute to resume or it will cancel the print. If I resume, the head goes and prints from the last position. That function I want to achieve but with commands in gcode.
Is all so simple and yet so complicated 
Thank you all for your effort!
mishu_28nmv, I've had some good luck making multi-color prints by doing the following.
1. Either create the g-code file with Cura (or other slicer) or decrypt the 3w file using ThreeDubber.
2. Find the beginning of the layer you want to switch colors at. In a Cura g-code file, you can find the layer because it will be named ;LAYER:30 or something like that.
3. Add this bit of code to it.
;DELAY
G91
G1 Z60 F60 E0
G1 X60 F60
G1 X-60 F60
G1 X60 F60
G1 X-60 F60
G1 X60 F60
G1 X-60 F60
G1 X60 F60
G1 X-60 F60
G1 X60 F60
G1 X-60 F60
G1 Z-60 F60
G90
;ENDDELAYThis will cause the printer to stop at this layer and very slowly move the print head up and then left and right for 5 minutes. During this time, you can pull the old filament out by hand, and load in new filament. You will have to push it in by hand until the new color starts to come out of the hot end. This will also mean you will need to very closely watch the print to make sure you don't miss the filament change time. This delay goes for about 5 minutes, but you can keep adding more of these lines to the middle of it to make the delay longer.
G1 X60 F60
G1 X-60 F604. Encrypt the file again with ThreeDubber.
This is the best solution for multi-color prints that I have found for my printer. It works pretty well if you are attentive enough to not miss the delay time.
Thank you. You are a God! Will try this ASAP!
Have you seen issues if the file has a large comment header? I noticed that using the beta to convert S3D generated Gcode files would result in various errors on the Jr 1.0w - generally SD Card error. I noticed that S3D adds a lot of comment info to the header and stripping all this out and then using your tool resolves the error. I attached an example that refuses to successfully print if it helps.
If this is a common thing, I wonder if in the conversion it should remove all the comments at the begining of the file (or warn if there are too many)
Have you seen issues if the file has a large comment header? I noticed that using the beta to convert S3D generated Gcode files would result in various errors on the Jr 1.0w - generally SD Card error. I noticed that S3D adds a lot of comment info to the header and stripping all this out and then using your tool resolves the error. I attached an example that refuses to successfully print if it helps.
If this is a common thing, I wonder if in the conversion it should remove all the comments at the begining of the file (or warn if there are too many)
I have the same issues now. When I print direct from S3D, at the end of print I receive "SD Card error". I will try to remove from S3D comments
Hi guys! I just downloaded it on my pc, not Mac, but unfortunately it isn't recognised! I downloaded the xyzware firmware, which installed the drivers as well, but nothing. On xyzware it is normally detected, on the program it just stays "not detected" .
Any possible solution? Thanks!
EDIT
I just uploaded to W10 and now everything works. However, I think there is a problem with the gcode. I generate the gcode with Cura, where thy setting the printing should take more or less 1.5h. If I upload the gcode to minimover, the time is lower, like 1.2h. I also note that the walls are missing! The item comes out perfect, but without walls.
Any suggestions? Thanks!
Hello Guys,
I have your program with this error:
Can you help me? I have a da Vinci mini w+. With the last update i can't use other filament.
Thanks
Your SDcard in the printer is bad. Or your comment section in your file is too large.
So just a thank you to david.tucker for putting the minimover together. I use Slic3r to turn my parts into gcode and then load it to my miniMaker with no problems. I also found that using NFC tags it doesn't matter what temp the tag says. The miniMaker will go to whatever temp I have set in Slic3r. This has been great when printing other materials. So thank you again.
Just a shot of my miniMaker without the skin on it.
Firstly, thank you so much for working on this small program, it's file conversion feature has helped me so much!
However, I am having a bit of an issue, my Davinci 1.0 Pro 3in1 is connected to my computer via a cable yet it isn't being picked up by the program. If I were to click auto detect and hit apply, I get an error saying "set wifi parameters failed". Am I missing a step?
Firstly, thank you so much for working on this small program, it's file conversion feature has helped me so much!
However, I am having a bit of an issue, my Davinci 1.0 Pro 3in1 is connected to my computer via a cable yet it isn't being picked up by the program. If I were to click auto detect and hit apply, I get an error saying "set wifi parameters failed". Am I missing a step?
Can you create a debug.txt file in the folder with the mini mover exe, then run the program and post the text file here.
I don't exactly know how to add in a text file, yet here's what was printed:
==================================================
Log started Tue Jul 09 22:13:40 2019
0000.06 SerialHelper::queryForPorts(XYZ)
0000.06 SerialHelper::queryForPorts failed to find any ports
0000.08 XYZV3::setStream(0)
0000.08 MainDlgSetStatus(not connected)
0000.08 SerialHelper::queryForPorts(XYZ)
0000.08 SerialHelper::queryForPorts failed to find any ports
0000.11 MainDlgUpdate()
0000.11 MainDlgSetStatus(not connected)
0010.11 MainDlgUpdate()
0010.11 MainDlgSetStatus(not connected)
0020.12 MainDlgUpdate()
0020.12 MainDlgSetStatus(not connected)
0020.12 MainDlgUpdate()
0020.12 MainDlgSetStatus(not connected)
0030.13 MainDlgUpdate()
0030.13 MainDlgSetStatus(not connected)
0030.13 MainDlgUpdate()
0030.13 MainDlgSetStatus(not connected)
0040.14 MainDlgUpdate()
0040.14 MainDlgSetStatus(not connected)
0040.14 MainDlgUpdate()
0040.14 MainDlgSetStatus(not connected)
0050.14 MainDlgUpdate()
0050.14 MainDlgSetStatus(not connected)
0050.14 MainDlgUpdate()
0050.14 MainDlgSetStatus(not connected)
0060.14 MainDlgUpdate()
0060.14 MainDlgSetStatus(not connected)
0060.14 MainDlgUpdate()
0060.14 MainDlgSetStatus(not connected)
0070.16 MainDlgUpdate()
0070.16 MainDlgSetStatus(not connected)
0070.16 MainDlgUpdate()
0070.16 MainDlgSetStatus(not connected)
0080.17 MainDlgUpdate()
0080.17 MainDlgSetStatus(not connected)
0080.17 MainDlgUpdate()
0080.17 MainDlgSetStatus(not connected)
0090.18 MainDlgUpdate()
0090.18 MainDlgSetStatus(not connected)
0090.18 MainDlgUpdate()
0090.18 MainDlgSetStatus(not connected)
0100.19 MainDlgUpdate()
0100.19 MainDlgSetStatus(not connected)
0100.19 MainDlgUpdate()
0100.19 MainDlgSetStatus(not connected)
0110.19 MainDlgUpdate()
0110.19 MainDlgSetStatus(not connected)
0110.19 MainDlgUpdate()
0110.19 MainDlgSetStatus(not connected)
0120.21 MainDlgUpdate()
0120.21 MainDlgSetStatus(not connected)
0120.21 MainDlgUpdate()
0120.21 MainDlgSetStatus(not connected)
0130.21 MainDlgUpdate()
0130.21 MainDlgSetStatus(not connected)
0130.21 MainDlgUpdate()
0130.21 MainDlgSetStatus(not connected)
0140.22 MainDlgUpdate()
0140.22 MainDlgSetStatus(not connected)
0140.22 MainDlgUpdate()
0140.22 MainDlgSetStatus(not connected)
0150.24 MainDlgUpdate()
0150.24 MainDlgSetStatus(not connected)
0150.24 MainDlgUpdate()
0150.24 MainDlgSetStatus(not connected)
0160.24 MainDlgUpdate()
0160.24 MainDlgSetStatus(not connected)
0160.24 MainDlgUpdate()
0160.24 MainDlgSetStatus(not connected)
0170.25 MainDlgUpdate()
0170.25 MainDlgSetStatus(not connected)
0170.25 MainDlgUpdate()
0170.25 MainDlgSetStatus(not connected)
0180.25 MainDlgUpdate()
0180.25 MainDlgSetStatus(not connected)
0180.25 MainDlgUpdate()
0180.25 MainDlgSetStatus(not connected)
0190.27 MainDlgUpdate()
0190.27 MainDlgSetStatus(not connected)
0190.27 MainDlgUpdate()
0190.27 MainDlgSetStatus(not connected)
0200.27 MainDlgUpdate()
0200.27 MainDlgSetStatus(not connected)
0200.28 MainDlgUpdate()
0200.28 MainDlgSetStatus(not connected)
0210.28 MainDlgUpdate()
0210.28 MainDlgSetStatus(not connected)
0210.28 MainDlgUpdate()
0210.28 MainDlgSetStatus(not connected)
0220.29 MainDlgUpdate()
0220.29 MainDlgSetStatus(not connected)
0220.29 MainDlgUpdate()
0220.29 MainDlgSetStatus(not connected)
0230.30 MainDlgUpdate()
0230.30 MainDlgSetStatus(not connected)
0230.30 MainDlgUpdate()
0230.30 MainDlgSetStatus(not connected)
0240.31 MainDlgUpdate()
0240.31 MainDlgSetStatus(not connected)
0240.31 MainDlgUpdate()
0240.31 MainDlgSetStatus(not connected)
0250.32 MainDlgUpdate()
0250.32 MainDlgSetStatus(not connected)
0250.32 MainDlgUpdate()
0250.32 MainDlgSetStatus(not connected)
0260.32 MainDlgUpdate()
0260.33 MainDlgSetStatus(not connected)
0260.33 MainDlgUpdate()
0260.33 MainDlgSetStatus(not connected)
0270.33 MainDlgUpdate()
0270.33 MainDlgSetStatus(not connected)
0270.33 MainDlgUpdate()
0270.33 MainDlgSetStatus(not connected)
0280.34 MainDlgUpdate()
0280.34 MainDlgSetStatus(not connected)
0280.34 MainDlgUpdate()
0280.34 MainDlgSetStatus(not connected)
0290.34 MainDlgUpdate()
0290.34 MainDlgSetStatus(not connected)
0290.34 MainDlgUpdate()
0290.34 MainDlgSetStatus(not connected)
0300.36 MainDlgUpdate()
0300.36 MainDlgSetStatus(not connected)
0300.36 MainDlgUpdate()
0300.36 MainDlgSetStatus(not connected)
0301.74 MainDlgSetStatus(auto detecting wifi)
0301.74 autoDetectWifi()
0301.75 MainDlgSetStatus(auto detect wifi succeeded)
0302.65 MainDlgSetStatus(set wifi parameters)
0302.66 XYZV3::setWifi(linksys, [Hidden], 11)
0302.66 XYZV3::serialSendMessage(XYZv3/config=ssid:[%s,%s,%d])
0302.66 XYZV3::serialSendMessage invalid input
0302.66 MainDlgSetStatus(set wifi parameters failed)
0307.65 MainDlgSetStatus(set machine name)
0307.65 XYZV3::setMachineName(July)
0307.65 XYZV3::serialSendMessage(XYZv3/config=name:[%s])
0307.66 XYZV3::serialSendMessage invalid input
0307.66 MainDlgSetStatus(set machine name failed)
0307.79 MainDlgSetStatus(auto detecting wifi)
0307.79 autoDetectWifi()
0307.80 MainDlgSetStatus(auto detect wifi succeeded)
0308.41 MainDlgSetStatus(set wifi parameters)
0308.41 XYZV3::setWifi(linksys, [Hidden], 11)
0308.41 XYZV3::serialSendMessage(XYZv3/config=ssid:[%s,%s,%d])
0308.41 XYZV3::serialSendMessage invalid input
0308.41 MainDlgSetStatus(set wifi parameters failed)
0310.36 MainDlgUpdate()
0310.36 MainDlgSetStatus(not connected)
0310.36 MainDlgUpdate()
0310.36 MainDlgSetStatus(not connected)
0320.37 MainDlgUpdate()
0320.37 MainDlgSetStatus(not connected)
0320.37 MainDlgUpdate()
0320.37 MainDlgSetStatus(not connected)
0330.39 MainDlgUpdate()
0330.39 MainDlgSetStatus(not connected)
0330.39 MainDlgUpdate()
0330.39 MainDlgSetStatus(not connected)
==================================================
To confirm, the printer is showing up as a port in device manager (As shown in the picture)
And here's to confirm the name
For some reason I'm not seeing your com port at all. Download this program and run it then copy out the result and paste it here. Attached is a sample run on my machine attached to com 4.
https://drive.google.com/open?id=1a5U18 … 6aOgH605QJ
For some reason I'm not seeing your com port at all. Download this program and run it then copy out the result and paste it here. Attached is a sample run on my machine attached to com 4.
https://drive.google.com/open?id=1a5U18 … 6aOgH605QJ
It's listed right there under ports as COM6 in his screen shot.
Here's the results:
Firstly, thank you so much for working on this small program, it's file conversion feature has helped me so much!
However, I am having a bit of an issue, my Davinci 1.0 Pro 3in1 is connected to my computer via a cable yet it isn't being picked up by the program. If I were to click auto detect and hit apply, I get an error saying "set wifi parameters failed". Am I missing a step?
Where it says Printer: Auto on the program change it to com6 or what is the current com port of the printer.
Captchaaa wrote:Firstly, thank you so much for working on this small program, it's file conversion feature has helped me so much!
However, I am having a bit of an issue, my Davinci 1.0 Pro 3in1 is connected to my computer via a cable yet it isn't being picked up by the program. If I were to click auto detect and hit apply, I get an error saying "set wifi parameters failed". Am I missing a step?
Where it says Printer: Auto on the program change it to com6 or what is the current com port of the printer.
Upon doing that, the dropdown menu doesn't display anything about a port, ty though!
An update on my printer, I moved it to another room in my house and plugged it into a different computer. When I downloaded Minimover, it detected the printer instantaneously with no issues whatsoever, and I've been doing everything from that computer. I guess the issue was just my computer all along, but at least the problem is solved! Thanks for the help guys
Wow,
Just wow, thank you. I inheritted a Davinci Jr for my little one to mess with. I mainly run Linux on Raspberry Pi's as a desktop. Was having no luck getting threedub working (crypto errors). But now I can slice in Slic3r, covert and send to the printer. I can't currently setup the WIFI as it needs Windows PC to do that (I have laptop at work being refreshed over the summer!)
But a small amount of fiddling and 3 metre USB and we're in business. Now just need to dial in the settings. Cura won't run on the Pi. Boo.
But thank you so much for keeping this thread going.
Quick questions to anyone out there who can maybe help.
I'm trying to write a bash script for Slic3r so when you export GCode it then runs the script to convert and print using MiniMoverConsole. I've got it working pretty well, but then only thing I can't sort out is how to end the process once it has printed. I've tried a variety of things. I can easily deal with the Press Any Key after the conversion process but is there some why to run the MinimoverConsole so you don't get the press any key to continue at the end of the monitoring print, or even turn off monitoring the print via a switch. I know these features are not high on the list. But I've managed to so much with this utility on a Raspberry Pi running Linux and a USB cable, it's like magic.n Can you turn off monitoring in the console?
Quick questions to anyone out there who can maybe help.
I'm trying to write a bash script for Slic3r so when you export GCode it then runs the script to convert and print using MiniMoverConsole. I've got it working pretty well, but then only thing I can't sort out is how to end the process once it has printed. I've tried a variety of things. I can easily deal with the Press Any Key after the conversion process but is there some why to run the MinimoverConsole so you don't get the press any key to continue at the end of the monitoring print, or even turn off monitoring the print via a switch. I know these features are not high on the list. But I've managed to so much with this utility on a Raspberry Pi running Linux and a USB cable, it's like magic.n Can you turn off monitoring in the console?
Isn't it just a wait statement in code? It is probably just there for user confirmation and not needed. Have you tried finding it in the coed and commenting it out to see what happens?
I found this worked for me. The PKill is killing the monitoring process and on a Pi frees back up the resource and Slic3r.
The echo's were just there for testing. The xdotool just pretends to generate a keypress. The $1 is the filename, this is passed from Slic3r, but you can test in the command line by adding the path and filename you want to convert and print!
So in Slic3r under Print Settings->Output options just add the name of this script, in my case Printy_NoGUI.sh
(make sure this executable in linux, chmod +x and don't try running any other scripts from Slic3r first! I had one to work out print time, but this seemed to cause nothing but errors.
#!/bin/bash
sleep 3s
echo "./home/pi/Downloads/miniMover-0.9.5/miniMoverConsole/minimover -d ttyACM0 -c $1"
sleep 2s && xdotool key a | /home/pi/Downloads/miniMover-0.9.5/miniMoverConsole/minimover -d ttyACM0 -c $1
echo "this worked!"
sleep 3s
echo "./home/pi/Downloads/miniMover-0.9.5/miniMoverConsole/minimover -d ttyACM0 -p ${1::-6}.3w"
/home/pi/Downloads/miniMover-0.9.5/miniMoverConsole/minimover -d ttyACM0 -p ${1::-6}.3w & sleep 60s && pkill -f minimover
echo "finished"SoliForum - 3D Printing Community → XYZ Printing Hacks & Mods → print gcode files to miniMaker
Powered by PunBB, supported by Informer Technologies, Inc.