LabRadar Help

First topic message reminder :

Greetings,

I have the big LabRadar that has the SD Card storage.

Great tool. I have lots of data. Currently up to Series 0534.

Problem, the card became corrupt and upon booting up the LabRadar went to a previous Series???

Removing the SD Card and viewing it via my LapTop, I found two bogus looking file names with bad dates.

Four hours later, I managed to correct the file names and date stamps.

Inserting the SD Card into the LabRadar it boots up and goes to the correct series.



I would like to learn how to start with a new SD Card and rename the default SR0001 folder to whatever number I choose (SR0001-SR9999)

Just renaming the folder on the LapTop does not work. When you insert the card, Labradar creates a new SR0001 Folder and renames my folder with a bogus date stamp.

Thus far, LabRadar tech support is not useful. They did respond to my original plea for help and pointed me to the corrupt folders; but, follow up emails have gone unanswered.



I am a fairly good Hacker with Linux and command line experience. For you knowledgeable types I have learned the "touch" command.



If you have a solution, please contact me offline. Once the process is tested and verified, I will gladly post it for all to see.


Cheers,

Dave

Hello all,

When I got my degree, I had to take a class in Fortran.  I feel old and inadequate. 

Jim

lol spursnguns wrote:Hello all,

When I got my degree, I had to take a class in Fortran.  I feel old and inadequate. 

Jim

Only one?  You mean there’s life after fortran?

straybrit wrote:It's a binary file. As far as I can tell the second 16 bit word is a big endian number which should correspond to the series number. I've sent Dave a file to test. I use a Garmin so I can't test the theory myself. I can tease a certain amount of structure out of it.

I understand it is a binary file; and I see what you mean in the hex dump:



I agree, it looks like the series number is in the first 3 hex digits represent the series number- for those following along, please see: https://kb.iu.edu/d/afdl Start at the 3rd hex digit, match up the code to a value on the table provided and note the series number, which is also the file name.

The problem, as I see it, is that there isn't a programmatic way to meet the feature request solicited at the beginning of the thread from what we know right now. The rest of the hex/binary/data is probably some bit of output that can be toggled from the menu (for instance, how would you notate bullet weight, and then which of these values is the actual weight notation?) in addition to the measurements it collects for the series- or at least, until you select a new series. It's very telling that you can't go back and add to a previous series; that was a design choice. When the new .LBR file is written with the creation of a new series, all sorts of stuff is getting tossed into that file. How many of those values have to have a value that needs to be passed to write the file? Is the file merely written to, or loaded into memory, written, and then output the flat file? If the answer is all that's needed is a series number, will the LabRadar honor that file without the other needed data? 

We need the file format/structure. However, winter is coming, so it would be entirely possible to sit around and start to determine similar patterns in various files, looking for output differences, if one were so inclined.

-Chase

Dr.Don wrote:Dave, I've used a Labradar for several years and I like it.  Knowing you I have to believe you tested it against your former chronograph equipment.  How did that turn out?

Don

Greetings Don,

The numbers compared rather well.

I measured the distance to my PACT chronograph and it was 12 yards.

Then, within the LabRadar set up menu you have five distances it will record.

I set the LabRadar values to Muzzle (V0) and 12 yards (V12).

The shot velocities aligned very well between the units.

The only LabRadar errors I have recorded were shooting pellets in the hallway. The Radar waves were bouncing off the walls giving wild results. Moving outside onto the deck the LabRadar functioned correctly.

At my home range we have large concrete baffles to contain the shots from the Plinkers. I have to wonder if those baffles will cause the same echo effects.

I really appreciate my LabRadar. Although, the Garmin Xero and LabRadar LX should work equally as well, both being Doppler Radar devices.

Cheers,

Dave

Greetings Chase,

What application do you use for the HEX dump?

Windows or Linux?

HEX/Binary ....  Grrrrr...

Reminds me of taking Assembly Language class.

Cheers,

Dave

Ghex is what I'm using to create the tests

Is the file merely written to, or loaded into memory, written, and then output the flat file? If the answer is all that's needed is a series number, will the LabRadar honor that file without the other needed data?

So - using a 'blank' file - i.e. one with no tracking data - I'm fairly sure there's a checksum in there. The problem being trying to isolate the algorithm to (re)generate it. I'm not shooting right now (nursing a foster dog to get her ready for adoption) so it's giving me something to do.
My hope is that we can programmatically generate another 'blank' file that LR will accept as valid so it will use that as a sequence seed when it generates the next one.

Basic DOS class, junior college night course. I might still know how to use some of it ... if I could remember ... or figure out... how to access it.

Put 20 rds in the vicinity of 'downrange' today. A bit late, sun was peeking over the roof so it was 'hot' at 10:30.

First shot a miss... shot at the upper target on my 'pellet trap'... a box from a wine shipment stuffed with the molded cardboard trays. Got a 45 out of the other 19, a couple more outside the rings.

Tremors ... and poor trigger control on more than a few. And somehow the distance portion of my progressives is now about perfect on the front sight. Don't have to tip my head back anymore ... for now ...

Hey Dave,

Your testing the Labradar at 12 feet for comparison was smart.  I'm glad the data compared well.  The unit I retired in favor of the Labradar was a Caldwell.  I retired it for the setup convenience of the Labradar.  I'm aware that the Garmin unit is also Doppler, but I read somewhere that the data comparison between the Labradar and Garmin was not great.  That is unsubstantiated for me since I cannot recall where I saw it or who posted it.  But it was someone who had access to both units.

Don

Dr.Don wrote:Hey Dave,

Your testing the Labradar at 12 feet for comparison was smart.  I'm glad the data compared well.  The unit I retired in favor of the Labradar was a Caldwell.  I retired it for the setup convenience of the Labradar.  I'm aware that the Garmin unit is also Doppler, but I read somewhere that the data comparison between the Labradar and Garmin was not great.  That is unsubstantiated for me since I cannot recall where I saw it or who posted it.  But it was someone who had access to both units.

Don

Greetings Don,

All the reports comparing the Labradar to the Garmin Xero claimed the results paralleled.

The only complaint was the file format Garmin uses. Garmin has updated their *.csv file transfer.

I have the original LabRadar with the removable SD card.

Worked well for me until recently. The SD file system got corrupt and LabRadar did not like that.

Hence the start of this thread.

Cheers,

Dave

Here's a comparison of the LabRadar, a Magnetospeed, and a Oehler 35P chronograph:

https://bulletin.accurateshooter.com/2019/11/chrono-test-labradar-vs-magnetospeed-vs-oehler-35p/

The Magnetospeed isn't designed to work with pistols, although they have an adapter that you can get is your pistol has a rail under the barrel.  

The Oehler (which was the "gold standard" chronograph for many decades) had a very consistent ~ 10 FPS offset from the other two, but out of 3000 FPS, that's a third of a percent.  All three system tracked pretty well, other than that offset.