First, let me thank those that have replied. I appreciate you taking the time. This is getting curiouser and curiouser. I dug out another computer with a serial port and put the Wisp2 software on it and connected to the '628 and lo and behold it worked. This rules out the '628. The RS232 port on my development computer will send and receive data from my application board (16F876A with a serial interface and connected to an ADXL202 accelerometer). The board sends a reading from the ADXL on demand from the host (in this case a terminal program) this RS232 link (COM1) works perfectly sending and receiving, but the development system cannot communicate with the '628 over the same port. I cannot account for this behaviour! Why does the comm port (COM1) work for some apps and not for others? The windows device manager shows the port is working. Any ideas? Any enlightenment will be appreciated. TIA Vic ________________________________________________________ Victor Fraenckel - The Windman victorf ATSIGN windreader DOTcom KC2GUI Home of the WindReader Electronic Theodolite Read the WIND "Dost thou not know, my son, with how little wisdom the world is governed?" -Count Oxenstierna (ca 1620) to the young King Gustavus Adolphus "People sleep peacefully in their beds at night only because rough men stand ready to do violence on their behalf." -George Orwell "When a true genius appears in the world you may know him by this sign: that all the dunces are in confederacy against him." -Jonathan Swift ----- Original Message ----- From: "Jan-Erik Soderholm" To: Sent: Thursday, May 12, 2005 2:23 PM Subject: RE: [PIC] Wisp628 problem | 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 | | | -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist