Add 100kbps Baud rate

[hugovw1976]

Can you add 100Kbps to Can Baud rate?

[corygrant]

tested, working

[hugovw1976]

Where can I download the firmware?

[corygrant]

Where can I download the firmware?

Just merged it into the testing builds here:
https://github.com/corygrant/dingoConfig/releases/tag/testing-latest
https://github.com/corygrant/dingoFW/releases/tag/testing-latest

[hugovw1976]

Just star some test in Dashboard/Device/Bitrate show Unknown in configuration after read device Bitrate show 100K

[corygrant]

Ah yea looks like I need to fix that text field.
100k is working okay with your other devices though?

[hugovw1976]

I've only just started testing the settings; I'll begin real testing this weekend.

[hugovw1976]

I found another issue, after configuring all channels and can inputs I save all and burn board and all is fine, but after disconnect and "reopen" dingoConfig I can't load saved file (I chack folder and file is saved) but I get error to load file. I return to previus firmware V0.4.28 dingoConfig V0.1.5 and don't have this problem only firmware V0.5.3 dingoConfig V0.2.5

[corygrant]

Renamed a var when I shouldn't have, both should be fixed in testing release v0.2.6

[hugovw1976]

Screen.Recording.2026-05-19.094905.mp4

Test release v0.2.6 100k tested with others modules and communication is "ok" randomly lost communication but notice pc connection also lost randomly even without any connection on module (just usb).
In v0.1.5 Works perfectly

[corygrant]

The connected status is looking for messages from the device every 0.5s.
What do you see in CAN Log?

[hugovw1976]

I did more testing. In version V0.1.5, I can send CAN messages and control all 8 outputs. I can also read the messages sent by the module.

In version V0.2.6, I can read the CAN messages sent by the module, but I can't send messages to control the outputs. The message I send (ID 0x0FC) doesn't appear in the CAN log. I also noticed that the offset in the CAN messages is never saved in the *.json file.
I also configured CAN output messages (0xFE ID) with the data from Digital 1 and Digital 2, setting them to 8 bits long. However, in the CAN log, they always appear as 1 bit long with a value of 0xF9. When Digital 1 is activated, the value changes to 0xFA, but there's no change with Digital 2.