At present I'm working on the UDS integration in current project.
UDS is nice standardised protocol that helps you to get rid of clunky custom code and respect it with standard library for UDS.
Out at least that's how looked. Anyway I'm quite ahead with the UDS protocol working with read ID and wrote ID services I.e. 0x22 and 0x2E implemented on virtual can.
Now I'm trying to integrate it all on device can. Having lots of issues there. But I'll manage.
MQTT is an IoT protocol used for transporting small amount data in a structured way between IoT peripherals.
The protocol is simple - all IoT peripherals are connected over LAN/WiFi and they publish/subscribe to a MQ Broker.
There are a variety of clients and servers that support various versions of this protocol. The latest version was 3.0.1 at the time of writing this.
The protocol is simple in that the overhead is minimum, the data persistence and delivery QoS is assured by the server, and there are various levels of QoS which help assume the optimal strategy.
The publishers publish to a topic to MQ Server over persistent TCP/IP connections. The subscribers subscribe to topics and are assured latest message delivery ASAP.
MQTT client library typically has about 6-8 source files and the protocol overhead is only a few bytes, this has made it popular.
I am back from a big vacation and so got tons of photos. While viewing them on mg laptop I saw some slowdowns after a while - usually after an hour of photo viewing.
This was observed on Linux mint. On windows 10 there was no such problem. So I looked around and the system manager showed huge memory taken by cinnamon.
I logged out and relogged in, and it would clean it up but after half an hour again we would be going back to the sluggish state.
This has me irritated and I'm thinking about changing back to Ubuntu. Let's see.