<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'><BR>Bill, thanks for the response. Following your suggestions, it turns out a brand new USB cable was the culprit. I'm happy to say that my HPSDR system works, Penelope transmits and looks good ... heck, my wife is even proud of me :) - Now just waiting for my Mercury board to arrive.<BR>
<BR>
Best and 73,<BR>
Dan<BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Tue, 21 Oct 2008 22:57:30 -0500<BR>> To: dquigley@msn.com; hpsdr@hpsdr.org<BR>> From: bill@ewjt.com<BR>> Subject: Re: [hpsdr] Problem: Ozy/USB malfunction/not recognized<BR>> <BR>> Hmmm ... any chance the USB port is not USB2 - USB 1.1 hub <BR>> perhaps? Can you try a different USB cable? Is the +5v supply on <BR>> Atlas stiff - can you measure the current draw on the +5v line?<BR>> <BR>> If it is reporting 0x0 for VID and PID something is not quite <BR>> right. It should be 0xfffe/0x7 (VID/PDI) if the EEPROM on Ozy is <BR>> being recognized as programmed and 0x4b4/0x8613 if the EEPROM is not <BR>> programmed.<BR>> <BR>> If that does not do it, any chance of trying another computer to try <BR>> and isolate it to being a computer side problem or board side problem?<BR>> <BR>> Regards,<BR>> <BR>> Bill (kd5tfd)<BR>> <BR>> <BR>> At 03:09 PM 10/21/2008, Daniel Quigley wrote:<BR>> >***** High Performance Software Defined Radio Discussion List *****<BR>> ><BR>> ><BR>> >Hello,<BR>> ><BR>> >I received Ozy/Atlas/Janus and Penelope boards this past week so I <BR>> >am an hpsdr newb. I've read the pdf instructions and searched the <BR>> >reflector archives for additional info. However, I am having what <BR>> >seems like a very basic problem: my XP system does not recognize Ozy <BR>> >USB and reports it as malfunctioning.<BR>> ><BR>> >Windows XP reports Ozy as a malfunctioning/unknown USB device and <BR>> >does not bring up the driver wizard. The USBIO driver is installed <BR>> >though and I have tried the manual driver installation <BR>> >method. Device manager reports that the Ozy USB device is sending a <BR>> >null (0000) VID and 0000 for the first 16 bits of the PID. Voltages <BR>> >on the Atlas backplane are good and with the exception of USB ident, <BR>> >Ozy (and the others when plugged in) power up as the docs predict.<BR>> ><BR>> >I am running XP build 2600 SP3 with all subsequent microsoft <BR>> >updates. The box is an eMachine laptop; a K8 processor (not running <BR>> >64bit) and 1Gb ram. Other USB devices run fine.<BR>> ><BR>> >Apologies in advance if I have missed something basic. I do need <BR>> >some suggestions/help.<BR>> ><BR>> >Thanks in advance,<BR>> >Dan (N7HQ)<BR>> ><BR>> <BR>> <BR><BR></body>
</html>