Actually I was sending with baudrate 1000000/2000000 as this error occured. Ealier I had the ECU connected with the Vector Box + CANalyzer and my Teensy Board only as listener on the bus. There everything with baudrate 1000000/2000000 was fine.
But what occured to me just now is, that I had a config loaded whilest this experiment, and the config may altered the baudrate and the clock to the functioning 1000000/2000000 and 60! And later when I wanted to start sending with the teensy and for debugging just connected the teensy to the CANalyzer but without a config and the default values of CANalyzer may vary! So I will look into this next week!
Much Thanks for your help and patience with me!
But still I'm a bit confused, because I was also trying to get the teensy board sending directly to the ECU, which should have the correct baudrate/clock because I was able to read the messages earlier (Or did I just read the ones from the CANalyzer script? Gotta check), but the ECU didnt answer. And it should answer once it gets some messages, so this could be that the messages I was sending were not the one the ECU expected or some other problem...
I will continue to try and keep you updated / will come back for help! Thank you very much!
But what occured to me just now is, that I had a config loaded whilest this experiment, and the config may altered the baudrate and the clock to the functioning 1000000/2000000 and 60! And later when I wanted to start sending with the teensy and for debugging just connected the teensy to the CANalyzer but without a config and the default values of CANalyzer may vary! So I will look into this next week!
Much Thanks for your help and patience with me!
But still I'm a bit confused, because I was also trying to get the teensy board sending directly to the ECU, which should have the correct baudrate/clock because I was able to read the messages earlier (Or did I just read the ones from the CANalyzer script? Gotta check), but the ECU didnt answer. And it should answer once it gets some messages, so this could be that the messages I was sending were not the one the ECU expected or some other problem...
I will continue to try and keep you updated / will come back for help! Thank you very much!