Panel due and sensor
-
I'll preface my comment with the fact that I'm a relative noob in the 3D printing world. I haven't used the dc42 firmware yet either, but I have been doing a whole lot of reading before hooking things up.
It also would be good to know what type your printer is and what mods you have done to it.
Can't really help with the Panel due or the sensor, but the motor stuff is possibly easier.
Don't know if you've seen this yet, but it looks to be pretty helpful.
https://miscsolutions.wordpress.com/2015/01/05/upgrading-the-mini-kossel-to-duet-electronics-part-2-software-and-commissioning/Here's a good test from the above blog to see if the motors are set up right:
…
Send G91 to select relative mode. Then test the motors individually by using the G1 command with the S2 parameter. Be ready to hit the power switch if anything goes wrong. First, send G1 S2 X10 F500. This should cause the X carriage to go slowly up 10mm and stop. Changing the parameter to X-10 should make it go down 10mm. Similarly, test the Y and Z motors by using Y10, Y-10, Z10 and Z-10 in place of X10.
...You probably want to go back to absolute mode after doing this, or maybe just reset the Duet.
Some other links I've put together in preparation are these:
http://reprap.org/wiki/Configuring_and_calibrating_a_delta_printer_using_the_dc42_fork_of_RepRapFirmware
http://reprap.org/wiki/G-code
http://sublimelayers.blogspot.com/2016/01/reprapfirmware-dc42-branch-config-files.html#comment-form -
It's a delta printer to start and it has been working prior to installing the upgraded board just a lil stuck now
-
Rommie, please can you post photos showing how the PanelDue cable is connected, at both ends. Also check that you have the PanelDue and Z probe cables connected to the correct connectors on the Duet WiFi, since the connectors for those two ports are of the same type.
-
will drop the pics up a bit later today when im home, I was thinking it may be that the TX and RX are the incorrect way round, I was going to try that a bit later also. As for the sensor I had it on a duet 0.6 prior as such it was split into 2 connectors so I installed it to a 4 pin Molex and have it powered just no response from it on the web interface. im not sure I have the signal in the correct pin, currently signal pin goes to z_probe_in.
I will also link the config file just in case I have made a boo boo there but I cant see any mistakes as yet
thanks for the reply DC
-
The order of the PanelDue wire colours should be the same at both ends of the PanelDue cable, which if you are using the standard colours will be red-black-blue-green. If you are using Molex connectors at both ends, they will be reversed with respect to the tongue position. The Z probe out wire goes to one of the end pins of the Z probe connector.
Here is a photo of my PanelDue and Z probe wiring. My PanelDue cable uses a white wire in place of a blue one.
-
ok my headers had somehow got changed so got the panel working now, although I have chased the sensor up and still having a hard time with that, it is set out the exact same way as in your picture, and still having an issue with the motors too
; Configuration file for dc42 Kossel
; Communication and general
M111 S0 ; Debug off
M550 PKossel ; Machine name (can be anything you like)
M551 Preprap ; Machine password (used for FTP);;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0x42 ; MAC Address (hexadecimal);*** Wifi Networking
M552 S1 ; Enable WiFi
M555 P2 ; Set output to look like Marlin
M575 P1 B57600 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue); Axis and motor configuration
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes backwards
M569 P4 S0 ; Drive 4 goes backwards
M574 X2 Y2 Z2 P1 ; set endstop configuration (all endstops at high end, active high)
M665 L343 R175.92 H251.28 X-0.18 Y-0.56 Z0.0 B140 ; set delta radius, diagonal rod length, printable radius, homed height and XY tower corrections
M666 X0.14 Y0.85 Z-0.99 ; put your endstop adjustments here, or use auto calibration to find them
mal)
M350 X16 Y16 E16 I1 ; Set 16x microstepping with interpolation
M92 X200 Y200 Z200 ; Set axis steps/mm (20 tooth pulleys, 0.9deg/step motors)
M906 X1000 Y1000 Z1000 E1000 ; Set motor currents (mA)
M201 X3000 Y3000 Z3000 E1000 ; Accelerations (mm/s^2)
M203 X18000 Y18000 Z18000 E3600 ; Maximum speeds (mm/min)
M566 X1200 Y1200 Z1200 E1200 ; Maximum instant speed changes
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves; Thermistors and heaters
M305 P0 T100000 B4008 R4700 H0 L0 ; Typical Chinese bed thermistor. Put your own H and/or L values here to set the bed thermistor ADC correction.
M305 P1 T100000 B4404 R4700 H0 L0 ; E3Dv6 hot end. Put your own H and/or L values here if necessary to set the first nozzle thermistor ADC correction.
M301 H0 P20 I0.5 D1000 T0.85 W150 B5 ; PID settings for the bed
M301 H1 P10 I0.10 D100 T0.50 ; PID settings for extruder 0
M570 S300 ; Allow extra heating time; Tool definitions
M563 P0 D0 H1 ; Define tool 0
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
M92 E497 ; Set extruder steps per mm for first and second extruders; Z probe and compensation definition
M558 P1 X0 Y0 Z0 H5 F300 T10000 ; Z probe is IR and is not used for homing any axes, Z probe dive height 3mm, probing speed 300mm/min, travel speed 12000mm/min
G31 X0 Y0 Z2.65 P500 ; Set the zprobe offset and threshold (put your own values here). For a delta, use zero X and Y offset.;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0 ; Axis compensation here
M207 S7.0 F3600 Z0.1 ; Set firmware retraction details
M572 D1 S0.14 ; set pressure advance
T0 ; select first print headjust hoping I'm not missing anything on there motor wise
-
woooohoooo its fixed
-
woooohoooo its fixed
Glad you got it working! A couple of questions:
1. What fixed it? (in case it helps other people)
2. When you say "the headers got mixed up", can you confirm that you don't mean the board was manufactured with the connectors fitted the wrong way round?
-
Hi dc,
In terms of the panel due the d in and D out where the wrong way round on the panel due side of my wiring so as per your picture above your white wire was my green and vice versa, that solved the panel issue. As for the motors going mad I noticed whilst moving some of the wires that 2 had completely sheared at the top of the molex on the z motor, just a quick install of 2 new crimps and that sorted that issue. Lastly for the ir sensor I have no idea what or how that got fixed but after the motors were sorted it just worked.
I think maybe when I have been installing the duet I have caught and caused the crimps to break and just did not notice it till earlier on, will teach me to check , check and check again
-
The duet board itself for the panel due and ir sensor plugs is perfect and no issues from manufacture
