We are working on assisted braking system based on pedestrian detection.
How to send signals from the CAN to the ECU using C++ code.
We are unable to send and receive signals between TX2 and Canalyser even after doing all the setup mentioned in the forums.
Thanks for your response.
We are following the same steps mentioned above but currently using AMIS-30663-D as the transceiver to CAN0 port only.
While checking with the oscilloscope probes we can see the variations of the signal being passed from Canalyzer to the transceiver.The signal is getting detected at the transceiver level as well. But at pin5(Rx) of J26 port, we can’t detect any signal being received.
The Canalyzer throws an error NAK(not acknowledged).
When we probe Tx and Rx pin we don’t see data getting sent or received.
Have you successfully been able to send CAN data using the Jetson before (I’m assuming you’re using Vector Canalyzer)? Could it be a terminating resistor issue?
I would recommend getting SocketCan working first with Canalyser before trying anything else in custom software.
Hi _david_evans_g,
We have implemented socketCAN code on Jetson TX2 to send data using it.
But we haven’t been sucessful.
While probing the Rx and Tx pin of J26 port, we don’t see any data getting transmitted/received.
We have a terminating resistor(120ohms) after transceiver between CANH and CANL pin.
Yes i agree .
We are using can-utils .These are the set of commands we are using to initialize the driver and set up the interface:
sudo modprobe can
sudo modprobe can_raw
sudo modprobe mttcan
sudo ifconfig -a
sudo ifconfig can0 down
sudo ifconfig can1 down
sudo ip link set can0 type can bitrate 500000 dbitrate 2000000 berr-reporting on fd on
sudo ip link set up can0
sudo ifconfig can0 up
sudo ip link set can1 type can bitrate 500000 dbitrate 2000000 berr-reporting on fd on
sudo ip link set up can1
sudo ifconfig can1 up
sudo apt-get install can-utils
cansend can0 123#abcdabcd
Our transceiver is externally powered up , but the common ground point of J26 port i.e pin 10 and 11 are grounded externally as well.
I can only comment on my setup, but mine is powered by the Jetson, I think as a test you should try powering your CAN transceiver from the Jetson as a test (check the voltages).
We did the setup for our CAN transceiver but no luck with it .
Can you share a picture of the other side of the transceiver?
Can I also know which was the transceiver used by you?
We are using AMIS - 30663- D as the transceiver.
I have attached an image of the connection we use - Imgur: The magic of the Internet
When we use the oscilloscope probes at pin 5/7 of J26 port we see no signal being sent or received.
We can see the signal getting passed at the transceiver level, hence the transceiver seems to be connected fine.
Is there any jumpers to enable the J26 port? We can’t see any signal other than voltage levels at pin2 and pin8 of J26 port.
I really don’t know the issue, my only concern is that maybe the CAN transceiver is not compatible with the Jetson, or may need additional setup… It should work, but I don’t know what is causing the issue.
The only suggestion I can make is try a different CAN transceiver… for example, MCP2551 or SN65HVD230… Transceivers that are known to work with the TX2.
Hi David,
Pin 8 of the transceiver goes to Pin 2 of J26 port - 3.3V
Pin 4 of the transceiver goes to Pin 5 of J26 port - CAN0 Rx
Pin 1 of the transceiver goes to Pin 7 of J26 port - CAN0 Tx
Pin 3 of the transceiver goes to Pin 8 of J26 port - 5 V
Pin 2 of the transceiver goes to Pin 10 of J26 port - gnd
Pin 7 goes to CAN_H of DB9 connector
Pin 6 goes to CAN_L to DB9 connector
120 ohms across CAN_H and CAN_L
We have used this transceiver for our previous setups and has worked fine.
Yes , will surely try with SN65HVD230 once available with us.
Is there any additional setup at J26 port ?
We cannot detect any signal getting sent/ received other than supply voltages at J26.
I really can’t figure out what’s wrong with your setup, everything appears to be correct. My only concern is that maybe your CAN transceiver isn’t compatible with the Jetson, or it might require a subtle change to the Jetson device tree or CAN driver to make it work.