Slow Comms Port

[Merryterry]

I have an Airband Radio connected to my Windows XP via Comms Port 1 and a RS232 type connector. I use it to feed in frequencies via a programme calledAOR Ctrl. It takes a long time, sometimes up to 15 mins and many tries to get the programme to recognise the radio. The Baud Rates, Stop Bits, Parityetc all match on the Comms Port, the Programme and the radio. The radio recognises that it is connected straight away but the programme doesnt. I have tried to update the driver for the comms port but XP tells me it is working and the latest version. Any ideas?

Merryterry

 

[JJ]

I have an Airband Radio connected to my Windows XP via Comms Port 1 and a
RS232 type connector. I use it to feed in frequencies via a programme
called AOR Ctrl. It takes a long time, sometimes up to 15 mins and many
tries to get the programme to recognise the radio. The Baud Rates, Stop
Bits, Parity etc all match on the Comms Port, the Programme and the
radio. The radio recognises that it is connected straight away but the
programme doesnt. I have tried to update the driver for the comms port
but XP tells me it is working and the latest version. Any ideas?

Does this problem occur when the radio is still new? Most COM port based
devices are slow.

Make sure you already set the baud rate setting in the AOR Ctrl program as
high as possible that the radio can handle based on its specifications. Some
device uses only one fixed baud rate, some can accept multiple baud rates.

Also try:

* Using a different COM port socket on the PC, if you have more than one.

* Not to place the COM port cable right beside high-voltage cables.

 

[Merryterry]

Does this problem occur when the radio is still new? Most COM port based

devices are slow.



Make sure you already set the baud rate setting in the AOR Ctrl program as

high as possible that the radio can handle based on its specifications. Some

device uses only one fixed baud rate, some can accept multiple baud rates.



Also try:



* Using a different COM port socket on the PC, if you have more than one.



* Not to place the COM port cable right beside high-voltage cables.

Thanks. I have set Baud Rate highest. Seems better if I leave everything 'cooking' for a while and then log on to device. Not got another Com Port. Do you mean Mains Voltage when you say 'High Voltage' Cable?

Again many thanks

merryterry

 

[R.Wieser]

Hello Terry,

The radio recognises that it is connected straight away
but the programme doesnt

That could have simply to do with it sensing a correct voltage on any
(combination) of its pins. It does not need to mean it can communicate.

Have you checked if the radio sends something back, directly after it
notices it's connected ? Does that data meet expectations of it ?

Its also possible that your radio tries to auto-sense the baudrate, and it
does not get the right data for it to be able to do it.

Andoyther thing is that you might want to check what the wiring and
handshaking is expected to be. Not sending (the correc) handshake signals
when the other side expects them could also throw a wrench into it.

Another thing is that the higher the baudrate, the more precise the
baudrate-timing must be and the shorter the cable between the two devices.

Hope that helps,
Rudy Wieser


-- Origional message:
Merryterry <[email protected]> schreef in berichtnieuws
(e-mail address removed)...
I have an Airband Radio connected to my Windows XP via Comms Port 1 and a
RS232 type connector. I use it to feed in frequencies via a programme called
AOR Ctrl. It takes a long time, sometimes up to 15 mins and many tries to
get the programme to recognise the radio. The Baud Rates, Stop Bits, Parity
etc all match on the Comms Port, the Programme and the radio. The radio
recognises that it is connected straight away but the programme doesnt. I
have tried to update the driver for the comms port but XP tells me it is
working and the latest version. Any ideas?

Merryterry

 

[Merryterry]

I have an Airband Radio connected to my Windows XP via Comms Port 1 and aRS232 type connector. I use it to feed in frequencies via a programme called AOR Ctrl. It takes a long time, sometimes up to 15 mins and many tries to get the programme to recognise the radio. The Baud Rates, Stop Bits, Parity etc all match on the Comms Port, the Programme and the radio. The radio recognises that it is connected straight away but the programme doesnt. I have tried to update the driver for the comms port but XP tells me it is working and the latest version. Any ideas?



Merryterry

Thanks Rudy,

It seems to be behaving itself a bit better now without any changes. Strange. It logged itself on first time yesterday. I do leave it 'cooking' for a while before I load the software though.

Thanks again

Terry