New duet 3 install with toolboard.
-
I know its got to be something simple as possible my config or something like this. I have ran the tool board command to check to see if its getting thought to the main board it comes back with the normal responses. Give me the firmware version also. This is the response I get back.
M115 B50 Board TOOL1LC firmware 3.1.0 (2020-05-15b1)Now Im not getting any temps from the heater or getting responses from the Bltouch, it blinks from time to time. Also the red light is blinking. Thought it was the cheaper RJ11 cord that only had 4 slots on it. So got a actually adsl cord that has 6 pin slots so they would line up with the pins on the main board. Even though your only using the two middle lines. It still does the same thing. Its giving me these errors. So guessing something is off on my config.g maybe.
7/3/2021, 4:53:53 PM Error: M307: Board 50 received unknown msg type 6049 7/3/2021, 4:53:53 PM Warning: M950: Sensor number 1 has not been defined 7/3/2021, 4:53:53 PM Error: M308: Board 50 received unknown msg type 6031 7/3/2021, 4:53:53 PM Error: M906: Board 50 received unknown msg type 6043 7/3/2021, 4:53:53 PM Error: M92: Board 50 received unknown msg type 6042 7/3/2021, 4:53:53 PM Error: M350: Board 50 received unknown msg type 6042 7/3/2021, 4:53:53 PM Error: M584: Board 50 received unknown msg type 6042Heres my config.g file, if anyone can help me get this printer back working.. I really can't have it down this long. I had my duet 2 wifi in it for long time and has been great board. Was really looking forward to this. Just this alot to try to figure out. I gotten alot of it. I also use the RRF config tool to make the config.g so not sure what is wrong. I also changed the tool number to 50 to try to see if it would help.
;Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Jun 30 2021 22:12:28 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name M586 P2 S1 T1 ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S0 ; physical drive 0.2 goes backwards M569 P50.0 S0 ; physical drive 121.0 goes backwards M584 X0.0 Y0.1 Z0.2:0.4 E50.0 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X100.00 Y100.00 Z800.00 E476.00 ; set steps per mm M566 X600.00 Y600.00 Z18.00 E300.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min) M201 X1500.00 Y1500.00 Z100.00 E10000.00 ; set accelerations (mm/s^2) M906 X500 Y500 Z500 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-33 Y-10 Z0 S1 ; set axis minima M208 X220 Y220 Z240 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io1.in M574 Y1 S1 P"io2.in" ; configure active-high endstop for low end on Y via pin io2.in ; Z-Probe M558 P0 H5 F120 T7200 ; disable Z probe but set dive height, probe speed and travel speed M557 X20:200 Y20:200 S40 ; 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 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S130 ; set temperature limit for heater 0 to 130C M308 S1 P"50.temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin 121.temp0 M950 H1 C"50.out0" T1 ; create nozzle heater output on 50.out0 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S275 ; set temperature limit for heater 1 to 275C ; Fans M950 F0 C"50.out1" Q500 ; create fan 0 on pin 50.out1 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"50.out2" Q500 ; create fan 1 on pin 50.out2 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 S"Herema" D0 H1 F0 ; 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 ; Custom settings are not defined ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue T0 ; select first toolThanks for any help.
-
The toolboard is firmware 3.1, but what firmware is your mainboard? They should both be at 3.3 at this point.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
Upload that zip file to the system tab in DWC. Then after it reboots send M997 B# where # is the CAN bus address of the toolboard to update it's firmware as well.
-
@phaedrux I finally got it working.. It was the cable i ended up replacing the whole cable with whole adsl cable. It works now. But Im having issues getting PID tunes. It come back with Error: Failed to start heater tuning. It looks like it wants to start. But then i get that really quick. So far everything seems to be working. Except that. Haven't checked the Bltouch yet on the tool board. Also I updated the toolboard firmware and the mainboard though my pi.
-
@phaedrux I read somewhere I might have to move the heater to the board to do the pid tune? Is this correct?
-
@kordris said in New duet 3 install with toolboard.:
@phaedrux I read somewhere I might have to move the heater to the board to do the pid tune? Is this correct?
As of firmware 3.3 it's supported on expansion boards.
https://duet3d.dozuki.com/Wiki/Duet_3_firmware_configuration_limitations
-
@phaedrux Only problem I got now.. Is my X-Axis doesn't want to home all the way. It thinks the 0.0 is like almost close to the endstop. But when I try to home it. It moves a little and stops. No errors etc... I tried to edit the homex.g file. This is what I got since its new firmware and they changed alot not sure if its something else. But my y-axis is homing fine without any issues. The probe is working so far.
G91 ; relative positioning G1 Z5 F7200 H2 ; lift Z relative to current position G1 H1 X-258 F1800 ; move quickly to X axis endstop and stop there (first pass) G1 X5 F7200 ; go back a few mm G1 H1 X-258 F360 ; move slowly to X axis endstop once more (second pass) G1 Z-5 F7200 H2 ; lower Z again G90 ; absolute positioningAlso not sure why I couldn't get the toolboard to do pid tune on the heater. I updated the toolboard to the 3.3 I think I will try to update it again to make sure.
-
The homex look's correct based on your config.
Check your X axis by turning off the motors with M18, move the print head somewhere near the center of the bed and send G92 X100 to tell the firmware the X axis is homed and free to move. Now send G1 X10 F1000. It should move to the right 10mm. Measure the distance moved with a ruler to make sure it's actually moving that far. If it doesn't go to the right, or doesn't move the right amount you'll need to address that by either changing the direction of rotation of the x motor or changing the steps per mm for x.
For the toolboard firmware, send M115 B# where # is the can bus address of the toolboard to check it's firmware version.
-
@phaedrux I got the toolboard on the newest and its finally working on the pid tune. Not sure why it didn't work the other time. Maybe i didn't do it right. But I try the x axis. But my steps on axis on y and x should only be 100. Even on my duet 2 thats what they were. Unless it has changed.
-
@kordris said in New duet 3 install with toolboard.:
M208 X-33 Y-10 Z0 S1 ; set axis minima
Well your axis minima for X is -33, so when it hits the endstop it thinks it's at -33 and 0 would be 33mm to the right. If this is what you're seeing, that's to be expected. If you want 0 to be right at the endstop, change the axis minima to 0.
Usually the reason for using a negative value for the minima is if the endstop is off the edge of the printable bed surface and you want 0,0 to be on the printable area.
-
@phaedrux that is what the config tool made it. This is what my orginal config is on my duet 2 wifi was. So i even tried this also. It still stops or doenst move to a certain point.
; Axis Limits M208 X0 Y-22 Z0 S1 ; Set axis minima M208 X210 Y220 Z240 S0 ; Set axis maxima from 0 to 250, Y bed goes from 0 to 210 -
@kordris said in New duet 3 install with toolboard.:
It still stops or doenst move to a certain point.
Can you show a video of this behaviour? I'm not really sure what you mean.
-
@phaedrux Give me a few once the pid tune is finished I can do a quick video. I think it thinks the 0.0 is where it stops at. Because that is what is showing on the screen. I have tried to put the print head on the endstop and then tighten the belt and then it still ends up doing it again.
Heres a video on something I could record.. Its not much I can try to record something else. But its not even moving much in the video here. It won't go to the right. It wants to keep going to the left. I have changed the movement command also in the config.g which will reverse the movement. It still gives me same issues.
-
@kordris said in New duet 3 install with toolboard.:
I have changed the movement command also in the config.g which will reverse the movement.
Is the X endstop on the left side?
Does -X make the head move to the left?Your video link is private so I cannot see it.
-
@phaedrux Yes the endstop is on the left.. and when I click on the -x it moves to the left. But when i hit home x it starts the process of homing like it should but it acts like the endstop is tripping. Almost like right away. Its then giving the herema a 0.0 so I cant move it to the left any more. Also I fixed the link this should work now. Might try to recrimp the end to make sure its not a bad crimp.
-
@kordris said in New duet 3 install with toolboard.:
But when i hit home x it starts the process of homing like it should but it acts like the endstop is tripping. Almost like right away.
Ok, that sounds like your endstop is detecting as triggered when it shouldn't. And your video seems to confirm that.
Please test your endstop status by sending M119 once when the switch is not depressed and again while the switch is depressed. Does the x endstop status change?
Is your endstop wiring running next to other wiring and picking up interference? How is the endstop connected? Normally open, or normally closed?
-
@phaedrux I have tried the M119 command it reacts like it should. When I hold it down its detecting a pressed switch. They are microswitches so. I only have two switches on the board so shouldn't pick up much interference. I tried them both ways it seems to detect both ways. I have checked that. Only other thing I could try is the switch it self is bad. It wasn't before I switched the board.
-
After some testing and going though a few things. It looks like I figured it out. It was either some type of interference with the type of endstop I was using or bad endstop which I don't think it was because it would work fine when I pulled it away from the other wires and keep it alone. I also tried another of the same type of endstop. It behaved the same way. It worked just fine when I had it alone. But as soon as I put it with a few motor wires and zip tied them up it would cause some type of interference. I ended up having to use a 3 pin endstop that uses 5 volts, signal line, and ground. This seemed to fix the issue. I had to make a new mount after I did some quick tinkercad modification on my old one. Then slap it into my SLA printer. Then inserted some brass knurl nuts into it. It made a nice little mount. I have noticed this board is really picky with stuff like this. At least I know when I go though this again on my other AM8 printer. I will have this all down.
-
@phaedrux Thank you for the help you gave me.. Really would love to look into some Hall effect sensors. They are now just coming onto the market for the Voron. Like the idea of not having to use any contact. Might also look at replacing my bed micro sensor to a 3 pin one also. As of right now its been fine its working good. Guess because its not getting any interference. Anyways are there any newer plug ins or addons I should look at? or anything I should look at with the new duet 3 that the duet 2 wifi didn't do.
