Re: Cannot connect to PC

Thanks for all your answers.
After further investigation it seems that the batch of cables supplied to the supplier are faulty!
The suspect cable was sent to Bob Freeth who confirmed the problem.
So it seems the problem has been solved!
I'm just waiting for a correct replacement cable.
Thanks again everyone.

--- In [email protected], wejones@... wrote:
>
> On 24 Jun 2013 at 19:12, Dave Hartman wrote:
> 
> > With the cable connected to your PC, and the DB9 end not connected, jump 
> > pins 2 and 3 (RXD/TXD), then open a terminal program like Hyperterminal, 
> > select the com port, and when you type something you should see it back 
> > on the screen with echo off, and see double with echo on.  If not, 
> > you've gor the wrong com port, ..................................................
> 
> With VR5Ks with the old firmware, if  you connect the receiver to the computer with Hyperterm running, and then 
> turn on the receiver, you will see the firmware version printed on the computer screen.
>   I seem to remember that something changed re this behavior with newer firmware versions, but I'm not sure.  
> But it's worth a try. 
>    The OP'er didn't say what OS is being used, but you should be able to go to the control 
> panel/system/hardware/device manager (other ways of getting there), and there should be a "Ports" item in the 
> list.  It will tell you what COM# is being used, and right click properties will tell you the port parameters.  You can 
> change the port# or the parameters to match what is being used by the VR5K.  
>    You can also change the BAUD rate on the VR5K by hitting FUNC-Ent , and choosing MISC, and scrolling 
> down to the CAT line.   I have both computer and VR5K set to 9600 baud.  The computer program SHOULD be 
> able to set the baud rate on it's own, but I've found that it sometimes helps to set it in the control panel.  
>    Also, if an older computer with a real serial port is available, it might be helpful to try that computer, because 
> some of the new USB--RS232 converters are flakey.  One particular issue I've seen is that they keep changing 
> port numbers each time they are used, or if you go to another USB port.  I had to go into the device manager as 
> above, and into advanced, which allows you to change the COM#.  It may tell you that the port# you want is in 
> use, but you can over-ride that. 
>    This COM port stuff works best with older computers and older OSs.  The newer the OS, the more likely it is 
> that the security will confuse things.  I haven't used mine in years, but yesterday, I connected it to my XP-Pro 
> laptop, and it works fine with an old cheap USB---RS232 adapter.  Didn't need any additional drivers or anything.  
> I DID have to restore the COM# to the one being used by my software, however, as described above.
>