PEAK-System Forum

Hi Stephan,

thanks!
It seems I would need a higher wait time than 1,5 ms.
Can we discuss a way to extend this period?

Regards
Thomas

Thanks!
Thus, the valid range for this parameter is 0..150 translatingt into 0..15 ms?

Thanks!

From the developer documentation I would assume irq_time_limit is in 1ms instead of 100us.

Would ypu mind double checking if its 1000 or 100 us?

Thanks again
Thomas

Hi,

we got hold on FD DR gateways and could experiment with irq_time_limit and irq_count_limit.

When does the relevant timer start?

Assume, the irq triggers and a UDP message is send. Thus, we're having a 'clean' state.
Does the timer start already now, or only after the 'first' CAN frame arrives ...

Understood.

Probably last question for now: But w/the GW FD DR feature mentioned earlier, the 3-in-1 approach should be feasible?

Thanks!

In my application, every 20ms, 3 CAN packets are coming very close (<1ms).
Thus, if there is way to 'play' with this timeout also with the 'normal' GW, that would be apprecicated very much!

Thanks, I'll try with the PCAN-Ethernet Gateways FD.

For the normal Gateway:
As my goal is to always aggregate 3 consecutive CAN frames into 1 IP packet, it seems I would rather need a 'min. CAN frames per IP packet'.
Do I understand correct that there is still no way to achieve this in the 'normal ...

Hi Stepan,

I just read FD DR developer manual section 2.1.1 'Configuring CAN IRQ Limits'...

Do I understand correctly, this (new?) feature enables me to have a new (then larger) UDP packet being sent only every 3 CAN packets?

Best Regards
Thomas