DUEX 5 V0.8 TO DUEX 5 V0.11

paolozampini1973

@tekkydave I am willing to do all the tests you say but before doing any tests that I did not understand what you explained to me because I do not speak English very well please answer please please and please I did not have all these problems i had only a small problem the printer worked fine and i didn't have all these problems please help me understand why now with the V 011 or all these problems instead of upgrading i did a download the facts say this would you be so kind to explain to me thank you

paolozampini1973

@tekkydave maybe I can't explain myself I mean I'll give you an example that has nothing to do with it You have a car with an engine that at 200,000 km but works well gives you just a few small problems You mount a new engine and the car gives you many problems with a new engine then either it is the engine that is not good or you have the wrong connections But yes the connections are the same and identical because the engine is not working well This is what I am trying to understand I hope that I have explained myself Thanks for your attention

droftarts

@paolozampini1973 Great! Some information at last! So currently:
Duet 2 drivers 1 (Z1), 3 (E1) and 4 (E2) are in use, 0 and 2 not used.
DueX5 drivers 5 (E3), 6 (E4), 7 (X, external), 8 (Y, external) and 9 (Z2) are in use.

Seems like the obvious solution is to move the Z2 axis to the Duet mainboard, driver 0 or 2. Then run the DueX in DueX2 mode, as has been already suggested many times.

Also, post your config.g and M122, as I've asked before.

I don't understand what you mean by this:

HOW DO POWER SUPPLY X + Y GO WITHOUT ANY DATA COMMAND

If you mean how will X and Y get step commands in DueX2 mode, don't worry, it will.

Ian

paolozampini1973

@dc42 my printer configuration:
Z is configured with two INDEPENDENT motors FOR SELF-LEVELING one on Driver 1 = Z one on the driver 9 = Z then X = DRIVER 7 EXSTERNAL DM860H Y = DRIVER 8 EXSTERNAL DM860H then I have 4 driver instructors 3 TMC2660 + driver 4 TMC2660 + driver 5 TMC2660 + driver 6 TMC2660
PROBLEMS WITH DUEX5 V0.11 IN DUEX5 OFF DRIVE MODE 7 AXIS X + DRIVER 8 AXIS Y WHY I NEED TO USE IT

HOW DO POWER SUPPLY X + Y GO WITHOUT ANY DATA COMMAND

HIGH TEMPERATURE M906 I TRIED TO PUT ALL AXES AT 0 MHA THE PROBLEM PERSISTS CONTINUOUSLY THE TEMPERATURE DRIVE TMC2660 AND 24 ° DEGREES

I ALWAYS HAVE THE SAME STEP LOSS PROBLEM AS DUEX 5 V0.8

THERMOCOUPLES REPORT 18 DEGREES LESS

I hope that now I have been clearer How I repeat all the problems I have with the V 011 I did not have before I only had the loss of the step on one type of seam and that's it now These are the main problems I find myself

droftarts

@paolozampini1973 Of course, running the external drivers on the DueX still doesn't resolve the original problem of your external drivers needing 5V signalling.

Ian

paolozampini1973

@droftarts config (17).g i mean that in DUEX 5 mode WITH DIRVER7 TMC2660 + DRIVE 8 TMC2660 OFF AXIS go on the move as soon as I turn on the electronics they instantly move very slow but they move as soon as I turn on the electronics I hope I was clear they remain still only when it is in DUEX2 mode which is a mode that I cannot use for my configuration and I repeat I did not have all these problems with the V 08 I did not have all these problems Only problem was a small loss of Step now I have all these problems as I have already listed before why

droftarts

@paolozampini1973 In DueX5 mode, the Duet 2 will be trying to communicate with the drivers, and the external drivers are picking up the signal. That is why you need to disable them by using DueX2 mode. As I said before, move the stepper motor on DueX driver 9 to the Duet 2 board. Why can't you do this?

For the other issues, please please please please post your config.g and M122.

Ian

paolozampini1973

@droftarts I have mounted the 74hc 14 but the problem has worsened on the stability and however it goes Iasi they go in motion without any command I repeat again I did not have this problem before mounting the V 011 now I have also mounted the 74hc 14 okay I have it done But it is even worse because it loses much more so after making all these changes I have made the problem worse I have not improved the problem what I say guys I agree with you but if I give him 5 times he still loses me the more I pass but I immediately lose any movement so the facts say this is not goodDM860H V3.3 act英文 (1).pdf
there is what I try to say is that by putting even more electronics even more modern even better but I have more problems because thanks

paolozampini1973

@droftarts Yes I can also teach them abitare 3 nema 17 I throw them it is not a problem but it is not normal that before with the V 08 I did not have this problem you tell me that I owe them if living is not a problem I just detach them I disassemble them from the printer but so I was still another problem So it means that then three other motors I as command and then because before I did not have all these problems and now I have this problem with the v08 I did not have these problems understand that I want to tell you please can you explain it to me. Thanks

paolozampini1973

@droftarts Please excuse me but what I want to understand if before I did not have these problems because now I have these problems with this new version I should not have any kind of problem and instead I have 4 new serious problems of the other Please explain me
That is, for me all this is a contradiction because I should not have had these problems with the V 08 I did not have these problems I had only a small loss of pace please please please try to explain to me why you tell me to go IN MODE DUEX2 Okay but why do I have to disconnect three engines that then I don't know how to drive them anymore and therefore I still have another problem I want to understand Excuse me for my very bad English

paolozampini1973

@droftarts I want to ask a question I do not know if I have explained myself you have understood that for me the problem has worsened a lot to install the V 0.11 for me it was much worse I have a lot of problems so many problems that I did not have before please answer me if I have been clear Please please

tekkydave

@paolozampini1973 Yes you are correct. But now you have two choices:

Accept that your new engine is crap and go back to the old one.
Take some advice on how to work round the issues you have and fix them to get your car working again.

You seem very reluctant to take option 2. If you read back over the advice in this thread all the answers are there. If you supply us with the information we have asked for - the output of the M122 command and your config.g we can help even more.

tekkydave

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

@droftarts I want to ask a question I do not know if I have explained myself you have understood that for me the problem has worsened a lot to install the V 0.11 for me it was much worse I have a lot of problems so many problems that I did not have before please answer me if I have been clear Please please

Yes very clear. We all understand it has got worse for you. Move on from that and give us the information we need to help you.

paolozampini1973

@tekkydave

droftarts

@paolozampini1973 You know you can just copy and paste text from the Console window?

Ian

paolozampini1973

@droftarts 21/3/2022, 14:42:59 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 (24 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 77448 of which 0 recycled
Never used RAM 13092, free system stack 184 words
Tasks: NETWORK(ready,15.8%,233) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,319) DUEX(notifyWait,0.0%,24) MAIN(running,81.5%,413) IDLE(ready,2.6%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:29 ago, cause: power up
Last software reset at 2022-03-20 12:12, reason: User, GCodes spinning, available RAM 13092, slot 0
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 24.0, current 27.5, max 27.7
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-21 14:42:57
Cache data hit count 1127564131
Slowest loop: 10.85ms; 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: ok
=== DueX ===
Read count 1, 2.04 reads/min
=== Network ===
Slowest loop: 41.04ms; 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 23760
WiFi IP address 192.168.1.5
WiFi signal strength -64dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
21/3/2022, 14:42:46 Connected to 192.168.1.5

droftarts

@paolozampini1973 Great! Now config.g.

Ian

paolozampini1973

@droftarts config (17).g

paolozampini1973

@droftarts I am sending you a photo to make you understand the axes are made up entirely with sfU 1204 and 15 mm linear guides
4 ESTRUDE .jpeg

droftarts

@paolozampini1973 There are a lot of errors in you config.g. Just to start...

; Drives
M569 P0 S0 R-1 ;T2.5:2.5:6:5                       ; X    physical drive 0 goes forwards
M569 P1 S1 R-1 ;T2.5:2.5:6:5                       ; Y    physical drive 1 goes forwards
M569 P2 S1 R1 T5:5:5:5                             ; Z    physical drive 2 goes forwards
M569 P3 S0                                         ; E0   physical drive 3 goes forwards
M569 P4 S0                                         ; E1   physical drive 4 goes forwards
M569 P5 S0                                         ; E2   physical drive 5 goes forwards
M569 P6 S0                                         ; E3   physical drive 6 goes forwards
M569 P7 S0 R1 T2:2:2:5                         ; E4 X physical drive 7 goes forwards
M569 P8 S1 R1 T2:2:2:5                         ; E5 Y physical drive 8 goes forwards
M569 P9 S1 R1 T5:5:5:5                             ; E6 Z physical drive 9 goes forwards
M584 X7 Y8 Z2:9 E3:4:5:6:7:8:9 S0                  ; set drive mapping

Don't set timings for internal TMC drivers. (M569 P2 S1 R1 T5:5:5:5)
Your timings for the external drivers are very short.
Your M584 should not have the X, Y and Z2 drivers mapped to E. S0 is not needed. Change to:

M584 X7 Y8 Z2:9 E3:4:5:6

For M350, M92, M566, M203, M201 and M906 commands, make sure E has 4 parameters, eg

M350 X16 Y16 Z16 E16:16:16:16 I1

Ian