FlyDump un-encodes the payload for each record and then presents all possible number types for each location in the payload. I.e., character, hex, 1 byte decimal, short Int, Unsigned short int, int, unsigned int, long int, float, and double. You're right it's huge. You could re-direct the output into a file and then view that with an editor.I run below from the window 7 command line prompt. The shell window displays numbers, lots of them, and after about 20 seconds stops and beeps(seems like it crashes). What am I doing wrong? Shouldn't the dump be saved to a txt file?
java -jar FlyDump.jar -f <FLYXXX.DAT filename>
I see that I need to add some command line arguments to reduce the output. E.g. to just produce the output between 2 tick#, or between 2 file positions. Also, to just produce output for selected payload type(s).
I'm guessing that you thought there should have been a .txt produced because you thought that FlyDump converted the input to a .txt that would have been produced by the DJI GO App?