Bug: J1939 Inactive time

mbowdich
Posts: 209
Joined: Tue Oct 05, 2010 10:54 am

Bug: J1939 Inactive time

Post by mbowdich » Sat Dec 11, 2010 10:28 pm

There are several J1939 PGNs that are transmitted at 10s intervals, which exceed the built in invalid data timer of the PV750. Is there a workaround for this?

Below are some examples:
PGN 65279
PGN 65268
PGN 64977
PGN 64980

I would suggest adding a column to the J1939 database page that allows the user to set the timout for each PGN.
dwills
Enovation Controls Development
Enovation Controls Development
Posts: 26
Joined: Fri Jul 30, 2010 8:27 am

Re: Bug: J1939 Inactive time

Post by dwills » Mon Dec 13, 2010 8:37 am

Adjustable time outs have been requested in the past, and is being considered for future releases.
JZanni
Posts: 29
Joined: Tue Oct 12, 2010 3:09 pm

Re: Bug: J1939 Inactive time

Post by JZanni » Tue Dec 14, 2010 7:55 am

It definitively would be better to be able to set the timeout individually as suggested by Mbowdich. But should it not be by default a multiple of the frequency? This would eliminate the issue listed here.
For the current version, what is the timeout value and is it adjustable? Is the status of a variable (valid or not) accessible in programming?
jpurdum
Enovation Controls Development
Enovation Controls Development
Posts: 153
Joined: Mon Jun 21, 2010 11:19 am

Re: Bug: J1939 Inactive time

Post by jpurdum » Tue Dec 14, 2010 11:29 am

We have a 2.3 release towards the end of 1st Qtr 2011. Will try to have this feature in by then.

In the meantime, here's the other info you're asking for.
- Current timeout is 5seconds on all modbus, 1939, and CANopen parameters
- You can control the timeout in scripting of other variable. In 2.1, we give you the option to do a write with timeout from scripting (see scripting guide viewtopic.php?f=5&t=37&start=0 Section 7.4). Obviously it's not the ideal solution that you've suggested, but it can help alleviate problems till then.

Thanks for the input!
john p.