Mark
10-21-2008, 02:42 PM
I forget where the firmware feature requests are, so I'll just add my own thread.
Now that the PDR-100 can start and stop on its own without any user input, there's no reason for the user to look at it while it's running and in my setup, the PDR screen is not visible at all.
So, what happens when there is an error- such as the flash is too slowno video input, fragmentation issues, no flash, etc?
It might be nice to have the PDR write an error file, ERRORS.TXT, to the flash with the time and date of the errors (okay, maybe not that last "no flash" error).
Yeah, it doesn't help with your lost run, but at least when you go to look at the footage later, you can tell what went wrong instead of having to go back to the car and troubleshoot it, pulling things out, changing the setup, etc.
Obviously, you might want to limit the size of the error file to the last N issues, but if you're able to fill up a 4 GB text file with errors, you truly haven't been paying any attention for a while.
Now that the PDR-100 can start and stop on its own without any user input, there's no reason for the user to look at it while it's running and in my setup, the PDR screen is not visible at all.
So, what happens when there is an error- such as the flash is too slowno video input, fragmentation issues, no flash, etc?
It might be nice to have the PDR write an error file, ERRORS.TXT, to the flash with the time and date of the errors (okay, maybe not that last "no flash" error).
Yeah, it doesn't help with your lost run, but at least when you go to look at the footage later, you can tell what went wrong instead of having to go back to the car and troubleshoot it, pulling things out, changing the setup, etc.
Obviously, you might want to limit the size of the error file to the last N issues, but if you're able to fill up a 4 GB text file with errors, you truly haven't been paying any attention for a while.