PanelDue extend the wire

[wilriker]

@FBG I use a cable about 2m long. Nothing fancy. 4x0.34mm², no shield, no pairs twisting (apart from the four wires slowly twisting in the outer sheath), run it at 115200 baud and except once I never saw any communication problems.

Can you be a bit more precise on the errors you see? Also what's the resistance of your wires?

[FBG]

@Phaedrux I use a wire shielded twisted pair but the problem happen...

@wilriker If i choose 115200, the PanelDue not show me the files that there are inside the SDCard of Duet...
My wire is 4x0.25-> https://www.igus.com/product/?artnr=CF240-02-04
Maximum conductor resistance at 20 °C (following DIN EN 50289-1-2)-> 79 [Ω/km]

Errors not always is the same. One of them is:
Error: M409: control character in string

Best Regards

[wilriker]

@FBG of course you need to adjust your M575 command accordingly if you switch to another baud rate - otherwise there is no more communication possible at all.

The control character error indeed looks like a communication issue. Can you try another cable? Maybe check your crimps. If possible measure the resistance yourself end to end (including crimp pins). You could also try to further lower the baud rate.

[FBG]

@wilriker yes yes, always i change the baud in the config.g

[Phaedrux]

@FBG Just to be clear the baud rate in the config.g must match the baud rate set on the paneldue setup page.

[FBG]

@Phaedrux yes yes sure, and after reboot

[Phaedrux]

Can you show how you have your shielded cable connected and routed? Where is the shield grounded?

[FBG]

@Phaedrux Attach a photo of the shield.
Tested again with 115200 and SD card not show, and the error messages show.

Is aleatory, now:
Error: Bad command: M[]09 F"d99f"
Error: M4: Command is not supported in machine mode FFF

[Veti]

@FBG

instead of increasing the speed go with a lower than 57k baud rate

[FBG]

@Veti Yes Veti, i tested all baudrates, with another baud rates the SD CARD work, but the error message, always happen

[Veti]

you never wrote what the length of your wire is.

also check what wires that wires crosses or runs next to.

also which version is installed on the paneldue and which version of the duet firmware are you running?

[FBG]

@Veti PanelDue 7i version3.2.0, Duet2Ethernet with 3.1.1
Wire long around 3meters

[Veti]

@FBG said in PanelDue extend the wire:

Wire long around 3meters

from the documentation

There have been reports of cables up to 1500mm long being successfully used.

so you are double the longest possible length

[dc42]

A 3m cable should work as long as the conductors are not too thin.

[FBG]

@dc42 I will test with 1mm wire, the actual is only 0.25mm

[dc42]

@FBG, the maximum recommended resistance per conductor is 0.1 ohms. However, lower than that may allow higher baud rates.

[FBG]

@dc42 My actual wire say: Max conductor resistance 79 ohms/km

The new wire 1mm say: Max conductor resistance 19.5 ohms/km

What do you think?

[dc42]

@FBG said in PanelDue extend the wire:

@dc42 My actual wire say: Max conductor resistance 79 ohms/km

The new wire 1mm say: Max conductor resistance 19.5 ohms/km

What do you think?

0.079 ohms/m * 3 is about 0.24 ohms, well above the recommended 0.1 ohms maximum. The new wire will be about 0.06 ohms, so well within range.

[wilriker]

@FBG said in PanelDue extend the wire:

@Veti PanelDue 7i version3.2.0, Duet2Ethernet with 3.1.1

Note that PanelDueFirmware 3.2 will have some minor issues with RepRapFirmware below 3.2. You are using RRF 3.1.1. The expected issues do NOT contain the "Bad command" errors you posted (these are actually more related to your wiring) but once you have sorted them you will still possibly encounter some issues like slower update rates.

[FBG]

@wilriker @Veti @dc42
Now testing in 1.24PanelDue and 3.1.1Duet2Ethernet.
Same errors.

With wire 1mm and 0.06 is worse, only show temperature one time and is as no update nothing...

I am desperate, i don't know that do...