Wheel rotation graphs have been a prominent part of our story so far – our founder Aleksandar Filipov have used these graphs since the very beginning to explain what RemotiveLabs tooling is all about. Our tooling makes it simpler to prototype, build and test vehicle software. But how does that relate to those graphs?
Explaining what we do at RemotiveLabs is not all that easy. When Alekandar Filipov first founded RemotiveLabs and wanted to explain what the original product – the RemotiveBroker – does, he would demonstrate the wheel rotation graphs in the RemotiveBrokerApp.
Aleksandar Filipov: “Wheel rotations are relatable for everyone as it is something dynamic with the wheels rotating at different speeds as the car turns”
Using recorded drive cycles is a way to reduce hardware dependencies and one of the steps toward virtualization. RemotiveLabs platform enables collaboration in the cloud and the ability to feed signals to external applications like ProtoPie or an Android Automotive stack. A RemotiveBroker can run on any hardware with as many busses (LIN, CAN, Flexray, etc) as the hardware allows. We package our solution in ways that allow software engineers to abstract away hardware in vehicle development.
Most of our users actually primarily appreciate access in code rather than graphics. RemotiveLabs tooling is different from traditional automotive tooling in several ways:
Anything you see, you can script! Traditional toolings create frustration because developers want to automate and integrate code efficiently with scripting. RemotiveLabs as a company was sprung out of the frustration automotive developers experience trying to iterate efficiently in ECU functionality and vehicle software development.
