-
|
I have completed the first (buggy) version of a Fprime-to-YAMCS interface; here is my architecture. First tests are very conclusive, but in this new YAMCS instance there are two things which are very inconvenient and I would like to know if it is normal. I have checked and sendEvent() does get called, and all the variables used here to construct the event look good as well. There are no exceptions. Any idea? Attached: YAML config (stock YAMCS) yamcs.fprimeTest.txt |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
|
Just a thought, but maybe check your generation times. Both the events and the packets page default to only showing the "Last hour" of data (relative to gentime) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply. For packets, the preprocessor only returns data that goes straight through the mission database parsing so I'm not sure I'm supposed to do anything for them to be seen in the Packets page? For events, I started from a stripped down CfsEventDecoder - the time handling is identical so if that service is supposed to work I'm not sure what I'm doing wrong. Finally I've already tried changing the window of the list to the max and it remains empty. |
Beta Was this translation helpful? Give feedback.
-
|
10000
Actually, I take that back. You're right, I remembered setting the time window to the bottommost option but it was custom - "No limit" was just above and it did it, for both. Turns out I always have a gentime of 0001-01-01 00:00:00.192 UTC, not sure why (especially considering what I just wrote) but now I'll be able to investigate. Thanks! FYI I'm using TimeEncoding.getWallclockTime() for the preprocessor and onTuple's t.getColumn(TM_RECTIME_COLUMN or GENTIME_COLUMN) |
Beta Was this translation helpful? Give feedback.
-
|
Fixed it:
Thanks again for the lead! |
Beta Was this translation helpful? Give feedback.
-
|
Is your code public somewhere? |
Beta Was this translation helpful? Give feedback.
-
|
It will be, with pleasure. Let me just add some error handling and actually test it with Fprime (for now it's only been tested with examples of packets I tapped from Wireshark) and I'll link to a github repo. Happy to share but that's also in my best interest since I would definitely value your input on the Java classes (I'm not a Java developer initially, even less in YAMCS). You should see it pop in in the next few weeks I think. |
Beta Was this translation helpful? Give feedback.
Just a thought, but maybe check your generation times. Both the events and the packets page default to only showing the "Last hour" of data (relative to gentime)