I put ProScan on record and left the scanner in FTO mode. After the first actual fire call (in this case 6:30 Nightly test) ProScan started making files in large numbers, all silent. There was only one actual call in all of this and it was the first call. The squelch has not been broken since 6:30. This is definitely not working correctly. Any insight as to what is going on?
Roveer,
I got the email and started work on this. This is what's going on. The Fire-Tone Out Logging and Recording problem on BCDx36HP scanners was all messed up.
The main problem is ProScan was logging and recording when it shouldn't have. The returned data from the scanner was intermittently reporting Squelch Status open when no signal was received as I could tell. The data returned on a signal received and on a no signal received are identical except one param being the Property Mute is set to Unmute on a received signal. That's fixed so now ProScan accurately detects Fire-Tone-Out traffic.
The Second problem is the recorder which is mainly used for conventional and trunk systems and not really designed for Fire Tone-Outs. I'm thinking about adding a separate tab for Fire Tone-Out recordings.