thank you for your answer,
What I meant was that I tried on a corporate network and it didn't work, so I tried on my home network and it didn't work either. So I changed my DUET IP address to 192.168.1.202 and now DWT works fine.
Thank you for your reactivity and your precise answers.
Here are the setting for micron cobra motors.
M92 E1600; Set steps per mm for 16x microstepping
M566 E120; Set maximum instantaneous speed changes (mm/min)
M203 E1200; Set maximum speeds (mm/min)
M201 E600; Set accelerations (mm/s^2)
M906 E800 I30; Set motor currents (mA) and motor idle factor in per cent
OK, everything is working. I swapped the hot-end and bed heater connections back to the default positions, used A11, C99000, D2000 to get the PID tuning to run on the chamber heater.
At first the Panel Due wouldn't control the hot-end temperature, but I found a reference to the T0 statement for the config file, added it, and now it's all behaving as expected.
Thanks for the help and suggestions!
I'm glad you got it working. When upgrading firmware, you should read the upgrade notes for the new version and all the versions you skipped. The particular item that you missed is that the default deployprobe.g and retractprobe.g files must be deleted.
@dc42 said in External 5Vdc Voltage Input Reporting Bug in DWC?:
@snowcrash said in External 5Vdc Voltage Input Reporting Bug in DWC?:
That just leaves my 2 questions above which are easy to miss so I thought I'd repeat them here:
Do you think I have a voltage leakage somewhere? Is it something I should be concerned about (short- or long-term)?
No I don't think you need worry about that. I just tested a board on my bench with USB power only and I get similar results: 1.7V across the VIN terminals on my multimeter, and DWC also shows 1.7V. My guess is that the TMC2660 drivers leak a small amount of current between their +3.3V and VIN pins.
Very happy to hear! Thank you very much for taking the time to test this on your machine, @dc42, very much appreciated!