I'm in Hilliard so when i am in town i will help as much as i can
Ohio DSDPlus users (check-in)
- Thread starter mtindor
- Start date
- Status
Davey1
Member
One place where 461.5625 is used is as a conventional DMR frequency at the Toledo Museum of Art [License WQE316]. Color Code 13, Group Call 11. That's all I have on it for now.
Lol we are on a dedicated from Columbus to Seattle and Back
Sent from my iPhone 8 using Tapatalk Pro
Jason WX4JCW
XPR7550 - SDS100
Ok, that's definitely not what I had in mind. I guess I should be more specific:
System ID: L289
NXDN 48
Site 11 CC: 464.15
Site 13 CC: 461.5625
They are nowhere near me. I think they are probably Smartlink Systems sites in NWOH and are likely part of the bigger Michigan system called Deltacom (which is a combination of radio shops creating a wide area system).
So NWOH users are looking specifically for NXDN48 transmissions on those two frequencies, and they would be control channels advertising System ID L289 and Site numbers 11 and 13.
If nobody in NWOH ever manages to pick up these over the course of time, then they probably aren't in Ohio and are probably in Southern MIch.
But I'm leaning towards them being Smartlink sites in Ohio being part of Deltacom.
Mike
AtlasFBG2
Member
I have got this about 3-4 months ago.
464.1250 Sys 289 site 11 nx 4 ran 11
Signal was weak so I would say it is in Michigan
464.1250 Sys 289 site 11 nx 4 ran 11
Signal was weak so I would say it is in Michigan
Here is the location of the SmartLink Comm site in Ohio that has 464.125 licensed. Isn't this about the same distance (from your location) as Michigan would be? I guess it could be across the water in MI from you. But seems to me that the location below would be reasonable as well, no?
https://goo.gl/maps/KV3xv1ad8WL2
Mike
Hold that thought. Somebody might be able to help you with DSDPlus and SDRPlay (presumably with SDRuno software). I can likely help you too, but would not be able to get into something that involved til the weekend.
I'll try to make up some instructions in the meantime that I can post (regarding DSDPlus) for the benefit of anyone reading this thread who is wanting to download / install the free version of DSDPlus from www.dsdplus.com.
Basically, I think you will need to install both DSDPlus and VB-Cable -- unless SDRuno supports some virtual audio piping of it's own. And I know that in SDRuno you would have to click EXW in the receiver control and then unselect DEEM (so de-emphasis is turned off).
SDRuno <-- VB Cable --> DSDPlus 1.01
DSDPlus 1.01 and DSDPlus 1.101 DLL Files zips ( https://www.dsdplus.com/download-2/ )
VB-Cable ( https://www.vb-audio.com/Cable/ )
You would download the two DSDPlus zipfiles and unarchive them into a folder that you can easily access such as in C:\DSDPlus . Then you would download and install VB-Cable. Then you would turn off DEEM (de-emphasis) in SDRuno. If you can do those three things you are well over halfway there. The rest is all just learning how to adjust SDRuno correctly and make it output audio to the virtual cable, and then learn how to fire up DSDPlus so that it pulls in the audio from the same virtual cable.
Like I said, too involved for me to personally spend time on it now. But that will get you started.
mike
Attachments
Sorry, I meant:
System ID: L289
NXDN 48
Site 11 CC: 464.125 ( posted wrong freq in my previous post)
Site 13 CC: 461.5625
I put the L289-11 and L289-13 info in the Deltacom section of the wiki for safe keeping until we can pin down where they are (Ohio or Michigan) and have them added accordingly.
DeltaCom Unknown Sites - The RadioReference Wiki
Mike
Smart-Link Systems portion of L289 Deltacomm NXDN
I actually suspect that L289-11 and L289-13 are in Ohio. I actually suspect that L289 Sites 11 through 15 are all in Ohio. I suspect Site 11 is in Toledo and that Site 13 is in Findlay. Based upon site neighbors.
Here is a Google Map of all of the UHF trunked licenses I could find for Smart-Link Systems under 3-4 FRNs.
Incidentally, the following sites also have updated FCC licenses with NXDN48 emissions on them:
wapakoneta
bluffton
lima
new riegel
findlay
So that is more reason to think that aside from Site 11 (which I think may be Toledo), sites 12-15 are probably one of the five locations listed directly above. And heck, there may even be a site 16 that we just don't know about because it isn't a neighbor of Sites 11 and 13.
Monitored 8-23-2018
L289-11 (RAN: 11)
ch 517 464.125 control channel
ch 430 unknown freq - listed as alternate control channel
ch 519 unknown freq
neighbors: 4, 12, 13, 21 (with 4 and 21 being in MI)
Monitored 6-25-2018
L289-13 (RAN: 13)
ch 631 461.5625 control channel
Neighbors: 11, 12, 14, 15
L289-11: CC=517 - 464.125 is this neighbor's control channel
L289-12: CC=681 - unknown control channel freq
L289-14: CC=581 - unknown control channel freq
L289-15: CC=715 - unknown control channel freq
So if you are inclined to take a look at that map, and then (if you around the area) check the frequencies associated with the licenses at those locations for an NXDN control channel advertising itself as L289, you may just find sites 12, 14, and 15 somewhere up in that cluster in NEOH.
mike
I actually suspect that L289-11 and L289-13 are in Ohio. I actually suspect that L289 Sites 11 through 15 are all in Ohio. I suspect Site 11 is in Toledo and that Site 13 is in Findlay. Based upon site neighbors.
Here is a Google Map of all of the UHF trunked licenses I could find for Smart-Link Systems under 3-4 FRNs.
Incidentally, the following sites also have updated FCC licenses with NXDN48 emissions on them:
wapakoneta
bluffton
lima
new riegel
findlay
So that is more reason to think that aside from Site 11 (which I think may be Toledo), sites 12-15 are probably one of the five locations listed directly above. And heck, there may even be a site 16 that we just don't know about because it isn't a neighbor of Sites 11 and 13.
Monitored 8-23-2018
L289-11 (RAN: 11)
ch 517 464.125 control channel
ch 430 unknown freq - listed as alternate control channel
ch 519 unknown freq
neighbors: 4, 12, 13, 21 (with 4 and 21 being in MI)
Monitored 6-25-2018
L289-13 (RAN: 13)
ch 631 461.5625 control channel
Neighbors: 11, 12, 14, 15
L289-11: CC=517 - 464.125 is this neighbor's control channel
L289-12: CC=681 - unknown control channel freq
L289-14: CC=581 - unknown control channel freq
L289-15: CC=715 - unknown control channel freq
So if you are inclined to take a look at that map, and then (if you around the area) check the frequencies associated with the licenses at those locations for an NXDN control channel advertising itself as L289, you may just find sites 12, 14, and 15 somewhere up in that cluster in NEOH.
mike
Last edited:
ctpd845
Member
Mike,
I agree that site L289-11 is in Toledo. Earlier while in Perrysburg I had a very strong signal on 464.1250. Now at home, which is southeast of Toledo, I get a decent signal but not as strong as it was while in Perrysburg.
Running DSDPlus I am getting the following as neighboring sites
L289-3 CC=92
L289-4 CC=126
L289-12 CC=681
L289-13 CC=631
L289-21 CC=900
As far as 461.5625 I was able to get a weak signal while in Perrysburg. At home I cannot get anything. That would leave me to believe that it could be in Findlay.
I agree that site L289-11 is in Toledo. Earlier while in Perrysburg I had a very strong signal on 464.1250. Now at home, which is southeast of Toledo, I get a decent signal but not as strong as it was while in Perrysburg.
Running DSDPlus I am getting the following as neighboring sites
L289-3 CC=92
L289-4 CC=126
L289-12 CC=681
L289-13 CC=631
L289-21 CC=900
As far as 461.5625 I was able to get a weak signal while in Perrysburg. At home I cannot get anything. That would leave me to believe that it could be in Findlay.
Thank you. That's great information. If nothing else it makes myself more confident that Site 11 is Toledo, and even that Site 13 is Findlay.
Based upon Toledo site neighbors and the DB, Site 3 is Southfield, Site 4 is Detroit, and Site 21 is probably in SEMI (just using some logic, as twisted as it may sound). And site 12 (being a neighbor of both 11 and 13 may end up being one of the sites on the map that is not a ? question mark (the question mark notation on the map I linked to is an indication that hte license has NXDN48 emissions on it). I added the licenses / frequencies for each site to the map shoudl anyone want to reference the map from their location and then take a stab at looking some frequencies on the licenses in those locations for an active L289 control channel.
Mike
belvdr
No longer interested in living
- Joined
- Aug 2, 2013
- Messages
- 2,567
I will take a look at this tonight or tomorrow. My neighbor needs some help first and that's what neighbors are for.
Thanks for the quick write-up. I'm tech-savvy (not radio savvy) so this should be the easy part for me.
belvdr said:I will take a look at this tonight or tomorrow. My neighbor needs some help first and that's what neighbors are for.
Indeed, unless you have neighbors like mine
You're welcome. Good deal. You will probably be able to figure it out. Assuming you get SDRuno piping output to the VB-Cable (instead of headphones/speakers), then you can run dsdplus from commandline all by itself without any options. It will unumerate the various input/output devices available.
I'll give you a screenshot of mine (I use VAC - Virtual Audio Cable, but VB-Cable is good too and is free).
So, in my case I have four virtual audio lines and I want to use Line 1 (Virtual Audio Cable) for the link between SDRSharp and DSDPlus. In my SDRSharp I would send output to Line 1 (Virtual Audio Cable). Then in DSDPlus I would use the -i and -o options to set the input and output in DSDPlus.
dsdplus -i2 -o1 -v4
- where -i2 is input device 2 aka Line 1 (Virtual Audio Cable)
- where -o1 is output device 1 aka Speakers / Headphones (IDT High)
- where -v4 is verbosity level (i like high verbosity)
Depending upon the audio devices, everybody's list of audio devices and numbering will look different in DSDPlus.
Mike
Attachments
You are welcome. Hopefully you start off with successful decodes. In SDRSharp I set it to NFM (I have no mode called DIGITAL in SDRSharp) and set a bandwidth filter of about 4 khz for NXDN48 / IDAS and 8 khz for NXDN96 or DMR and about 9.5 khz for P25.
Your mileage may vary. I don't know if you have the ability to adjust filter with down to 4 / 8 / 9.5 khz in SDRuno. I also don't know what "DIGITAL" is for, or if it should be used in place of NFM.
Just tossing that out there.
In my experience, on a 20 db+ signal you should be able to get error free decode on NXDN, DMR and P25.
Mike
belvdr
No longer interested in living
- Joined
- Aug 2, 2013
- Messages
- 2,567
Ran across this on 451.010. I do not see this in the database nor on another SW Ohio monitoring group's list (monix.net):
DMR:
Current network: 113
Current site: 113-19
Neighbors 1, 2, 12, and 17.
Another on 451.500:
Current network: 128
Current site: 128-2
No neighbors listed.
Again, not radio savvy, so if this is useless, let me know.
DMR:
Current network: 113
Current site: 113-19
Neighbors 1, 2, 12, and 17.
Another on 451.500:
Current network: 128
Current site: 128-2
No neighbors listed.
Again, not radio savvy, so if this is useless, let me know.
belvdr
No longer interested in living
- Joined
- Aug 2, 2013
- Messages
- 2,567
I might be gaining an understanding. Got into 451.9115, and started getting more about this system, such as TGs and radio IDs. It has:
Current network: 113
Current site: 113-12
Neighbors are the same, except a new one added: 1, 2, 16, 17, and 19. This one is rather scratchy so may be further away.
When you see a DMR or NXDN site that shows a network ID and a site ID, do this:
1. Go to https://www.radioreference.com/apps/db/
* Navigate down to "Search by System ID"
* type in 128 and submit
* type in 113 and submit
You will see that System 128 is Mobilcomm (TRBO and that Site 2 is in Taylor Mill, KY
You will see that System 113 is P & R Communications Connect Plus (Ohio) and that Sites 12 and 19 are Greenhills OH and Taylor Mill KY
So the real idea is to look for things, search them in the database, and if you find new frequencies in use for an existing site or you find new frequencies for a system that isn't in the database, that is the kind of information we are looking for.
The 451.9115 that you speak of is actually 451.9125
The 451.01 that you speak of is actually 451.009375
You don't want to always take the center off the freq as being the actual frequency listed in the DB or on a license. It's going to be at 3.125, 6.25 or 12.5 khz spacing.
You are doing well. I'm not trying to shoot you down at all. But what we will be looking for / most interested in is new information that isn't already in the DB, or updating informatino that might have changed.
For instance, if System 123, site 4 lists neighbors of 7,8,9 in the DB but you copy the control channel and the neighbor list now says 7, 8, 10, 11, that's something we are interested in.
Or if you look on a license and see there are 10 frequencies licensed to the site but only two listed for the site in the DB (as confirmed active frequencies), then if you find activity on some of the additional frequencies and the data from DSDPlus shows that the frequency is part of that site, then we want to know what that new frequency is so that we can add it to the database.
This thread isn't limited to searching out new things, but should be. For instance, let's say I'm reporting a new trunked license...
P&R Communications ( WRBR616 ) for South Charleston, OH (Clark Co),
- it is a trunked license
- DMR emissions are listed on the license
- it will likely eventually become a new site on System 113 (if it isn't already)
So we might ask somebody in that general area to keep an eye on the frequencies on the license to see if they detect a control channel.
451.075
461.7625
462.275
464.7875
If somebody in/near SOuth Charleston tunes to one of those frequencies above and finds a new control channel advertising System 113, Site ###, then we want to know about that kind of thing.
You will also find a lot of DMR / NXDN that isn't part of trunked sites but rather are just conventional DMR or NXDN repeaters. They won't advertise a System ID or Site ID and won't have a 24/7 constant control channel.
Mike
- Status
Similar threads
