RomRaider

I want to add several my hand-made gauges in to the logger :

I see thet the logger has a lot of additional devices and gauges. I have only used Innovate LC2.
I was already adding EGT and fuel pressure to the log using the 0-5v input signal from the rear oxygen sensor. My Ecu only has one empty input. But i want to use K-line or CAN Bus to log the parameters of my gauges. So far i don`t have an interface in the gauges because i don`t know how to them to the romraider.
I want to go the way with minimal resistance, i found that these parameters use the CAN Bus:

And i also found these gauges:

But i couldn’t find anything about these gauges on Google.
So I’m thinking maybe using an exchange protocol with them and making my own sensors based on these gauges.

The easiest way is to format your gauge output to one of the existing protocols.
AEM and MRF gauges use a simple ASCII format on serial. If you want to send on CANBus you need to write a driver for a CANBus interface and provide a suitable device that the logging computer can connect to CANBus with and then write the plugin for your gauge parameters in the CAN protocol.

MRF gauge is discussed here:
viewtopic.php?t=6179

Code is here:
https://github.com/RomRaider/RomRaider/ ... ternal/mrf

Thanks for the answer.
I don't like UART serial. Because it is slow and unstable. And I don't want to use another interface. Because when I connect to Subaru I use one tatrix interface and if I want to also watch AFR I need another interface. And if I want to register my gauges, I will need another interface. And now these are three USB cables
My first thought was to use the standard tatrix <-> ecu exchange, I thought i could add some new parameters to the romraider logger and add a response from my gauges. But when I did my research, i realized i couldn't. Because romraider makes one general request and waits for a response from the ECU with all the data. And then I started looking for parameters of additional modules that respond via the CAN bus. To use them for my purposes. But I only found what I wrote about. Something started to happen and the connection was interrupted, and i thought that they were working using this protocol.
How difficult is it to add a parameter to the romrider, when enabled, a parallel request will be sent either via Kline or via the CAN bus, depending on what is enabled.
Something like: CAN ID: 0x07E1 data: 05 00 00 00 00 01 00 00 (00 00 00 01 my adress)
And my gauges get answer: 0x09E1 data: 02 00 5F 00 00 00 00 00 (5F my data, 95 in dec Oil temp for example.)

I don’t understand well how data exchange occurs during diagnostics because i spent only a couple of hours researching.
While i was writing the text, an idea came to me about how to get into the standard exchange and add my data. I'll try and write.

The Logger currently only supports one session through the Openport 2, and that session is addressed to log the ECU. There would need to be code changes to the Logger to support communicating with more than one CANbus address, and then integration into your external gauges "plugin". Right now all plugins use serial comms.
I have not tried logging through the Openport 2 with more than one session to different targets, potentially using different protocols.

I did some tests. Basically it works.
What I've done:
Added a new module to romraider logger defs:

I connected my adapter (pressure gauge) with my code to the CAN bus.
How it works:
1.Tatrix sends CAN ID 0x06D1
2. My adapter receives 0x06D1 with data.
3. My adapter sends 0x07E0 (emulates a normal tatrix request)
4. The ECU responded 0x07E8 with data.
5. My adapter receives 0x07E8 with data.
6. My adapter sends 0x06D0 with data.
7. Tatrix receives 0x06D0 with data and displays it in the RR logger.

The next step is to add new parameters to the definition with my addresses.
And when my adapter sees that the Tatrix is asking for my address, I can add whatever I want to the answer in the empty spaces in step 5.
True, I have not yet studied how the exchange works during diagnostics

During the test I found a bug, my CAN library sometimes changed the order of CAN packets and RR lost connection.

Good idea.
And yes, the parameter response received in the Logger must be in the same order as originally requested since there is no parameter identification in the ECU response to indicate any order other than what was originally requested.