Help: Temp Sensors and Homing Issues
-
Your M575 P1 setting is correct, so it should be able to communicate with the PanelDue assuming that the PanelDue is set to 57600 in the Settings page.
Next step is to check whether the Duet is receiving data form PanelDue. Connect to the Duiet via YAT and send M111 S1 P3. It should report that debugging enabled for the GCodes module. It will then echo all received GCode commands in the YAT main window. Do you see any messages beginning "aux: M408" ? You should get those as long as the PanelDue is not on the Setup page.
If you are using the ribbon cable, make sure it is plugged into the CONN_SD socket on the Duet. Not CONN_LCD.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
Here is the result from DWC YAT is not giving me connection options for comm ports. YAT is to difficult
console.txt -
@94118 said in Help: Temp Sensors and Homing Issues:
YAT is to difficult
console.txtM111 S1 P3 has enabled debugging messages to steam to the USB port. You will need either YAT or some other USB terminal to view it.
-
having problems with USB terminal emulators they do not see anything beyond comm 1
-
Does the duet show up as a device in device manager?
-
NO it does not
-
But you are able to connect to the duet via the network and DWC?
-
When you connect the Duet via USB does it make the usb device detected sound?
-
Have you followed this part of the getting connected guide?
Have you installed the drivers?
It also covers YAT.https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7#s5
-
Duet to the network Yes. Duet to USB NO Sound from windows. Unable to install duet drivers cause DM states not compatible with 64bit
-
Request an update for recent message about the paneldue
-
Duet 2 wifi seems to good with USB but not the paneldue
-
Please see the post from DC42 above. https://forum.duet3d.com/post/134957
You need YAT connected via USB so that we can see if there is communication between the paneldue and the duet.
-
Direct from YAT: with Duet 2 plugged in to USB talking to Paneldue
Debugging enabled for modules: GCodes(3)<LF>Debugging disabled for modules: Platform(0) Network(1) Webserver(2) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15) LinuxInterface(16)<LF>
NO (aux: M408)
What next
-
dc42 said in Help: Temp Sensors and Homing Issues:
If you are using the ribbon cable, make sure it is plugged into the CONN_SD socket on the Duet. Not CONN_LCD.
In your first picture it shows the PanelDue ribbon cable plugged into the wrong port. Are you still connected that way? Have you tried the 4 wire cabling option?
-
disconnected ribbon cable now it shows Idle And Temps
-
So it's working now? Your responses are so short it's hard to know what's actually going on, which makes it very challenging to help you out.
-
I have and got it working by removing the ribbon cable. Now i think its my endstops conflicting with homing controls and commands (https://drive.google.com/open?id=1DxrsV36-5PN991DjbJJKdIKGP0n85crk) picture included status of endstops state Yes
-
If the endstop state says that it' triggered when it's not, then it's likely been defined incorrectly for the switch type.
I don't know what type of switches you have, or how the endstops have been defined in config.g.
https://duet3d.dozuki.com/Wiki/Gcode#Section_M574_Set_endstop_configuration
It's likely a case of needing to change an S0 to S1 or vice versa.
-
Mechanical ENdstops
