Skip to main content

Railster OS 7.0 release notes

Release notes for the Railster operating system

Updated over 10 months ago

Here are the release notes for the Railster operating system:

RailsterOS 7.0.4 (06/05/2025)

New features

  • Add a local caching subsystem for the LuaCEP

  • Update the FPGA images to include differential channels on Railster 2U ADC

Bugfixes and Improvements

  • Fix link advertising speeds for Ethernet interfaces on production images

  • Fix update daemon not always reporting the GPS firmware version at boot

RailsterOS 7.0.3 (24/03/2025)

Bugfixes and Improvements

  • Change service dependencies to ensure all hardware info are collected

  • Change service start order to ensure the "state" is present in the first message

RailsterOS 7.0.2 (17/03/2025)

Bugfixes and improvements

  • Adjust a systemd timer and service to enhance the time syncing feature between Linux and the Platform Manager

Railster OS 7.0.1 (10/03/2025)

Bugfixes and Improvements

  • Fix production system regression creating no-comm situation in certain cases

RailsterOS 7.0.0 (03/03/2025)

Security

All third-party applications and libraries have been updated to their latest LTS releases.

Fixed CVEs: 0
New CVEs: 0


New features


Systemd for production RailsterOS

  • Add core daemons systemd services.

  • Add systemd boot services.

  • Configure ethernet in systemd.

  • Add systemd services for fpgaload (loads the FPGA image) and uipd (controls the UIP ports).

  • Migrate the metrics daemon to use systemd.

  • Add platform manager systemd services.

  • Add seedrng.service.

  • Make the OTA update daemon compatible with systemd.

  • Switch the init system from BusyBox init to SystemD on production RailsterOS.

Safety critical

  • enhance XT75 test suite to include long running test for output stability

Bugfixes and Improvements

  • Fix the battery validity status when the battery memory is not readable.

  • Migrate to pydantic v2 & update our custom python library

  • Increase the coverage and ruggedness of the QoS daemon.

  • Add QoS rules for supercaps and battery safety status.

  • Add a check that enforces that our base OS is never downgraded into master.

Did this answer your question?