I'll try here. There is still no solution for the double controller with the same function?

@DIY-O-Sphere excellent solution. Thanks.

After rewiring all components, I have an interesting problem, which opens up after triggering the G32 6 times. Before that, the difference became smaller and smaller. Now the distance of the real axis increases to the unbearable.

Any hints here?

@chrishamm @deckmann,

I thank you very much for this great hint.

@deckingman

Yes exactly, here I call up filament-specific settings. But after a restart the filament is still set to e.g. PETG but the settings are not loaded.
So I ask if it is possible to automatically load the config file of the correspondingly loaded filament when starting?

Filament config.g

Is there a way to use the preloaded filament, e.g. PETG loaded with load.g, which will run the appropriate config.g on next reboot. So that the filament settings for the loaded filament are also present again, e.g. M572 or similar?

@norder

Tja, dass mit der Falschlieferung ist mir auch passiert. Das machne die Chinamänner wohl gerne.
Der Ausbau mit dem Flachbandkabel und dem Sub-9 Stecker, wie du hier zeigst, habe genauso gemacht!
Tja, wenn ich der 1. Lauf starte klapp es oftmals und ich kann Daten sammeln. In den späteren versuchen
kommt dann der "HeatTaskStuck"-Fehler.

Ich finde es recht witzig, dass es erst geht und später nicht mehr. Bist du der Meinung, das es mit einem USB-Kabel getan ist?

Viele Grüße

Sebastian

@chrishamm Hello Christian, thx for your tip to reinstall IS after upgrade to 3.4.1.. Its working.
But the movementinterruption still exist. Going to collect data, set up the movement 1x(0 to130);2x(-130 to 130);3y(-130 to 130); 4y(-130 to 0). I didn´t knew if it a bit to much. Someting it ending with data to analyse , sometime not. The config is a Delta with Dia 340mm. The messurement is a LIS3DSH or a LIS3DH. what you want.