That's just crudely estimated from the number of telemetry points transmitted by the aircraft that are not received by the RC.
I'm curious which recorded categories found in a converted .txt to .csv file are being used for the crudely estimated telemetry points?
well, that's not entirely trueThey are all transmitted ten times per second, and either all or none seem to make it in each set - I've never seen a log file where just some of the data in a row are recorded.
As do I.BudWalker does the same thing when processing DAT logs
well, that's not entirely true
just like in the DAT logs (you can see it in column description), in TXT logs it's the same: various categories have various update rates
for example CUSTOM, OSD are updated 10 times per second, battery information only once per second
I write new CSV row with each OSD on the input
"I've never seen a log file where just some of the data in a row are recorded"
that's because all non-updated columns retain their values until next update (with some exceptions of course)
BudWalker does the same thing when processing DAT logs
As do I.
For both the .txt and the .DAT the fields are grouped into record types. Each record type has it's own update frequency. Both converters write a new row in the .csv at a fixed interval. The value for each field written to the .csv is the current value; i.e., it doesn't depend on any of the values since the last update.OK - thanks for the clarification. So do the updates to the various fields show up as completely independent data packets, or are they grouped together somehow? I've never attempted to delve into the data structure of the txt or DAT files.
For both the .txt and the .DAT the fields are grouped into record types. Each record type has it's own update frequency. Both converters write a new row in the .csv at a fixed interval. The value for each field written to the .csv is the current value; i.e., it doesn't depend on any of the values since the last update.
With TXTlogToCSVtool this isn't an issue because the interval is fixed at 0.1 secs which is the highest sampling rate.
But, with DatCon the sampling rate can be adjusted. It's defaulted to 30 Hz which is slower than the sampling rate of some record types. This was done to keep the size of the .csv files from getting too large. This could be a problem since some data, e.g. gyro data, can be different from the value when it's written to the .csv. Increasing the sample rate will overcome this but also make for sometimes humongous (possibly gynormous) .csv file sizes.
I expect that the tablet .DAT is being written as packets arrive from the AC; i.e., "data is being transmitted at different rates". So, the higher frequency record types arrive more often than the lower frequency ones. But, that detail is lost when the .csv is created. DatCon, and I think TXTlogToCSVtool, writes an entire row that contains all the latest values.Right - that makes sense. In the context of the original question, I was really referring to how the data are transmitted from the aircraft, but that's probably lost once written to the log files. In particular, if the downlink becomes marginal we see entire rows missing from the files, but if the data are being transmitted at different rates from the aircraft then one might expect to see rows with only partial data.
Right on -- the TXTlogToCSVtool and my log viewer do this too.DatCon, and I think TXTlogToCSVtool, writes an entire row that contains all the latest values
I'm curious which recorded categories found in a converted .txt to .csv file are being used for the crudely estimated telemetry points?
Can you attach one of your TXT files here so we can try it?Seen few files now and in the camera sn field illegal chararters are used or wrongly decryped, so reading csv will give errors or not all records are in the csv file.
Can you attach one of your TXT files here so we can try it?
I was sent few files by early testers, and they asked me not to publish their files.Can you attach one of your TXT files here so we can try it?
That makes sense. I haven't made any changes to handle the Mavic Mini logs yet.Uploaded txt files to phantomhelp shows for instance 4 cells batt values....
I don't think so, but could be. You can use @msinger s online log tool. It basically does the same thing.is there a MAC version for this amazing looking tool please??
Sorry if its;'s been asked before but with 32 pages of posts I haven't been right through them all, is there a MAC version for this amazing looking tool please??
We use essential cookies to make this site work, and optional cookies to enhance your experience.