You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently CI_LAB directly forwards the data received from the network socket onto the software bus.
But in some configurations - particularly heterogeneous environments with mixtures of different CPU types - the data from the socket is not directly interpretable as a "C" struct.
Describe the solution you'd like
Separate this into a separate source file, and add a hook in CI_LAB to allow the read from the socket to include a decoding step prior to sending on SB. In the default implementation it would be a pass-through as it is today.
Additional context
For example, missions may dictate that all data appear in on the interconnections in "big endian" (network) byte order, and the local CPU might be little-endian, thus it needs to be decoded/translated before being forwarded to SB. This would provide the appropriate hook to allow that to happen.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Add an intermediate step during ingest to allow the buffer to be decoded
prior to sending to SB. Initial implementation is just a pass-through,
thus matching existing behavior.
jphickey
added a commit
to jphickey/ci_lab
that referenced
this issue
Nov 1, 2023
Add an intermediate step during ingest to allow the buffer to be decoded
prior to sending to SB. Initial implementation is just a pass-through,
thus matching existing behavior.
Is your feature request related to a problem? Please describe.
Currently CI_LAB directly forwards the data received from the network socket onto the software bus.
But in some configurations - particularly heterogeneous environments with mixtures of different CPU types - the data from the socket is not directly interpretable as a "C" struct.
Describe the solution you'd like
Separate this into a separate source file, and add a hook in CI_LAB to allow the read from the socket to include a decoding step prior to sending on SB. In the default implementation it would be a pass-through as it is today.
Additional context
For example, missions may dictate that all data appear in on the interconnections in "big endian" (network) byte order, and the local CPU might be little-endian, thus it needs to be decoded/translated before being forwarded to SB. This would provide the appropriate hook to allow that to happen.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: