@supczinskib Sorry for the delay, been working on another project. I managed to get ssl to work with the device and tested out a lot of the configuration options. I had an issue with the example and posted it along with a solution in another thread -> Setting up ssl/tls with mosquitto = "A TLS error occured" solution. Hope this answers your question.
For a "just monitoring" device it could not have any trouble once the ECU do the great of the processing activities before transferring data to/from CAN. So, would be possible to translate DTC Codes to a more friendly languages, define some alerts (eg.: out of safe range of AFR, engine temp as too hot/cold, some other relevant pressures), even some additional resources like calculations to give hints like shift up/down.
For a piggyback use, probably would need an "special order" dock by having some more modules, once would need a more real time processing, fast enough to convert data on-the-fly and do the ECU read this new data to make you need (like "aftermarket" turbocharged, supercharged or even with nitrous vehicles).
For a standalone EMS, it's really a topic for more engineering capable people, once it demands an amount of modules and controllers. And, unfortunately is not my case considering time and health conditions.
So my focus tends to be restricted to a "monitor" device only.
@Angus-Ryan Did you solve your problem? I had something similar with the Dock 2 and a 3.5" TFT display. The problem was a conflict between I2C communication between the omega and the Dock's AVR chip with uses pins A4 and A5. But the pin corresponding to A4 resets the TFT display, So I cut this pin on the display and wired it to the Tx pin on the Dock 2, to do a hard reset when needed, but not during I2C transfers. The other added wire in the picture enables GPIO11 to receive data from the Arduino, but that is unrelated to the flakey operation I had before cutting the reset pin on the display.
Hope that's helpful.![0_1609001112703_20201222_175626b.jpg](Uploading 76%)
I am still trying to recover my old account, but here you can download the pre-built mono package for Omega2 and Omega2+.
@LightSwitch The ADC Expansion package is for Python only, it won't work for micropython.
To interact with the ADC Expansion with micropython, I recommend calling the adc-exp command-line tool from micropython.
See the OS function in micropython-lib: https://github.com/micropython/micropython-lib/tree/eae01bd4e4cd1b22d9ccfedbd6bf9d879f64d9bd/os
Ok I finally got around to installing the micropython-lib on one of my Dash modules. I went to the Git hub site and used the example code there for the umqtt.simple client, to my disappointment it does not return a clean string for the message so for my projects where I convert the string into Json, this simply won't work as is. After searching I found that I had to create a routine to convert the binary text to a proper string I posted it below. I really don't understand why people don't go the extra distance to make things clean when they write code when did "good enough" become the norm?
@crispyoz said in Project "liburtc" the library to operate external RTC devices:
Not sure where I would buy old Russian diodes here on Australia though
You can try 1N34A that's Germanium Diode too and say us result.
Looks like your connection to Community was lost, please wait while we try to reconnect.