A lift controller's legacy firmware, rewritten for a new microcontroller

The new lift control platform of Intec GmbH is built around a new microcontroller. We rewrote the controller's legacy firmware for it, and on the new chip the main lift logic responds within 5 ms.

answers within 5 msOLED DISPLAYthe service menusCANopen BUSto more than 10 unitsOLD MICROCONTROLLERwith its legacy firmwareDRIVERStalk to the new chipMIDDLEWAREand the operating systemLIFT LOGICmore than 10 units, one liftMENUSon the OLED displaysTHE FIRMWARE, WRITTEN AGAINNEW MICROCONTROLLER5 msDISPLAYBUSOLD CHIPDRIVERSMIDDLEWARELIFT LOGICMENUSNEW FIRMWARENEW CHIP
  1. The lift controller runs firmware written for its old microcontroller.
  2. A new microcontroller takes its place. Firmware written for one chip does not run on another.
  3. We write the firmware again for the new chip, with its drivers, middleware, lift logic and menus.
  4. The lift runs on the new chip, and its main logic responds within 5 ms.

The old microcontroller is set aside with its firmware. The new one sits in its place, under the four parts of the firmware that were written again: drivers, middleware, lift logic and menus.

From the project: the four parts of the firmware we wrote again.
Illustration: an example board, not the client's.

Project sheet

Client
Intec GmbH
Industry
Lift and building technology
Our scope
Legacy firmware rewritten for a new microcontroller: architecture, drivers and middleware, the logic of the distributed system, menus on OLED displays
Stack
  • BusCANopen
  • OSRTOS
  • UIOLED menu system

The challenge

The lift had to behave as before, on a different chip

Firmware is written for one particular chip. How it reads a switch, sends a message or keeps time depends on the microcontroller underneath.

The lift controller of Intec GmbH had firmware written for its old microcontroller. For the new platform, that firmware had to be written again.

It also had to be fast. More than 10 units share one CANopen bus, on which only one unit can send at a time, and the main lift logic must respond within 5 ms.

What we did

Firmware architecture and code for the new chip

We designed the firmware architecture and wrote the drivers for the new chip, the middleware above them, and the logic that makes more than ten units on one bus work as one lift.

A real-time operating system gives the main lift logic priority over everything else the controller does, so it responds within 5 ms.

We also wrote the graphical interface and the menu system for the platform's OLED displays. It is what a technician sees when the lift is set up and serviced.

MACHINE ROOMFLOOR 0FLOOR 1FLOOR 2FLOOR 3CANopen BUSTRAVELLING CABLE8910111234567
SERVICE DISPLAYon the controller, unit 1

Units on the bus

  1. 1Controller
  2. 2Drive
  3. 3–7On the car: inputs and outputs, door drive, car panel, position, load
  4. 8–11A call panel at every landing
From the project: more than 10 units on one CANopen bus, and a menu system on OLED displays.
Illustration: the route of the bus, the eleven units and the menu entries are examples.

Result

The lift controller runs on its new microcontroller

5ms

Response of the main lift logic in hard real time, on the new microcontroller.

From the project

>10

Units in the distributed system, on one CANopen bus.

From the project
Oleksii Kvasnikov

Oleksii Kvasnikov · Founder and lead engineer

Moving firmware to a new microcontroller

Send us the old code and tell us which chip it has to run on.