Tool setup: Motor, Extruder & Heater mapping
-
; ======={ Tools}========================================== M563 P0 S"LEFT" D0 H2 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R35 S150 ; set initial tool 0 active and standby temperatures to 0C M563 P1 S"RIGHT" D1 H3 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R35 S150 ; set initial tool 1 active and standby temperatures to 0C
With the updated corrections the DWC still shows that my Tool-0 and my Tool-1 have no assigned heaters.
@deckingman said in Tool setup: Motor, Extruder & Heater mapping:
One other thing that leapt out at me (but is unrelated to heaters) is this
M350 X16 Y16 Z16 U16 E16:16 E1.9:2.0That "E1.9:2.0" on the end makes no sense - remove it.
RE: I removed it, I am pretty sure that just spat out from the configurator. I still have to calibrate once I get everything ready to move and heat.
Oh, and I don't see any M669 at the beginning of your config.g to define the kinematics type either. I guess that'll be OK if your kinematics happen to be the default which I think is Cartesian.
RE: It is being ran under a cartesian setup.
-
Can you send M98 P"config.g" and report the results?
-
I have some wires not connected, such as AC the signal wire for the IDEC relay for both the bed and chamber. My hotends are capable of going above 400C from what I've been told.
@Phaedrux
9/30/2020, 4:02:14 PM Error: Response timeout: CAN addr 2, req type 6026, RID=18
Error: Heater 3 not found
Error: Bad command: H143 H3 S300
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
9/30/2020, 4:02:12 PM Error: Response timeout: CAN addr 1, req type 6017, RID=14
Response timeout: CAN addr 2, req type 6017, RID=15
Error: bad grid definition: Too many grid points; suggest increase spacing to 21.2mm
Error: Response timeout: CAN addr 1, req type 6026, RID=16
Error: Heater 2 not found
Error: Bad command: H143 H2 S300
9/30/2020, 4:02:07 PM Error: Response timeout: CAN addr 1, req type 6021, RID=12
Response timeout: CAN addr 2, req type 6021, RID=13
Error: in file macro line 42 column 50: M203: array too long, max length = 2
9/30/2020, 4:02:05 PM Error: Response timeout: CAN addr 2, req type 6018, RID=11
9/30/2020, 4:02:04 PM Error: Response timeout: CAN addr 1, req type 6018, RID=10"Error response too long"
-
@kroybal said in Tool setup: Motor, Extruder & Heater mapping:
"Error response too long"
Send from the gcode console window itself.
-
Have you set the address of your toolboards?
https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board#Section_Commissioning_a_new_Tool_Board
@kroybal said in Tool setup: Motor, Extruder & Heater mapping:
Error: Bad command: H143 H3 S300
I'm not sure if it matters, but I notice you are definining heaters 2 and 3 before you define heaters 0 and 1. I suggest rearranging that to start with 0 and move up from there.
-
@Phaedrux said in Tool setup: Motor, Extruder & Heater mapping:
Send from the gcode console window itself.
I sent "M98 P"config.g" as a command through the Console tab using the DWC and it still reports "Response too long, see Console". I am pretty certain I am sending the command through the gcode console window, unless there is another prompt which I can send code.
Have you set the address of your toolboards?
Check later for an updated edit. I will work on addressing the toolboards now.
EDIT: according to the section
https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board#Section_Buttons_and_LEDs
I am not seeing a flashing red LED whatsoever, which would suggest sync between the board and my Duet3. I do have the Vin LED fired up indicating power. Perhaps there is a common wiring issue that can occur here?Describing my setup I have an RJ11 wire going straight through to my distribution board, and on my tool distribution board I have jumpers across the CAN out standoff. I also have jumpers across the bypass standoffs on T2 and T3 ports (I am planning to only use T0 & T1.) Currently the distribution board is grabbing 24V & 15A. I have two CAN-FD cables running straight through from the distribution board to my two separate toolboards.
-
-
@kroybal as you describe this it should work.
to help with diagnosis can you try one tool board at a time. (with the jumper to bypass the other). Also its worth checking the continuity between the Duet 3 CAN header and the tool distribution board CAN header (you can do this with a multimeter with the power turned off)
-
@kroybal said in Tool setup: Motor, Extruder & Heater mapping:
I am not seeing a flashing red LED whatsoever, which would suggest sync between the board and my Duet3. I do have the Vin LED fired up indicating power.
As well as the blue VIN LED on the tool board being lit when you apply VIN power, is the red 5V LED next to it lit?
-
@T3P3Tony I have yet to check for continuity I will get to that when I reinstall the boards. I have reduced the setup to just the one toolboard for now and will add the other once its properly commissioned.
EDIT: I checked for continuity from one end of the JST ZH to the opposite and each pin had continuity across. I did the same for the RJ11 cable that I am using. every wire/pin being used is in operating condition.
-
@dc42 I did not see the 5V lit, I was wondering why it failed to turn on. The only light indication is the Vin blue LED. I have removed the setup from my black box to get a clearer image of the setup.
Assume the RJ11 is connected to the CAN_out on the duet3 I also have a heater, and a motor connected via molex. Pardon the image quality, however, the jumpers seem to be appropriately placed. I am grabbing 24V 15A from a power supply to my distribution board. Does anything stand out as to why the board doesn't show the 5V red LED or cannot be addressed using M115 B121/B10?
-
@dc42 When you brought the 5V LED to question I had checked the power supply and it was not operating as expected. My issues stem from the most trivial solution. Does it have power
-
glad you found the problem!