This Forum is Dedicated For all The Object Oriented PIC Lovers .......... The concept behind OOPic is straight forward. Use preprogrammed multitasking Objects from a library of highly optimized Objects to do all the work of interacting with the hardware. Then write small scripts in Basic, C, or Java syntax styles to control the Objects. During operation, the Objects run continuously and simultaneously in the background while the scripts run in the foreground telling the objects what to do.

Wednesday, October 24, 2007

Re: [oopic] Trouble with PC communicating with OOPIC-R

Larry M. Leitch wrote:
>
> ooPIC Tech Support wrote:
> >
> > What ooPIC are you using? If it is an ooPIC R or ooPIC C board then you
> > can use straight through DB9 cables. If you are using an ooPIC S board
> > then you will need the RS232 level converter in there to communicate
> > with the serial port to the PC.
> >
> > DLC
> >
> > Larry M. Leitch wrote:
> > > Hi Folks,
> > >
> > > I keep getting the "Cable Not Found" message when I try to connect to
> > > the OOPIC to program it.
> > >
> > > Do I need a Null-Modem? I think the answer is NO.
> > >
> > > Do I need an RS-232 to TTL Converter? I think the answer is YES and I
> > > use one (a UTEK)
> > >
> > > The firmware is C.1.1+. As far as I can tell, the cables are good;
> they
> > > are from Radio Shack and not home made.
> > >
> > > Thanks
> > >
> > > Larry
> > >
> > >
> > >
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> >
> > --
> > ------------------------------------------------------
> > Dennis Clark ooPIC Tech Support
> > www.oopic.com
> > ------------------------------------------------------
> >
> >
>
> The OOPIC is an OOPIC-R and it now works because I removed the
> serial-TTL converter. This setup (with the level converter) used to
> work, although intermittently (I was blaming the OOPIC).
>
> Recently, I had the firmware updated to C.1.1+ AND switched to a new
> USB-Serial converter - changed two things at once and that was a no-no.
>
> The next step would have been to take the OOPIC to work where my PC has
> a regular Comm port. I would have still used the level converter if I
> had not heard from the group.
>
> Thank you very much.
>
> Larry
>
>

Hi All,

Two weeks ago, I was able to communicate with the OOPIC-R via the serial
port and now I can not. I am back to getting the "Cable Not Found"
dialog. I have made no *INTENTIONAL* changes that I know of that would
cause the serial link between the PC and the OOPIC to stop working.

My setup: OOPIC-R and Windows XP running on Toshiba laptop.
I have no printer port and no serial port, only USB.

No serial to TTL level converter.

*NO* null modem cable.

When I do Tools...Cable Configuration...Find Serial Cable, I get the
"Can not find a serial cable connected to an OOPIC" dialog.

disabled LPT1 and COM1, USB shows up as COM3.
device manager shows: USB Serial Port (COM3)
same result.

uninstalled LPT1 and COM1
device manager shows: USB Serial Port (COM3)
same result.

reboot, COM1 and LPT1 reappear. uninstall COM1 and LPT1 drivers again.
Find Serial cable => Found no installed serial ports to check.

rename COM3 to COM1 => same
"Can not find a serial cable connected to an OOPIC" dialog.


Went to a PC with a real serial port (only one) and checked that is was set
to 9600 baud, no parity, and one stop bit. No better luck. One time, I got the message
"sent y and received fhsa(*(*^%$$#$" or something like that. Sometimes received:
"Can not find a serial cable connected to an OOPIC" dialog.

Thank you for all help that you can offer.

Larry Leitch



Yahoo! Groups Links

<*> To visit your group on the web, go to:

http://groups.yahoo.com/group/oopic/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:

http://groups.yahoo.com/group/oopic/join

(Yahoo! ID required)

<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:

http://docs.yahoo.com/info/terms/

No comments: