Here is your troubleshooting check list:
All connected CAN devices must have common ground. Use shield from the CAN cable to achieve that on each CAN device.
T-block short CAN cables should not exceed 30cm.
120ohm terminating resistors should be put only on each side of the CAN cable. That's 2 in total, and only on the ending sides. In between CAN devices ...
Generally there are two very different flavours of CAN networks.
Large networks with lots of nodes/sensors, such as industrial/factory automation applications.
Control system networks where something is responding fast and in real-time, such as cars, machines, general actuators. These are often mission-critical.
In the "large industrial network" ...
In j1939 I can't find a PGN defined with SPN for A/C buttons.
So you'd probably have to use the manufacturer proprietary fields and set your source addresses accordingly, source address 25 is for climate control ecu 1 for example.
For the other way around check SPN 7853 in PGN 64993 for example.
The CAN ID is compiled from the PGN, source and destination ...
Of course you can, that's why the CAN network is used on those encoders. But, you don't solder anything there, you buy a Y-splitter and prefabricated cables of specified lengths. Many different manufacturers do sell this cables. Read the manual of encoder and PLC carefully.
CAN co-mingles the message ID and priority. Message IDs imply the priority, but have no other low-level meaning if you look only at the basic CAN protocol layer 1 and 2 given in ISO 11898-1 (with very few exceptions).
This makes sense when you think of the applications of CAN: always relatively small networks, where each node is quite constrained in what it ...
The ISO standard for "high speed CAN" doesn't cover connectors. Therefore the CANopen standards have become the most canonical source instead. The relevant one being CiA 303-1, which contains standardization for RJ10, RJ45 and lots of other common connectors. You can download the document for free from the non-profit organization CAN in Automation ...
I found details for CAN pinouts at http://www.interfacebus.com/Can_Bus_Connector_Pinout.html. These included both 4p4c and 8p8c modular connectors (sometimes misnamed RJ10 and RJ45).
For the 4p4c version, the pin assignments are
Pin 1: CAN V+,
Pin 2: CAN_H,
Pin 3: CAN_L,
Pin 4: CAN_GND
Somewhat surprisingly, the pinout recommended for 8P8C does not put ...
NART is apparently "no automatic retransmission". That's a non-standard setting which shouldn't be used. Commonly, CAN nodes should alway attempt to re-send a frame if they fail to do so the first time. Because one reason for failing could be that they lost in the bus arbitration procedure, yielding to another node with higher priority. That's not ...