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
There's a use case where only the oldest or newest (see #541) message on the pipe should be kept, and the rest dropped. For example on a low rate link you may just want up to one message of each type, even though they may be getting produced at a higher rate (say if you want to slowly round-robin through HK msgs). This intentional dropping causes the error event and if/when it does get filtered since the event ID is shared with all the other pipes a legitimate issue (on a pipe where you don't want to exceed MsgLim) would be hidden.
Describe the solution you'd like
Add a pipe option to selectively ignore this error.
Describe alternatives you've considered
Could use QOS instead of pipe opts.
Additional context
Would be helpful to fix along with keeping newest msg:
Note the use case is actually that there's multiple links supporting different rates... so changing the production rate doesn't solve it. Desire is to get all the packets on the high rate link, and just one of each round-robin on the low rate.
Is your feature request related to a problem? Please describe.
Currently
CFE_SB_MSGID_LIM_ERR_EID
only reports the first 16 events on any pipe:cFE/cmake/sample_defs/cpu1_platform_cfg.h
Lines 258 to 259 in e35c3da
There's a use case where only the oldest or newest (see #541) message on the pipe should be kept, and the rest dropped. For example on a low rate link you may just want up to one message of each type, even though they may be getting produced at a higher rate (say if you want to slowly round-robin through HK msgs). This intentional dropping causes the error event and if/when it does get filtered since the event ID is shared with all the other pipes a legitimate issue (on a pipe where you don't want to exceed MsgLim) would be hidden.
Describe the solution you'd like
Add a pipe option to selectively ignore this error.
Describe alternatives you've considered
Could use QOS instead of pipe opts.
Additional context
Would be helpful to fix along with keeping newest msg:
Requester Info
Jacob Hageman - NASA/GSFC
The text was updated successfully, but these errors were encountered: