Posts made by Spodeopieter

@briskspirit @dc42 @deckingman Thanks for helping me out !

Yes , but then each would be a independent extruder axis , I need them to function as one , I have the two extruders inline , they both push the same piece of filament (I need to have very high extrusion force) .

I need Drives 3 and 4 to function together as an E-axis , but with different steps per mm , because I have two different extruders.

I can probably do it with a g code parser , but this would not be ideal.

I want to drive one extruder axis from the integrated E0 and E1 drivers , but with different steps per mm for the two drivers, because I have different motors driving the same axis , inline extruders on the same piece of filament.

configuration with M92 and M584 does not seem to be able to do this.

How can I make this work, do you have any ideas/suggestions ?

Can I bind one axis to another axis so they move the same amount of units ?

@dc42 said in No communication after erase button pressed:

cept that you have tried multiple PCs. Have you measured the voltage on the +3.3V rail? Is any of the chips or the WiFi module on the Duet getting hot?

3.3 v rail seems good , the SAM chip is getting a little hot , around 40 degrees , the esp is ice cold.

Just another thing I noticed , if I press the erase or reset button , nothing happens , no flashing of any LED's

@dc42

Reliable shipping to USA and back would cost me quite a bit of money. Buying a new one would be a better bet for me.

I would really like to give the JTAG reflash a go.

What programmer do you use for flashing over JTAG ? and can you provide me with a wiring diagram ? Also , what binary should I flash ?

Can you assist me with a jtag reflash ?

@dc42

I am in South Africa , Pretoria

@dc42

So what are the next steps ?

@denke

Ok , so I just tried this , still no luck. I also tried running through usb isolator.

@dc42

Noted. I have been trying without the SD card anyway, so what is the next step ?

@denke

Dmesg

[846482.444916] usb 3-6: new full-speed USB device number 33 using xhci_hcd
[846482.556934] usb 3-6: device descriptor read/64, error -71
[846482.772945] usb 3-6: device descriptor read/64, error -71
[846482.988898] usb 3-6: new full-speed USB device number 34 using xhci_hcd
[846483.100971] usb 3-6: device descriptor read/64, error -71
[846483.316940] usb 3-6: device descriptor read/64, error -71
[846483.532862] usb 3-6: new full-speed USB device number 35 using xhci_hcd
[846483.533051] usb 3-6: Device not responding to setup address.
[846483.736958] usb 3-6: Device not responding to setup address.
[846483.940851] usb 3-6: device not accepting address 35, error -71
[846484.052817] usb 3-6: new full-speed USB device number 36 using xhci_hcd
[846484.053010] usb 3-6: Device not responding to setup address.
[846484.257021] usb 3-6: Device not responding to setup address.
[846484.460791] usb 3-6: device not accepting address 36, error -71
[846484.460831] usb usb3-port6: unable to enumerate USB device
[846508.071353] usb 3-6: new full-speed USB device number 37 using xhci_hcd
[846508.183413] usb 3-6: device descriptor read/64, error -71
[846508.399383] usb 3-6: device descriptor read/64, error -71
[846508.615249] usb 3-6: new full-speed USB device number 38 using xhci_hcd
[846508.727321] usb 3-6: device descriptor read/64, error -71
[846508.943313] usb 3-6: device descriptor read/64, error -71
[846509.159258] usb 3-6: new full-speed USB device number 39 using xhci_hcd
[846509.159404] usb 3-6: Device not responding to setup address.
[846509.363394] usb 3-6: Device not responding to setup address.
[846509.567269] usb 3-6: device not accepting address 39, error -71
[846509.679246] usb 3-6: new full-speed USB device number 40 using xhci_hcd
[846509.679451] usb 3-6: Device not responding to setup address.
[846509.883424] usb 3-6: Device not responding to setup address.
[846510.087244] usb 3-6: device not accepting address 40, error -71
[846510.087315] usb usb3-port6: unable to enumerate USB device

lsusb

Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 04ca:7022 Lite-On Technology Corp.
Bus 003 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader
Bus 003 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 012: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
Bus 003 Device 006: ID 0e8d:763e MediaTek Inc. MT7630e Bluetooth Adapter
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

@dc42

Yes , I have tried a few different cables.

Should I have the sd card inserted or not ?

@dc42

Both of those are true. What does this mean happened ?

My duet is no longer under warranty.

I would be quite disappointed and angry if I should buy a new one.

@dc42
yes , I have tried this , it makes no difference.

@dc42
Also I have tried the usb ports of ,multiple windows 10 PC's , all with the same issue.
Also tried a Linux pc , no luck.
Should I try a windows 7 pc perhaps?

Perhaps reflash over jtag would be an option ?

@dc42

I am running the board without anything connected to it.

Hello ,

I have accidentally pressed the erase button on my duet3dwifi , It was working fine beforehand.

I am trying to reinstall the firmware with SAM-BA , but I am not getting the device to show up as anything else than unknown usb device , have tried multiple cables and pc's.

I have tried installing drivers from duet and from microchip, but I am still getting unknow device , will attach screenshots.