Changes since 1.22: 

1. IR Mini operation mode bug fix:
   Resolved an issue concerning the default settings for the IR Mini where connecting the IR Mini and then starting the CarManager would set the operation mode back to analogue mode. This bug only affected the CarManager version 1.22. 
2. Inductive Charger DCC address:
   The Inductive Charger does not have a DCC address configured by default, but it was erroneously shown as address 1 in the CarManager. 
3. Inductive Charger vehicle status:
   If the vehicle was fully charged and switched to idle mode, sometimes it could still be shown in the CarManager as charging instead of idle.

This version is only recommended for older operating systems on which the x64 version does not start. Please only use the x64 version if possible! 

Some functions of the x64 version are not available in this x86 version! Unpacking the archive is mandatory before running the application!

Publication date: 28.03.2025

Note: To open an app from an unverified developer, hold down the "ctrl" key and click on the app icon and select "Open" from the context menu. 

Fixed an error when updating the InductivCharger and IR Mini.
For changes to version 1.22, see CarManager 1.24 (Windows x64).

1. Macro distance limit bug fix
   If a macro was triggered by the Inductive Charger, the distance limit set in the vehicle was ignored. 
2. Saving settings before an update:
   The settings are permanently saved only when the vehicle is switched off or disconnected from the CarManager. However, this caused any settings made immediately before an update to be lost after the update. Now, the settings are also saved to permanent storage before an update.
3. Smoother departure from the Inductive Charger
   In cases of a less-than-ideal connection between the vehicle and the charger, the vehicle could sometimes brake or even stop shortly after starting to drive away. This could happen when the vehicle was not properly centered, the charger was not precisely installed, it was placed in a curve, or the road surface was not optimal in thickness. Now, the vehicle's departure is smoother and more reliable even in such cases. 
4. Smoother stop on the Inductive Charger at low speeds
   If the vehicle arrives at the Inductive Charger at a speed of 10 km/h or lower, it will now slow down more smoothly. Previously, the vehicle appeared to stop twice: once when it began searching for the stopping position and again at the final stop.

Publication date: 21.03.2025

1. Bug fix for switching vehicle off when fully charged
   Powering the vehicle off did not work when the vehicle was fully charged and in idle mode. 
2. Better handling of vehicles in case of poor connection:
   In cases of a less-than-ideal connection between the vehicle and the charger, a warning about the vehicle having outdated firmware was sometimes displayed, even though the firmware was up to date. In these cases, the maximum charging time was sometimes not respected, and the vehicle's departure was hindered because the connection was continuously lost and re-established. This could occur when the vehicle was not properly centered, the charger was not precisely installed, it was placed in a curve, or the road surface thickness was not optimal. Now, communication with vehicles is more stable in such situations. 
3. More reliable saving of operational data in case of a weak power supply
   The device saves the operation mode and other temporary data when it detects a loss of power and restores them at the next startup. However, with a very weak power supply (15 VA or less), it could occasionally happen that this save was corrupted. The most visible effect was that the last operation mode was not restored, and the warning for conflicting vehicles appeared, even if no inputs were configured as sensors.
   Now, the saving of operational data functions correctly regardless of the power supply’s output. However, we still recommend using a sufficiently powerful power supply. 
4. Better collision avoidance for the serial charging station
   When multiple chargers were linked into a serial charging station, and the distance between the chargers was large, a collision could occur under certain conditions. If two vehicles arrived driving too close to each other, and the second vehicle stopped at its charger sooner than the first vehicle, it could happen that after the first vehicle stopped, the second one incorrectly started moving, causing a collision.
   A charger in a serial charging station can track a vehicle that has left it until the next charger in the row reports that the vehicle has arrived. This was always the case, but previous versions could make an error in this calculation when multiple vehicles were involved, depending on the order in which they arrived. This issue has now been fixed.
   There is a setting (currently only available under "Direct configuration") where a time limit can be set for how many seconds a vehicle is tracked. This can be adjusted in CV38. A value of zero means there is no time limit. When a vehicle leaves a charger in the serial charging station, this charger still reports itself as occupied to the charger behind it to avoid collisions in cases where multiple vehicles arrive close to each other. This status remains until either the set time runs out or the next charger in the row reports the arrival of the vehicle.