Download here: http://gg.gg/uv70e
*Led Edit 2018 Original Software Download Windows 7
*Led Edit 2018 Original Software Download 64-bit
Note 2: You can also do pairing by touching “New paired” button in software ’LED Editor’, “New paired” button is sub button under the “send” button in Main Interface of LED Editor. When open ’LED Editor’ on the phone, it will appear the above interface. Select: it used to decide whether the message be send or not. LEDEditor V10 is a content creation and content management software for LED signs and LED displays, with rich features and options, superior performance and very easy to use interface. LEDEditor V10 supports wide ranges of multimedia formats like video, audio, images and text as well as Word, Excel, and PPT. Led Edit free download - Video Edit Master, Video Edit Magic, Hex Edit Free, and many more programs.
LED Editor is a LED sign software with network capabilities that allows the software to control the LED sign through the network, meaning that the sign can be further away as long as it is connected to the network. The auto-importing and adjustment function in the LED sign software makes it easy to insert media files to the LED sign. New file- use when the first time to edit effects for the new project: Opening- when re-edit, preview, increase or change the effects made,directly open the save path of the original file (you need to find out the save path of the original file, open the. PJB file in the folder) Exiting- exit the edit status, and the software closed.Data management, monitoring, and control software for the Whistler WS1040 and WS1065, GRE PSR-500 and PSR-600, as well as the RS PRO-106, PRO-197, PRO-651, and PRO-652 Digital Trunking Scanners, plus the GRE PSR-310 and PSR-410 Analog Trunking ScannersWin500Remote Monitoring Client FreePocketPC Remote Client FreeVersion 2.08
2015.04.06 12:35 MSTVersion 1.17
2011.01.27 15:18 PSTVersion 1.05
2009.01.27 08:20 PSTDownloadDownloadInfoIMPORTANT: Win500 v1.74 (and later) requires the latest version of the drivers for the USB / Serial programming cable. FTDI, the manufacturer of the chipset used in the GRE/RS programming cable, makes those drivers available here.Note to Linux users: If you need to access the USB/Serial cable as a ’COM port’ under Wine, you can run the Win500_COM.EXE executable. The only difference between it and the Win500.EXE file is how the program accesses the cable (COM port vs. directly to driver).
Whistler has prepared a brief ’Programming Example’ PDF that describes using Win500 and the RadioReference downloads with the WS-1040 and WS-1065 scanners. You can download that PDF here.
Register($30.00)FeaturesWhat’s newFactory V-ScannersSystem requirementsInstallation
PocketPC Remote Monitoring Client
*No support.
*Works like a stripped-down version of the PC version of Win500Client
*It is presumed that you know how to download a .CAB file, put it on your phone, and ’install’ it
*No support! Requirements:
*PocketPC device running Windows Mobile 5.0 or later
*Display format minimum of QVGA (240x320)
*A network connection on the phone (ActiveSync, WiFi, a cellular data plan, etc)
*.NET Compact Framework 3.5. If you don’t have it, you can download/install it from Microsoft Minimalist instructions:
*Copy the .CAB file to your PocketPC device
*Install the .CAB file (i.e. by ’clicking’ on it in File Explorer on the PocketPC)
*Run ’Win500 Remote Client’ from the Programs menuDevelopers: A description of the Win500 Remote Protocol is available here. It describes the packet formats exchanged by my Win500 application and PocketPC client app. It should provide sufficient information for someone ’ordinarily skilled in the art’ to create a client app for their desired platform.
This release is the result of some ’goofing around’ over a weekend with some new development tools. My ’day job’ has some pretty hectic deadlines approaching, so I won’t be able to spend much time adding new features, fixing any found problems, etc. (this is why there is currently ’no support’!).
Here’s a list of PocketPC devices that have been tested so far. Some are based on my own testing, while others are based on user reports:
*HTC Touch Pro (’Raphael’), Windows Mobile 6.1, Sprint/WiFi
*HTC 6800 (’Mogul’), Windows Mobile 6.1, Sprint
*HTC 6900 (’Tilt’), Windows Mobile 6.0
*HTC Imagio, WM 6.5, Verizon
*Dell Axim X51v, (presumed) Windows Mobile 5, unknown network type Here’s how it looks on some sample PPC devices. Most color settings (especially buttons and backgrounds within the Win500Client app) are user-configured:
HTC Touch ProHTC Touch ProHTC 6800
Win500 Features
*Download from and upload to the PSR-500 and PSR-600, including V-Scanner folders
*Edit Trunking Systems (TSYS), Talkgroups (TGRP), Conventional Channels (CONV), Search Ranges (SRCH), and Spectrum Sweeper (SWPR) objects, including full control of their ’Object ID’ values, with cut/copy/paste support
*Edit all of the items that appear in the GLOB and FUNC+GLOB menus on the radio, plus Weather settings
*RadioReference.com Web Import for trunking systems and their talkgroups, as well as conventional channels
*Maintain ’Notes’ for every object. These won’t, of course, be sent to the scanner, but they allow you to add long, descriptive text to each object as displayed in Win500.
*Import P96 and P97 files, as well as reading directly from the PRO-96, PRO-97, PRO-2096, and PRO-2055 scanners. Support for PRO-92/2067, PRO-93/2053, and PRO-95 scanners is intentionally omitted, as data from those radios can be converted to P96 files via the ’freeware’ Win92, Win93, Win95, and WinXX Data Converter programs.
*Monitoring and contol of the PSR-500 and PSR-600, with internal updating of Hit Counts and auto-creation of new TGRPs when Wildcards are hit while scanning.
*Remote Monitoring and Control with Streaming Audio over IP. The server side continues full activity logging, recording, hit count updates, TGRP auto-creation, etc., while the client side gets LCD data, status information, and audio.
The server can be configured so that it is not controllable. The client can be configured to mute received audio (allowing you to monitor several radios at once via multiple instances of Win500, but only listen to a subset of them).
The client and server can also send simple text messages to each other; the text will appear in the ’logging’ list box (TIP: don’t use the mouse to click the ’Send’ button; as long as your fingers are on the keyboard, press TAB then SPACE to ’click’ that button).
Please post questions and/or look for answers about the Remote feature on the RadioReference.com Software forum, instead of asking via email or on other groups/forums. That RR.com forum will have the largest cache of information and will reach the largest number of Win500 users. If you’re not a RadioReference.com member, joining is easy and free.
*A Standalone Remote Monitoring Client is also available for download. It provides the features of the main Win500 Monitor / Control tab - those that are available when connecting to a Win500 Server as a ’Client’.
*Activity logging for all objects (to each object’s ’Notes’ field and/or a separate log file)
*Audio Recording for all objects, with an optional time limit per ’hit’. Recording is enabled/disabled per object, with an additional ’master’ enable on the Monitor/Control tab
*File contents not limited by radio’s memory size. You can create ’P500’ files with up to 100,000 objects. Of course, before uploading to the radio, you must ’trim’ such files so that they’ll fit in the radio. While this feature is intended primarily for managing large collections of data that can then be copied/pasted into smaller, radio-compatible files, it can also be used to copy/paste into a file that’s ’nearly full’ without overflowing, prior to deleting some items.
*Batch editing of various object properties (scan list membership, alert settings, attenuation, lockout, and delay flags, etc.)
*Change ’Object IDs’ at will, including incremental assignment of IDs for any number of selected objects
*Sort objects by:
*Object ID
*Object Type
*Alpha Tag
*Hit Counts
*Frequency
*Talkgroup ID
*Trunking System Type
*Priority flag
*Attenuation flag
*Delay flag
*Lockout flag
*LED Color
*Import and export ’.BIN’ files compatible with the ’PSR-500/600 Demo’ program included with the radio.
*Text-based copy/paste for CONV and TGRP objects, to create new objects from tab-delimited text from external data sources (e.g. Excel generates tab-delimited text when you ’Copy’ a set of rows and columns).
*Configure columns in CONV, TGRP, and SRCH/SWPR ’grids’, showing any object data in any order you wish. Right-clicking on column headers in those grids gives options for deleting the current column or adding any that are not already displayed.
Planned Features
Things that will be added soon include (but are not necessarily limited to):
*A ’Help’ file
*CSV import of CONV, TSYS, and TGRP objects.
*Additional enhancements to per-object data (perhaps)
System Requirements
In order to run Win500, you’ll need the following:
*A copy of the Win500 program
*A PSR-500 or PSR-600 Scanner, or the RadioShack equivalents: PRO-106 or PRO-197
*The blue GRE USB Scanner Programming cable that came in the box with your scanner. If using a RadioShack scanner, you’ll need to buy a cable: either the GRE cable or RadioShack’s catalog #20-047. Older ’serial’ cables will not work with these radios.
*A PC running Windows 2000 or later (i.e. 2000, XP, Vista, 7). Earlier versions of Windows, such as 95, 98, and Me, are not supported.
Installation
Win500 does not use an ’installer’ like many Windows programs. You merely download a ZIP file that contains the program and decompress it to a new folder on your machine. Uninstallation merely requires that you delete the program files from your machine.
It is suggested that you use a dedicated ’unzipper’ like WinZip, as opposed to the unzipping utilities that are built into various versions of Windows. In particular, you CANNOT merely view the ZIP file in Windows Explorer, ’open’ it in Explorer, and run Win500 from there. You must explicitly extract the contents of the ZIP file.
Factory V-Scanner Contents
Here are the factory V-Scanner contents of my PSR-500, retrieved from the radio and saved as Win500 ’P500’ files
Version 2.08 2015.04.06 12:35 (GMT -0700)
*Fixed HEX input of talkgroup IDs.
Version 2.07 2014.04.01 16:35 (GMT -0700)
*Added ’default model’ selection when creating a new .P500 file. Note that this only affects the ’Welcome Text’ on the General Settings tab; since you’re almost certainly going to change this field from the default, it really doesn’t matter what you select here. That is, you can just click OK (or press ENTER) and edit the field the way you want.
Version 2.06 2011.12.19 07:35 (GMT -0700)
*Added support for new system flavor ’TDMA’ in RR trunked imports.
Version 2.05 2011.11.07 08:00 (GMT -0700)
*In trunked RR imports, added support for the new ’rfss’ field in P25 sites, based on the current version (9) of the RR API. It appears that data that used to be in the sites’ ’zoneNumber’ field has been moved to the new ’rfss’ field.
Version 2.04 2011.09.28 10:25 (GMT -0600)
*Added support for ’Nationwide’ frequencies in conventional imports, based on the current version (9) of the RR API.
Version 2.03 2011.09.21 11:46 (GMT -0600)
*In trunked Web Imports, added county name to the site name (display purposes only). This is to address recent RRDB edits where sites that once had redundant county name text now just have a site name - the county info is still present in the site records, and Win500 now uses that info.
Version 2.02 2011.03.30 08:18 (GMT -0700)
*Added horizontal scroll bar to ’log entries’ listbox on Monitor/Control tab.
Version 2.01 2011.03.16 13:18 (GMT -0700)
*Fixed ’squelch mode’ problem when downloading from PSR-310/410 (was changing CONV objects whose mode was ’Search’ to ’NAC’)
Version 2.00 / Remote Client Version 1.17 2011.01.27 15:28 (GMT -0800)
*Fixed PSR-310 Monitor/Control functions (mostly related to larger LCD). The Win500 Monitor/Control tab as a new checkbox under the ’START’ button. This item must be checked if, and only if, you’re connected to a PSR-310 or PSR-410.
*The client app automatically detects the type of data it’s receiving, so there’s no user intervention needed
*IMPORTANT: This new version requires CPU firmware version 1.1 in the PSR-310/410. If necessary, you can update your scanner via the U1.1 file available at GRE America’s Support Page
*The Windows Mobile client app is not yet compatible with the PSR-310/410. It will only work with the PSR-500 family of scanners
Version 1.99 2011.01.12 06:53 (GMT -0800)
*Fixed PSR-310 upload speed
Version 1.98 2010.12.21 14:00 (GMT -0800)
*Fixed P25 RR imports for FDMA/TDMA systems (e.g. PG County, MD)
Version 1.97 2010.12.15 11:51 (GMT -0800)
*Added ’Font’ control to General Settings tab for PSR-310/410.
Version 1.96 2010.12.08 07:25 (GMT -0800)
*Minor bug fix.
Version 1.95 2010.11.09 16:35 (GMT -0800)
*Added support for the PSR-310 and PSR-410 scanners.
Version 1.94 2010.05.07 10:50 (GMT -0700)
*Changed handling of imported fleet map data to match peculiar RadioReference.com convention.
Version 1.93 2010.04.05 13:23 (GMT -0700)
*Re-wrote SOAP interface to RR. This should improve import times. This version no longer requires my RRLib.DLL file or Microsoft’s .NET runtime.
*Fixed double download of trunked systems
*Added progress indication to trunked system download from RR
*Added zone number to site info in RR download and sorted site list by zone/site
*Fixed mismatch between Win500’s and scanner’s alpha tags (embedded NUL characters)
Version 1.92 2010.01.20 06:45 (GMT -0800)
*Fixed bug in RadioReference imports where Win500 was not correctly importing system-wide trunking tables
Version 1.91 2009.12.16 09:48 (GMT -0800)
*Added support for site-specific trunking tables in RR downloads
*Sped up trunked system downloads from RR (e.g. I used to see ~10 minutes for MPSCS, I now see ~3 minutes).
Version 1.90 2009.12.02 14:26 (GMT -0800)
*Fixed NAC import in RR web interface.
Version 1.89 2009.09.15 15:15 (GMT -0700)
*Speed enhancements to RR imports.
Version 1.88 2009.09.03 10:49 (GMT -0700)
*Changes to address duplicate private TGRPs being created in the Monitor/Control mode.
Version 1.87 2009.08.22 13:25 (GMT -0700)
*Fixed ’bad trunking table’ warning when importing some P25 systems
*Accommodated RR’s changes to ’County’ vs. ’City’
Version 1.86 2009.08.03 06:40 (GMT -0700)
*Fixed selection problems in RR import ’trees’.
Version 1.85 2009.08.01 14:52 (GMT -0700)
*Added handling for RR DB’s ’splinter’ and ’rebanded’ flags.
Version 1.84 2009.07.27 15:25 (GMT -0700)
*Fixed RRLib.dll to correctly import some Mot fleetmaps.
Version 1.83 2009.07.27 12:36 (GMT -0700)
*Modified RadioReference.com imports to use the SOAP interface.
Version 1.82 2009.07.01 13:15 (GMT -0700)
*Fixed extra carraige returns in activity log
Version 1.81 2009.05.01 09:26 (GMT -0700)
*Minor bug fixes
Remote Client Version 1.16 2009.02.23 08:37 (GMT -0800)
*Changed default volume setting to 100% from 0%
Remote Client Version 1.15 2009.02.09 12:10 (GMT -0800)
*Added copy of ’L/OUT’ button next to LCD, so the main window can be shrunken but still have access to that button
Remote Client Version 1.14 2009.02.07 16:47 (GMT -0800)
*Added volume control
Version 1.80 2009.02.04 15:50 (GMT -0800)
*Changed the audio spectrum analyzer ’toy’:
*Fixed a bonehead mistake in log scale. Each grid line is 6dB.
*Moved peak detect indication into main window
Version 1.79 2009.02.03 13:57 (GMT -0800)
*Changed the audio spectrum analyzer ’toy’:
*Amplitudes are now shown in a logarithmic scale. Each grid line is 3dB.
*Added grid lines (horizontal axis) at 200Hz intervals
*Removed the ’auto scale’ (right-click) option, since it’s not needed with a log vertical scale
*Speed increases / CPU usage decreases
*The analyzer’s ’tone detect’ (shown in its title bar) looks for a peak that is 3dB above any other peak, with a little hysteresis once it’s found one
Version 1.78 2009.02.02 14:17 (GMT -0800)
*Changed the ’uncompressed’ audio: streamed data is sent at 8000 samples per second, 8 bits per sample. Files are recorded at 16000 samples per second, 16 bits per sample.
*Some modifications to the ’toy’ introduced in version 1.77:
*Cleaned up how the data is fit to the window
*Left-clicking in the window toggles between a bar graph and a line plot (defaults to line plot).
*Right-clicking in the window toggles auto-scaling on/off (defaults to off). If auto-scaling is on, the plot is scaled to fit within the window
*Single ’tones’ detected are shown in the window’s title bar.
*Drastically reduced CPU usage
Version 1.77 2009.01.30 14:48 (GMT -0800)
*Added a new ’toy’ to the Monitor/Control tab. Still thinking of uses for it (I already know about the obvious one - trying to think of others).
PocketPC Client Version 1.05 2009.01.27 08:20 (GMT -0800)
*Changed how the client ’looks up’ addresses at connection time.
Version 1.76 2009.01.26 06:35 (GMT -0800)
*Fixed problem where having a bad log directory selected in the Monitor/Control tab would force you to stop and re-start the program before you could start the monitoring function.
Version 1.75 2009.01.25 15:27 (GMT -0800)
*Worked-around a problem with the FTDI drivers where opening multiple cables in a particular order could cause problems.
Version 1.74 2009.01.24 18:27 (GMT -0800)
*Removed all ’COM port’ nonsense from the program. Win500 now automatically finds a single connected USB-Scanner Programming Cable, and will prompt you to choose between cables if you have more than one connected (with the option to remember which cable was selected).
You may need to update your cable’s drivers to use this new version. If that’s required, the program will suggest it. You can get the new FTDI drivers from the FTDI web site.
Remote Client Version 1.13 2009.01.23 08:35 (GMT -0800)
*Fixed crash that could occur when server streams uncompressed audio.
Version 1.73 / Remote Client Version 1.12 / PocketPC Client Version 1.04 2009.01.22 11:30 (GMT -0800)
*In the Monitor/Control tab, added option to compress audio or not (prior versions always compressed audio). Compression is turned on by default. If you clear the new checkbox, and you use (or allow) remote connections to the Win500 server, any clients connecting will need to upgrade their client app(s).
Turning off compression will increase bandwidth consumption from ~2300 to ~8700 bytes per second (from ~18400 to ~70000 bits per second). You may want to take that into consideration if allowing multiple client connections via the TCPMux app.
Remote Client Version 1.11 2009.01.20 07:50 (GMT -0800)
*Fixed memory leak introduced in 1.10.
Remote Client
https://diarynote-jp.indered.space
*Led Edit 2018 Original Software Download Windows 7
*Led Edit 2018 Original Software Download 64-bit
Note 2: You can also do pairing by touching “New paired” button in software ’LED Editor’, “New paired” button is sub button under the “send” button in Main Interface of LED Editor. When open ’LED Editor’ on the phone, it will appear the above interface. Select: it used to decide whether the message be send or not. LEDEditor V10 is a content creation and content management software for LED signs and LED displays, with rich features and options, superior performance and very easy to use interface. LEDEditor V10 supports wide ranges of multimedia formats like video, audio, images and text as well as Word, Excel, and PPT. Led Edit free download - Video Edit Master, Video Edit Magic, Hex Edit Free, and many more programs.
LED Editor is a LED sign software with network capabilities that allows the software to control the LED sign through the network, meaning that the sign can be further away as long as it is connected to the network. The auto-importing and adjustment function in the LED sign software makes it easy to insert media files to the LED sign. New file- use when the first time to edit effects for the new project: Opening- when re-edit, preview, increase or change the effects made,directly open the save path of the original file (you need to find out the save path of the original file, open the. PJB file in the folder) Exiting- exit the edit status, and the software closed.Data management, monitoring, and control software for the Whistler WS1040 and WS1065, GRE PSR-500 and PSR-600, as well as the RS PRO-106, PRO-197, PRO-651, and PRO-652 Digital Trunking Scanners, plus the GRE PSR-310 and PSR-410 Analog Trunking ScannersWin500Remote Monitoring Client FreePocketPC Remote Client FreeVersion 2.08
2015.04.06 12:35 MSTVersion 1.17
2011.01.27 15:18 PSTVersion 1.05
2009.01.27 08:20 PSTDownloadDownloadInfoIMPORTANT: Win500 v1.74 (and later) requires the latest version of the drivers for the USB / Serial programming cable. FTDI, the manufacturer of the chipset used in the GRE/RS programming cable, makes those drivers available here.Note to Linux users: If you need to access the USB/Serial cable as a ’COM port’ under Wine, you can run the Win500_COM.EXE executable. The only difference between it and the Win500.EXE file is how the program accesses the cable (COM port vs. directly to driver).
Whistler has prepared a brief ’Programming Example’ PDF that describes using Win500 and the RadioReference downloads with the WS-1040 and WS-1065 scanners. You can download that PDF here.
Register($30.00)FeaturesWhat’s newFactory V-ScannersSystem requirementsInstallation
PocketPC Remote Monitoring Client
*No support.
*Works like a stripped-down version of the PC version of Win500Client
*It is presumed that you know how to download a .CAB file, put it on your phone, and ’install’ it
*No support! Requirements:
*PocketPC device running Windows Mobile 5.0 or later
*Display format minimum of QVGA (240x320)
*A network connection on the phone (ActiveSync, WiFi, a cellular data plan, etc)
*.NET Compact Framework 3.5. If you don’t have it, you can download/install it from Microsoft Minimalist instructions:
*Copy the .CAB file to your PocketPC device
*Install the .CAB file (i.e. by ’clicking’ on it in File Explorer on the PocketPC)
*Run ’Win500 Remote Client’ from the Programs menuDevelopers: A description of the Win500 Remote Protocol is available here. It describes the packet formats exchanged by my Win500 application and PocketPC client app. It should provide sufficient information for someone ’ordinarily skilled in the art’ to create a client app for their desired platform.
This release is the result of some ’goofing around’ over a weekend with some new development tools. My ’day job’ has some pretty hectic deadlines approaching, so I won’t be able to spend much time adding new features, fixing any found problems, etc. (this is why there is currently ’no support’!).
Here’s a list of PocketPC devices that have been tested so far. Some are based on my own testing, while others are based on user reports:
*HTC Touch Pro (’Raphael’), Windows Mobile 6.1, Sprint/WiFi
*HTC 6800 (’Mogul’), Windows Mobile 6.1, Sprint
*HTC 6900 (’Tilt’), Windows Mobile 6.0
*HTC Imagio, WM 6.5, Verizon
*Dell Axim X51v, (presumed) Windows Mobile 5, unknown network type Here’s how it looks on some sample PPC devices. Most color settings (especially buttons and backgrounds within the Win500Client app) are user-configured:
HTC Touch ProHTC Touch ProHTC 6800
Win500 Features
*Download from and upload to the PSR-500 and PSR-600, including V-Scanner folders
*Edit Trunking Systems (TSYS), Talkgroups (TGRP), Conventional Channels (CONV), Search Ranges (SRCH), and Spectrum Sweeper (SWPR) objects, including full control of their ’Object ID’ values, with cut/copy/paste support
*Edit all of the items that appear in the GLOB and FUNC+GLOB menus on the radio, plus Weather settings
*RadioReference.com Web Import for trunking systems and their talkgroups, as well as conventional channels
*Maintain ’Notes’ for every object. These won’t, of course, be sent to the scanner, but they allow you to add long, descriptive text to each object as displayed in Win500.
*Import P96 and P97 files, as well as reading directly from the PRO-96, PRO-97, PRO-2096, and PRO-2055 scanners. Support for PRO-92/2067, PRO-93/2053, and PRO-95 scanners is intentionally omitted, as data from those radios can be converted to P96 files via the ’freeware’ Win92, Win93, Win95, and WinXX Data Converter programs.
*Monitoring and contol of the PSR-500 and PSR-600, with internal updating of Hit Counts and auto-creation of new TGRPs when Wildcards are hit while scanning.
*Remote Monitoring and Control with Streaming Audio over IP. The server side continues full activity logging, recording, hit count updates, TGRP auto-creation, etc., while the client side gets LCD data, status information, and audio.
The server can be configured so that it is not controllable. The client can be configured to mute received audio (allowing you to monitor several radios at once via multiple instances of Win500, but only listen to a subset of them).
The client and server can also send simple text messages to each other; the text will appear in the ’logging’ list box (TIP: don’t use the mouse to click the ’Send’ button; as long as your fingers are on the keyboard, press TAB then SPACE to ’click’ that button).
Please post questions and/or look for answers about the Remote feature on the RadioReference.com Software forum, instead of asking via email or on other groups/forums. That RR.com forum will have the largest cache of information and will reach the largest number of Win500 users. If you’re not a RadioReference.com member, joining is easy and free.
*A Standalone Remote Monitoring Client is also available for download. It provides the features of the main Win500 Monitor / Control tab - those that are available when connecting to a Win500 Server as a ’Client’.
*Activity logging for all objects (to each object’s ’Notes’ field and/or a separate log file)
*Audio Recording for all objects, with an optional time limit per ’hit’. Recording is enabled/disabled per object, with an additional ’master’ enable on the Monitor/Control tab
*File contents not limited by radio’s memory size. You can create ’P500’ files with up to 100,000 objects. Of course, before uploading to the radio, you must ’trim’ such files so that they’ll fit in the radio. While this feature is intended primarily for managing large collections of data that can then be copied/pasted into smaller, radio-compatible files, it can also be used to copy/paste into a file that’s ’nearly full’ without overflowing, prior to deleting some items.
*Batch editing of various object properties (scan list membership, alert settings, attenuation, lockout, and delay flags, etc.)
*Change ’Object IDs’ at will, including incremental assignment of IDs for any number of selected objects
*Sort objects by:
*Object ID
*Object Type
*Alpha Tag
*Hit Counts
*Frequency
*Talkgroup ID
*Trunking System Type
*Priority flag
*Attenuation flag
*Delay flag
*Lockout flag
*LED Color
*Import and export ’.BIN’ files compatible with the ’PSR-500/600 Demo’ program included with the radio.
*Text-based copy/paste for CONV and TGRP objects, to create new objects from tab-delimited text from external data sources (e.g. Excel generates tab-delimited text when you ’Copy’ a set of rows and columns).
*Configure columns in CONV, TGRP, and SRCH/SWPR ’grids’, showing any object data in any order you wish. Right-clicking on column headers in those grids gives options for deleting the current column or adding any that are not already displayed.
Planned Features
Things that will be added soon include (but are not necessarily limited to):
*A ’Help’ file
*CSV import of CONV, TSYS, and TGRP objects.
*Additional enhancements to per-object data (perhaps)
System Requirements
In order to run Win500, you’ll need the following:
*A copy of the Win500 program
*A PSR-500 or PSR-600 Scanner, or the RadioShack equivalents: PRO-106 or PRO-197
*The blue GRE USB Scanner Programming cable that came in the box with your scanner. If using a RadioShack scanner, you’ll need to buy a cable: either the GRE cable or RadioShack’s catalog #20-047. Older ’serial’ cables will not work with these radios.
*A PC running Windows 2000 or later (i.e. 2000, XP, Vista, 7). Earlier versions of Windows, such as 95, 98, and Me, are not supported.
Installation
Win500 does not use an ’installer’ like many Windows programs. You merely download a ZIP file that contains the program and decompress it to a new folder on your machine. Uninstallation merely requires that you delete the program files from your machine.
It is suggested that you use a dedicated ’unzipper’ like WinZip, as opposed to the unzipping utilities that are built into various versions of Windows. In particular, you CANNOT merely view the ZIP file in Windows Explorer, ’open’ it in Explorer, and run Win500 from there. You must explicitly extract the contents of the ZIP file.
Factory V-Scanner Contents
Here are the factory V-Scanner contents of my PSR-500, retrieved from the radio and saved as Win500 ’P500’ files
Version 2.08 2015.04.06 12:35 (GMT -0700)
*Fixed HEX input of talkgroup IDs.
Version 2.07 2014.04.01 16:35 (GMT -0700)
*Added ’default model’ selection when creating a new .P500 file. Note that this only affects the ’Welcome Text’ on the General Settings tab; since you’re almost certainly going to change this field from the default, it really doesn’t matter what you select here. That is, you can just click OK (or press ENTER) and edit the field the way you want.
Version 2.06 2011.12.19 07:35 (GMT -0700)
*Added support for new system flavor ’TDMA’ in RR trunked imports.
Version 2.05 2011.11.07 08:00 (GMT -0700)
*In trunked RR imports, added support for the new ’rfss’ field in P25 sites, based on the current version (9) of the RR API. It appears that data that used to be in the sites’ ’zoneNumber’ field has been moved to the new ’rfss’ field.
Version 2.04 2011.09.28 10:25 (GMT -0600)
*Added support for ’Nationwide’ frequencies in conventional imports, based on the current version (9) of the RR API.
Version 2.03 2011.09.21 11:46 (GMT -0600)
*In trunked Web Imports, added county name to the site name (display purposes only). This is to address recent RRDB edits where sites that once had redundant county name text now just have a site name - the county info is still present in the site records, and Win500 now uses that info.
Version 2.02 2011.03.30 08:18 (GMT -0700)
*Added horizontal scroll bar to ’log entries’ listbox on Monitor/Control tab.
Version 2.01 2011.03.16 13:18 (GMT -0700)
*Fixed ’squelch mode’ problem when downloading from PSR-310/410 (was changing CONV objects whose mode was ’Search’ to ’NAC’)
Version 2.00 / Remote Client Version 1.17 2011.01.27 15:28 (GMT -0800)
*Fixed PSR-310 Monitor/Control functions (mostly related to larger LCD). The Win500 Monitor/Control tab as a new checkbox under the ’START’ button. This item must be checked if, and only if, you’re connected to a PSR-310 or PSR-410.
*The client app automatically detects the type of data it’s receiving, so there’s no user intervention needed
*IMPORTANT: This new version requires CPU firmware version 1.1 in the PSR-310/410. If necessary, you can update your scanner via the U1.1 file available at GRE America’s Support Page
*The Windows Mobile client app is not yet compatible with the PSR-310/410. It will only work with the PSR-500 family of scanners
Version 1.99 2011.01.12 06:53 (GMT -0800)
*Fixed PSR-310 upload speed
Version 1.98 2010.12.21 14:00 (GMT -0800)
*Fixed P25 RR imports for FDMA/TDMA systems (e.g. PG County, MD)
Version 1.97 2010.12.15 11:51 (GMT -0800)
*Added ’Font’ control to General Settings tab for PSR-310/410.
Version 1.96 2010.12.08 07:25 (GMT -0800)
*Minor bug fix.
Version 1.95 2010.11.09 16:35 (GMT -0800)
*Added support for the PSR-310 and PSR-410 scanners.
Version 1.94 2010.05.07 10:50 (GMT -0700)
*Changed handling of imported fleet map data to match peculiar RadioReference.com convention.
Version 1.93 2010.04.05 13:23 (GMT -0700)
*Re-wrote SOAP interface to RR. This should improve import times. This version no longer requires my RRLib.DLL file or Microsoft’s .NET runtime.
*Fixed double download of trunked systems
*Added progress indication to trunked system download from RR
*Added zone number to site info in RR download and sorted site list by zone/site
*Fixed mismatch between Win500’s and scanner’s alpha tags (embedded NUL characters)
Version 1.92 2010.01.20 06:45 (GMT -0800)
*Fixed bug in RadioReference imports where Win500 was not correctly importing system-wide trunking tables
Version 1.91 2009.12.16 09:48 (GMT -0800)
*Added support for site-specific trunking tables in RR downloads
*Sped up trunked system downloads from RR (e.g. I used to see ~10 minutes for MPSCS, I now see ~3 minutes).
Version 1.90 2009.12.02 14:26 (GMT -0800)
*Fixed NAC import in RR web interface.
Version 1.89 2009.09.15 15:15 (GMT -0700)
*Speed enhancements to RR imports.
Version 1.88 2009.09.03 10:49 (GMT -0700)
*Changes to address duplicate private TGRPs being created in the Monitor/Control mode.
Version 1.87 2009.08.22 13:25 (GMT -0700)
*Fixed ’bad trunking table’ warning when importing some P25 systems
*Accommodated RR’s changes to ’County’ vs. ’City’
Version 1.86 2009.08.03 06:40 (GMT -0700)
*Fixed selection problems in RR import ’trees’.
Version 1.85 2009.08.01 14:52 (GMT -0700)
*Added handling for RR DB’s ’splinter’ and ’rebanded’ flags.
Version 1.84 2009.07.27 15:25 (GMT -0700)
*Fixed RRLib.dll to correctly import some Mot fleetmaps.
Version 1.83 2009.07.27 12:36 (GMT -0700)
*Modified RadioReference.com imports to use the SOAP interface.
Version 1.82 2009.07.01 13:15 (GMT -0700)
*Fixed extra carraige returns in activity log
Version 1.81 2009.05.01 09:26 (GMT -0700)
*Minor bug fixes
Remote Client Version 1.16 2009.02.23 08:37 (GMT -0800)
*Changed default volume setting to 100% from 0%
Remote Client Version 1.15 2009.02.09 12:10 (GMT -0800)
*Added copy of ’L/OUT’ button next to LCD, so the main window can be shrunken but still have access to that button
Remote Client Version 1.14 2009.02.07 16:47 (GMT -0800)
*Added volume control
Version 1.80 2009.02.04 15:50 (GMT -0800)
*Changed the audio spectrum analyzer ’toy’:
*Fixed a bonehead mistake in log scale. Each grid line is 6dB.
*Moved peak detect indication into main window
Version 1.79 2009.02.03 13:57 (GMT -0800)
*Changed the audio spectrum analyzer ’toy’:
*Amplitudes are now shown in a logarithmic scale. Each grid line is 3dB.
*Added grid lines (horizontal axis) at 200Hz intervals
*Removed the ’auto scale’ (right-click) option, since it’s not needed with a log vertical scale
*Speed increases / CPU usage decreases
*The analyzer’s ’tone detect’ (shown in its title bar) looks for a peak that is 3dB above any other peak, with a little hysteresis once it’s found one
Version 1.78 2009.02.02 14:17 (GMT -0800)
*Changed the ’uncompressed’ audio: streamed data is sent at 8000 samples per second, 8 bits per sample. Files are recorded at 16000 samples per second, 16 bits per sample.
*Some modifications to the ’toy’ introduced in version 1.77:
*Cleaned up how the data is fit to the window
*Left-clicking in the window toggles between a bar graph and a line plot (defaults to line plot).
*Right-clicking in the window toggles auto-scaling on/off (defaults to off). If auto-scaling is on, the plot is scaled to fit within the window
*Single ’tones’ detected are shown in the window’s title bar.
*Drastically reduced CPU usage
Version 1.77 2009.01.30 14:48 (GMT -0800)
*Added a new ’toy’ to the Monitor/Control tab. Still thinking of uses for it (I already know about the obvious one - trying to think of others).
PocketPC Client Version 1.05 2009.01.27 08:20 (GMT -0800)
*Changed how the client ’looks up’ addresses at connection time.
Version 1.76 2009.01.26 06:35 (GMT -0800)
*Fixed problem where having a bad log directory selected in the Monitor/Control tab would force you to stop and re-start the program before you could start the monitoring function.
Version 1.75 2009.01.25 15:27 (GMT -0800)
*Worked-around a problem with the FTDI drivers where opening multiple cables in a particular order could cause problems.
Version 1.74 2009.01.24 18:27 (GMT -0800)
*Removed all ’COM port’ nonsense from the program. Win500 now automatically finds a single connected USB-Scanner Programming Cable, and will prompt you to choose between cables if you have more than one connected (with the option to remember which cable was selected).
You may need to update your cable’s drivers to use this new version. If that’s required, the program will suggest it. You can get the new FTDI drivers from the FTDI web site.
Remote Client Version 1.13 2009.01.23 08:35 (GMT -0800)
*Fixed crash that could occur when server streams uncompressed audio.
Version 1.73 / Remote Client Version 1.12 / PocketPC Client Version 1.04 2009.01.22 11:30 (GMT -0800)
*In the Monitor/Control tab, added option to compress audio or not (prior versions always compressed audio). Compression is turned on by default. If you clear the new checkbox, and you use (or allow) remote connections to the Win500 server, any clients connecting will need to upgrade their client app(s).
Turning off compression will increase bandwidth consumption from ~2300 to ~8700 bytes per second (from ~18400 to ~70000 bits per second). You may want to take that into consideration if allowing multiple client connections via the TCPMux app.
Remote Client Version 1.11 2009.01.20 07:50 (GMT -0800)
*Fixed memory leak introduced in 1.10.
Remote Client
https://diarynote-jp.indered.space
コメント