PCR-1000 Communications Problem
Chris Spacone
When scanning from memory lists the unit will stop and display on the
window titlebar "Connectio...". At the same time the controls for the
radio go dead, the S-meter drops to zero and the scanner needs to be
restarted. This is happening at regular 10-12 second intervals.
Clearly something is hitting the com port (com 2) and interrupting
communications between the PC and the radio. I had MS ActiveSync 3.0
installed to sync my PDA (on com 1), removed that and have removed or
disabled all the software I can think of to stop this annoying
behaviour.
Other than that everything works great. Any ideas?
Thanks,
Clay Schneider
http://www.sysinternals.com -- it does a good job of following and recording
all comm activity, and allows you to filter the activity list to make it
more readable.
Good luck.
Clay
"Chris Spacone" <cspa...@pacbell.net> wrote in message
news:3a0cdde5...@News.pacbell.net...
Chris Spacone
Thanks to a suggestion by Clay, I found portmon a program that allows
me to look at the command strings going to the radio. I found that on
fairly regular (10 to 12 second) intervals the Icom PCR-1000
application sends command G105 which forces the radio to 38400 baud.
This has the effect of stopping all activity on the radio until
communications is re-established. I ran portmon with TalkPCR and the
only time G105 is sent is during initialization.
So the question now is: Is there a firmware problem with the PCR-1000?
For example is it supposed to continue as normal after receiving G105
command (not likely). Or is the problem with the Icom application? It
is clear to me that the application is sending the set baudrate
command G105 at regular intervals. It seems the fix should be fairly
trivial.
Could it be that I am the only person who has identified a causal
relationship between the Icom app and the radio's behaviour during
scanning? In any case I'll be forwarding this to Icom in the hope that
they will address what I consider to be a bug that should never have
left the developers PC.
Thanks
Chris Spacone
On Sat, 11 Nov 2000 05:54:21 GMT, cspa...@pacbell.net (Chris Spacone)
wrote:
Clay Schneider
While there has been much discussion of individuals having problems with the
Icom software, what Chris is reporting, as far as I remember back to when
the 1000 first came out, is, in fact, 'new' information -- namely, that the
software is resetting the baud rate of the radio at regular intervals with a
G105 command.
What is even more interesting is that, using the same software to monitor
the transactions between the Icom software and the 1000, I do not see a G105
command being sent in my environment except at power-on, which is why I am
among those who have never had a problem with the Icom software, and may
explain why Icom has never 'fixed' what they too might never have seen in
their own environment.
Clay
Scott C. <qine...@lnubb.pbz> wrote in message
news:4k0k1tc289fd22llu...@4ax.com...
> On Sun, 12 Nov 2000 17:01:12 GMT, cspa...@pacbell.net (Chris Spacone)
> wrote:
>
> >So the question now is: Is there a firmware problem with the PCR-1000?
> >For example is it supposed to continue as normal after receiving G105
> >command (not likely). Or is the problem with the Icom application?
>
> It is a well-known problem with the application. Third party software,
> such as TalkPCR, does not suffer from this problem.
>
> >Could it be that I am the only person who has identified a causal
> >relationship between the Icom app and the radio's behaviour during
> >scanning? In any case I'll be forwarding this to Icom in the hope that
> >they will address what I consider to be a bug that should never have
> >left the developers PC.
>
> Don't waste your time. They were told about this problem YEARS ago; as
> you can see, they have not bothered (or don't have the software
> development expertise) to fix it.
>
Sasha Z.
told by ICOM, that is was a compatibility issue with windows 98 and 95, can
you believe it? ICOM said that it would work excellent in 95, but for some
reason communications between the PCR-1000 and windows 98 are incompatible.
So my next question to ICOM was "Do you have a patch or a new version?"
"NO", was his answer. Can you believe it?
Anyhow if you manage to fix it, let me know.
--
__________________________________________________________
Sasha A. Zivanovic "Sash"
Office Manager
Sloga Transport Co. Ltd.
sas...@slogatransport.com
www.slogatransport.com
"Chris Spacone" <cspa...@pacbell.net> wrote in message
news:3a0ec9f...@News.pacbell.net...
> I think I have narrowed the problem.
>
> Thanks to a suggestion by Clay, I found portmon a program that allows
> me to look at the command strings going to the radio. I found that on
> fairly regular (10 to 12 second) intervals the Icom PCR-1000
> application sends command G105 which forces the radio to 38400 baud.
> This has the effect of stopping all activity on the radio until
> communications is re-established. I ran portmon with TalkPCR and the
> only time G105 is sent is during initialization.
>
> So the question now is: Is there a firmware problem with the PCR-1000?
> For example is it supposed to continue as normal after receiving G105
> command (not likely). Or is the problem with the Icom application? It
> is clear to me that the application is sending the set baudrate
> command G105 at regular intervals. It seems the fix should be fairly
> trivial.
>
> Could it be that I am the only person who has identified a causal
> relationship between the Icom app and the radio's behaviour during
> scanning? In any case I'll be forwarding this to Icom in the hope that
> they will address what I consider to be a bug that should never have
> left the developers PC.
>
> Thanks
> Chris Spacone
Gary P. Fiber
constantly is looking for Plug and Play devices attached to the comm
port and the PCR-1000 is not one. It just might do the trick. Go into
device manager and turn off automatic settings for the comm port in
use.
Gary