Vic Fraenckel wrote :

> 
> Jan-Erik Soderholm wrote:
> | The RS232 cable have slipped out of the connector a little ?
> | "Someone" has moved the cable to COM2 ?
> 
> My post stated:
> | > I have determined that the COM1 connection to the
> | > programmer is functional. I have a PIC app that sends
> | > data to a terminal program when commanded to do
> | > so by sending a '?' character from the terminal program.
> | > This functions perfectly.
> 
> further - my computer only has one com port - COM1 and my 
> test certainly proves that the port is functional.
> 
> he further wrote:
> | I'm not sure I follow here...
> | Everything else *but* the Wisp628 seems to work. Yet
> | you do *not* think it's the Wisp628 that is the problem ?
> | Is that correct ? And if so, why not ?
> 
> I had written:
> | > the programmer has not worked since. I concede that the
> | > problem might not be the programmmer. What else?
> 
> with the question 'What else?
> I'm just looking for a cause of the problem.
> 
> Vic

He he... :-)
OK, sorry I put my nose into it.
It *still* sounds like a dead (or at least non-functional) Wisp628.
Have you tested it on another PC (to verify the Wisp628) ?

Regards,
Jan-Erik.



-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist