Going from various problems I saw with systems with smaller time wraps, setting a time after wrap occurs misses most of the problems which wall occur. Many systems will work fine with either 'negative

when I did this to myself recently, I had changed the shells default umask value to 077 which caused exactly what you are listing. I would check to see if the users or system wide umask was changed re

I am looking at getting one of these so do not have final answers. However looking at http://www.port.de/cgi-bin/CAN/CanFaqErrors https://stackoverflow.com/questions/64892746/socketcan-device-state-st