Tevo Little Monster and Duet WiFi… Problems



  • Hi,

    My name is Manuel Peiro, I am from Valencia (Spain), and I post here searching help and council.

    I am proprietary of a printer Tevo Little Monster, and a month ago, decided change original board for a Duet WiFi.

    Duet3d Wi-Fi arrived past week, and make the hardware transformation, with a few issues that I can solve, and start the software version past weekend, and one word.

    PROBLEMS.

    This can be a series of post, where I hope, can solve the issues, one after other.

    All is bad? No… But i am far to print...

    What work:

    • With Prontface I have setup wifi, following wiki.
    • I have calibrated temperature of the bed, and hot until 100
    • I have hot, hotend until 220
    • I have moved manually axes with issues, when move z axis, the move is short, and if send a positive movement, the Nozzle goes down (I have solved this, changing axis direction in config.g)
    • I have do work Bltouch, with macros (deploy, retract, test...)

    And few more...

    When I have try a calibration... Head crash with bed

    What is next?
    I will like test axis endstops... But how
    Someone can make light, say me the method?


  • administrators

    Please share your config.g and bed.g files.

    Does homing the printer work properly?



  • Ok… Now I am out of home, later.

    But when I send G28(homing) nozzle only rises half the height, and in the web of Duet, you can see that it is at maximum 525 in my case



  • CONFIG.G

    ; Configuration file for Duet WiFi (firmware version 1.17)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool on Tue Oct 24 2017 12:28:59 GMT+0200 (Hora de verano romance)

    ; General preferences
    M111 S0 ; Debugging off
    G21 ; Work in millimetres
    G90 ; Send absolute coordinates…
    M83 ; ...but relative extruder moves
    M555 P2 ; Set firmware compatibility to look like Marlin

    ;*** The homed height is deliberately set too high in the following - you will adjust it during calibration.
    M665 R157 L397.1073 B157 H575 ; Set delta radius, diagonal rod length, printable radius and homed height
    M666 X0 Y0 Z0 ; Put your endstop adjustments here, or let auto calibration find them
    M208 Z0 S1 ; Set minimum Z

    ; Endstops
    M574 X2 Y2 Z2 S1 ; Define active high microswitches
    M558 P4 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
    G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
    M557 R157 S20 ; Define mesh grid

    ; BL-Touch
    M307 H3 A-1 C-1 D-1 ; reserve pin 21 for M42 or servo use
    M558 P5 X0 Y0 Z1 H5 F100 T2000
    G31 P25 X0 Y0 Z1.0 ; Set Z probe trigger value, offset and trigger height
    ;INCREASE VALUE WILL LOWER NOZZLE CLOSER TO THE BED, DECREASE THIS VALUE WILL RAISE THE NOZZLE FROM THE BED

    ; Drives
    M569 P0 S1 ; Drive 0 goes forwards
    M569 P1 S1 ; Drive 1 goes forwards
    M569 P2 S1 ; Drive 2 goes forwards
    M569 P3 S1 ; Drive 3 goes forwards
    M350 X32 Y32 Z32 E32 I0 ; Configure microstepping without interpolation
    M92 X160 Y160 Z160 E837 ; Set steps per mm
    M566 X1200 Y1200 Z1200 E3000 ; Set maximum instantaneous speed changes (mm/min)
    M203 X39960 Y39960 Z39960 E3000 ; Set maximum speeds (mm/min)
    M201 X1000 Y1000 Z1000 E1500 ; Set accelerations (mm/s^2)
    M906 X1800 Y1800 Z1800 E1500 I30 ; Set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Heaters
    M143 S260 ; Set maximum heater temperature to 260C
    M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
    M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1

    ; Tools
    M563 P0 D0 H1 ; Define tool 0
    G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
    G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

    ; Network
    M550 PDuet TLM ; Set machine name
    M552 S1 ; Enable network
    M587 SDLink-869L.2,4 P"DLink-869L.2,4" ; Configure access point. You can delete this line once connected
    M586 P0 S1 ; Enable HTTP
    M586 P1 S1 ; Enable FTP
    M586 P2 S1 ; Enable Telnet

    ; Fans
    M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

    ; Custom settings are not configured

    ; Miscellaneous
    T0 ; Select first tool



  • BED.G

    ; bed.g
    ; called to perform automatic delta calibration via G32
    ;
    ; generated by RepRapFirmware Configuration Tool on Tue Oct 24 2017 12:28:59 GMT+0200 (Hora de verano romance)

    ; Clear any bed transform
    M561

    ; Home all towers
    G28

    ; Probe the bed at 12 peripheral and 3 halfway points, and perform 6-factor auto compensation
    ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
    G30 P0 X0 Y156.9 H0 Z-99999
    G30 P1 X78.45 Y135.88 H0 Z-99999
    G30 P2 X135.88 Y78.45 H0 Z-99999
    G30 P3 X156.9 Y0 H0 Z-99999
    G30 P4 X135.88 Y-78.45 H0 Z-99999
    G30 P5 X78.45 Y-135.88 H0 Z-99999
    G30 P6 X0 Y-156.9 H0 Z-99999
    G30 P7 X-78.45 Y-135.88 H0 Z-99999
    G30 P8 X-135.88 Y-78.45 H0 Z-99999
    G30 P9 X-156.9 Y0 H0 Z-99999
    G30 P10 X-135.88 Y78.45 H0 Z-99999
    G30 P11 X-78.45 Y135.88 H0 Z-99999
    G30 P12 X0 Y78.4 H0 Z-99999
    G30 P13 X67.9 Y-39.2 H0 Z-99999
    G30 P14 X-67.9 Y-39.2 H0 Z-99999
    G30 P15 X0 Y0 H0 Z-99999 S6
    ; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
    ; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)



  • When i lower the Nozzle until the bed manually, can read this…

    Machine Status
    Head Position X Y Z
    0.0 0.0 350.10



  • i have lower the head until touch bed, and i have sended: G92 Z0, now:

    Machine Status
    Head Position X Y Z
    0.0 0.0 0.0


  • administrators

    @peirof:

    Ok… Now I am out of home, later.

    But when I send G28(homing) nozzle only rises half the height, and in the web of Duet, you can see that it is at maximum 525 in my case

    See the Common Problems page in the Troubleshooting section of the wiki.



  • If I have understand… Tomorrow will try... Is send a G30 gcode

    Before, is necesary deploy Bltouch?

    After, I must save the changes? How?


  • administrators



  • 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.



  • @dc42:

    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 moves

    why? 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


  • administrators

    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



  • @dc42:

    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



  • @dc42:

    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 card

    Jurgen



  • 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.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.