Hi Bruce,

I'm probably being obtuse here...

SrmOpen seems to offer two different ways to open the port, using wither
hardware or logical port IDs:

Logical port ID's (for physical ports only):
    $8000 = Cradle Port, RS-232 serial
    $8001 = IR Port
    $800n = reserved for future types of ports
A four-character string specifying the port name:
    'u328' specifies the cradle port using the 68328 UART
    'u650' specifies the IR port on an upgraded Palm III
            device
    'ircm' specifies the IRComm virtual port


I have been opening the port using $8001. If that is IrComm... cool, no
problem.

However, if I open the port for RS for RS-232 serial, the only (apparently)
relevant opcodes for SrmControl appear to be IrDA-related:

srmCtlIrDAEnable,            // Enable  IrDA connection on this serial port
                             // valueP = 0, valueLenP = 0

srmCtlIrDADisable,           // Disable  IrDA connection on this serial port
                             // valueP = 0, valueLenP = 0

srmCtlRxEnable,              // enable receiver  ( for IrDA )
    
srmCtlRxDisable,             // disable receiver ( for IrDA )

(The above are from the SerialMgr.h file in the 3.5 support files).

Should I open the port using $8000 and then call SrmControl with
srmCtlIrDAEnable? Or should I open it with $8001 and then srmCtlIrDADisable
it?

Also, I assume that srmCtlRxDisable is to prevent "feedback" where the
receiver sees the emitted data being sent... correct?

Can you please clarify the above? Thanks a million!

    --Lou
_________________________________________________________________
Lou Krieg, President                          Tel: (802) 865-2728
Green Mountain Software Corporation           Fax: (802) 865-2468
85 Prim Road - Suite 302, PO Box 700       Internet: [EMAIL PROTECTED]
Colchester, Vermont 05446-0700                http://www.GMSW.com

On 11/22/99 12:31 PM, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:
> 
> Hi Lou,
> The problem is that the IR Port you are using is actually the
> IrComm port running over the IrDA protocol suite. Probably _not_
> what you're wanting.
> 
> What you need to do is open the normal serial port then place
> it into IR mode. The SrmControl call is used to enable/disable IR
> mode and to enable/disable the IR receiver.
> 
> Cheers,
> Bruce Thompson
> Senior Developer Support Engineer
> Palm Computing, Inc.
> 
> --------------------------------------------
> Date: 19 Nov 1999 18:07:11 -0800
> From: Lou Krieg <[EMAIL PROTECTED]>
> Subject: New Serial Manager and IR
> 
> I need to send serial IR ASCII data to an external device (custom hardware,
> etc). The transfer will be one way.
> 
> I have written a simple data sending app (and a receiving app for testing
> purposes) using the New Serial Manager. The apps work fine when I test them
> using a crossover cable and the cradle ports. However, when I make the
> change of calling SrmOpen with the logical port ID of the IR Port rather
> than the Cradle Port, the Palm devices (a V and a III, both running OS 3.3)
> don't seem to be able to communicate.
> 
> I have set the flags using SrmControl to not do flow control, and I open the
> port at 9600bps. Oh, and yes, I have both devices preferences set to not
> receive beams, since I imagine this grabs the port periodically to look for
> senders.
> 
> Any thoughts on where to look for problems will be most welcomed!
> 
> -- Lou


Reply via email to