DUEX 5 V0.8 TO DUEX 5 V0.11

droftarts

@paolozampini1973 Yes, I understand the machine. You're just posting the same images again. PLEASE ANSWER THESE QUESTIONS!

In DueX2 mode, you said that the external drivers (X and Y) move correctly (except for the original problem of skipping), but you cannot move the extruders on driver 5 and driver 6. Correct?
In DueX2 mode, can you move the Z2 motor on driver 9?
Is there any reason you cannot connect Z2 motor to driver 0 (X) or 1 (Y) on the Duet 2 WiFi board?
Please post a good picture of how your DueX v0.11 board is set up.
What is the exact specification of the thermistors that you have for your tools and bed? Make, model or link would be useful.

If you don't understand the questions above, please say.

Ian

paolozampini1973

@droftarts
i can't move them because i have it busy driver 5 driver 6 are busy driver 4 is busy driver 3 is busy there are 4 extruders connected

paolozampini1973

@droftarts Sorry my dear I sent you the photos because I can't explain I have 4 instructors as you can see from the photos they are connected then I need two outputs for X and Y then I need two independent outputs for Zeta and this seems to me that we understand each other Have patience because the printer is a bit complex
self-leveling takes place via two switches As you can see from the photos Look carefully at the photos Maybe so I can explain myself better Forgive me for my poor English

droftarts

@paolozampini1973 Can you move the motor connected at the bottom of the image, to the top?

Ian

paolozampini1973

@droftarts

DRIVER 3 E0 extruders
DRIVER 4 E1 extruders
DRIVER 5 E2 extruders
DRIVER 6 E3 extruders
TOTAL 4 extruders
these are four extruders these Drivers are already engaged Tell me if I have made myself clear please
Z1 DRIVER 2 Z2 DRIVER 9 Here are the independent AXIS Z

paolozampini1973

@droftarts YES THIS Z2 that is Z2 driver 9

droftarts

@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:

@droftarts YES THIS Z2 that is Z2 driver 9

Yes. Can you move it as indicated?

Ian

paolozampini1973

@droftarts Yes of course I can move it but once we have moved Z you are doing all this to switch to DUEX 2 correct me if I'm wrong ?
Ok I moved Z2 But where do you tell me that's driver 1 = Y

paolozampini1973

@droftarts I moved like you told me now what to do?

droftarts

@paolozampini1973 In config.g, change:

M569 P1 S1                                   ; Z2 (Y)    physical drive 1 goes forwards

M584 X7 Y8 Z2:1 E3:4:5:6 S0                  ; set drive mapping

Reset after this change, then test Z works correctly

Ian

paolozampini1973

@droftarts AXIS Z OK
M574 Z2 S1 P"!zstop+!duex.e6stop" I have to reconfigure it as I configure it because otherwise the switches don't work rightly?

droftarts

@paolozampini1973 duex.e6stop should still work in DueX2 mode, but if you want you can move it to the Duet 2. I suggest ystop.

Ian

paolozampini1973

@droftarts Yes you're right No it's okay let it stay where it is

paolozampini1973

@droftarts Ok Now what do you want me to do ?

droftarts

@paolozampini1973 Next, remove these 4 jumpers on DueX:

1 for DueX2 mode:

3 to disable on board stepper drivers:

Ian

paolozampini1973

@droftarts Yes I have already done this

droftarts

@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:

@droftarts Yes I have already done this

Including the jumper on EN9?

Ian

paolozampini1973

@droftarts YES

droftarts

Reset Duet and DueX. Check that DueX is recognised as DueX2. Send M122 to check.

Ian

paolozampini1973

@droftarts 22/3/2022, 15:31:27 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: 6 of 24 (20 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 77448 of which 0 recycled
Never used RAM 13092, free system stack 184 words
Tasks: NETWORK(ready,10.5%,246) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,313) DUEX(notifyWait,0.0%,24) MAIN(running,86.4%,433) IDLE(ready,2.9%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:25 ago, cause: power up
Last software reset at 2022-03-22 15:15, reason: User, GCodes spinning, available RAM 13092, slot 1
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 25.3, current 29.0, max 29.1
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 15:31:26
Cache data hit count 987899119
Slowest loop: 6.44ms; 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 0.7ms, 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: ok
=== DueX ===
Read count 1, 2.32 reads/min
=== Network ===
Slowest loop: 39.64ms; fastest: 0.00ms
Responder states: HTTP(0) 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 23400
WiFi IP address 192.168.1.4
WiFi signal strength -63dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
22/3/2022, 15:31:20 Connected to 192.168.1.4