DUEX 5 V0.8 TO DUEX 5 V0.11
-
@paolozampini1973 So yes, activates when the nozzle is on the bed. I hope this may fix the homez.g.
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@droftarts Yes but the LEDs light up so it indicates that it recognizes it and in any case it has always worked so useless that I change the output if you want, but it has always worked like this
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 So yes, activates when the nozzle is on the bed. I hope this may fix the homez.g.
Ian
if the LEDs on the electronics indicate that they are on and the configuration is correct it means that everything is correct So in my opinion there is a problem on the electronics that is on the hardware I understand what I want to tell you you saw it with your own eyes I also sent you the photos
-
@paolozampini1973 Test it, please. I don't have much time left to help you today, only 10 minutes.
Ian
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 Test it, please. I don't have much time left to help you today, only 10 minutes.
Ian
Okay ok So what do you want me to do
-
@paolozampini1973 Test that Z homing works. Or do you still receive an error in Console?
Ian
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 Test that Z homing works. Or do you still receive an error in Console?
Ian
No now I don't get any errors but it doesn't work
2/3/2022, 17:41:14 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX2
Board ID: 0JD0M-9P6M2-NW4SN-6J1DD-3SJ6K-KAURK
Used output buffers: 3 of 24 (22 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 77448 of which 0 recycled
Never used RAM 13092, free system stack 174 words
Tasks: NETWORK(ready,14.7%,237) HEAT(delaying,0.1%,330) Move(notifyWait,0.1%,340) DUEX(notifyWait,0.0%,24) MAIN(running,85.1%,411) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:22:33 ago, cause: software
Last software reset at 2022-03-22 17:18, reason: User, GCodes spinning, available RAM 10060, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 29.6, current 30.4, max 31.4
Supply voltage: min 25.6, current 25.7, max 25.8, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2022-03-22 17:41:11
Cache data hit count 4294967295
Slowest loop: 10.18ms; fastest: 0.18ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Filament sensors ===
Extruder 0 sensor: no filament
Extruder 1 sensor: ok
Extruder 2 sensor: no filament
Extruder 3 sensor: no filament
=== DueX ===
Read count 1, 0.04 reads/min
=== Network ===
Slowest loop: 39.72ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address 40:f5:20:0d:6b:49
WiFi Vcc 3.37, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 20648
WiFi IP address 192.168.1.4
WiFi signal strength -60dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 4 0 0 0 0 0 0
22/3/2022, 17:41:01 Connected to 192.168.1.4
- WiFi -
-
@paolozampini1973 If the LED turns on and off, that just means that the switch is working. The axis movement has to be in the correct direction. Your homez.g has the axis moving to minimum Z, but endstop was defined in config.g as maximum Z. So it's a configuration error, not hardware.
Ian
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 If the LED turns on and off, that just means that the switch is working. The axis movement has to be in the correct direction. Your homez.g has the axis moving to minimum Z, but endstop was defined in config.g as maximum Z. So it's a configuration error, not hardware.
Ian
Ok What should I change because I repeat it has always worked so it is always good V0.8 what should I change In your opinion -
@paolozampini1973 What do you mean "It doesn't work"? What doesn't work?
It's possible that the filament sensor is still configured on duex.e2stop.
I think if you move the Z2 endstop back to duex.e6stop, now that the direction is correct, it should work.
Then send
M574 Z1 S1 P"!zstop+!duex.e6stop"Make sure this is in config.g as well.
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
What should I change because I repeat it has always worked so it is always good V0.8 what should I change In your opinion
You have made a lot of changes to your config.g. If you put your 0.8 back in, I'm sure you would have just as many problems. The problem isn't the hardware, it's the configuration. Now I know more about your machine, I can update your config.g and fix the issues.
Ian
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 What do you mean "It doesn't work"? What doesn't work?
It's possible that the filament sensor is still configured on duex.e2stop.
I think if you move the Z2 endstop back to duex.e6stop, now that the direction is correct, it should work.
Then send
M574 Z1 S1 P"!zstop+!duex.e6stop"Make sure this is in config.g as well.
Ian
-
@paolozampini1973 You still have Z2, should be Z1:
M574 Z1 S1 P"!zstop+!duex.e6stop"(Sorry, made a mistake in my earlier post, edited)
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 You still have Z2, should be Z1:
M574 Z1 S1 P"!zstop+!duex.e6stop"(Sorry, made a mistake in my earlier post, edited)
Ian
I did and modified it there is nothing to do It does not work it does not work it does not work I did as you told me but it does not work even in the Z1 site it does not work
-
@droftarts explain to me why the same configuration with the V 08 everything worked and with the V 011 there are all these problems You can help me to understand Forgive me if I insist but I want to understand I want to understand Thanks and thanks for the time you are DETICATING me
Excuse me I was wrong to write that you are dedicating to me Thanks for the time you are dedicating to me
-
@paolozampini1973 Okay, I'm going to have to stop. I'll try and edit your config.g this evening. I'm available tomorrow.
I still don't think this is a hardware problem. If it is, it's because you are using a clone Duet 2, not one made by Duet3D.
Check that the pins on the expansion connector are not loose or bent over, and properly soldered, on both the Duet 2 and on the DueX (both of them).
If you feel like it, put the v0.8 back on and see if it works (which is also a clone, not produced by Duet3D). On looking at the external driver pdf you linked, your stepper timings are too fast; try:
M569 P7 S0 R1 T3:3:6:6 ; E4 X physical drive 7 goes forwards M569 P8 S1 R1 T3:3:6:6 ; E5 Y physical drive 8 goes forwardsIan
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 Okay, I'm going to have to stop. I'll try and edit your config.g this evening. I'm available tomorrow.
I still don't think this is a hardware problem. If it is, it's because you are using a clone Duet 2, not one made by Duet3D.
Check that the pins on the expansion connector are not loose or bent over, and properly soldered, on both the Duet 2 and on the DueX (both of them).
If you feel like it, put the v0.8 back on (which is also a clone, not produced by Duet3D).
Ian
Look for me there are no problems anyway I think it's better to go all the way if it's okay with you So we can talk tonight?
-
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
So we can talk tonight?
Probably not, I have ill kids.
Ian
-
@droftarts I am so sorry that you have sick children anyway Many thanks I am sending you the PDF file so we continue tomorrow at least out of curiosity to see how it endsDM860H V3.3 act英文 (1).pdf
-
@paolozampini1973 I have found one piece of information for you this evening, regarding thermistors on V0.11. From https://docs.duet3d.com/Duet3D_hardware/Duet_2_family/DueX2_and_DueX5#pcb-revision-history
Modified the series resistors of the temperature inputs to be 2k2 so they perform better with PT1000 sensors. From RRF3.4 the DueX5 version will be detected and the correct R values set in M308, for RRF 3.3 and earlier use R2200 in the M308 command.
In config.g, change M308 for the following:
M308 S3 P"duex.e2temp" Y"thermistor" T100000 B4138 R2200 ; configure sensor 3 as PT1000 on pin duex.e3temp M308 S4 P"duex.e3temp" Y"thermistor" T100000 B4138 R2200 ; configure sensor 4 as PT1000 on pin duex.e3tempThis should fix the temperature reading. But I think the thermistor configuration is still wrong. What hot ends are you using? Link to where you bought them?
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
