Unwanted CAN Bus generated time parameter

58 views
Skip to first unread message

Stephen Hersh

unread,
Jan 22, 2025, 11:22:48 AMJan 22
to IADS
Hello, 

I'm ingesting some CAN bus via a ch10 udp stream. That CAN Bus seems to generate a "ch10 CAN (Busline #)" and a corresponding time parameter when using the CAN IADS plugin. The time channel seems to have some random time and date on it that seems to be conflicting with the rest of the data. Is there a way to continue getting the data from the bus without generating the time parameter?

Thank you,
Stephen

Chant, Adam

unread,
Jan 22, 2025, 12:43:01 PMJan 22
to ia...@googlegroups.com

Stephen,
IADS obtains official IRIG Time from the CH10 UDP packet and any additional time parameters contained in the data would be viewed as just another parameter.

Is the IRIG Time on the Dashboard displaying random time and date values or is it a time parameter contained in the CAN bus?


Thank you,

Adam Chant
Project Engineer, IADS

Curtiss-Wright
190 Sierra Court A-3 Palmdale, CA 93550
T: 661.273.7003 x 2210
ach...@curtisswright.com

iads-s...@curtisswright.com

 

From: ia...@googlegroups.com <ia...@googlegroups.com> On Behalf Of Stephen Hersh
Sent: Tuesday, January 21, 2025 4:53 PM
To: IADS <ia...@googlegroups.com>
Subject: [IADS] Unwanted CAN Bus generated time parameter [EXTERNAL]

 

WARNING: This message came from an external source. Please exercise caution and proper judgment when opening any attachments, clicking links or responding to this message.


 

--
You received this message because you are subscribed to the Google Groups "IADS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iads+uns...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/iads/0cbe4d53-deb6-447e-8cc4-1113cae37902n%40googlegroups.com.


This e-mail and any files transmitted with it are proprietary and intended solely for the use of the individual or entity to whom they are addressed. If you have reason to believe that you have received this e-mail in error, please notify the sender and destroy this e-mail and any attached files. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the Curtiss-Wright Corporation or any of its subsidiaries. Documents attached hereto may contain technology subject to government export regulations. Recipient is solely responsible for ensuring that any re-export, transfer or disclosure of this information is in accordance with applicable government export regulations. The recipient should check this e-mail and any attachments for the presence of viruses. Curtiss-Wright Corporation and its subsidiaries accept no liability for any damage caused by any virus transmitted by this e-mail.

For information about how we process personal data and monitor communications, please visit https://www.curtisswright.com/privacy-notice/default.aspx

Chant, Adam

unread,
Jan 23, 2025, 10:40:58 AMJan 23
to Stephen Hersh, IADS

Stephen,
IADS obtains Time from the CH10 UDP packet. However, where that packet obtained its time is not always known to IADS.

The logs will show any discrepancies in the delivery of Time and Data to IADS.
We would need to review the logs to understand better what might be happening with IADS Time in relation to your CAN bus time


Thank you,

Adam Chant
Project Engineer, IADS

Curtiss-Wright
190 Sierra Court A-3 Palmdale, CA 93550
T: 661.273.7003 x 2210
ach...@curtisswright.com

iads-s...@curtisswright.com

 

From: Stephen Hersh <stephen....@gmail.com>
Sent: Wednesday, January 22, 2025 5:58 PM
To: IADS <ia...@googlegroups.com>

Subject: Re: [IADS] Unwanted CAN Bus generated time parameter [EXTERNAL]

 

When we add the CAN bus packets, the time will shoot up a few hundred days. I'll wireshark those packets again to double check. 
To make sure I understood that correctly, the ChCAN_Time parameters that it generates won't have an affect on the IRIG time counter on the IADS dash?

Stephen Hersh

unread,
Jan 24, 2025, 10:24:21 AMJan 24
to IADS
Hi Adam, 

I've packaged the logs and a PCAP of our CAN data issue. They should be on Kiteworks in a couple minutes. 
The chapter 10 log appears to have the correct time, but the timeout text files and TPP log appear to have erroneous times after a second or two. I checked via wireshark, and my secondary header appears to have the correct time for all of the packets.
Would I have better luck trying the IADS.CAN function instead of selecting the plugin for the stream?

Thank you,
Stephen Hersh

Kathy Rodittis

unread,
Jan 27, 2025, 12:34:09 AMJan 27
to ia...@googlegroups.com

Hi Stephen-

No, IadsBus.CAN won’t help here.

I’ve got the logs and PCAP and I’ll be looking at it this week.

-Kathy1

Stephen Hersh

unread,
Jan 29, 2025, 6:16:18 PMJan 29
to IADS
Hi Kathy,

I ended up getting data working a different way. We removed the secondary header and synced the data using a different method and that seems to have resolved our issue.
I'm curious to know why the data wasn't working, but it's not a roadblock anymore.

Thank you,
Stephen

Reply all
Reply to author
Forward
0 new messages