PEAK-System Forum

The mention of listen mode only was the bit I needed. The code on the receiving end was written by me and when I looked at it I found that it was only enabling normal mode if there were messages to transmit from it's side. I changed the code to enable normal mode (non-listen mode) and now everything ...

I've been doing a bit of research on this and as I understand it the "acknowledge slot" issue means the transmitting end did not "see" the dominant ACK bit. When that happens the transmit end begins retrying the transmit forever until an ACK is detected. Is my understanding of this correct?

Looking ...

Enabling the trace shows bunches of

Other Error, Tx, Acknowledge slot, RxErr=0, TxErr=XXX

Does that mean the Peak USB-CANFD device is detecting an issue with the ACK sent back from the remote CAN-FD device? If so, what is the scope of issues that could be responsible for that sort of issue? Thanks ...

I double checked and clock frequency (20Mhz), TSEG1, TSEG2, BRP, and SRJ for both arbitration and data bit rates for both ends and they are identical. As I stated, nothing is transmitted on the wire at all by the Peak device when I click "Send". But when I click "Disconnect" after clicking "Send ...

I am using PCAN-View with a USB - CAN-FD device and have a weird transmit issue.

I've created a message to transmit at 1M arbitration/4M data bit rates.
The LED on the CAN-FD device is flashing green and status at the bottom of the PCAN-View window shows "OK".

When I click "Send" nothing happens ...