Iadsbus.SerialText

[Ges Tablet]

I am trying to parse a number of messages that come from an RS422 datastream.

I am receiving the data as BLOBs and using Iadsbus.SerialText to decode the messages.

Each Message is a mixture of numbers and text items delimited by commas.

I can successfully read the numerical data, but there is no setting in Iadsbus.SerialText to return data of type ASCII, so I can't read the text items.

I can't use DECOM to do this because the text items vary in length and so it is impossible to index the correct number of bytes into the BLOB.

Is there any way to return text data using Iadsbus.SerialText?

Regards,

Gez

[Chant, Adam]

Ges,
Apologies, but the documentation is a bit out of date and is missing the ASCII Data Type for Argument 4.

Arg0 = Name of blob parameter to pass in ( for Acra data this is the "block" parameter from the UBM card ).

Arg1 = Field delimiter : quoted text. Use "" for no delimiter.

Arg2 = 0-based number of which field to look for after sync pattern OR number of bytes to offset from sync if delimiter is blank.

Arg3 = Starting sync pattern (quoted if text or a number - use "" for no sync pattern).

Arg4* = Data type  ( 0 = unsigned integer, 1 = integer, 2 = unsigned long, 3 = long, 4 = float, 5 = double, 6 = ASCII). Default is 0. Must also set ParamType accordingly.

Arg5* = Number of bytes for sync pattern ( use this if non-text sync has leading zeros ) OR number of bytes for data field, if delimiter is blank.

Arg6* = Text type. Currently only ASCII is supported. Defaults to 0.

Arg7* = Reserved, please put 0.

Arg8* = Blob includes IADS header (1) or not (0). Default is 1.

Arg9* = Data spans multiple upstream packets (1). Default is 0 ( does not span ).  For use when multiple Chapter 10 or other packets need to be concatenated to reconstruct the serial data.

Arg10* =  Check Chapter 10 error and return "empty" if error bit is set. Default is 0 ( do not check ).

 

Example:

For data that looks like this:

  $GPZDA,115559,15,07,FAULT_3

If you select sync pattern = "$GPZDA" then

  Field 0 =

 Field 1 = 115559

  Field 2 = 15

  Field 3 = 07

  Field 4 = FAULT_3

Because when sync pattern is removed, data looks like this:

  ,115559,15,07,FAULT_3

Consequently Iadsbus.SerialText(TEST_BLOB,",",4"$GPZDA",6,1,0,0,0) will return FAULT_3.

Note: the Derived Parameter ParamType for ASCII must be set to ascii.

 

Thank you,

Adam Chant

Project Engineer

 

IADS - Palmdale, Defense Solutions Division

Curtiss-Wright

190 Sierra Court Suite A3, Palmdale, CA 93550 United States

T: 661.273.7003 x2210

ach...@curtisswright.com | www.curtisswright.com

From: ia...@googlegroups.com <ia...@googlegroups.com> On Behalf Of Ges Tablet
Sent: Wednesday, February 4, 2026 1:17 AM
To: IADS <ia...@googlegroups.com>
Subject: [IADS] Iadsbus.SerialText [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/27a80902-ab61-4cec-a2c2-28e7aaf4a07fn%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

[Ges Tablet]

Adam,

Thanks for the quick answer - using data type 6 worked a treat.

I have one other question:

Is it possible to use non-printing characters as field delimiters?

I am thinking particularly about <CR><LF>  (0x0D, 0x0A). If so, what is the correct formatting to use for these characters in Arg1?

Regards,

Ges

[Chant, Adam]

Ges,
Not at this time. The delimiter can only be normal printed characters.
How are they represented in a serial string? As their hex values or something else? Have you attempted to send IADS the raw data to verify that it contains the entire string with the CR and LF in it?(or blanks for CR LF) It’s quite likley that sending a serial string with CR LF in it might just end the string at the first instance of the CR LF and is probably not a good method for delineation.

 

We have added a feature request to our feature request database for additional delimiters to include non-typed chars like tab (/t) to will be considered for a future release of IADS.

To view this discussion visit https://groups.google.com/d/msgid/iads/23cc9d31-9a63-41bf-bb4d-bc1e4033d7een%40googlegroups.com.