there is 2.5v on the can because the high can is at 5v and the low can is at 0v, this is for those who are wondering, a can which communicates will be around 2.3v, because there is more of low signals than high therefore the average between the two and their signal frequency. the simplest is an oscilloscope to see the data transitions on each channel. the low can being the mirror of the high can, the best is to have two inputs on the oscilloscope to check the absence of distortion in the signal. For those who want more👍 nice chanel! why don't read the cheap directly and save the data on an other chip and solder it until read it with the scan tool?
thank you so much! Yes, I did connect the scope to confirm that CAN is not present. As far as programming the chip: yes that would be the best solution here especially since the customer has the ROM file backed up, however, I have never performed that procedure, I don't even know how to connect to that chip and what communication standard it uses (SPI, I2C...?) if you have that information, feel free to share it :) thank you
there is 2.5v on the can because the high can is at 5v and the low can is at 0v, this is for those who are wondering, a can which communicates will be around 2.3v, because there is more of low signals than high therefore the average between the two and their signal frequency.
the simplest is an oscilloscope to see the data transitions on each channel.
the low can being the mirror of the high can, the best is to have two inputs on the oscilloscope to check the absence of distortion in the signal.
For those who want more👍
nice chanel!
why don't read the cheap directly and save the data on an other chip and solder it until read it with the scan tool?
thank you so much! Yes, I did connect the scope to confirm that CAN is not present.
As far as programming the chip: yes that would be the best solution here especially since the customer has the ROM file backed up, however, I have never performed that procedure, I don't even know how to connect to that chip and what communication standard it uses (SPI, I2C...?)
if you have that information, feel free to share it :)
thank you
Polska #1