Question about "Map" tab

[chud goo]

I've heard that many/most P25 systems transmit each radio's GPS coordinates when they key up.

I know this tab has been in SDRTrunk for a long time, but never I've seen anything beyond what appears to be a default location in New Jersey. 

Is this mapping working for everyone else, or is this lack of activity just proof that my local system is not using this function?  

[sdrtrunk]

The Fleetsync decoder is currently the only decoder that pushes GPS locations to the map.

I still have to add support for decoding P25 messages on the uplink side (mobile-2-repeater).  I'm down in Texas at the moment, so I don't have my P25 docs available.  I don't recall if there is a P25 GPS message or not.

I'll add support for GPS when I add the DMR decoder.  I think I'll also add support for plotting systems/sites when I add the interface to RR.

Denny

[Jean-françois Lepage]

Hello

I would like to know if the problem is solved, since it's been several weeks since I try to find a way to operate the map tab, without success.

And at the same time, the Fleetsync decoder works with which type of system; LTR, DMR, MPT1327 .....

Thank you for your help and for this great program.

[sdrtrunk]

Fleetsync is an audio band protocol that can be layered on top of any of the analog radio channels.  Around here they use it with FM, LTR, LTR-Net and Passport radios.

[Ron Webb]

This is a little off the topic of SDRTrunk, but an explanation of how I useFleetSync.

I am a volunteer with the Placer County Sheriff's Search and Rescue Communications Unit. We facilitate and dispatch searchers in the field during a search. Placer County includes some extremely rugged areas of the Sierra Nevada Mountain range of Northern California. We have an array of fixed, mountain top repeaters and a portable repeater that we can deploy via hike, vehicle or helicopter deployment. All of our activity is on the VHF-high band (150-170 MHz). When I first began, we hand-wrote a log of all radio traffic, which could easily be hard to read, being written in a hurry. We would frequently have many teams in the field and it wasn’t difficult to forget that a team was even out if they had not talked to us recently. We were supposed to check on each team hourly for a disposition and location, but as things got busy, we’d frequently forget. Thankfully, someone from our neighboring county developed a computer program (in Python) for keeping track of searchers in the field; Radiolog. Not only did it computerize our logging software, but by connecting the computer to a Kenwood radio, it would automatically identify which radio was transmitting and which team the radio was assigned. With the addition to a GPS microphone attached to the Kenwood portable radio the searchers were using, it would automatically log where the radio was being transmitted from. The software would keep track of what teams were in the field and how long it had been since we had last communicated with them. It would then remind us to perform a status check on a team we had not heard from in one hour. An awesome new feature was added to Radiolog that would automatically push the GPS location of each radio transmission to an offline SARTopo map. SARTopo was created by one of our searchers from the Tahoe-Nordic Search and Rescue, using JAVA. I built a dedicated SARTopo server in our communications truck, that those of us in communications, as well as the Incident Command Support Group (operations and planning) can all simultaneously view an active map of the search, with multiple layers and with different types of maps. If you were to follow the link to SARTopo, you will see the "Online" version of SARTopo, but we may not have Internet access, so everything is maintained on the server I built, including multiple map layers... some being different topographical versions while others are satellite or low-level aerial photographic layers.

All of this is possible with the addition of FleetSync. My only gripe against it is FleetSync is a proprietary technology from Kenwood. All of our portable cache radios are Kenwood TK-2170s. I have my own personal TK-2180 with a GPS microphone and in my vehicles, I have a TK-7360HV in one vehicle and a TK-7180HV in the other, both with a GPS receiver installed inside. I have been working with the author of the Radiolog software and the SARTopo software in standardizing our fleet and radio ID numbers as well as the standard format of the FleetSync data (such as the baud rate and the use of FleetSync as opposed to FleetSync II because the TK-2170s do not support FleetSync II). When transmitting GPS, it is directed at only one FleetSync fleet/radio ID number. I’m guessing that in SDRTrunk, it ignores the fact of who the GPS information is directed. In a FleetSync system, a user can see “caller ID” of a radio transmitting (I disable caller ID in our cache radios), but it ignores the GPS data if it is not the intended recipient.

[sdrtrunk]

Ron, have you tried decoding your fleetsync bursts with sdrtrunk? I'm guessing it doesn't decode fleetsync 1. But, I'd like to add support for fleetsync 1. I didn't have any good recordings with the format.

Denny

[Ron Webb]

Just for the fun of it, I created a channel for our simplex search frequency. I told SDRTrunk to decode all the different data and record. I then started the channel. First, since there is no squelch control, it was playing static until I keyed my TK-2180. I heard the chirps of the FleetSync data and blank audio before I released the PTT button. The radio is set to send the fleet/radio ID at the beginning of transmission and fleet/radio ID, along with GPS info at the end of the transmission. As I recorded it, I've trimmed it down to JUST one transmission without the static. If it were to be decoded, it should reveal that my radio is "131-3001" and I'm sending my GPS information to "100-1001" at a data rate of 2400 bps. The NMEA sentence for GPS is essentially JUST lat/long to keep burst short. No data was decoded by SDRTrunk.

[Ron Webb]

The big difference between FleetSync I and FleetSync II is error correction; FleetSync II has error correction while FleetSync I does not. Nevada County started using FleetSync II, as all of their radios were TK-2180 or TK-7180, but both Tahoe-Nordic and the general Placer County SAR units are using TK-2170 portables which do not support FleetSync II. As we want our radios to work with mutual aid, I believe Nevada County changed to FleetSync I, as we've had very good results despite not using error correction. Tahoe-Nordic reported that they have one problematic repeater that is causing issues with our baud rate of 2400 but seems to be fine with 1200... I believe that repeater is about to be replaced, so they told us not to change for that one repeater. Tahoe-Nordic began as an independent SAR group, but has been taken under the umbrella of the Placer County Sheriff's SAR, so we are kind-of the same entity but also different at the same time. They operate out of the North Tahoe sub-station area on the far east side of the county while we operate out of the sheriff headquarters in Auburn, CA, a little west of center in the county.

[sdrtrunk]

I'd like to write a decoder for this (after I finish Phase II).  I'll store this sample for now, but may ask for more samples later, if you don't mind?

Thanks for recording it!

Denny

[Jim LongwoodFL]

I'm using Phase 1 for now as my local area is Phase1. Would this map issue do something with the maps tab? Currently my Map tab displays a grey screen with small clocks all over it spaced about two inches apart.

[DRL-XM43]

The map tab in previous versions at least displayed a map for me - the Phase II version is just a grey screen with clocks all over it. The zoom seems to work but no map.

On Tuesday, March 21, 2017 at 9:31:32 AM UTC-4, chud goo wrote:

[Dave C]

My last version before phase 2 only displayed clocks, no map.

[Jim LongwoodFL]

When I first started using Phase 1 Map tab opened a map but at some random location. It never displayed anything like locations etc. Just some random location. At some point (don't know when) it stopped doing that and just displays the grey screen. Anyway... I was just wondering if this was something Phase 1 or Phase ll could even do and it might someday work.  Heres hoping!! HA! 

[DRL-XM43]

That was about the same for me, however it did let me move the map to my area of interest, I could zoom it and it retained that setting.... until it disappeared :-) perhaps in the future it will work for LRRP or something similar.

[Bernard Nicoll]

Hello, I'm new to SDRTrunk. I installed Alpha on Windows64. No issue with P1&P2 decoding.

Like you, I cannot obtain a map. Everything is greyed out.

I am seing this int eh event Log.

[map tile fetcher-pool-1] ERROR o.j.s.m.AbstractTileFactory - Failed to load a tile at url: http://tile.openstreetmap.org/2/1/1.png, retrying  [111MB/147MB 75%]
java.io.IOException: Server returned HTTP response code: 403 for URL: http://tile.openstreetmap.org/2/1/1.png

That link (openstreetmap...) is VALID. Maybe some SSL issue to review in the code?

--
You received this message because you are subscribed to the Google Groups "sdrtrunk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sdrtrunk+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sdrtrunk/65054a69-d5f8-466d-9873-1af277b96a02%40googlegroups.com.

[Jim LongwoodFL]

There is nothing "wrong" with your SDRTrunk. Just currently  that feature is not available. There are so many other things being worked on, this one has understandably been given low priority.  I was just curious of the status of the "maybe" map feature working when I posted. But enjoy your phase 1 and Phase ll. This is one heck of an awesome program. For approximately $60 you have a very versatile scanning program that can do what $600-$800 scanners do!! Plus more. 

To unsubscribe from this group and stop receiving emails from it, send an email to sdrt...@googlegroups.com.

[Russell Linderer]

The issue is OpenStreetMap redirects http to https which SDRTrunk currently can't handle.  https://github.com/DSheirer/sdrtrunk/issues/570

To unsubscribe from this group and stop receiving emails from it, send an email to sdrt...@googlegroups.com.