Re: Serial IO / Mac OS X [was: (no subject)]

FROM : William Reading
DATE : Sun Dec 05 17:23:06 2004

Aside from finding the port (which is done for you automagically by
IOKit), this kind of thing is done the same way that you would on any
*nix platform. I recently ported a little tool for my watch from Linux
to Mac OS X, the code of which is at:

http://reading.is-a-geek.com/cgi-bin/cvsweb.cgi/fton/rupserial.c

(was originally written by a Japanese fellow for a Seiko ruputer, then
ported to the American Onhandpc, then I ported it to Mac OS X)

I wouldn't use the same flags that I did, unless you've only got three
pins on your serial port like the device I was using and can't do flow
control, etc.

--Bill

Michael Swan wrote:

> I need some help finding a starting point to communicate with an RS485
> device I am building. It is a modified version of a USB RS232 adapter
> so the drivers exist already I just can't wrap my head around opening
> the port, setting speed, etc, sending the data and closing the port.
> Most of the sample code I have found deals with modems and isn't
> commented to the point that I can figure out what parts are modem
> specific and what parts aren't. I'm sure there is a book or website
> out there somewhere that will provide the hand holding I need I just
> can't find it. I have looked through Apple's Serial port sample and
> get a little of it but not much. If anyone knows of something like
> _Cocoa Programming for Mac OS X_, or _Programming with Objective C_
> (as these have been very helpful in other areas) that covers USB,
> serial ports, etc I would appreciate it.
>
> Thanks,
> Mike
> "Change itself is not painful it is resistance to change that causes
> pain."
>
>------------------------------------------------------------------------
>
> _______________________________________________
>Do not post admin requests to the list. They will be ignored.
>Cocoa-dev mailing list      (<email_removed>)
>Help/Unsubscribe/Update your Subscription:
>http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
>This email sent to <email_removed>
>