- Status
i'm waiting to try the new firmware for my problems with Capmax 
racingfan360
Member
- Joined
- Dec 19, 2005
- Messages
- 1,187
1.22 is already available via Sentinel
Can't be. I have it on good authority that Uniden has abandoned the x36HP line and is concentrating solely on the SDS series of scanners. :wink:
1.22 is already available via Sentinel
ticoman71
Member
You funny guy! Yes, 1.22 is available now!
NXDN standard is not for 25 kHz. If they are operating standard NXDN, it will be OK. Just because an agency is licensed for 25 kHz does not mean that their equipment is actually using the full bandwidth.
My NXDN radios only do narrow and very narrow. I don’t think there has ever been a 25khz NXDN format.
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
Thanks upman
I also learned that some nxdn radios have a wide selection button on the side. Mostly the railroads are doing the 25 wide thing. But we verified a few using 25 wide at the radio shop.
Thought maybe it could affect conventional nxdn decode.
Ic-3101d models!
They had to have some wide models to be retro compatible with older wide radios that train crews were still using. They use nxdn as well as analog in many of the intermodal facilities as well as yards. some rr freqs and others IG
I also learned that some nxdn radios have a wide selection button on the side. Mostly the railroads are doing the 25 wide thing. But we verified a few using 25 wide at the radio shop.
Thought maybe it could affect conventional nxdn decode.
Ic-3101d models!
They had to have some wide models to be retro compatible with older wide radios that train crews were still using. They use nxdn as well as analog in many of the intermodal facilities as well as yards. some rr freqs and others IG
Last edited:
According to this log file, it appears that LCN Finder was stopped at about line 4900 (line starts 3555103). And, from there it seems to be scanning a Connect + and P25 systems. Intentional?
I forgot to turn off the logging immediately after I gave up on LCN Finder.
But while LCN Finder was active, there were several transmissions that should have been picked up (the 536 doing normal scan connected to the same antenna confirmed the voice traffic on the system) but were ignored by LCN Finder on the 436 for some reason.
But while LCN Finder was active, there were several transmissions that should have been picked up (the 536 doing normal scan connected to the same antenna confirmed the voice traffic on the system) but were ignored by LCN Finder on the 436 for some reason.
Thanks. I'll let you know if engineering needs more info.
- Status
