Thank you. That format worked! I added support for the P25_TSBK style messages. I'll add support for the P25_PDU multi-block messages before I release it. Here are some images of Pro96Com being driven by the P25RX.Todd - I sent you an email with a possible solution to the data format.
Tried new version. I probably need faster CPU, Pro96Com raw data log has a lot of noise in it. The packet dump tab looks okay.Testing version 2021-09-15_0005 has full support for Pro96Com control channel
You might want to try a different powered USB hub? The TSBK and PDU messages are 100% crc checked, so there are no errors in any of the data sent to Pro96Com when in this mode unless it gets corrupted during the transfer over the USB serial port. You did quit the BTConfig software to free up the serial port?Tried new version. I probably need faster CPU, Pro96Com raw data log has a lot of noise in it. The packet dump tab looks okay.
The TDMA CC mode will not work with Pro96Com at this point. I haven't looked into what TDMA CC messages would work if they were sent out. Obviously Pro96Com was intended to work with a standard P1 control channel, but I think there is at least some common overlap between P1/P2 control messages. Pro96Com looks like it can be configured to log unknown packets, so it might be worth a try to output them and see what happens. I'll do this.Is there a command to switch between P25 and TDMA CC without rewriting config? I do not see anything that looks like one when entering "?" on console.
Should the TDMA CC mode work in the same way as P25. Entering "Pro96_en 1" does not change output.
Getting noise. I'm off to get a powered hub. I have been connected directly to computers USB port. The data on the Console tab of BTconfig looks good so its possibly an overrun on the Pro96Com side. I will also try connecting a PSR800 to Pro96Com to see if it does same thing.please give 2021-09-15_0852 a try in TDMACC mode with 'pro96_en 1'
If it looks good in BTConfig, then it should look good in Pro96Com. The issue may be something else. Maybe it is the serial driver that Pro96Com is using on your system. I tested on WIndows 10. I realized that I didn't quite get the TDMACC support right on the latest release. I need to account for one other difference. I will have another version ready soon.Getting noise. I'm off to get a powered hub. I have been connected directly to computers USB port. The data on the Console tab of BTconfig looks good so its possibly an overrun on the Pro96Com side. I will also try connecting a PSR800 to Pro96Com to see if it does same thing.
Sounds like two different issues. You are definitely having some kind of issue with either USB, serial driver, etc. Phase 1 output is working 100% correct in the firmware here. I see a constant receive rate of 100% (usually displays 102%), so no data is being lost from the control channel. P1 data is all either CRC16 or CRC32 validated before sending to Pro96Com. The issue with TDMACC not working at all is probably firmware. Please send me a new image for that mode or a sample of the output and I will see if I can figure out what is going on.Running the 2021-09-15_1038 version. Both P25 Phase 1 and TDMA CC sites producing bad data lines (Ph 1 raw data below). The Ph 1 site does show data in the Packet Dump tab. The TDMA CC does not appear to have changed. Nothing is decoded.