DUEX 5 V0.8 TO DUEX 5 V0.11

tekkydave

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

@tekkydave DRIVER 5 + DRIVER 6 in DUEX mode 2 they do not work they are disabled understood This is a test that I have already done they do not work only 7 8 and 9 works I think you don't know this thing you've never tried But they don't work

Correct - I haven't tried it. I only have a duex2 in my printer as I only have one extruder and 3 Z motors plus X & Y. I am simply repeating the information that others have already given days ago. Good luck solving your issues. Now I am convinced this thread is a Turing Test

paolozampini1973

@tekkydave Please Unfortunately, this version has problems that in the design phase it can happen that one does not notice it But in fact I now take down the 0:11 you were Monterò from 08 However I do not recommend to buy the 011 Until proven otherwise it is that I now have 6 problems including 4 are very serious

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
5)and then I have the problem that in two ex 5 it gives Short Circuit error only in DUEX 5 mode
Vorrei lasciare V 011 ma la Y x si muove senza dargli il comando quindi è inutile parlare di altri problemi c'è da risolvere il primo Questo è il problema Va bene aspetterò quando ti libererai lo farò pubblica il file di configurazione grazie

21/3/2022, 15:38:13 Errore: cortocircuito verso terra segnalato dai conducenti 7 8
Errore: spegnimento per sovratemperatura segnalato dai conducenti 7 8
21/3/2022, 15:38:08 Errore: cortocircuito verso terra segnalato dai conducenti 7 8
Errore: spegnimento per sovratemperatura segnalato dai conducenti 7 8
21/3/2022, 15:38:04 Errore: cortocircuito verso terra segnalato dal conducente( s) 7 8
Errore: spegnimento per sovratemperatura segnalato dai conducenti 7 8
21/3/2022, 15:37:59 Errore: cortocircuito verso terra segnalato dai conducenti 7 8
Errore: spegnimento per sovratemperatura segnalato da driver(i) 7 8
21/3/2022, 15:37:55 Errore: cortocircuito verso terra segnalato dal conducente(i) 7 8
Errore: spegnimento per sovratemperatura segnalato dal conducente(i) 7 8
21/3/2022 , 15:37:50 Errore: cortocircuito verso terra segnalato dai conducenti 7 8
Errore: spegnimento per sovratemperatura segnalato dai driver 7 8
21/3/2022, 15:37:49 M122
=== Diagnostica ===
RepRapFirmware per Duet 2 WiFi/Ethernet versione 3.3 (2021-06-15 21:44 :54) in esecuzione su Duet WiFi 1.02 o successivo +
ID scheda DueX5: 0JD0M-9P6M2-NW4SN-6J1DD-3SJ6K-KAURK
Buffer di uscita utilizzati: 3 di 24 (20 max)
=== RTOS ===
Ram statico: 23876
Ram dinamico : 77448 di cui 0 riciclato
Mai usato RAM 13092, stack di sistema libero 184 parole
Attività: NETWORK(ready,10.4%,231) HEAT(delaying,0.1%,330) Move(notifyWait,0.1%,319) DUEX(notifyWait,0.0 %,24) MAIN(in esecuzione,86.5%,411) IDLE(ready,3.0%,29), totale 100.0%
Mutex di proprietà:
=== Piattaforma ===
Ultimo ripristino 00:00:25 fa, causa: software
Ultimo ripristino del software alle 15:37 del 21-03-2022, motivo: utente, rotazione di GCodes, RAM disponibile 13092, slot 1
Codice di ripristino del software 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/MAIN status Freestk:
Error 0x00
Errori Aux0 0,0,0
Intervallo max timer passo 0
Temperatura MCU: min 29.3, corrente 30.0, max 30.3
Tensione di alimentazione: min 25.6, corrente 25.7, max 25.8, eventi di sottotensione: 0, eventi di sovratensione: 0, alimentazione buona : si
Heap OK, gestisce allocata/usata 0/0, memoria heap allocata/usata/riciclabile 0/0/0, cicli gc 0
Driver 0: posizione 0, fermo, SG min/max non disponibile
Driver 1: posizione 0, fermo , SG min/max non disponibile
Pilota 2: posizione 0, fermo, SG min/max non disponibile
Pilota 3: posizione 0, fermo, SG min/max non disponibile
Pilota 4: posizione 0, fermo, SG min/max non disponibile
Pilota 5: posizione 0, fermo, SG min/max non disponibile
Driver 6: posizione 0, fermo, SG min/max non disponibile
Driver 7: posizione 0, spegnimento temperatura! corto a terra, fermo, SG min/max non disponibile
Driver 8: posizione 0, spegnimento della temperatura! da corto a terra, fermo, SG min/max non disponibile
Pilota 9: posizione 0, fermo, SG min/max non disponibile
Pilota 10: posizione 0
Pilota 11: posizione 0
Data/ora: 21-03-2022 15:37 :49
Conteggio hit dati cache 981081507
Ciclo più lento: 6,48 ms; più veloce: 0,19 ms Errori
I2C nak 0, timeout di invio 0, timeout di ricezione 0, finishTimeouts 0, reset 0
=== Archiviazione ===
Voci file libere: 10
SD card 0 rilevate, velocità interfaccia: 20,0 MBytes/sec
SD card letta più lunga tempo 1,0 ms, tempo di scrittura 0,0 ms, numero massimo di tentativi 0
=== Sposta ===
DM creati 83, maxWait 0 ms, compensazione letto in uso: nessuno, offset comp 0,000
=== MainDDARing === Movimenti
pianificati 0, movimenti completati 0 , singhiozzo 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], stato CDDA -1
=== AuxDDARing === Mosse
pianificate 0, mosse completate 0, singhiozzo 0, stepErrors 0, LaErrors 0, Underruns [0 , 0, 0], stato CDDA -1
=== Calore ===
Riscaldatori letto = 0 -1 -1 -1, riscaldatori a camera = -1 -1 -1 -1
Riscaldatore 1 acceso, I-accum = 0.0
=== GCodes ===
Segmenti rimasti: 0
Blocco movimento mantenuto da null
HTTP è inattivo in stato(i) 0
Telnet è inattivo in stato(i) 0
Il file è inattivo in stato(i) 0
USB è inattivo in stato(i) 0
Aux è inattivo in stato(i) 0
Trigger è inattivo in stato(i) 0
La coda è inattiva nello stato(i) 0 Il
display LCD è inattivo nello stato(i) 0
Daemon è inattivo nello stato(i) 0
La pausa automatica è inattiva nello stato(i) 0 La
coda del codice è vuota.
=== Sensori filamento ===
Sensore estrusore 0: nessun filamento
Sensore estrusore 1: ok
Sensore estrusore 2: nessun filamento
Sensore estrusore 3: ok
=== DueX ===
Conteggio letture 1, 2,36 letture/min
=== Rete ===
Ciclo più lento: 39,88 ms; più veloce: 0,00 ms
Stati del risponditore: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessioni Sessioni
HTTP: 1 di 8

WiFi -
Lo stato della rete è attivo
Il modulo WiFi è connesso al punto di accesso
Messaggi di errore: in sospeso 0, non pronto 0, noresp 0
Versione firmware WiFi 1.26
Indirizzo MAC WiFi 40:f5:20:0d:6b:49
WiFi Vcc 3.37, motivo ripristino Attivato per processore principale
Dimensioni flash Wi-Fi 4194304, heap libero 20888
Indirizzo IP Wi-Fi 192.168.1.5
Potenza segnale Wi-Fi -64dBm, modalità 802.11n, riconnessioni 0, modalità sospensione modem
Registro orologio 00002002
Stati socket: 0 4 0 0 0 0 0 0
21/3 /2022, 15:37:46 Errore: cortocircuito verso terra segnalato dai conducenti 7 8
Errore: spegnimento per sovratemperatura segnalato dai conducenti 7 8
21/3/2022, 15:37:41 Errore: cortocircuito -a terra segnalato dal/dai conducente/i 7 8
Errore: spegnimento per sovratemperatura segnalato dai driver 7 8
21/3/2022, 15:37:39 Connesso a 192.168.1.5config (18).g

paolozampini1973

@dc42 I would like to know why you cannot pay attention to my problem it is a curiosity Thanks At least after one I will disturb more I have written to you many times

paolozampini1973

@dc42 she lets me think about this by not answering I have a problem that technically in my experience is very serious in my opinion and she is aware of it

paolozampini1973

@dc42 I want to thank you for all the attention you gave me even if you didn't even spend 10 seconds on more important things.

paolozampini1973

@droftarts please when you have some time we can clarify there is a software problem or a hardware problem At least this otherwise I want to return it honestly it only created problems for you too I tried to contact @ dc42 several times but I have not received no reply I don't know why thank you you are very kind

paolozampini1973

@engikeneer I WANTED TO THANK YOU FOR THE DEDICATED TIME

paolozampini1973

@dc42 so it is the confirmation that you are not interested in the problems of version 0.11 because you have not paid attention you have serious problems that v 0.11 has good

paolozampini1973

Hello everyone So I'll explain the problem of the card The problem is that the card is that the drivers are not correctly disconnected This is why it gives the error and whoever designed it does not seem to care about the very serious design problem v0 11 would be to remove it from the market from the sale it goes complements magazine and from how I have seen no one has been able to give an answer because it gives short circuit errors But I must admit that giving solutions to get around the problem are all good but the real solution I have not seen this great skill Today I take apart the card and throw it away because for me personally it has created serious problems and I see that whoever designed it is a big manager if he was a responsible person he would have questioned us he would have talked about it would have understood he would have made himself heard anyway I want to thank those people who gave you a less decent answer but those people who try to get around the problem don't work that way guys get around the problem doesn't work Go you have to solve the problem you have to understand where the problem is I'm used to it so for many maybe they do it as a pastime as a game.

droftarts

@paolozampini1973 I have some time this afternoon to help you. However, I need you to answer my questions, test things as I ask you to, and please no long arguments and saying again and again "there's a problem!". If I can get the information I need, we can work out where the problem is. Okay?

Ian

paolozampini1973

@droftarts yes yes Thank you for your time with me

paolozampini1973

@droftarts So what I would like to ask you I want to reassemble the v 0.8 and solve the problems with the v0.8 version because I repeat the only problem that I had a small loss of step and that's it I didn't have any kind of problem except to make some very small optimizations the rest worked everything is fine for you if you start reassembling v0.8 ?

droftarts

@paolozampini1973 I'd like to work out if there is a hardware problem with your V0.11 board. If there is, it can be replaced or refunded. Disabling the drivers through hardware on the V0.11 board is a better way of controlling the external drivers, which you can not do on the V0.8 board.

Ian

paolozampini1973

@droftarts Yes it's fine ok I was saying for you because I didn't want to take advantage of your time for me it's fine thanks

droftarts

@droftarts 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 it connected to an external driver as well?
Is there any reason you cannot connect Z2 motor to driver 0 or 1 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.

Try to keep your answers short and accurate!

Ian

paolozampini1973

@droftarts 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

paolozampini1973

@droftarts I have sent you my configuration I hope it is clear that I was able to explain if there is something that I have not been clear Please tell me thanks

droftarts

@paolozampini1973 Please answer the questions. I can't help you if you don't answer the questions.

Ian

droftarts

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

Z is configured with two INDEPENDENT motors FOR SELF-LEVELING one on Driver 1 = Z one on the driver 9 = Z

This is incorrect. Your config.g shows the first Z motor on driver 2.

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

Ian