Win96 error

milf · #1 (**permalink**) 08-06-2009, 02:39 PM

OK was doing some loading from the database here,and discovered that Win96 is displaying the Entergy system with a Fleetmap.... this is strange as this system has NO fleetmap as it is a Type II Motorola Smartzone, listed as an Omnizone for now till changes are made in the next few weeks. Don, this one is a lil confusing.... glitch?

DonS · #2 (**permalink**) 08-06-2009, 03:22 PM

The RadioReference SOAP call for that system (sid=164) is returning a fleet map. Based on the data returned from RR, Win96 seems to be behaving fine.

milf · #3 (**permalink**) 08-06-2009, 03:30 PM

Hmmm then its a interface glitch.... will let the other admins know.

jblake76 · #4 (**permalink**) 08-06-2009, 05:03 PM

It is doing the same thing with the NJSP with both win96/win500.

DonS · #5 (**permalink**) 08-06-2009, 05:31 PM

Quote:

Originally Posted by jblake76

It is doing the same thing with the NJSP with both win96/win500.

What system? (i.e. what's the "sid=" value in the URL when you look at the system in the RR DB?).

If it's this system: Scanner Frequencies: State of New Jersey Troop A South Trunking System, Various, New Jersey , it's doing the same thing for the same reason.

jblake76 · #6 (**permalink**) 08-06-2009, 06:16 PM

Don I am not saying it is a software issue with win, I am just saying. I am just curious as to why it is doing this now when before the change over it never did.

milf · #7 (**permalink**) 08-06-2009, 07:32 PM

This has been reported on the admin bug reporting server so now all we can do is wait and see how it gets fixed.

milf · #8 (**permalink**) 08-07-2009, 01:25 PM

Per Lindsay- Problem fixed.

DonS · #9 (**permalink**) 08-07-2009, 01:35 PM

Quote:

Originally Posted by milf

Per Lindsay- Problem fixed.

It's fixed for sid=164, but the other system referenced above (sid=141) is still returning "O" (letter OH, not numeral ZERO) for all 8 fleet map entries.

jblake76 · #10 (**permalink**) 08-07-2009, 02:12 PM

So for example for the NJSP it is being entered into my scanner as a fleet map is this ok eventhough this is not a fleet map system? I am new so be nice. I am not trying to get anyone riled up for the weekend.

DonS · #11 (**permalink**) 08-07-2009, 02:22 PM

Quote:

Originally Posted by jblake76

So for example for the NJSP it is being entered into my scanner as a fleet map is this ok eventhough this is not a fleet map system? I am new so be nice. I am not trying to get anyone riled up for the weekend.

With a bad fleet map programmed, your talk groups could be displayed incorrectly.

Until it's fixed in the database, you can go ahead and import into Win96/500/97, then change the fleet map to "Type II" after importing.

In Win96 or Win97, change all of the fleet map entries from "S13" to "S00".

In Win500, select the imported TSYS and click the "Fleet Map" button. In the window that appears, select "Type II" under "Fleet Map Type".

milf · #12 (**permalink**) 08-07-2009, 02:23 PM

No, this messes up the talkgroups. You will have to manually type the entries into your Win96 for this system until the entire bug is fixed. This is a bit of typing, but still a lot simpler than manually programming the scanner. I updated the admin forum so that they know this is a widespread bug. Apparently it affects any of the systems that are Omnizone.

jblake76 · #13 (**permalink**) 08-07-2009, 02:45 PM

Quote:

Originally Posted by DonS

With a bad fleet map programmed, your talk groups could be displayed incorrectly.

Until it's fixed in the database, you can go ahead and import into Win96/500/97, then change the fleet map to "Type II" after importing.

In Win96 or Win97, change all of the fleet map entries from "S13" to "S00".

In Win500, select the imported TSYS and click the "Fleet Map" button. In the window that appears, select "Type II" under "Fleet Map Type".

Thanks for the speedy reply Don & Milf!