hello,
We bought an original hands-free device from Siemens on eBay for 10€.
There's now an Atmel microcontroller inside.
It's attached to an S25.
Due to the 'red phonebook,' only calls from numbers listed in the 'red phonebook' will be accepted.
By using a small configuration trick on the S25, all signals are effectively ignored, except for calls from numbers listed in the red phonebook.
SMS or other messaging services are not working.
so that you don't have to open the S25.
Let's record the speaker signal that is present on the connector for the hands-free system.
The signal is small, but with the internal AD converter in the Atmel microcontroller, it's possible to 'analyze' the ringing. To prevent it from reacting to interference pulses, the program includes a software-based integration over a specific time (100ms).
To enable the speaker signal to be transmitted over the line, PIN8 must be connected to ground.
That's what the ATM does.
The hands-free device also has a charger built in, which we can use.
It only charges while the ignition is on. Based on experience, this is sufficient to keep the battery almost fully charged.
Unfortunately, the S25 only supports one function at a time: either battery charging (pin 8 is not connected) or hands-free calling (pin 8 is connected to ground).
When the ignition is turned on, the Atmel microcontroller handles the switch from FSP (Field Stop Power) to charging mode. This is because a few seconds must pass between disabling FSP and enabling charging; otherwise, the phone's charging status may not be recognized correctly.
It also has the advantage that you can't turn it on via your phone when the ignition is on. It would be pointless anyway if you were already in the car.
The first version used DIP switches, allowing the time to be programmed in increments of 1 to 128 minutes. Unfortunately, it had a disadvantage: there was no function check and no monitoring of the remaining runtime.
The original clock, which was also connected via the Atmel microcontroller, takes precedence.
To turn off the instant heating function that was activated via the mobile app before the timer runs out, you only need to press the 'instant heating' button and then turn it off again.
[img][/img]
it basically worked well for a few days

.
until the new version came out
Since a functional check is beneficial, and the remaining lifespan is also of interest.
The idea came to mind that a display was needed.
But it's a shame to use a display when you already have one.
idea
1. Remove the Webasto clock and use the additional display for all functions.
2. Take the Webasto clock and display all information on it.
thought, done.
'I opened the clock, connected the buttons (+, -, heat) with 3 wires, and also connected them to the microcontroller (Atmel) via an RCR (debouncing and short-circuit protection) circuit.'
the result:
If you call, the system will 'press' the 'heating' button and magically turn on the heating.
'And so that you can also adjust the time, after pressing the 'heat' button, press the '+' or '-' button until the desired time is reached.'
Without feedback, meaning that for 25 minutes, the device presses the '-' button 5 times, and for 40 minutes, it presses the '+' button 10 times.
To prevent any false readings, debouncing has been implemented to ensure the sensor doesn't miss any data.
and as if by magic, the desired time is set when you make the call

.
And since everything is so neatly integrated and hidden, it's not very convenient to adjust the timing using the dip switches, so there's another great feature.
While the 'heating' button is pressed on the clock and a call is being made simultaneously (which only works if you're using a mobile phone while in the car), the thermostat enters 'programming mode.'
Now, you can use the '+' or '-' buttons to adjust the duration.
When you release the 'heat' button, the 30-minute timer appears. If you then set it to 35, ...
Then, the microcontroller recognizes that the '+' button has been pressed 5 times and stores this information for the configured time when the device is turned on via the mobile phone.
If no button is pressed for longer than 10 seconds, the programming mode will be deactivated and the device will switch to normal operation.
If you call now, the time will magically be reset to 35 minutes.
It's working perfectly so far.
Power-on check and remaining runtime display via the webasto control unit.
It doesn't even have the original Webasto remote control (or at least, I think it doesn't).
It is also possible to 're-schedule' the heating. If you call while the heating is already running, whether it's controlled by a timer or a mobile app, the pre-programmed time will be set.
It's simple: when the clock is on (and connected to the ATmega microcontroller), the ATmega briefly turns the clock off and then back on, allowing it to reset the clock to the defined 30-minute interval and ensuring the time is correctly set by the ATmega.
It works because, during the program's execution, the microcontroller can switch the pins between input and output modes as needed.
'It's all in the original FSP housing, so it comes with nice connectors for wiring.'
The quiescent current with the ignition off is approximately 5 to 8 mA, which is a very low and acceptable value.

[img]
[/img][img]
The clock has now been moved to a better location, so please don't complain. [/img]

[img]
greetings[/img]http://pics.m-eit.de/webasto/handyFB1.JPG{MARKER}http://pics.m-eit.de/webasto/handyFB2.JPG{MARKER}http://pics.m-eit.de/webasto/handyFB3.JPG{MARKER}http://pics.m-eit.de/webasto/handyFB4.JPG{MARKER}