Skip to main content Skip to search Skip to main navigation
Menu

Software / Firmware Archiv

Configuration software archive from version 1.26
  • CarManager Setup 1.26 (Windows x64)
    CarManager Setup 1.26 (Windows x64) (Binary file, 26.39 MB)

    Publication date: 29.08.2025

    Changes since 1.24: 

    1. Support for new features introduced in recent updates: 

    • Sounds for vehicles (requires vehicle firmware 1.44 or newer) 
    • Custom event based on vehicle filters (requires inductive charger firmware 1.10 or newer) 
    • Sound commands for IR Mini (does not require an IR Mini update) 

    2. Reorganized macro editor for vehicles. 

    Now the commands which can have temporary duration (based on time or distance limits) are grouped together with the end conditions, for better understanding. 

    3. Uploading a backup from older versions no longer resets settings that did not exist in the old backup.

  • CarManager Setup 1.26 (Windows x86)
    CarManager Setup 1.26 (Windows x86) (Binary file, 28.5 MB)

    Publication date: 29.08.2025

    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!

  • CarManager 1.26 (MacOS version 11 or higher, Big Sur)
    CarManager 1.26 (MacOS version 11 or higher, Big Sur) (Binary file, 50.89 MB)

    Publication date: 29.08.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.24, see CarManager 1.26 (Windows x64).

Configuration software archive
  • CarManager 1.00 x64.exe
    CarManager 1.00 x64.exe (Binary file, 24.4 MB)
  • CarManager 1.00 x86.zip
    CarManager 1.00 x86.zip (Binary file, 26.26 MB)
  • CarManager 1.04 x64.exe
    CarManager 1.04 x64.exe (Binary file, 24.41 MB)
  • CarManager 1.04 x86t.zip
    CarManager 1.04 x86t.zip (Binary file, 26.27 MB)
  • CarManager Setup 1.22 (Windows x64)
    CarManager Setup 1.22 (Windows x64) (Binary file, 25.7 MB)

    Changes since 1.10: 

    1. New Inductive Charger Support:
      Added support for the new inductive charger, featuring a completely redesigned user interface for settings and function descriptions.
    2. IR Controller Bug Fix:
      Resolved an issue in the user interface for the IR Mini where some numerical fields could become hidden under specific conditions (disconnecting the IR Mini, connecting a vehicle, and reconnecting the IR Mini). This was a visual issue only and did not impact functionality. 
    3. Improved Update Process:
      Enhanced the robustness of the update process with additional error handling to address potential issues caused by poor connection quality. 
    4. New Roof Beacon Option:
      Introduced a new continuous light option for vehicle roof beacons. This feature requires vehicle firmware version 1.40 or newer.

    Improved Update Stability 

    We’ve identified and resolved a rare issue in the CarManager that could occur during updates over USB. Previously, if the program experienced significant lag (caused by an older, slower computer or interference from other programs like antivirus software) it could lead to lost or damaged data packets. While our system is designed to handle and correct these errors, in very rare cases, an uncorrected packet could result in update failure. With the latest version of the CarManager, we’ve introduced robust improvements to handle lag more effectively, ensuring data packets are no longer lost or damaged. This enhancement eliminates the risk of update failures caused by this issue.

  • CarManager Setup 1.22 (Windows x86)
    CarManager Setup 1.22 (Windows x86) (Binary file, 27.91 MB)

    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!

  • CarManager Setup 1.24 (Windows x64)
    CarManager Setup 1.24 (Windows x64) (Binary file, 25.72 MB)

    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.
  • CarManager Setup 1.24 (Windows x86)
    CarManager Setup 1.24 (Windows x86) (Binary file, 27.98 MB)

    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!

  • CarManager 1.25 (MacOS version 11 or higher, Big Sur)
    CarManager 1.25 (MacOS version 11 or higher, Big Sur) (Binary file, 49.72 MB)

    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).

  • CarManager 1.26 x64.exe
    CarManager 1.26 x64.exe (Binary file, 26.39 MB)
  • CarManager 1.26 x86.zip
    CarManager 1.26 x86.zip (Binary file, 28.5 MB)
  • CarManager 1.26.dmg
    CarManager 1.26.dmg (Binary file, 50.89 MB)
  • CarManager Mac 1.00.dmg
    CarManager Mac 1.00.dmg (Binary file, 16.01 MB)
  • CarManager Mac 1.04.dmg
    CarManager Mac 1.04.dmg (Binary file, 45.72 MB)
  • CarManager 1.22 (MacOS version 11 or higher, Big Sur)
    CarManager 1.22 (MacOS version 11 or higher, Big Sur) (Binary file, 49.12 MB)

    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. 

    For changes to version 1.10, see CarManager 1.22 (Windows x64).

  • CarManager 1.24 (MacOS version 11 or higher, Big Sur)
    CarManager 1.24 (MacOS version 11 or higher, Big Sur) (Binary file, 49.07 MB)

    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. 

    For changes to version 1.22, see CarManager 1.24 (Windows x64).

Updates for firmware archive
  • IR Mini Firmware-Version 1.04
    IR Mini Firmware-Version 1.04 (Binary file, 0.01 MB)
  • InduktivCharger firmware V1.08
    InduktivCharger firmware V1.08 (Binary file, 0.02 MB)

    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.
  • car 1.02.zip
    car 1.02.zip (Binary file, 0.02 MB)
  • car 1.04.zip
    car 1.04.zip (Binary file, 0.02 MB)
  • car 1.06.zip
    car 1.06.zip (Binary file, 0.02 MB)
  • Vehicle-Firmware V1.20
    Vehicle-Firmware V1.20 (Binary file, 0.02 MB) Requires CarManager 1.10 for most of the new features.
    Changes since 1.08:
    1. Automatic detection of trailers. In earlier versions it had to be selected manually whether a trailer or semitrailer is connected to the vehicle, in order for the vehicle to know where the infrared signals should be emitted from. Now the vehicle can detect the trailers automatically, and it even adjusts its length information accordingly. This automatic detection can be deactivated, and it is still possible to set manually whether a trailer is attached or not. This enables the usage of custom-made trailer lights which are not guaranteed to be detected. The vehicle checks for the trailer when it is switched on, when it is standing still, and shortly before it starts moving. However, trailers can not be immediately detected if they are connected while the vehicle is lifted off the road with its wheels are still turning. More information in the CarManager in „Infrared / Adaptive cruise control“ 
    2. The expansion output can now be configured. These are the solder pads at the rear of the vehicle. This new function can now be controlled similarly to the lights, with the remote controller, magnetic commands, etc. It is also possible to set it to copy another existing function. If the roof beacons are selected as a source, the blinking is asynchronous with the other beacons, this allows the addition of a third blinking beacon without it blinking in sync with one of the others. More information in the CarManager in “Lights” 
    3. Vehicles with overhang are now taken into consideration for the adaptive cruise control. If a vehicle has this setting activated, then following vehicles will brake a little harder, and therefore they keep slightly more distance. More information in „Infrared / Adaptive cruise control“ 
    4. Bugfix: If a macro was set up to switch on the main lights, it did not switch the rear lights on. 
    5. The crawling speed (for example due to a South magnet) can now be interrupted both by the remote controller (“Play” button) and the IR Mini, and by the command “restore default mode” (for example, a SN magnetic sequence). 
    6. The “continue / drive away” command previously ignored all magnets, therefore magnetic sequences were also ignored (for example, at a green light, with the IR Mini). From now on, magnetic sequences are evaluated even in case the “continue” command is active. Only the stopping and braking commands are now ignored, all others will be executed. 
    7. Improved compatibility with OpenCar. Instead of only starting and stopping, now the speed information is evaluated, this allows for a smoother distance control. 
    8. Possibility to set up a minimum braking distance in case of smooth braking. If the braking distance is longer than the distance limit (for example, due to an external module sending a brake command with a custom braking distance), the vehicle did not brake completely, but it started to accelerate before the full braking distance was covered. Now there is a new option under Magnetic control / South: Smooth braking: “expand distance limit in case of a longer braking distance”. 
    9. The test modes now use the turn signals in cases of vehicles with don’t have roof beacons. 
    10. The test mode for the infrared communication (Infrared / Adaptive cruise control) now shows DCC commands as well, with a lower brightness than our adaptive cruise control protocol. Left = speed commands, right = function commands. 
    11. Bugfix: Uploading a backup could temporarily corrupt the traffic lanes. 
    12. Bugfix for DCC: with some command stations (for example ECOS2) the vehicle used the crawling speed at speed step 0 instead of stopping completely. 
    13. The commands which are executed automatically after a departure from a magnetic stop, now have a new option to delay the departure. This allows to first use the turn signals, switch the lane, etc. and then drive out of a bus station only a few seconds later. 
    14. Many new IR Mini commands and options are now supported. The default settings of the IR Mini also work with older vehicle firmware version, but for most of the other commands, this update is necessary. 
    15. Option to overrun yellow lights at a traffic light (with infrared control). If a vehicle received a “continue” command, and then immediately receives a compact stop command, it can ignore the stop command, depending on the speed it was traveling at. This can be used to overrun yellow lights and keep driving, instead of coming to a halt after passing the lights and the infrared emitter. More information in the CarManager in „Infrared / Adaptive cruise control / Finetuning“ 
    16. The option “Infrared / Traffic lanes / complete the lane switch immediately on a stopping magnet” now also works if the stop was caused by an IR Mini. 
    17. More intelligent handling of the + and – buttons on the remote controller If there is a temporary speed command active due to a macro or an IR command, the remote controller is now allowed to change the speed. However, in case of a speed limit or a minimum speed, the old speed before entering this zone will be restored at the end of the zone, except for the case the remote controller exceeded it.
  • Vehicle-Firmware V1.20
    Vehicle-Firmware V1.20 (Binary file, 0.02 MB) Requires CarManager 1.10 for most of the new features.
    Changes since 1.08:
    1. Automatic detection of trailers. In earlier versions it had to be selected manually whether a trailer or semitrailer is connected to the vehicle, in order for the vehicle to know where the infrared signals should be emitted from. Now the vehicle can detect the trailers automatically, and it even adjusts its length information accordingly. This automatic detection can be deactivated, and it is still possible to set manually whether a trailer is attached or not. This enables the usage of custom-made trailer lights which are not guaranteed to be detected. The vehicle checks for the trailer when it is switched on, when it is standing still, and shortly before it starts moving. However, trailers can not be immediately detected if they are connected while the vehicle is lifted off the road with its wheels are still turning. More information in the CarManager in „Infrared / Adaptive cruise control“ 
    2. The expansion output can now be configured. These are the solder pads at the rear of the vehicle. This new function can now be controlled similarly to the lights, with the remote controller, magnetic commands, etc. It is also possible to set it to copy another existing function. If the roof beacons are selected as a source, the blinking is asynchronous with the other beacons, this allows the addition of a third blinking beacon without it blinking in sync with one of the others. More information in the CarManager in “Lights” 
    3. Vehicles with overhang are now taken into consideration for the adaptive cruise control. If a vehicle has this setting activated, then following vehicles will brake a little harder, and therefore they keep slightly more distance. More information in „Infrared / Adaptive cruise control“ 
    4. Bugfix: If a macro was set up to switch on the main lights, it did not switch the rear lights on. 
    5. The crawling speed (for example due to a South magnet) can now be interrupted both by the remote controller (“Play” button) and the IR Mini, and by the command “restore default mode” (for example, a SN magnetic sequence). 
    6. The “continue / drive away” command previously ignored all magnets, therefore magnetic sequences were also ignored (for example, at a green light, with the IR Mini). From now on, magnetic sequences are evaluated even in case the “continue” command is active. Only the stopping and braking commands are now ignored, all others will be executed. 
    7. Improved compatibility with OpenCar. Instead of only starting and stopping, now the speed information is evaluated, this allows for a smoother distance control. 
    8. Possibility to set up a minimum braking distance in case of smooth braking. If the braking distance is longer than the distance limit (for example, due to an external module sending a brake command with a custom braking distance), the vehicle did not brake completely, but it started to accelerate before the full braking distance was covered. Now there is a new option under Magnetic control / South: Smooth braking: “expand distance limit in case of a longer braking distance”. 
    9. The test modes now use the turn signals in cases of vehicles with don’t have roof beacons. 
    10. The test mode for the infrared communication (Infrared / Adaptive cruise control) now shows DCC commands as well, with a lower brightness than our adaptive cruise control protocol. Left = speed commands, right = function commands. 
    11. Bugfix: Uploading a backup could temporarily corrupt the traffic lanes. 
    12. Bugfix for DCC: with some command stations (for example ECOS2) the vehicle used the crawling speed at speed step 0 instead of stopping completely. 
    13. The commands which are executed automatically after a departure from a magnetic stop, now have a new option to delay the departure. This allows to first use the turn signals, switch the lane, etc. and then drive out of a bus station only a few seconds later. 
    14. Many new IR Mini commands and options are now supported. The default settings of the IR Mini also work with older vehicle firmware version, but for most of the other commands, this update is necessary. 
    15. Option to overrun yellow lights at a traffic light (with infrared control). If a vehicle received a “continue” command, and then immediately receives a compact stop command, it can ignore the stop command, depending on the speed it was traveling at. This can be used to overrun yellow lights and keep driving, instead of coming to a halt after passing the lights and the infrared emitter. More information in the CarManager in „Infrared / Adaptive cruise control / Finetuning“ 
    16. The option “Infrared / Traffic lanes / complete the lane switch immediately on a stopping magnet” now also works if the stop was caused by an IR Mini. 
    17. More intelligent handling of the + and – buttons on the remote controller If there is a temporary speed command active due to a macro or an IR command, the remote controller is now allowed to change the speed. However, in case of a speed limit or a minimum speed, the old speed before entering this zone will be restored at the end of the zone, except for the case the remote controller exceeded it.
  • Vehicle firmware version 1.40
    Vehicle firmware version 1.40 (Binary file, 0.02 MB)

    Requires CarManager 1.22 for most of the new features. Please update your CarManager to version 1.22 or higher first and create a backup file to back up your vehicle settings (see CarManager manual).

    1. Inductive charging fully integrated
      Older vehicle versions also support the inductive charging, but with severe limitations 
    2. New roof beacon option:
      Introduced a new continuous light option for the roof beacons. This allows for custom modifications to use them as upper headlights.
  • Vehicle-Firmware V1.42
    Vehicle-Firmware V1.42 (Binary file, 0.02 MB)

    Publication date: 21.03.2025

    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.