EBM/101 out from IADS..

[Adam Chant]

We have the EBM/101 Ethernet but monitor from ACRA to read in a UDP
message from another DAS and was wondering if anyone has already gone
through the process of recreating the Ethernet messages from IADS? Such
that another application can process the messages as if it was directly
connected to the DAS. I guess this would be TCP/IP tunneling over TM.

Also does anyone care to share any pitfalls/shortcuts/tricks to getting
the most out of the EBM/101?

Just duplicating what the DAS application does in IADS is not an option
at this time due to time constraints and complexity.


-Adam

[ka...@iads-soft.com]

Hi Adam-

It's funny you should post this now because another user just asked me about this.

Right now unfortunately your choices for dealing with the data that comes from this card is to either

a) use the various concat, bit_pick and convert functions to split your data from the 16 bit words directly. 

b) use the MakeBlob function to return the message to its original size and then use the Decom function to split out the words you're interested it from the original packet.

MakeBlob will contatenate multiple words into a "blob" ( packet ) and is invokved like so:

MakeBlob( numberOfBitsPerParameter, Param1, Param2, ..., ParamN )

I don't have any direct experience with this card but I looked at the documentation and if you have multiple packet types appearing in the Ethernet link to this card, you will have to specify the filters pretty tightly in order to distinguish one packet from another ( i.e. to make sure your data is separate for each group of parameters you use ).

I am planning on offering automatic support for this card under IadsTpp but I can't really do it until after the 6.6 release, when I support Blob types as a native type. :(  That will ease the sting a little but the biggest "work" is still going to be translating the payload into IADS parameters and since the content is unknown to both kSetup and IadsTpp, I'm afraid there's no automated setup I can provide there.

If anybody out there is using this and is looking for automated ways to translate their custom "databases" of packet content into IADS parameters, I invite them to contact me at kathy_at_iads-soft.com ( replace _at_ with @ ). 

-Kathy

On Sat Nov 14 22:08 , Adam Chant sent:

--

You received this message because you are subscribed to the Google Groups "IADS" group.
To post to this group, send email to ia...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/iads\?hl=.

[James Bretz]

Adam,

>MakeBlob will contatenate multiple words into a "blob" ( packet ) and is
>invokved like so:
>MakeBlob( numberOfBitsPerParameter, Param1, Param2, ..., ParamN )

If you want to use the MakeBlob function to recreate the original packet,
you should probably run it as an OA equation and trigger off the last
parameter in the PCM map:

SetTriggerParam( ParamN ), MakeBlob( numberOfBitsPerParameter, Param1,
Param2, ..., ParamN )

If you need help formulating the Decom function arguments for a given field,
just let me know. Some customers have actually built custom ActiveX displays
to take in the entire Blob and process it. I guess it all depends on the
content.

Let me know if you have any other questions,
Jim

[Diarmuid]

Hi Adam,

As you probably know, the EBM/101 is an Ethernet PARSER. Essentially,
it captures an entire incoming IP packet, compares it to the user
defined "signature" and if the packet is "interesting" it stores the
entire packet in a buffer (which can be up to 1518 bytes in size -
driven by the MTU). You can then choose which words from the message
you want to transmit.

My understanding of your message is that what you want to do is have
the DAS, TM link, and ground software behave like a piece of wire -
put Ethernet traffic in at one end and get the same Ethernet traffic
out at the other end. Correct? And you are using traditional PCM as
the TM link - correct?

The first bit is easy. You define the message(s) you want to capture
and define a data word for each 16-bit chunk of those messages
(incuding IP header and so on). You then transmit all of these
parameters in your PCM frame. The problem is making the connection
from recieved PCM frame to putting that data out the Ethernet port of
the recieving PC. Kathy has already spoken to some of the issues
involved here. In theory it is straightforward but I don't beleive
there is any off the shelf software to do it - right now.

Diarmuid