Thanks,

Do you have to use version 3.3 of the OS for this? Will all the future
OS versions allow you to use the serial manager??

Gerry


> -----Original Message-----
> From: Jimmy Stricker [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, October 22, 1999 9:49 AM
> To:   '[EMAIL PROTECTED]'
> Subject:      RE: IR without IRDA
> 
> You don't have to use the IRDA stack, you can use your
> own protocol through the IR by using the serial library.
> 
> All you have to do is enable the the IR port.
> 
> 
> #ifdef PALM_PRO
>       err = SysLibFind("IrSerial Library", &pDcb->hComm);
> #else
>     err = SysLibFind("Serial Library", &pDcb->hComm);
> #endif   
>     
>     err |= SerOpen(pDcb->hComm,0,pDcb->baudRate);
>     emSetBaud(pDcb);
>     if (pDcb->echoOn != 0)
>     {
>       SerControl(pDcb->hComm, serCtlIrDAEnable, 0, 0);
>               
>       }
>     if (err == 0)
>       sts = EM_STS_OK;
> 
> 
> This snipit will use the IR port to send and recieve my
> own custom protocol.
> 
> Hope this helps, 
> 
> Jimmy
> 
> -----Original Message-----
> From: Rigdon, Gerald [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 22, 1999 9:38 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: IR without IRDA
> 
> 
> Hi,
> 
> Thanks for the input. I am still a little fuzzy about IRDA. If we use
> IrCOMM on the palm, does this use the IRDA protocol stack? If so, then
> would we be forced to comply with IRDA protocol on the embbeded
> system.
> 
> We had planned to develop our own protocol to avoid overhead the full
> IRDA overhead on the embedded system. Using the current version of the
> serial manager, we were going to treat IR communications as a serial
> port using our own protocol. So, our original question was whether
> this
> would still be supported. We are trying to avoid the use of the IRDA
> protocol on the embedded system. Perhaps this is what you understood
> in
> your first reply. However, from what little I have read, IrCOMM is
> simply the top layer of IRDA protocol that abstracts everything. This
> is
> great for the palm, but doesn't this force the details onto the
> embedded
> system??
> 
> Thanks
> 
> Gerry
> 
> > -----Original Message-----
> > From:       Ben Williams [SMTP:[EMAIL PROTECTED]]
> > Sent:       Thursday, October 21, 1999 7:46 PM
> > To: [EMAIL PROTECTED]
> > Subject:    Re: IR without IRDA
> > 
> > > We are developing an embedded application that does not have
> enough
> > > memory for the IRDA stack.  We are getting the Palm to communicate
> > > through the serial manager to the IR hardware successfully.  The
> > > question is, will this type of functionality be supported in the 
> > > future and is there better support right now for it?  We had to do
> 
> > > alot of guessing by reading the include files and  trial and
> error.
> > 
> > It depends exactly what you mean. If you are using the serial
> manager 
> > to communicate via IrCOMM then this is certainly implemented in the 
> > future - you can either use the IR enhancements from 3com which
> allow 
> > you to map serial output as IrCOMM - it gives the user a new panel
> in 
> > preferences to swap between cradle and IR serial functions (this can
> 
> > be used to IR HotSync, also...). The other way is to upgrade to OS 
> > 3.3 and use the new serial manager - this allows you to open the 
> > serial port as 'ircm' directly and send as IrCOMM without any 
> > prerequisite for the user to change the port map. The new sm also 
> > allows you to open the IR hardware directly(?). Have at look at 
> > 'Specifying the Port ID' on page 205 of the programmers companion 
> > (and also the stuff before it).
> > 
> > If anyway an point me in the right direction to get the header files
> 
> > so that I can actually _use_ the New Serial Manager, I would be very
> 
> > very grateful... 8).
> > 
> > 
> > 
> > 
> > --
> > Is your email secure? http://www.pop3now.com
> > (c) 1998,1999 Cave Creations Corp. All rights reserved.
> > 

Reply via email to