No, a communication link opened with the serial manager call SrmOpen and
serportirport is not "raw" as I think you mean, but it is "raw" speaking
IrDA, that is a link using the physical layer of the IrDA stack (SIR). So
there is still coding of rs-232 signals into pulses, all according to the
IrDA phy specification.

And as far as I know, there is no way to just "blink" with the IR-LED
simulating a "1" or "0" using high level functions in the Palm OS API. You
have to do Motorola assembler to achieve that.

/Henrik

"Mike" <[EMAIL PROTECTED]> skrev i meddelandet
news:100226@;palm-dev-forum...
>
> Aside from this garbage at the beginning, is this communication really
> raw.  I mean, is there the total lack of any IrDA protocol?  Is it just
> the raw text without any addressing, etc sent?
>
> Thanks,
>
> > I'm just sending some ASCII text. I also received a byte or two of
> > garbage at the start of each transmission, but could simply ignore it.
> >
> > James Screech
> >
> > "Henrik Fredriksson" <[EMAIL PROTECTED]> wrote in message
> > news:100202@;palm-dev-forum...
> >>
> >> Now I don't know what you are sending, but I tried this approach first
> >> as well, and while looking at an oscilloscope I could see that opening
> >> the
> > port
> >> drops some crap on the IR, atleast my oscilloscope (connected to a
> > MCP2120)
> >> triggered on it, and it was very hard to set the right trigger level
> >> to bypass this initial data to see the actuall data on the
> >> oscilloscope. This usually doesn't mean anything because it is
> >> probably crap data and usually you are waiting for something special
> >> on the receiving side (perhaps the string "ABC") so this initial
> >> message will not bother you. But in some
> > cases
> >> it might disturb you.
> >>
> >> Noone could tell me what this was and I found no information about it
> >> in
> > the
> >> docs. What I did from that day on was to open the port at application
> >> startup so that I would get a "clean" send. I havn't tried to
> >> investigate
> > if
> >> this "open port pattern" occurs on some other device, I mean it could
> >> be
> > my
> >> Palm that is acting wierd for one or another reason :/.
> >>
> >> I use a m515 btw..
> >>
> >> /Henrik
> >>
> >> "James Screech" <[EMAIL PROTECTED]> skrev i meddelandet
> >> news:100201@;palm-dev-forum...
> >> >
> >> > I while ago I was looking into using raw IRDA to communicate between
> >> a
> >> Palm
> >> > (m100) and an instrument. I wrote the following code snippet to test
> >> sending
> >> > data and it work (on a m100).
> >> >
> >> > if (SrmOpen(serPortIrPort,BAUD,&iPort) == 0)
> >> > {
> >> >     SrmControl(iPort,srmCtlIrDAEnable,NULL,0);
> >> >     SrmControl(iPort,srmCtlGetFlags,&iFlags,&iSizeFlags);
> >> >     iFlags |= srmSettingsFlagStopBits2;
> >> >     SrmControl(iPort,srmCtlSetFlags,&iFlags,&iSizeFlags);
> >> >     SrmSend(iPort,pData,iSize,&err);
> >> >     SrmSendWait(iPort);
> >> >     SrmControl(iPort,srmCtlIrDADisable,NULL,0);
> >> >     SrmClose(iPort);
> >> > }
> >> >
> >> > However before anything was developed the project was put on hold.
> >> I've now come back to looking at the project and I've tried to run
> >> my
> > old
> >> > test program on my newer Palm (m505) and I find the it nolonger
> >> works. Is there any difference in the IRDA implementation between a
> >> m100 and an m505 that could be effecting this code?
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >>
> >
> >
> >
> > --
> > For information on using the Palm Developer Forums, or to unsubscribe,
> > please see http://www.palmos.com/dev/support/forums/
>
>
>
>
>



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to