LAN2CAN is not working in CAN baud rate 100K

[S.Michaelsen]

Have you also tested to switch CAN channels or Ports of your Routes? Are you able to monitor your network connection to see the fraes how they are really transmitted (e.g. using Wireshark)? Is it possible that there are some ports or connections are blocked on your device?
There is no difference between sending frames on first or second port on various baude rates so there is no serious reason why one LAN to CAN route should work while the other does not if the connections on your peer are both handled correct.

[gh.yu]

Hi,

Yes, I tested my can message with same CAN channel after I changed only baudrate from 100K to 500K.
And it's working well.

Could you test LAN2CAN with my can message on CAN 100K, sw ver 2.6.0?
And then let me know the result, please.

Or, could you share the debugging way like checking debugging log on Gateway?

Regards,

[S.Michaelsen]

Hi,

I already tested sending on an 100k bus here even containing your CAN-ID and data - time stamp is discarded no need to set it. What other participants are on your 100k CAN bus? What happens if you switch both buses to 100k connect them to each other (with a properly terminated cable of course!) and send your message.
Again: are you able to check if the message you are trying to send is really sent as you expected?
Which software version is installed on your gateway?
There is no additional log beside the information about the routes and the CAN interfaces displayed in expert mode.
What are status of your CAN interface after you try to send (don't forget to refresh the page)? Is there any traffic on the bus? How do you monitor CAN frames on this bus? Do you see if any error occurs?

[gh.yu]

My version is 2.6.0.
Could you share your sw image.
If so, I will try your sw image.

[S.Michaelsen]

Look, there is a page for the product on our homepage. I already posted the link earlier. There you can find any current documentation and also the current image but as you may read on the hardware information page 2.6.0 is the current version.
Would you kindly also answer the other questions?

[gh.yu]

OK I will check your other questions.
Just I want test another verion SW.
I want 2.5.0 verion. But I cant find 2.5.0 on your link.
If possible, pls share it.

[gh.yu]

Hi,

As you request, I tested LAN2CAN both 100K CAN channel 1 and 100K CAN channel 2 network.
And I checked that 100K CAN 1 is working well, but 100K CAN 2 was not working.

Following is the route status on expert mode.
Though I repeat to send can message, no packets are arrived after one packet is arrived as below.

Please check it out.

4 Local IP - Port:2048 CAN Channel 2 UDP
Index: 4
Status: PCAN-Gateway handshake is inactive.
Direction: Receive: IP > CAN
Source: Local IP - Port:2048
Destination: CAN Channel 2
Protocol UDP
CAN packets: 0
Reset
CAN frames: 0
CAN errors: 0
CAN frame drops: 0
CAN frames sent at retry: 0
Timeout between retries (CAN): 50
Number of retries (CAN): 6
IP packets: 1
IP messages: 1
IP errors: 0
Discarded LAN packages: 0
Dropped LAN packages: 0
Peers connected: 0
Buffer size: 221184
FPP stats: 0; 0; 0; 0; 0; 0; 0; 0;

Regards.

[S.Michaelsen]

Thanks. 2 done, 5 to go.

If there are no / wrong frames arrives at the LAN interface of course nothing can be sent on CAN. What client / software are you using to send your messages? Have you tried to use TCP routes instead to see that the connection establishment works well. UDP might loose packages even if it unlikely.

[gh.yu]

Hi,

As you commented, it' because of the udp packet with corrupted can message after checking udp packets.
it's not because of CAN baud rate 100K.
I guess wrong data in can message made CAN Gateway stalled.

Thank you for your help.

[PEAK-Support]

As Stephane wrote:

If there are wrong frames arrives at the LAN interface of course nothing can be sent on CAN

so thread could be closed