Forums › BB Series Discussions › IQ file epochnanos
- This topic has 2 replies, 2 voices, and was last updated 6 years, 7 months ago by
Andrew.
- AuthorPosts
Dan0ParticipantDear Signal Hound,
We mainly use our BB60C as a mobile RF recorder, and link a given chunk of IQ data to GPS position in the real world via time. We are (or would like to) use the
epochnanos
entry of the XML file to do this.Very frequently (in fact, all the time as of late)
epochnanos
has the value of zero, meaning that we have to parse file names and other undesirable things to figure out, and then only approximately, when the first IQ sample occurred.I am using the latest (V 3.2.2) version of Spike, but have had this issue with earlier versions as well, and was wondering if you also see this problem… or am I the only one?
Thanks for looking into this,
DAN
Dan0ParticipantHello Signal Hound,
Upon digging into this a little deeper, I have found that the zero
EpochNanos
value occurs on the first file recorded upon manual triggering (i.e. pressing the “Start” button in the IQ Record panel). If I set Maximum number of files to 3, for example, the first recorded file will haveEpochNanos=0
and the next two will have good values.I agree that the usefulness of an
EpochNanos
value is kind of limited in the case of a manual trigger, but it would be helpful nevertheless.If I trigger it externally via the BNC port on the rear of the BB60, I get good
EpochNanos
values, even for the first recorded file.This looks perhaps more like an issue within Spike, rather than anything to do with BB60C, sorry for posting this in the wrong forum. That being said, it would be helpful if you could forward this to the folks working on Spike, or I could re-post over there, if that is easier.
Thanks, and still curious if you can reproduce the issue…
DAN
AndrewModeratorHi Dan,
Thanks for the feedback and bug report. Don’t worry about reposting it in another forum.
Can you email me with more information about your setup. Initially I have been unable to reproduce the issue. Email me at “aj at signalhound dot com”. If you can send me a picture of the setup of the application at the time of the capture (including the settings control panel and the recording control panel), and any other information that would help me attempt to reproduce the issue. I think you are correct that it is an issue with Spike, it might be tied to a specific configuration.
Regards,
Andrew- AuthorPosts
You must be logged in to reply to this topic.