Solved Homing Y moves the Z motors + 1LC are not connected not detected
-
Hello,
I am having some problems with my setup of a Duet 3 Mini 5+ with the added Expansion mini 2+. But I also have the tools distro board with two 1LC v1.2. The printer I am building is a V-cast v1.5 so it has two Y-Axis driven with belts.
So here are my problems;
My firmware is 3.41
Problem 1= when I press home Y the two z motors spin. I have edited and tried different drivers sockets and etc.. I am pretty frustrated at this point. I will have my config file posted below:
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Jul 19 2022 13:41:07 GMT-0400 (Eastern Daylight Time) G4 S1 ;wait 1 second for expansion boards to start ; General preferences ;M575 P1 S1 B57600 ; enable support for PanelDue M111 S0 ; Debugging off G21 ; Work in millimetres G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Matt's IDEX" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards X1 motor M569 P0.1 S1 ; physical drive 0.1 goes forwards X2 motor (U) M569 P0.2 S1 ; physical drive 0.2 goes forwards Y1 Motor M569 P0.3 S1 ; physical drive 0.3 goes forwards Y2 Motor ;M569 P0.4 S0 ; physical drive 0.4 goes forwards M569 P0.5 S1 ; physical drive 0.5 goes forwards Z1 Motor M569 P0.6 S0 ; physical drive 0.6 goes backwards Z2 Motor M569 P121.0 S1 ; physical drive 121.0 goes forwards E0 motor M569 P122.0 S1 ; physical drive 122.0 goes forwards E1 motor M584 X0.0 Y0.5:0.6 Z0.2:0.3 U0.1 E121.0:122.0 ; set drive mapping M350 X16 Y16:Y16 Z16:Z16 U16 E16:16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00:80.00 Z400.00:Z400.00 U80.00 E562.00:562.00 ; set steps per mm M566 X900.00 Y900.00:900.00 Z180.00:Z180.00 U900.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00:6000.00 Z180.00:Z180.00 U6000.00 E1200.00:1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00:500.00 Z20.00:Z20.00 U500.00 E250.00:250.00 ; set accelerations (mm/s^2) M906 X1200 Y1200:Y1200: Z1200:Z1200 U1200 E450:450 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X300 Y300 Z300 S0 ; set axis maxima M208 X0 Y300 S0 ; set axis maxima Extruder 1 (X0.1) M208 X300 Y0 S0 ; set axis maxima minima 2 (U0.2) ; Endstops M574 X1 S1 P"!io0.in" ; configure switch-type (e.g. microswitch) endstop for low end on X1 via pin !io0.in (X1) M574 U2 S1 P"!io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on U2 via pin !io1.in (U2) M574 Y0.5:0.6 S1 P"!io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin !io3.in (Dual Y) M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M558 P8 C"121.io2.in" H0.7 F1000 T6000 A20 S0.005 ; SuperPinda probe type to unmodulated and the dive height + speeds G31 P500 X0 Y0 Z2.5 ; Correct me for 8mm inductive prob - set Z probe trigger value, offset and trigger height (Super Pinda) M557 X25:300 Y25:300 S25 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C ;M307 H0 A286.0 C164.4 D2.9 S1.00 V24.0 B0 ; AC Heater 0 PID adjustment (Heatbed) M308 S1 P"121.temp0" Y"pt1000" ; configure sensor 1 as PT1000 on pin 121.temp0 M950 H1 C"121.out0" T1 ; create nozzle heater output on 121.out0 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S300 ; set temperature limit for heater 1 to 300C ;M307 H1 A286.0 C164.4 D2.9 S1.00 V24.0 B0 ; Extruder X1 Heater PID adjustment M308 S2 P"122.temp0" Y"pt1000" ; configure sensor 2 as PT1000 on pin 122.temp0 M950 H2 C"122.out0" T2 ; create nozzle heater output on 122.out0 and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H2 S300 ; set temperature limit for heater 2 to 300C ;M307 H2 A286.0 C164.4 D2.9 S1.00 V24.0 B0 ; Extruder X2 Heater PID adjustment ; Fans M950 F0 C"121.out1" Q500 ; create fan 0 on pin 121.out1 and set its frequency M106 P0 C"Heatsink fan 1" S1 H1 T45 ; set fan 0 name and value. Thermostatic control is turned on M950 F1 C"121.out2" Q500 ; create fan 1 on pin 121.out2 and set its frequency M106 P1 C"Part cooling 1" S1 H-1 ; set fan 1 name and value. Thermostatic control is turned off M950 F2 C"122.out1" Q500 ; create fan 2 on pin 122.out1 and set its frequency M106 P2 C"Heatsink fan 2" S1 H2 T45 ; set fan 2 name and value. Thermostatic control is turned on M950 F3 C"122.out2" Q500 ; create fan 3 on pin 122.out2 and set its frequency M106 P3 C"Part cooling 2" S1 H-1 ; set fan 3 name and value. Thermostatic control is turned off ; Tools M563 P0 S"Extruder 1" D0 H1 F0:1 ; 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 M563 P1 S"Extruder 2" D1 H2 F0:3 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C ; Miscellaneous ;NeoPixel LED Stip M150 X3 Q3000000 ; set LED type to NeoPixel and set SPI frequency to 3MHz M150 B255 P255 S30 f0 ; set first ALL (30) LEDs to Blue, half brightness ; Panic power loss and Resume M911 S20 R22 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power lossProblem 2= 121 and 122 are not being detecting. they keep timing out.
If I click "run config file" after saying the errors are below:9/5/2022, 7:53:04 PM Error: Response timeout: CAN addr 122, req type 6027, RID=50 Error: Fan number 2 not found Error: Response timeout: CAN addr 122, req type 6027, RID=52 Error: Fan number 3 not found 9/5/2022, 7:52:58 PM Error: Response timeout: CAN addr 122, req type 6026, RID=44 Error: Heater 2 not found Error: Heater 2 does not exist Error: Response timeout: CAN addr 121, req type 6027, RID=46 Error: Fan number 0 not found 9/5/2022, 7:52:50 PM Error: Response timeout: CAN addr 121, req type 6031, RID=38 9/5/2022, 7:52:43 PM Error: Response timeout: CAN addr 121, req type 6042, RID=31 Response timeout: CAN addr 122, req type 6042, RID=32 9/5/2022, 7:52:41 PM Error: Response timeout: CAN addr 121, req type 6042, RID=29 Response timeout: CAN addr 122, req type 6042, RID=30 9/5/2022, 7:52:39 PM Error: Response timeout: CAN addr 122, req type 6018, RID=28 9/5/2022, 7:52:38 PM Error: Response timeout: CAN addr 121, req type 6018, RID=27Important note via diag LEDS: The 122 toolboard is flashing fast red with solid blue light. But the 121 toolboard is just solid blue light. Doing a m115 command shows them not connected.
Please note:
-I have used a multimeter to check the connection on the Bus cable which is a twisted ribbon cable (2 wires) + "RJ-12" , connectors I crimped it myself. This checked it via continuity test and it is good-I have checked the connections with the 4 x small connector from the tool boards to the distro board(the jumpers ARE removed for the ones in use) This checked it via continuity test and it is good
I guess the thing to start with Problem 1. Then go from there.
Thank you so much for your help!
-
@voodoobane post your homing files so we can see what's going on.
And it sounds like you may not have a straight through RJ11 cable and that the middle 2 pins are swapped. I suggest changing that cable. You need to make sure it's one designed for ADSL
-
Please see the below:
; homex.g ; called to home the X axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jul 09 2022 21:54:56 GMT-0400 (Eastern Daylight Time) G91 ; relative positioning G1 H2 Z10 F6000 ; lift Z relative to current position G1 H1 X-305 F1800 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X5 F6000 ; go back a few mm G1 H1 X-305 F360 ; move slowly to X axis endstop once more (second pass) G1 H2 Z-10 F6000 ; lower Z again G90 ; absolute positioning; homey.g ; called to home the Y axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jul 09 2022 21:54:56 GMT-0400 (Eastern Daylight Time) G91 ; relative positioning G1 H2 Z10 F6000 ; lift Z relative to current position G1 H1 Y-305 F1800 ; move quickly to Y axis endstop and stop there (first pass) G1 H2 Y5 F6000 ; go back a few mm G1 H1 Y-305 F360 ; move slowly to Y axis endstop once more (second pass) G1 H2 Z-10 F6000 ; lower Z again G90 ; absolute positioning; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jul 09 2022 21:54:57 GMT-0400 (Eastern Daylight Time) G91 ; relative positioning G1 H2 Z10 F6000 ; lift Z relative to current position G1 H1 Z-305 F1800 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this) ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z10 F100 ; lift Z relative to current position ;G90 ; absolute positioning -
@voodoobane said in Homing Y moves the Z motors + 1LC are not connected not detected:
G1 H2 Z10 F6000 ; lift Z relative to current position
so in homey, your Z motors are expected to move 10mm. Is this what you're seeing?
-
That would make a lot of sense...kind feel dumb dumb at the moment... I ha build other printers before and I did seem to have this confusion...lol
I'll will get back to you ASAP.
Thank you
-
@voodoobane said in Homing Y moves the Z motors + 1LC are not connected not detected:
I have one more problem... So I can get 1 tool board to detect and register to 121 and I updated the firmware to tool board 3.41 from 3.30. but when I plug the 2nd tool board both do not connect... any ideas? Please and thank you.
-
Nevermind... I wired the 4x conductor connection wrong for the other tool board.
-
This Topic has been solved.
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
-
Update:
Turns out my Distro board was bad. I just replaced it. Everything is working as it should be now!
