Results 1 to 8 of 8
Thread: IRDA
Hybrid View
-
29th November 2009 18:11 #1
IRDA
. - ? .
Last edited by lazaretos; 29th November 2009 at 18:22.
-
1st December 2009 16:20 #2
-
1st December 2009 16:27 #3
. . , RS232 .
Alfa Romeo 159 1.9 jTDm 150 Sportwagon
Nokia Lumia 930
-
1st December 2009 17:15 #4Have no fear ike iz here.
CPU Cx486DLC@40MHz, RAM 4MB, VGA Trident 512KB, HDD Conner 160MB, Monitor 14" Color
-
1st December 2009 20:21 #5
++ Vectir 7 , . KingSun KS-959 USB infrared adapter.
-
1st December 2009 20:40 #6Have no fear ike iz here.
CPU Cx486DLC@40MHz, RAM 4MB, VGA Trident 512KB, HDD Conner 160MB, Monitor 14" Color
-
2nd December 2009 17:53 #7Registered User
Join Date: May:2009
Location: oz
Posts: 123
, ? .
-
2nd December 2009 22:07 #8@arcordi , , irda .Can I use them with LIRC, or with/as an IR remote control?
Several people have e-mailed me with this question, as well as with inquires/comments that assume LIRC support. Because of this, I will give both a short and a long answer.
The short answer is: no. These drivers cannot be used with LIRC or with remote controls.
The long answer consists of several reasons, as follows:
* The IrDA framing is too high a level of abstraction. LIRC requires raw access to the data read from the IR source, and IrLAP (part of the IrDA specification) framing and unframing gets in the way of the raw stream of data. This is why standard USB-IrDA dongles (for which framing is performed by the dongle itself) are explicitly not supported by LIRC.
* The IrDA physical layer uses an encoding scheme that is very different from the Consumer IR (CIR) encoding, even though both use infrared signals for communication. Many remote controls use a 38KHz sub-carrier for encoding, which is not one of the standard frequencies for IrDA. Some trickery to send and receive remote-control data with a SIR dongle can be done, but it is very timing-dependent, and depends on the ability to set a speed of 115200bps for the dongle (which only ksdazzle supports).
* Even after reprogramming the speed, the issue of timing remains. There is no hard guarantee in the USB bus about the timing of the requests for interrupt endpoints (the ones used by ksdazzle). This means that the timing required to decode the remote-control signals has too much uncertainity to have a reliable reception.Crashing is NOT normal. It is accepted as normal because of Windows.
Ah the Geforce 440 MX...all the power of the Geforce 2MX, without nearly a damn being changed...




Reply With Quote
R9 280,
7th May 2023, 21:28 in