Ingo said:
i setup the CA with Km and after reboot it is Mi again
yes on every boot
I can't duplicate this, but I'll investigate further.
Ingo said:
no error indicators - Th-in is ok
Do you get the 'Amps Limiting' flag?
I think the problem may be that your Digital Aux is running the current limiting down to Level 1 (0 Amps) - see the next section.
Start by turning off both analog and digital Aux features to get the CA basically running.
Ingo said:
i built it myself = with "tips" i mean buttons... sorry
no buttons = 1,46V - 4,99V Pot/voltage
left button = 0,76V
right button = 0v
You didn't say what firmware you were running before b21, but from the voltages it looks like the problem is that your DIY buttons are using regular diodes. Unfortunately, There was a design change and the conventional diodes were replaced with Schottky diodes. This means that your unit is not producing the proper voltages and so the CA is confused. There are two ways to fix this: one is to rebuild your unit with Schottkys (e.g. 1N5711) and the second is to get a DigiAux board or a whole unit from Grin. This all happened quite a while back and so I can't speak to the present state of free stuff, but Justin was mailing out free boards to DIYers who got zinged by this design change. You could just hook up some wires to your buttons and everything worked. Justin can also tell you about the latest circuit resistor values - There was a minor change as I recollect.
I can't find the post about that stuff just now but here's the one about the Schottky change and a possible substitute diode part if you want to DIY.
https://endless-sphere.com/forums/viewtopic.php?f=4&t=37964&start=3525#p1262509
email Justin at Grin if you want to pursue getting a board or button unit.
Anyhow, it looks like one or more issues relate to an outdated DigiAux Button assembly.
Ingo said:
next problem i noticed just now : i can read the setup with my computer but cannot write it.... CA showes me PC Connection...
Setup Utility showes me : cannot connect to CA.. etc.
I don't know about this one. Since it was working and now is not, it sounds like you have a hung com port. I know it sounds like the usual idiot-level solution, but rebooting is really the easiest way to clear up these serial com driver issues.