PEAK-System Forum

Hi,

for years, the PCAN-LIN we used as a converter between CAN (our test rigs "speak" CAN) and LIN (a device I had to embed into the rig "speaks" LIN) worked without problems.

Now I face a problem: Our operators installed a new device, which looks similar, but probably doesn´t "speak" LIN. The "Status" LED is blinking green very fastly, while the Transmission/Error LED seems to be constantly orange. I wanted to connect from the PC to PCAN-LIN just to check what is happening on the buses. I used an FTDI converter (USB-RS232) which I used successfully when doing the parameterization. But when I try to connect from PCAN-LIN CT to the PCAN-LIN, I see the error dialog "Try to connect to port/module 4 failed with message "A PCAN-LIN module could not be confirmed.". Do you want to try again?" This happens also when I unconnect the PCAN-LIN from the rig and just bring it to our lab, having only connected battery voltage. The COM interface is visible in the device manager, thus I assume drivers etc are working correctly. I tried all COM interface speeds, but none works.

Loading the .pclin file from some years ago also doesn´t fix the problem.

Is there the possibility to reset the device to factory defaults? Is there anything else I can do?

Many thanks in advance, best regards,

Gottfried Bruckmann

Hi,

can you please tell us the serial number (IPEH-xxxxxx yyyyyy) of the PCAN-LIN device, to see which hardware version you are using? Do you have the configuration available with which the device was configured? Possible issue could be that a used scheduler produces more data the serial connection could handle. In that case you need to setup a serial connection with a terminal program like hterm or similar, and send serial commands to stop the scheduler and set the device to default values again. You will find all details in the PCAN-LIN_ProtDef_eng.pdf which will be installed with PCAN-LIN-CT.

regards

Michael

Hi Michael,

thanks for your quick and extensive reply (as I´m used to when asking your support...)

The number on the "Bäbber" is IPEH-002029 03642.

"Configuration" is the .pclin file?

I´ll try to set up a direct serial connection.

Best regards from the city of fine wines and fine cars,

Gottfried Bruckmann

Hi,

"Bäbber" says latest hardware. To disable the scheduler by serial commands, please send 0x02 0x21 0xA4 0x00 0x85 by serial. Then you should be able to connect to the module again with PCAN-LIN CT (close terminal software before and don't reset the module, otherwise the scheduler will start again)

regards

Michael

Hi Michael,

unfortunately, this doesn´t work (yet). When looking at the RS232 bus signals between Pin 2 and Pin 5, there seems regular traffic (always repeating 2 kinds of "packages), with a bit rate of 38k4. I assume the configuration is 8N1. (Don´t know yet how to find it out)

When looking at the RS232 bus signals between Pin 3 and Pin 5, even when trying to send something via hterm, I don´t see anything. Does this mean the interface is broken???

Best regards, have a fine evening,

Gottfried

Hi,

if the standard configuration is used, the serial parameters are 38400/8/N/1. But someone could also set a different serial bitrate to the device. What kind of serial connection do you use (USB2Serial or native connection from the PCs mainboard)?

Maybe it will be helpfull to contact us by email to arrange a teamviewer/teams meating to check the device.

regards

Michael

The problem seems to be on my PC´s / interface´s side: A colleague asked me to have an RS232 loopback connector (Pins 2 and 3 short-circuited) to check if stuff which is sent via hterm is read back by hterm.

This isn´t the case, so I have to check this first.

Thanks for your support and patience!

Sodele,

we could prove that it´s the interface. Two of them didn´t work - neither with a PC with Windows 11 nor with a PC with Linux. Perhaps (but this is just an assumption) the hardware built there isn't supported any more by the FTDI driver.

A colleague has an USB-RS232 device, which was delivered together with a measurement device. We could lend it, and here everything works fine:

• The PCAN-LIN CT software can connect to the PCAN-LIN device.
• When looking at the bare signals between Pin2,3 and 5 in the RS-232 cable with an oscilloscope, one can also see hterm sending commands to the PCAN-LIN. With the old interface, one saw only the traffic sent from PCAN-LIN to the PC.
• hterm can read the output of PCAN-LIN

Best regards, and thanks again for your patience,

Gottfried Bruckmann