I built the Wisp628 a while ago.
Have been working fine (after removing a few solder bridges)

I'v seen that Wouter have updated both the formare in the
programmer and XWisp. I'n not sure it matters, but check that
that both are the same "generation". I updated a couple of days ago
and had no problem.

You wrote :
"It says try and type stuff, and if u see what you type then there is =
communication between pins. "

*Did* you see anything when typing ?

If you are concerned about the MCLR resistor, put three 10k's
in series. Or maybe you only have one ?
I don't think it would matter anyway.

Does XWisp say anything at all apart from the error message ?
What do you meen with "starts the process". How do you know.
Can you use the COM2 port for anything else ?
What operating system (Windows version)  are you using ?

Jan-Erik Svderholm.


>Hi,
>
>I'm having a little problem actually communicating with the product. =
>Using the XWisp  Tool i use the command xwisp.py com2 go led_1 (my =
>filename)  then it starts the process and i get:
>
>   raise self.WBus_Protocol_Error, \
>__main__.WBus_Protocol_Error: send=3D't' received=3D''
>
<And nothing else happens. I did what it mentions on the site, and short =
>serial port pins 2 and 3 and type
>
>xwisp.py port com2 term 1200
>
>It says try and type stuff, and if u see what you type then there is =
>communication between pins. Anyone got any ideas about this? I'm sure =
>I'm missing something small.
>
>Also, I'm only  using a 10K resistor instead of the 33k  between + and =
>MCLR pin as i don't have any 33k resistors/ and combinations to make 33k =
>or even close.=20
>
>Thanks
>-Peter


Jan-Erik Svderholm
S:t Anna Data
Sweden

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu