Hello is there a way to hardcode a by ID for real dash serial devices? I have a good few serial usb devices and they swap arround every reboot on the ttyxxx.
Used alot with 3d printers.
Or let me write the serial path insted of picking?
Kind regards
Hardcoding the serial path will not work because every boot of the device may result into a new path.
No, the by ID takes the ID from the device and will allways be the same no matter the reboot or other stuff. Only thing that can change the reported by-id is a firmware write to the adapter or alike.
The dev/ttyxxxxx will allways move on reboot. Mine have done that 4 times now, kinda annoying to go in after starting the car to change it 
I guess I culd do a symlink to by-id/xxx into /dev/* to get realdash to see it.
All this is ofc only for a Linux based system, no clue how android or windows will handle it
Hoping you will see this, this is what we do on 3d printers, and in the 5 ish years this pi have been rebooted every day, the serial /by-id never changed.
Or can you tell what realdash is looking for in a serial dev/tty* so we can use Udev to make a link that do not change? Im guesing a parameter in Udev? As making a link in udev with just ID_MODEL_ID and ID_VENDOR_ID do not get registered in Realdash. Or if theres a .ini file where the link is that i manualy can edit?
Its a little fustrating starting the car and having to edit the serial path before we can drive..
I understand that, but I must admit that I’m not super familiar of how Linux USB ports work, and its hard to make changes to the code without knowing what we are doing.
The COM ports are currently identified by files in /sys/class/tty/ and pipe is opened by the name of the device file. This is how its commonly done on many Linux USB libraries.
