P25RX Firmware Updates / Testing

[dispatchgeek]

Alright, so not quite then. I can fix mine by either re-writing config or doing a system_reset command.

The type of lock-up I'm referring to would be a firmware lock-up. Restarting the java software would not get it going again. It would require a power cycle to get it working. As I said, I have not observed this with the latest firmware, but this is what I'm currently testing for.

 

[btt]

Alright, so not quite then. I can fix mine by either re-writing config or doing a system_reset command.

That sounds like a firmware bug, but not a lock-up. I'll test the roaming mode after finishing the test for a fw lock-up.

 

[turnpike61]

What was the last version without the LSM/C4FM selection? I'd like to go back to that version of the software. Thanks.

 

[btt]

What was the last version without the LSM/C4FM selection? I'd like to go back to that version of the software. Thanks.

Send you a link to an older version.

 

[turnpike61]

Testing BTConfig-2022-06-05_1608 . File writes to the Dirwatch directory appears to be intermittent/broken in this version. Reverted to the most previous version and everything started working again. Is there a setting I should change? Thanks.

 

[btt]

Testing BTConfig-2022-06-05_1608 . File writes to the Dirwatch directory appears to be intermittent/broken in this version. Reverted to the most previous version and everything started working again. Is there a setting I should change? Thanks.

I've been running a change for about 26 hours on the P25RX with no related issues. I put this up as release 2022-06-07_1829. Let me know if that fixes it for you. If it does, I'll put the same change up for the other model. Thanks.

 

[turnpike61]

Same issue with the newer version. Dirwatch just does not populate. Maybe it's on my end. Will check more in the morning.

 

[btt]

Same issue with the newer version. Dirwatch just does not populate. Maybe it's on my end. Will check more in the morning.

Earlier versions let some bad filenames through. If any of these wav files are in the DirWatch directory, then you need to delete them. Some other notes: talkgroup, sys_id, date, time, frequency must all be valid for the files to get written.

 

[turnpike61]

Hi btt: I checked again this morning with 06-07 18:29, and same problem, even after clearing the dirwatch folder completely. One single recording is placed in the folder, it is ingested and plays fine, but despite further calls, no more recordings show up. 0603 10:05 works properly and have reverted.

 

[btt]

Hi btt: I checked again this morning with 06-07 18:29, and same problem, even after clearing the dirwatch folder completely. One single recording is placed in the folder, it is ingested and plays fine, but despite further calls, no more recordings show up. 0603 10:05 works properly and have reverted.

Thank you for testing that. I think I have it fixed now in 2022-06-08_0438. I've been testing this version on Windows. I'm going to update the other releases/models as well. The rdio_dirwatch directory no longer has to be empty for new files to be created.

 

[goldmyne99]

I am running P25RX 0608 0438 Win10. Running well after updated to rdio scanner version 6.4.1 just released on github. I had strange issues with 6.4.0.

Edit:
The rdio log matches the P25RX BtConfig TG log -- nothing missed.
Some wav files are not deleted in the dir watch folder due to file in use by another process. Most likely a Windows thing.

 

[turnpike61]

This one writes a single file, but the del after ingest function causes a file access error as mentioned by goldymne99. Not sure what is solved by these last three releases; I still need to set the file ingest delay in rdio-scanner to 30 seconds to avoid repeats of short transmissions.

 

[goldmyne99]

@turnpike61 What version of the rdio-scanner are you running? I had some issues with version 6.4.0. When I changed to 6.4.1 released today, I have not had any missed audio files.

Edit: my delay is 2 seconds

 

[btt]

This one writes a single file, but the del after ingest function causes a file access error as mentioned by goldymne99. Not sure what is solved by these last three releases; I still need to set the file ingest delay in rdio-scanner to 30 seconds to avoid repeats of short transmissions.

Thanks for the feedback guys. For Windows, I only tested to make sure that it was creating separate wav files and closing them properly (Windows requires this). There may still be an issue or it may be that V6.4.1 will solve the issue. I will work on getting a server configured on Windows 10 later and see if I have any issues here.

 

[goldmyne99]

I have not seen the wav file creation stop as @turnpike61 is seeing. My past issues appear to be all related to rdio server on version 6.4.0

 

[btt]

It could be an issue with different versions of Windows. I think it might be a system time thing. Some versions of Windows work differently with java regarding scheduled periodic timers than the rest of the platforms. There were similar issues in the past with audio. I think I know what is happening. I should have a new version soon.

 

[btt]

@turnpike61, please give 06-08_1220 a try.

 

[turnpike61]

@turnpike61 What version of the rdio-scanner are you running? I had some issues with version 6.4.0. When I changed to 6.4.1 released today, I have not had any missed audio files.

Edit: my delay is 2 seconds

I am on 6.4.0. I'll give the upgrade a try. Thanks.

 

[turnpike61]

@turnpike61, please give 06-08_1220 a try.

edit: Please change the server dirwatch timeout back to the default of 2 seconds.

I've done so, but multiple repeats. Am I supposed to have "delete after ingest" on?

 

[btt]

I've done so, but multiple repeats. Am I supposed to have "delete after ingest" on?

Yes, it should delete after ingest. This is the default option. I will update the instructions to include this.