Official PSREdit Software thread

[rfmanning]

PSRedit wont recognize COM14

I downloaded PSRedit and tried to use it with my PSR-500. The software won't recognize the com port my cable uses. Other software finds the cable just fine. Any ideas?

Bob

 

[mikey60]

I downloaded PSRedit and tried to use it with my PSR-500. The software won't recognize the com port my cable uses. Other software finds the cable just fine. Any ideas?

Bob

I've had other reports on this well, but have yet to find a cause for it. I'll look at the code again to see if I can find anything, but it doesn't happen here.

Mike

 

[iMONITOR]

I downloaded PSRedit and tried to use it with my PSR-500. The software won't recognize the com port my cable uses. Other software finds the cable just fine. Any ideas?

Bob

COM14??? I'm curious, how did you end up way out there?

 

[DonS]

COM14??? I'm curious, how did you end up way out there?

A few possible ways (all of which are in effect on my primary machine):
1. He may have set it explicitly via Device Manager
2. He may have lots of 'USB serial converters', each with its own COM port #
3. He and/or Windows may have created a bunch of virtual COM ports for things like Bluetooth, "network serial adapters", etc.

 

[fmon]

Mike,

If DSPDump is set to yes, the scanner will not download to PSREdit 1.07. It will with current Win500.

 

[mikey60]

Mike,

If DSPDump is set to yes, the scanner will not download to PSREdit 1.07. It will with current Win500.

Ok, I'll look into that... Probably a timing issue of some kind. What kind of error do you see?

Mike

 

[fmon]

Mike, I just tried it again with empty (Untitled.bin) and it works ok. I can re download to the same unsaved untitled.bin also, however, with open saved .bin it will fail. The transition bar in software will go to 4 or 5% and stall for a few seconds then a dialog pop up reads 'Transfer time out', Ok button available. Please make sure USB is connected and try again. Scanner display holds on 'Waiting start' with Cancl above F1

Clicking Ok in the dialog frees up the software. Pressing F1 reboots the scanner. Neither software or scanner appear to be corrupted by failed operation. Software does offer the unsaved nag with the 4% attempt.

 

[letarotor]

Program changing LTR frequencies

Geeze, please quit moving these threads around.

I'm having a problem with the software changing UHF LTR frequencies in the program. I entered the freqs into the program, and apparently after closing and re-opening the program at a future time it changed a bunch of frequencies in multiple UHF LTR frequencies, then wrote those changes to the radio. For example it changed 482.7750 to 482.774375, 452.8250 to 452.824375, 452.2000 to 452.199375. It didn't do the same thing to each frequency in each system, just a few at random. Any ideas???

I've also run into a problem with Type I MOT talkgroups. I was able to transfer a hybrid system from my PRO-96 into the PSR-Edit program and it wrote the type I talkgroups properly into the PSR-500 but the groups are displayed incorrectly in the program, for example groups 001-01 thru 3 are displayed as 001-04 and if I try to change them in the program it writes 002-00.

Mark

 

[mikey60]

Mike, I just tried it again with empty (Untitled.bin) and it works ok. I can re download to the same unsaved untitled.bin also, however, with open saved .bin it will fail. The transition bar in software will go to 4 or 5% and stall for a few seconds then a dialog pop up reads 'Transfer time out', Ok button available. Please make sure USB is connected and try again. Scanner display holds on 'Waiting start' with Cancl above F1

Clicking Ok in the dialog frees up the software. Pressing F1 reboots the scanner. Neither software or scanner appear to be corrupted by failed operation. Software does offer the unsaved nag with the 4% attempt.

The next version should correct this. It's a timing issue with the data coming in.

Mike

 

[mikey60]

Geeze, please quit moving these threads around.

I'm having a problem with the software changing UHF LTR frequencies in the program. I entered the freqs into the program, and apparently after closing and re-opening the program at a future time it changed a bunch of frequencies in multiple UHF LTR frequencies, then wrote those changes to the radio. For example it changed 482.7750 to 482.774375, 452.8250 to 452.824375, 452.2000 to 452.199375. It didn't do the same thing to each frequency in each system, just a few at random. Any ideas???

I can't reproduce this in the last release. Are you using 1.07?

I've also run into a problem with Type I MOT talkgroups. I was able to transfer a hybrid system from my PRO-96 into the PSR-Edit program and it wrote the type I talkgroups properly into the PSR-500 but the groups are displayed incorrectly in the program, for example groups 001-01 thru 3 are displayed as 001-04 and if I try to change them in the program it writes 002-00.

Can you email the p96 file that has this conversion issue to me? support@psredit.com will work for that.

Thanks,
Mike

 

[rfmanning]

I need to learn to find my way around this forum. I just looked and sure enough ports 1-13 were in use, according to device manager. Its probably all the other gadgets I've connected to the USB posts in the past. I just d/l'ed the latest version and it won't connect either.

Bob

 

[letarotor]

Mike,
Sorry, my head was squarely up my a**, just didn't think about that. I just downloaded the lastest version, will re-enter the bad freqs and get back to you. Mark

 

[iMONITOR]

I need to learn to find my way around this forum. I just looked and sure enough ports 1-13 were in use, according to device manager. Its probably all the other gadgets I've connected to the USB posts in the past. I just d/l'ed the latest version and it won't connect either.

Bob

Do you have any drivers/software installed for a Palm Pilot, or Pocket PC? Sometimes those cause problems.

 

[mancow]

Me too. I had to wipe the HP laptop clean with a reinstallation of XP. I went through the Vista maching deleting everything I could think of but it still says it can't open the com port.

People suggest deleting drivers and stuff but how do you find them to delete them? I don't see any driver software in the installed programs list.

I downloaded PSRedit and tried to use it with my PSR-500. The software won't recognize the com port my cable uses. Other software finds the cable just fine. Any ideas?

Bob

 

[fmon]

Me too. I had to wipe the HP laptop clean with a reinstallation of XP. I went through the Vista maching deleting everything I could think of but it still says it can't open the com port.

People suggest deleting drivers and stuff but how do you find them to delete them? I don't see any driver software in the installed programs list.

Right click. If you select properties, it will open another dialog as per second picture.

 

[mancow]

Right, but I may have been unclear. I was referring to drivers and software for other items that may be causing conflicts.

My cable works fine with WIN500 so I would think that it's not an issue with the driver for the GRE cable.

The problem is that something is causing a conflict somewhere. PSREdit can't seem to open it. Also...my computer puts the com port assignment way out as something like 14 or 15 like the other guy that posted earlier had mentioned. I'm thinking it has something to do with bluetooth taking up multiple port assignments.

The issue was the same on the HP laptop until I reloaded the OS. After being reloaded and the USB blue tooth software gone the com port assigments disappeared and PSREdit dropped back to slot 4.

 

[rfmanning]

Com 14 ??? Now Com 3 ???

Well, COM 14 didn't work. I went into device manager and forced COM 3. PSRedit connected. I edited a talkgroup, uploaded to the radio and shut down the software. I went back to continue editing the talkgroup. Now, it won't connect to COM 3. Hmmm.

Yes I do have PocketPC software installed. Should that make a difference?

Disconnect USB, reconnect, it works.

Bob

 

[mikey60]

Well, COM 14 didn't work. I went into device manager and forced COM 3. PSRedit connected. I edited a talkgroup, uploaded to the radio and shut down the software. I went back to continue editing the talkgroup. Now, it won't connect to COM 3. Hmmm.

Yes I do have PocketPC software installed. Should that make a difference?

Disconnect USB, reconnect, it works.

Bob

I'm going to see if I can add some descriptive text as to why the port could not be opened on the next release. Maybe that will shed some light on the issue.

Mike

 

[iMONITOR]

Well, COM 14 didn't work. I went into device manager and forced COM 3. PSRedit connected. I edited a talkgroup, uploaded to the radio and shut down the software. I went back to continue editing the talkgroup. Now, it won't connect to COM 3. Hmmm.

Yes I do have PocketPC software installed. Should that make a difference?

Disconnect USB, reconnect, it works.

Bob

PocketPC software can cause problems with other devices using serial, or USB ports. You could temporarily close, or disable the PocketPC software to see if it makes a difference. You can do this using your Windows Task Manager. If you need help let me know.

Also, do you think you actually have 14 different COM ports? Sometimes if you reinstall a driver, or software that uses ports, it will grab an additional port, and this can happen over, and over. Doing so can cause instability with port assignments.

You can check this using your Windows Device Manager. Normally a computer will have two actual serial ports, COM1, and COM2. Sometimes a third will show up if you have an internal dial-up modem, usually as COM3, sometimes COM4.

Newer computers sometimes only have one, some have none at all. The USB ports show up in another area, and should not be listed as COM ports, unless it is a USB-to-Serial Adapter. The USB adapter will emulate a serial port, and show up as an additional COM port.

My guess is that you have multiple instances of the same USB-to-Serial Adapter consuming several COM port assignments, which may be causing all the confusion. If you do, then you will need to delete the extra ones. Again if you need help, just ask.

 

[mancow]

Well with the newest version mine went from "can't open com port" to "com port doesn't exist".