Tevo Little Monster and Duet WiFi… Problems
-
Hi,
a dude, i have read there is a gcode, for move the nozzle, but it stops if detect Endstop or Z probe, is a flag of "G1" order. No?
but when i send, for example, this gcode: "G1 S0 Z20 F350"… Nothing happens...
what am I doing wrong?
Copy and paste of RepRapWiki
G0 & G1: Move
Support FiveD Teacup Sprinter Marlin Repetier Smoothie RepRapFirmware
yes yes yes yes yes yes yes
Usage
G0 Xnnn Ynnn Znnn Ennn Fnnn Snnn
G1 Xnnn Ynnn Znnn Ennn Fnnn Snnn
Variables
Not all variables need to be used, but at least one has to be used
Xnnn The position to move to on the X axis
Ynnn The position to move to on the Y axis
Znnn The position to move to on the Z axis
Ennn The amount to extrude between the starting point and ending point
Fnnn The feedrate per minute of the move between the starting point and ending point (if supplied)
Snnn Flag to check if an endstop was hit (S1 to check, S0 to ignore, S2 see note, default is S0)1
Examples
G0 X12 (move to 12mm on the X axis)
G0 F1500 (Set the feedrate to 1500mm/minute)
G1 X90.6 Y13.8 E22.4 (Move to 90.6mm on the X axis and 13.8mm on the Y axis while extruding 22.4mm of material)
The RepRap firmware spec treats G0 and G1 as the same command, since it's just as efficient as not doing so.2
Most RepRap firmwares do subtle things with feedrates.
1. G1 F1500
2. G1 X50 Y25.3 E22.4
In the above example, we set the feedrate to 1500mm/minute on line 1, then move to 50mm on the X axis and 25.3mm on the Y axis while extruding 22.4mm of filament between the two points.
1. G1 F1500
2. G1 X50 Y25.3 E22.4 F3000
However, in the above example, we set a feedrate of 1500 mm/minute on line 1, then do the move described above accelerating to a feedrate of 3000 mm/minute as it does so. The extrusion will accelerate along with the X and Y movement, so everything stays synchronized.
The RepRap spec treats the feedrate as simply another variable (like X, Y, Z, and E) to be linearly interpolated. This gives complete control over the acceleration and deceleration of the printer head in such a way that ensures that everything moves smoothly together, and the right volume of material is extruded at all points.3
To reverse the extruder by a given amount (for example to reduce its internal pressure while it does an in-air movement so that it doesn't dribble) simply use G0 or G1 to send an E value that is less than the currently extruded length.
Notes
1Some firmwares allow for the RepRap to enable or disable the "sensing" of endstops during a move. Please check with whatever firmware you are using to see if they support the S variable in this way, as damage may occur if you assume incorrectly. In Duet-dc42 firmware, using the S1 or S2 parameter on a delta printer causes the XYZ parameters to refer to the individual tower motor positions instead of the head position, and to enable endstop detection as well if the parameter is S1.
2In the RS274NGC Spec, G0 is Rapid Move, which was used to move between the current point in space and the new point as quickly and efficiently as possible, and G1 is Controlled Move, which was used to move between the current point in space and the new point as precise as possible.
3Some firmwares may not support setting the feedrate inline with a move.
4zpl fork of the Duet firmware implements an additional 'R1' parameter to tell the machine to go back to the coordinates a print was originally paused at.
Some older machines, CNC or otherwise, used to move faster if they did not move in a straight line. This is also true for some non-Cartesian printers, like delta or polar printers, which move easier and faster in a curve. -
I was referring to this one: https://duet3d.com/wiki/Common_problems_and_their_solutions#When_I_try_to_home_my_printer.2C_sometimes_the_carriage_or_carriages_move_only_part_of_the_way_towards_the_homing_switches.2C_and_I_have_to_command_it_to_home_again_to_make_it_go_all_the_way.
Hi,
when i try to send
G91 ;Relative movements
G1 S1 Z50 ;Move head 50 mm upwards with S1 (endstop detection,no?)Result… the head not moves, if i send G1 Z50, moves.
G90 ;Relative movements
G1 S1 Z300 ;Move head 50 mm upwards with S1 (endstop detection,no?)obtain of response:
Error: Attempt to move the motors of a Delta printer to absolute positions
and head, not moveswhy? The firmware not suport S1 flag?
When the printer uses procedures stored in homedelta.g? When i send G28?
In this moment, when i send a G28, the head, only go down aprox. 10 mm (not sure)
Other option.... In original board, Smoothieware:
1- I moved the head close to the bed (paper thing)
2- I sended the gcode M306 Z0 (this tell to board, what this point is Z=0)
3- I sended M500, for save changes.In Duet, there is similar procedure? in this moment, the printer think is aprox 200 mm under the real position, and S1 flag dont work....
Flash another firmare?ideas.... i don't know....
-
Hello dear TEVO Little Monster user, I would be very happy if someone of you would share a complete "sys" folder.
I have a Duet Wifi with 1.19 firmware and just can not convert the TEVO LM with it. My other Tevo LM with a Duet Ethernet and 1.17 Firmware works perfect,
I copied the 1.17 "sys" entries and modified the config (mac adress etc. ) but the BL Touch give me the error: "Z probe already triggered at start of probing move" and the board hangs after 2 steps.I have read all the threads, but nothing helps. The BL-Touch is ok, The wiring also.
Many, many thanks in advance.
Jurgen from Germany -
You should upgrade the 1.19 firmware to 1.19.2.
To seen the differences between 1.17 and 1.19.2 firmware and what adjustments you need to make to the configuration files, look at the upgrade notes for every firmware after 1.17 up to 1.19.2 in https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md.
Regarding bltouch, the main change is that deployment and retraction are automatic in G29 and G30 commands. Your bed.g file must use M401 to deploy the probe near the start, and M402 to retract it at the end.
HTH David
-
You should upgrade the 1.19 firmware to 1.19.2.
To seen the differences between 1.17 and 1.19.2 firmware and what adjustments you need to make to the configuration files, look at the upgrade notes for every firmware after 1.17 up to 1.19.2 in https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md.
Regarding bltouch, the main change is that deployment and retraction are automatic in G29 and G30 commands. Your bed.g file must use M401 to deploy the probe near the start, and M402 to retract it at the end.
HTH David
Thank you David!
Unfortunately, it still does not work. I would be really happy if someone would share a working 1.92 configuration. Then I could identify the problem.
Thanks a lot in advance
Jurgen -
You should upgrade the 1.19 firmware to 1.19.2.
To seen the differences between 1.17 and 1.19.2 firmware and what adjustments you need to make to the configuration files, look at the upgrade notes for every firmware after 1.17 up to 1.19.2 in https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md.
Regarding bltouch, the main change is that deployment and retraction are automatic in G29 and G30 commands. Your bed.g file must use M401 to deploy the probe near the start, and M402 to retract it at the end.
HTH David
Thank you David!
Unfortunately, it still does not work. I would be really happy if someone would share a working 1.92 configuration. Then I could identify the problem.
Thanks a lot in advance
Jurgen -
Hi,
after issues, my Telvo Little Monster Duet transformation, start to work….
Can you explain the issue?
-
Hello Peiro, thanks for your help.
My problem is the BL Touch. Sorry for my english
I have 3 identical Tevo LM printer and print parts for an art project.
I upgraded the first printer with the Duet Ethernet Board and everything worked right away without any problems. Firmware is 1.8.1.
I was so excited that I immediately upgraded the other two printers with Duet Ethernet boards. The new boards had version 1.9. as a firmware. That's when the problems started. I just had the configuration of
first printer copied. That did not work, because some had changed commands in version 1.19, David pointed out to me and I corrected that, as far as I understood.
But BL Touch still did not work properly.
Since I have the firmware downgraded to 1.81. I tried to use the configuration of the working printer, which also uses 1.81.
BL Touch starts normally, but touches the heating bed while probing and stays lit red. That's the same with both printers.
At first I thought that maybe some data from the config.override will be used. But I did not find this file on the SD cardJurgen
-
Hi,
At the end, I have changed Bltouch for Mini Ir Differential Sensor.
Works great..
-
Hi, that sounds good. Can you share details?
I would immediately replace the BLTouch. -
Hi,
At the end, I have changed Bltouch for Mini Ir Differential Sensor.
Works great..
I have now ordered the Mini IR probes to exchange the BlTouch probes. Could you please share the necessary adjustments in the configuration? Do you have a mount for the Tevo LM? That would be really great and would help.
-
I have finally understood everything and found the mistake that has probably already made some.
The trigger dive height was too low in the G31 command. Now all 3 printers work and I will now try to convert a Wasp3d 60100 with this fantastic Duet board.
Thank you! -
I'm glad it's working! Let us know how you get on with the Wasp
-
Do you still need instructions how install mini Ir?
It's simple, all info it's in escher webpage.
The most difficult part is the physical installation, if you can print.I can gave the system I used tomorrow.
It's simple… Even I could do it ... Suppose it's easy
-
Do you still need instructions how install mini Ir?
It's simple, all info it's in escher webpage.
The most difficult part is the physical installation, if you can print.I can gave the system I used tomorrow.
It's simple… Even I could do it ... Suppose it's easy
that would be fine if you post the configuration. do you have a stl file to mount the IRprobe? I ordered the IR-Probes on the escher page and already read the instructions, should not be a problem. I will definitely equip a printer with it.
Thank you!! -
Hi,
some pics…
Resume…
A piece of aluminum profile cut with a Dremel TM.If need i can gave more info, but if you can print, think is better if print a piece...
-
ok, thank you. I will print a similare adjustable mount.
-
Hi, I finally had time to deal with the adjustable mount for the Mini IR Probe.
It fits into the screw holes for the BL touch. The sensor can be mounted on both sides to determine the distance to the Nozzle. I like to send the STL file to request. I did not manage to show pictures here
I'm just wondering what I have to adjust in the config.g and other files. I think first I delete the deployprobe.g and the retractprobe.g, since the BL touch is now gone. In the config.d I have now the following:M307 H3 A-1 C-1 D-1; reserve pin 21 for M42 or servo use
M558 P4 X0 Y0 Z1 H3 F200 T5000
G31 P25 X0 Y0 Z1.3; Set Z sample trigger value, offset and trigger heightCan I take that for the IR probe, or do I have to change something. I think I have to adjust the value for the Z trigger. What else do I have to consider.
-
Connect the IR probe to the Z probe connector. Use P1 in M558, and P500 in G31.
-
Everything worked, the results are perfect.
I have exchanged all 5 BL-Touch against the Mini IR Probe and am now really happy with the workflow.
Thank you very much for the prompt and friendly support.
