Vic Fraenckel wrote :

> I have been using the '628 for some time now and have had no 
> problems with  it. I use the XWisp2w package to drive it.
> Yesterday I was working on a project and had been
> downloading updates to the application board (PIC16F876A)
> throughout the morning with absolutely NO problems. Then,
> after perhaps 6 downloads, XWisp2w could not find the '628
> and errored out with 'Failed to Activate WBus device' and
> ' XWisp2 failed after 1.12 seconds, rc23'.  I have been
> unable to use the programmer since. I run XWisp2x with 
> the following .bat
> 
> xwisp2w com1 baud 9600 go %1
> 
> the programmer has not worked since. I concede that the 
> problem might not be the programmmer. What else?
>
> 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.

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 am out of ideas as to why the '628 should stop functioning 
> so abruptly.

The RS232 cable have slipped out of the connector a little ?
"Someone" has moved the cable to COM2 ?

B.t.w, I don't think I've ever used the "baud" parameter to
Xwisp2w. Not sure it would make any difference, thought...

Finaly, I guess you don't have a second Wisp628 to compare
with, right ? :-)

Jan-Erik.



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