Issues with serial sources

66 views
Skip to first unread message

Marcelo Oliveira

unread,
Dec 12, 2024, 10:51:51 AM12/12/24
to IADS
Good morning dear IADS support team and IADS users!

Firstly I would like to apologize for any stupid questions in advance since I am a completelly newbie here...
So we had been trying to receive some real time ch10 uart streams coming from our DAS and we are having some issues with it. We suspect that it may have something to do with our TMATS but we couldn't figure out what is going on. The issue happens with all serial sources that we use (rs 232 and 485) and we tried to filter the messages, and transmitt the full bus but in both cases no success, here's how one of our messages looks like in the TMATS:
(R group)
R-1\TK1-95:832;  
R-1\DSI-95:GPS_FTI-[832];
R-1\TK4-95:832;
R-1\CHE-95:T;
R-1\CDT-95:UARTIN;
R-1\CDLN-95:GPS_FTI-[832];
R-1\UTF-95:0;
R-1\NUS\N-95:1;
R-1\USCN-95-1:1;
R-1\UCNM-95-1:GPS_FTI-[832];
R-1\UCR-95-1:19200;
R-1\UCB-95-1:8;
R-1\UCP-95-1:N;
R-1\UCS-95-1:0;
R-1\UCIN-95-1:1;
R-1\UCBS-95-1:82;
R-1\UCSL-95-1:297194;
R-1\UCSV-95-1:000000000000000000000000000000000000000000000000000000000001001000100011101010000;
R-1\UCBR-95-1:0;

(S group)
S-2\DLN:GPS_FTI-[832];
S-2\NS\N:1;
S-2\SNA-1:GPS_FTI-[832];
S-2\MDT-1:BINARY;
S-2\MDL-1:FIXED;
S-2\MES-1:8;
S-2\MIDL-1:4;
S-2\MLEN-1:82;
S-2\NMS\N-1:1;
S-2\MID-1-1:0000;
S-2\MNA-1-1:RS Transparent Filter-2;
S-2\NFLDS\N-1-1:2;
S-2\MN\N-1-1:1;
S-2\FNUM-1-1-1:1;
S-2\FPOS-1-1-1:1;
S-2\FLEN-1-1-1:1;
S-2\FNUM-1-1-2:2;
S-2\FPOS-1-1-2:2;
S-2\FLEN-1-1-2:1;
S-2\MN-1-1-1:GPS_2;
S-2\MBFM-1-1-1:UNSIGNED;
S-2\NML\N-1-1-1:1;
S-2\MFN-1-1-1-1:1;
S-2\MBM-1-1-1-1:11111111;
S-2\MTO-1-1-1-1:MSB;
S-2\MFP-1-1-1-1:1;

this is the error message we've got:

Sun Oct 27 22:11:42 2024 [Info] : Using version 9.2.1 (Build 16) ot ladsipp.
Sun Oct 27 22:11:42 2024 (Warning] : Config startup mode set to NEW: deleting D:\TEST RS 485\RELEASED
4 Logs\iadsConfigLog.txt
Sun Oct 27 22:11:43 2024 [Info]: Additional Chapter 10 log messages appear in DiNTEST RS 485\RELEASED
4\Logs\Chapter10Log.txt
Sun Oct 27 22:11:43 2024 [Info] : Time validation turned off.
Sun Oct 27 22:11:51 2024 [ERROR] : Cannot locate stream
GPS_FTI-(832] nor instantiate custom plugin by this name.
Error: Invalid class string
Sun Oct 27 22:11:51 2024 [ERROR): Error compiling.
Sun Oct 27 22:11:52 2024 [Info: Waiting for CDs to stop. bun Oct 27 22:11:52 2024 (Info]: CDS stopped.
Sun Oct 27 22:11:52 2024 [Info]: ladsipp stopped.

The streams are being recorded and we can playback the data using a ch10 package analyzer that show us the data that we are expecting. If you prefer we can send you some recordings for further investigation alongside our TMATS files.

Thank you very much for your support!

Best Regards 

Marcelo

mij...@curtisswright.com

unread,
Dec 12, 2024, 11:00:22 AM12/12/24
to IADS
It could simply be a matter that has been addressed already in the 6 years since version 9.2.1 was released.  Please reach out to me directly via email mijones at cw and at a minimum, I can get you the latest version to test with.

Regards,
Mike

Kathy Rodittis

unread,
Dec 12, 2024, 5:29:13 PM12/12/24
to IADS
Marcelo-
IADS doesn't really have support for the S group for parameter identification. What you need to do is
1) Upgrade to the latest version of IADS
2) Select IadsBus.Ch10Serial_4k as the "data stream" next to the serial channel. This will create a blob parameter (array) called "Ch10Serial4K_X" where X = the channel number. 
3) Use the IadsBus.SerialText() or Decom() derived functions to break apart the serial stream into parameters. ( Please see IADS help for details on using those functions. )

-Kathy

Marcelo Oliveira

unread,
Dec 13, 2024, 10:32:03 AM12/13/24
to IADS
Dear IADS team.

Thank you so much for your quick reply! I will make sure to update my system and test it again!

Best Regards

Marcelo
Reply all
Reply to author
Forward
0 new messages