Article # 250, added by Geoworks, historical record
| first | previous | index | next | last |

Some miscellaneous IrDA information.



Q. What is TinyTP?

A. TinyTP is the preferred protocol layer through which apps
   should use IrDA.


Q. Is IrCOMM enough to send/retrieve data through the Ir port?

A. Yes, but use of IrCOMM is discouraged unless there is a reason
   you can't use TinyTP.


Q. What COM# is the Ir port?

A. The IrDA port is on COM2.


Q. Which driver do you load?

A. If you want to use IrCOMM, you load ircomm.geo instead of the
   serial driver.


Here is some info on settings you'll put into the geos[ec].ini file:

;[irlmp]
;       deviceInfo = 
;               Hint bits and nickname returned by discovery.
;
;[ircomm]
;       flushTime = 2
;
;       The number of ticks before forcing a packet to be sent from the
;       output stream before it reaches the threshold (which is the packet
;       size).
;
; [irlap]                         IRLAP Driver
;
; driver = IRLAP Driver (Socket interface only)
; address = 
(Socket interface only) ; ; port = SerialPortNum (default is SERIAL_COM1) ; ; Negotiation parameters: ; ; baudRate = IrlapParamBaudRate ;default 9600 bps ; maxTurnaround = IrlapParamMaxTurnAround ;default 500 ms ; dataSize = IrlapParamDataSize ;default 64 bytes ; windowSize = IrlapParamWindowSize ;default 1 frame ; numBOFs = IrlapParamNumBof ;default 5 BOFs ; minTurnaround = IrlapParamMinTurnaround ;default 1 ms ; linkDisconnect = IrlapParamLinkDisconnect ;default 3 seconds ; ; Irlap negotiation parameters are records. Entries are numbers ; that represent appropriate masks. Each mask should turn on all ; the bits that correspond to the capacities that the current ; station can support. ; ; e.g. dataSize = 15 = 00001111b which means it can support ; data sizes of 512, 256, 128 and 64 bytes.