That is the easy part, implementing all the SAE and OEM protocols cost a lot of time and money. Do not fuzzy the can bus on a machine that you do not know... I have blown "something" on a brand new big rig with an automatic transmission, effectively bricking the engine, while using my own "telemetry reserved" ids... Warranty covered it, but their techs hates me now.
totoxahc Would you walk in a factory, plug into one of their assembly lines can-bus, start to fuzzy it and expect the whole thing not to shut down and all alarms to go off? Why would you expect being able to do the same thing on a vehicle? The particular bug I was describing here last year has since been fixed by Paccar, this was a case of me as a telemetry supplier doing perfectly valid things with the machine and still managing to brick it, just by having a PGN conflict on the bus. Do not ever fuzzy the can-bus of a live vehicle, you *will* fuck things up.
+jonharson well, there are inductive/capacitive interfaces that allow you to listen to the bus with no posibility of interfering it. That would be useful for telemetry in any system that streams the data (j1939, fms, etc). If you were sending messages to one of those networks I think that is a really bad idea
totoxahc I don't think you have the slightest experience working with those bus... You are not going to get anything useful from j1708/j1939 if you are not actively asking for it. Contactless-can does not in any way mean that it is read only. Brute forcing the address space to get all active PGM is harmless (there are tools made with just that purpose in mind), but if you start to fuzzy it with random garbage you will fuck things up guaranteed.
OK. I have realized that actually I have to create traffic myself using "cangen vcan0" command. Here is how to generate random can traffic: sudo modprobe vcan sudo ip link add dev vcan0 type vcan sudo ip link set up vcan0 cangen vcan0
![DDG & G Herbo - Nosey [Official Video]](http://i.ytimg.com/vi/I9Ra0Zc2NlQ/mqdefault.jpg)
The reason that the HW address is not set, is that CAN devices do not have hardware addresses the way e.g. Ethernet devices do.
...demo gods strike again!
That is the easy part, implementing all the SAE and OEM protocols cost a lot of time and money.
Do not fuzzy the can bus on a machine that you do not know... I have blown "something" on a brand new big rig with an automatic transmission, effectively bricking the engine, while using my own "telemetry reserved" ids... Warranty covered it, but their techs hates me now.
What were you especifically doing?
totoxahc Would you walk in a factory, plug into one of their assembly lines can-bus, start to fuzzy it and expect the whole thing not to shut down and all alarms to go off? Why would you expect being able to do the same thing on a vehicle? The particular bug I was describing here last year has since been fixed by Paccar, this was a case of me as a telemetry supplier doing perfectly valid things with the machine and still managing to brick it, just by having a PGN conflict on the bus. Do not ever fuzzy the can-bus of a live vehicle, you *will* fuck things up.
+jonharson well, there are inductive/capacitive interfaces that allow you to listen to the bus with no posibility of interfering it. That would be useful for telemetry in any system that streams the data (j1939, fms, etc). If you were sending messages to one of those networks I think that is a really bad idea
totoxahc I don't think you have the slightest experience working with those bus... You are not going to get anything useful from j1708/j1939 if you are not actively asking for it. Contactless-can does not in any way mean that it is read only. Brute forcing the address space to get all active PGM is harmless (there are tools made with just that purpose in mind), but if you start to fuzzy it with random garbage you will fuck things up guaranteed.
- So nobody, except you, is asking for useful PGNs?
- How could a contactless interface interfere with the bus?
- Agree.
I try to run virtual can, but candump and cansniffer shows nothing. What I am doing wrong? It stays just blank.
So, when I send can message using cansend, it shows with candump and cansniffer, but there is no other active messages.
OK. I have realized that actually I have to create traffic myself using "cangen vcan0" command. Here is how to generate random can traffic:
sudo modprobe vcan
sudo ip link add dev vcan0 type vcan
sudo ip link set up vcan0
cangen vcan0