The "scannerbox" guy (JasoVeen) specifically requested that the remote DLL API provide some means to distinguish individual VCOs so I believe he is working on this.
Unitrunker Release 31
- Status
information
Hi, I had unitrunker 1.0.39.10 installed on my hp laptop running Windows 8.1. I downloaded the new release of Unitrunker and I had to set it up again for a first time run, so I did that and set up my receiver UBC245XLT and when I try and change the receiver from stopped to Running it will not do anything it just stays stopped, I uninstalled everything and re-installed 1.0.39.10 and did the same setup and everything is OK, I have no problem changing stopped to running.
Steve
Hi, I had unitrunker 1.0.39.10 installed on my hp laptop running Windows 8.1. I downloaded the new release of Unitrunker and I had to set it up again for a first time run, so I did that and set up my receiver UBC245XLT and when I try and change the receiver from stopped to Running it will not do anything it just stays stopped, I uninstalled everything and re-installed 1.0.39.10 and did the same setup and everything is OK, I have no problem changing stopped to running.
Steve
Last edited:
Hi Matt!
Yuck. What system is this? To diagnose the problem, here's what I'd like you to do.
1. stop the signal receiver(s).
2. remove the radio IDs from the Groups tab.
3. turn of Decode logging on the signal receiver(s) (look for Logging check box on the VCO tab).
4. re-start the signal receiver(s).
5. when the radio IDs reappear on the Groups tab, stop the receivers and ...
6. please send me the decode logs.
You can post the logs here or send them to my gmail address.
Please also identify the erroneous group IDs. I can search the logs to figure out what went wrong.
Yuck. What system is this? To diagnose the problem, here's what I'd like you to do.
1. stop the signal receiver(s).
2. remove the radio IDs from the Groups tab.
3. turn of Decode logging on the signal receiver(s) (look for Logging check box on the VCO tab).
4. re-start the signal receiver(s).
5. when the radio IDs reappear on the Groups tab, stop the receivers and ...
6. please send me the decode logs.
You can post the logs here or send them to my gmail address.
Please also identify the erroneous group IDs. I can search the logs to figure out what went wrong.
Rick,
This is the system: Dauphin County Trunking System, Steelton, Pennsylvania - Scanner Frequencies. I will work through the steps you posted and get you some logs ASAP. Thanks again!
This is the system: Dauphin County Trunking System, Steelton, Pennsylvania - Scanner Frequencies. I will work through the steps you posted and get you some logs ASAP. Thanks again!
I enabled logging and have had some of the behavior occur again. I found a lot of files when I went looking for the log. What is the name or format of the log you want? I also didn't see your Gmail address on the Unitrunker website or here. I will email you the logs if you can point me where. Thanks.
The decode logs are prefixed "Decode". The name will include today's year, month and day.
Go to the signal receiver window and click on the folder tool button. If your receiver has multiple VCOs, the decode logs are named somerthing like DecodeA20150613.log (from the first VCO), DecodeB20150613.log (from the second VCO), DecodeC20150613.log (from the third VCO), and so on.
My gmail address is the same as my identity on radio reference.
Go to the signal receiver window and click on the folder tool button. If your receiver has multiple VCOs, the decode logs are named somerthing like DecodeA20150613.log (from the first VCO), DecodeB20150613.log (from the second VCO), DecodeC20150613.log (from the third VCO), and so on.
My gmail address is the same as my identity on radio reference.
Last edited:
Thanks Rick. Log sent. Let me know if there is anything else you need from me.
By the way group IDs on the system are 5 digits or less. All radio IDs are 7 digits.
Go to main window--> Info Tab --> scroll down to Apco 25 select Hex
All your radio ID's should change.
Not necessarily. Here's a channel grant with a low radio ID.
Code:
00 00 04 2A 8D 2B 5D 00 07 D6 6D 93 Group Voice Grant channel 2-A8D I 0007D6 -> G 2B5D, (4 priority, packet)7D6 = 2006 decimal which appears to be a valid four digit radio ID on this system.
Here's another grant with an equally valid high radio ID.
Code:
00 00 44 2A 9C 2E 1B 7B CC 5E 5C E2 Group Voice Grant channel 2-A9C I 7BCC5E -> G 2E1B, (4 priority, packet protected)Ok, I sort of misspoke. For the purpose of this all the radio IDs that populated into the group ID are 7 digits. The only radio IDs in decimal that are less than 7 digits are consoles which are 4 as you saw above and a few test IDs that are 2. All normal users fit into a 7 digit scheme, Anything that populated into the group ID section that is 7 digits is erroneous.
Airspy will not Start
Hi - I did not see the reply that I posted yesterday - I am running Win 7 Professional 64bit on a 4th gen I3. I can use the Airspy on both SDR# and SDR console.
I updated my Airspy firmware to RC5
Finally, I checked the Airspy driver and found an Open Moko driver 6.1.7600.16385. The instance ID is USB\VID_1D50&PID_60A1\AIRSPY_SN:16C463C83242A6C7
Not sure what else to provide
Hi - I did not see the reply that I posted yesterday - I am running Win 7 Professional 64bit on a 4th gen I3. I can use the Airspy on both SDR# and SDR console.
I updated my Airspy firmware to RC5
Finally, I checked the Airspy driver and found an Open Moko driver 6.1.7600.16385. The instance ID is USB\VID_1D50&PID_60A1\AIRSPY_SN:16C463C83242A6C7
Not sure what else to provide
I'll look into this. Thanks Steve!
I recently updated the harness utility to provide a little more information.
After you download and run the latest harness utility, please post the output here.
Thanks
Thanks I see you have been very busy updating the Unitrunker program.
I tried reinstalling the program Windows 8.1 And on my old computer running Windows 7 And still can not change the receiver from stopped to running, have no problems with the old unitrunker program.
Steve
Thanks I see you have been very busy updating the Unitrunker program.
I tried reinstalling the program Windows 8.1 And on my old computer running Windows 7 And still can not change the receiver from stopped to running, have no problems with the old unitrunker program.
Steve
I have tried to clean the registry to remove the old usb device data. Then reconnected the Airspy. Here is the latest harness data
C:\Users\X\Downloads>harness
AirSpy Test Harness
(c) 2015 All Rights Reserved.
Found an AirSpy
0 Device: \\.\USB#VID_1D50&PID_60A1#AIRSPY_SN:16C463C83242A6C7 Friendly: Descri
ption: AIRSPY Serial: AIRSPY_SN:16C463C83242A6C7 Symbolic: \\.\IUSB3#ROOT_HUB30#
4&419A9D0&1 Interface: {A75D0CA9-F466-43e9-8725-2F9C3278019C}
Opening \\.\USB#VID_1D50&PID_60A1#AIRSPY_SN:16C463C83242A6C7 (\\.\IUSB3#ROOT_HUB
30#4&419A9D0&1), Opening.
CreateFile fails, File Not Found(2).
Closing.
Opening.
Setting Policies.
Gathering interfaces.
Found 0 associated interfaces.
succeeds with alternate path.
Board ID: AIRSPY
Part ID: 6906002b:00000030
Serial: 00000000:00000000:16c463c8:3242a6c7
Closing.
Closing \\.\USB#VID_1D50&PID_60A1#AIRSPY_SN:16C463C83242A6C7, succeeds.
It Works!!!
Rick,
Thanks very much for the program fix. I have three VCOs working perfectly with three systems. Feels really good to see it working.
Thanks for your efforts and contributions.
Rick,
Thanks very much for the program fix. I have three VCOs working perfectly with three systems. Feels really good to see it working.
Thanks for your efforts and contributions.
The Strangest thing happened to me after I downloaded the 1.0.31.20. That being my Health Meter stayed at zero, when on version 1.0.31.18 my Health Meter works.
What do you guys think that is?
By the way, I love the new look on the 31.20! Keep up the Great Unitrunker!
What do you guys think that is?
By the way, I love the new look on the 31.20! Keep up the Great Unitrunker!
- Status
Similar threads
