From: Alex S. <ros...@st...> - 2002-05-09 17:05:17
|
Hi all, My serial dongle runs with the logitech driver. I dont have a logitech, i= =20 have an adaptek, but that is the driver that works the "best" for my=20 hardware. ( i think) lircd compiles,loads, and lets me record a remote, pasted in below. At first sight you can see, something is wrong, and irrecord had also=20 complained about " No toggle bit". however, restarting lircd with that new config and running irw shows code= s=20 like: 000000000000a048 01 5 /root/test4 000000000000a040 00 Vol-UP /root/test4 000000000000a040 01 Vol-UP /root/test4 000000000000a044 00 3 /root/test4 000000000000a044 01 3 /root/test4 000000000000a052 00 Power /root/test4 ... looking good, BUT: - Chan-UP is recognized as "5" - Mute, 0 are being recognized as "3" - TV/AV, Vol-DOWN, Chan-DOWN, 1,4,6,7,8 do not show up AT ALL Looking at the below codes (Panasonic), I see why. I tried with a different remote, a Pioneer, and all codes are recorded as 0x000000000000A0CE (see below) I wrote a little programm, that outputs series of ints from the serial po= rt. Here, the commands are easily distinguished, so the dongle is working (se= e=20 capture log below)=20 Now, I dont know, where to go from here. Is there a setting i can change? use raw mode, perhaps? - but i dont like raw... it sounds cpu-intensive compared to LIRC_MODE_CO= DE Shall i try n hack logitech.c to make it work? Shall i try n adapt another driver? Do you want more info? thx already, Alex #(Panasonic) begin remote bits 8 eps 30 aeps 100 one 0 0 zero 0 0 pre_data_bits 8 pre_data 0xA0 gap 129983 min_repeat 27 toggle_bit 0 begin codes 1 0x0000000000000000 2 0x0000000000000042 3 0x0000000000000044 4 0x0000000000000000 5 0x0000000000000048 6 0x0000000000000000 7 0x0000000000000000 8 0x0000000000000000 9 0x0000000000000050 0 0x0000000000000044 Power 0x0000000000000052 Vol-UP 0x0000000000000040 Vol-DOWN 0x0000000000000000 Chan-UP 0x0000000000000048 Chan-DOWN 0x0000000000000000 TV/AV 0x0000000000000000 Mute 0x0000000000000044 end codes end remote #(Pioneer) bits 16 eps 30 aeps 100 one 0 0 zero 0 0 gap 109998 toggle_bit 0 begin codes 1 0x000000000000A0CE 2 0x000000000000A0CE # Capturelog from serial dongle Typical commands look like (from both remotes): ##Reading on IR-Device Length of Burst:12 Int_view: 93 85 85 85 85 85 85 117 85 93 -9 0 -119 -71 10 #Pana 1 StringView: =80]UUUUUUuU]=F7 Length of Burst:12 Int_view: 93 85 85 85 85 85 -43 -43 -43 -43 117 0 -119 -71 10 #Pana 2 StringView: =80]UUUUU=D5=D5=D5=D5u Length of Burst:12 Int_view: 93 85 85 85 85 85 85 117 -43 117 -35 0 -119 -71 10 #Pana 3 StringView: =80]UUUUUUu=D5u=DD Length of Burst:12 Int_view: -53 -21 123 79 79 -53 79 123 79 111 123 0 -119 -71 10 #Pion UP StringView: Length of Burst:12 Int_view: -53 -53 123 79 111 123 -53 123 -21 79 123 0 -119 -71 10 #Pion D= own StringView: Length of Burst:12 Int_view: -21 -53 123 79 111 123 79 123 107 123 -49 0 -119 -71 10 #Pion R= ight StringView: Length of Burst:12 Int_view: -53 -53 123 79 79 -53 123 123 79 123 123 0 -119 -71 10 #Pion Le= ft StringView: NOTE: the first int is always omitted, it is always 0 or -128=20 |
From: <col...@hi...> - 2002-05-12 14:36:13
|
Hi! Alex Stragies "ros...@st..." wrote: [...] > My serial dongle runs with the logitech driver. I dont have a logitech, > i have an adaptek, but that is the driver that works the "best" for my > hardware. ( i think) [...] > Now, I dont know, where to go from here. I'd suggest that you begin with the basics: read the IrDA physical layer specification and a description of remote control protocols, e.g. my c't article. That should at least make clear why what you are trying does not work. Next step would be to study the lirc_sir driver to see what can be done with IrDA hardware. Christoph |
From: Alex S. <ros...@st...> - 2002-05-12 18:01:20
|
Hi Christoph & all, On Sunday 12 May 2002 11:40, you wrote: > Hi! > > Alex Stragies "ros...@st..." wrote: > > [...] > > > My serial dongle runs with the logitech driver. I dont have a logitech, > > i have an adaptek, but that is the driver that works the "best" for my > > hardware. ( i think) > > [...] > > > Now, I dont know, where to go from here. > > I'd suggest that you begin with the basics: read the IrDA physical layer I thought this dongle (Adaptek AIRport 2000) and other serial IR IRDA dongles dont "process" the IRDA signals by themselves, but send it on to the host to have it processed there. So it should give me some sort of raw output, which i do get. (and should be able to use as input) > specification and a description of remote control protocols, e.g. my c't > article. That should at least make clear why what you are trying does not > work. Why should it not work? - My dongle receives a signal over several meters - It outputs predictable Strings containing the code of each button I will add more info to my reply to Karl Bonger's mail. Thankx for your reply, Alex > Next step would be to study the lirc_sir driver to see what can be > done with IrDA hardware. > Christoph > |
From: <col...@hi...> - 2002-05-14 18:21:11
|
Hi! Alex Stragies "ros...@st..." wrote: [...] > I thought this dongle (Adaptek AIRport 2000) and other serial IR IRDA > dongles dont "process" the IRDA signals by themselves, but send it on > to the host to have it processed there. All serial port dongles *have to* process the IrDA signals to conform to the RS232 timings. Some ICs support tunneling the raw IR data over the serial port protocol. But that's an advanced feature and the only chip I know, that supports this, is the CS8130. > So it should give me some sort > of raw output, which i do get. (and should be able to use as input) What you get might be reproducable but it definitely is not what the remote contorl is sending. >> specification and a description of remote control protocols, e.g. my >> c't article. That should at least make clear why what you are trying >> does not work. > Why should it not work? > - My dongle receives a signal over several meters That only means that it has a considerably bad bandpass filter. > - It outputs predictable Strings containing the code of each button Hey, you are complaining that the strings are the same for some buttons... ;) If you really want to play with this dongle, have a look inside and tell us what IC(s) it uses. Christoph |
From: Alex S. <ros...@st...> - 2002-05-15 16:21:15
|
Hi Christoph, Karl & all, (Christoph: You had missunderstood part of my post, plz see below) On Tuesday 14 May 2002 08:03, Christoph wrote: > Hi! > > Alex Stragies "ros...@st..." wrote: > > > So it should give me some sort > > of raw output, which i do get. (and should be able to use as input) > > What you get might be reproducable but it definitely is not what the > remote contorl is sending. Ok, I see that now too. But if the dongle "translates" every button always to the same series of ints, it should be possible to build a .remote file with that data. Granted, that would be a problem, if lircd would try to send these codes. > > Why should it not work? > > - My dongle receives a signal over several meters > > That only means that it has a considerably bad bandpass filter. Care to explain, why good reception distance is a sign for a bad bandpass filter? (Only if it's short :) ) > > > - It outputs predictable Strings containing the code of each button > > Hey, you are complaining that the strings are the same for some buttons... > ;) You did not read all of my post(s). - I said, with the logitech driver i can (with no problem) record a conffile, with the only "funny" message being "no toggle bit found". THEN, if i use the recorded file, some buttons show up JUST FINE, some dont, and some get confused. - If i use my little C-Programm, basically some BlaBlah around a read(fd,buf,255) command, THEN i get unique&predictable int-series for ALL buttons. => This leads me to believe, that the logitech driver is doing basically the RIGHT thing, but does not look at "enough" of the signal. PERHAPS i could even make my dongle work by tweaking the config file alone, but i doubt it. (side note: Is there a page, where vals like "eps" and so are described? ) Karl Bongers wrote me in a different mail and expressed his opinions: - I should buy and/or build other hardware I want to build several devices, and want to use this dongle to try things first. And I dont like seeing unused hardware on my shelf :) - I should continue working on my little c-hack. I very much like the features of lirc, as in recording controls, executing programms/scripts, simulating button presses on x11-programms, emulating mouse movement etc. I dont want to (and cant) reinvent the (your) wheel. - I should write a lirc driver for this thing Since the logitech driver gets some of the remotecontrol buttons right, and i manage to get unique/predicatable strings with a simple read(fd,buf,255), i dont think, it should be too hard to write something on the basis of hw_logitech.c that will make my dongle work. BUT, since I have limited knowledge of lirc internals, i'm not quite sure, what logitech_rec() in hw_logitech.c SHOULD give back, if this WERE the original logitech dongle. Could somebody enlighten me? Somebody have any other info, that would help me on my quest to get another dongle on the "working-with"-list? > If you really want to play with this dongle, have a look inside and tell > us what IC(s) it uses. - It has 4 16V220uf Radial kondensators on it - Maxim MAX3222 CAP 9536 mediumsmall, with 20 legs - MAX640 CSA 9506 very small 8 legs - MAX8211 CSA 517 very small 8 legs - N(funny looking char) 506 NDS 9942 very small 8 legs - ATMEL514 93C46R SC27 very small 8 legs - smthing with metall case (quarz?) SM073-20 9522 - (main chip?) AIC-4210S AKKC521 PT 720011 FD305 JAPAN . Large, 24 legs I think, i see 2 transmit diodes too. The board has APA-9320 ASSY 921306-00 printed on it. I hope, the above is tellin' you something, it sure aint talking to me :) best regards & nice day, Alex |
From: Karl B. <ka...@tu...> - 2002-05-16 05:50:32
|
Hi Alex, I just noticed someone selling an Adaptek AIRport 2500 on ebay. They said it would do 115200 baud, IRDA. Not sure if this is the same as your 2000 model. The chip marked JAPAN is probably the critical part, but I found nothing on this from google. My guess is that it is private chip of Adaptecs. Heres some suggestions: Take a close look at your data. Press the same button 10 times. Is it really consistent? I've played with IRDA the last few days and at 2400 baud I will see about 10-20 bytes of what looks like repeating data, but it is not real consistent. With a working SIR IRDA setup, if I open the serial port at 115200 baud I get about 200-300 bytes of data per button press. If you see this, you might want to try the lirc_sir driver. Karl. Alex Stragies wrote: >Hi Christoph, Karl & all, > >(Christoph: You had missunderstood part of my post, plz see below) > >On Tuesday 14 May 2002 08:03, Christoph wrote: > >>Hi! >> >>Alex Stragies "ros...@st..." wrote: >> >>>So it should give me some sort >>>of raw output, which i do get. (and should be able to use as input) >>> >>What you get might be reproducable but it definitely is not what the >>remote contorl is sending. >> > >Ok, I see that now too. But if the dongle "translates" every button always to >the same series of ints, it should be possible to build a .remote file with >that data. >Granted, that would be a problem, if lircd would try to send these codes. > >>>Why should it not work? >>>- My dongle receives a signal over several meters >>> >>That only means that it has a considerably bad bandpass filter. >> > >Care to explain, why good reception distance is a sign for a bad bandpass >filter? (Only if it's short :) ) > >>>- It outputs predictable Strings containing the code of each button >>> >>Hey, you are complaining that the strings are the same for some buttons... >>;) >> > >You did not read all of my post(s). >- >I said, with the logitech driver i can (with no problem) record a conffile, >with the only "funny" message being "no toggle bit found". >THEN, if i use the recorded file, some buttons show up JUST FINE, some dont, >and some get confused. > >- >If i use my little C-Programm, basically some BlaBlah around a >read(fd,buf,255) command, THEN i get unique&predictable int-series for ALL >buttons. > >=> This leads me to believe, that the logitech driver is doing basically the >RIGHT thing, but does not look at "enough" of the signal. > >PERHAPS i could even make my dongle work by tweaking the config file alone, >but i doubt it. (side note: Is there a page, where vals like "eps" and so are >described? ) > > >Karl Bongers wrote me in a different mail and expressed his opinions: >- I should buy and/or build other hardware >I want to build several devices, and want to use this dongle to try things >first. And I dont like seeing unused hardware on my shelf :) > >- I should continue working on my little c-hack. >I very much like the features of lirc, as in recording controls, executing >programms/scripts, simulating button presses on x11-programms, emulating >mouse movement etc. I dont want to (and cant) reinvent the (your) wheel. > >- I should write a lirc driver for this thing >Since the logitech driver gets some of the remotecontrol buttons right, and i >manage to get unique/predicatable strings with a simple read(fd,buf,255), i >dont think, it should be too hard to write something on the basis of >hw_logitech.c that will make my dongle work. > >BUT, since I have limited knowledge of lirc internals, i'm not quite sure, >what logitech_rec() in hw_logitech.c SHOULD give back, if this WERE the >original logitech dongle. > >Could somebody enlighten me? >Somebody have any other info, that would help me on my quest to get another >dongle on the "working-with"-list? > >>If you really want to play with this dongle, have a look inside and tell >>us what IC(s) it uses. >> >- It has 4 16V220uf Radial kondensators on it >- Maxim MAX3222 CAP 9536 mediumsmall, with 20 legs >- MAX640 CSA 9506 very small 8 legs >- MAX8211 CSA 517 very small 8 legs >- N(funny looking char) 506 NDS 9942 very small 8 legs >- ATMEL514 93C46R SC27 very small 8 legs >- smthing with metall case (quarz?) SM073-20 9522 >- (main chip?) AIC-4210S AKKC521 PT 720011 FD305 JAPAN . Large, 24 legs >I think, i see 2 transmit diodes too. > >The board has APA-9320 ASSY 921306-00 printed on it. > >I hope, the above is tellin' you something, it sure aint talking to me :) > >best regards & nice day, Alex > >_______________________________________________________________ > >Have big pipes? SourceForge.net is looking for download mirrors. We supply >the hardware. You get the recognition. Email Us: ban...@so... > > |
From: <col...@hi...> - 2002-05-17 05:26:24
|
Hi! Alex Stragies "ros...@st..." wrote: [...] >>> Why should it not work? >>> - My dongle receives a signal over several meters >> >> That only means that it has a considerably bad bandpass filter. > Care to explain, why good reception distance is a sign for a bad > bandpass filter? (Only if it's short :) ) IrDA uses 875 nm. CIR uses 950 nm. An IrDA receiver that does not filter 950 nm noticably is prone to bit errors. [...] =>> This leads me to believe, that the logitech driver is doing basically =>> the > RIGHT thing, but does not look at "enough" of the signal. The Logitech driver never was ment to work at all with your device. > PERHAPS i could even make my dongle work by tweaking the config file > alone, Nope. [...] > BUT, since I have limited knowledge of lirc internals, i'm not quite > sure, what logitech_rec() in hw_logitech.c SHOULD give back, if this > WERE the original logitech dongle. You will have to find a way to squeeze your unique input into at most 64 bit still keeping it unique. [...] > I hope, the above is tellin' you something, it sure aint talking to me > :) The only reference to this dongle I've found is here: http://www.pasta.cs.uit.no/pipermail/linux-irda/2000-March/001212.html Maybe Fons Botman can provide you with some info. Christoph |
From: Karl B. <ka...@tu...> - 2002-05-12 16:25:15
|
Hi Alex, I did a google on Adaptec IR, but did not find anything on your dongle. It is probably either: 1.) IRDA SIR dongle. 2.) IR Control(TV remote) dongle. Do you have any doc on this? What is it intended to be use as? Can you provide a link to the manufacturer page? If it is #2, then it was probably bundled with a certain remote, and the hardware translates a certain IR control format to pre-processed RS232=20 codes. If it is #1, then it is translating IRDA style RS232(SIR) to a stream of bytes on the RS232 port. Karl. Alex Stragies wrote: >Hi all, > >My serial dongle runs with the logitech driver. I dont have a logitech, = i=20 >have an adaptek, but that is the driver that works the "best" for my=20 >hardware. ( i think) > >lircd compiles,loads, and lets me record a remote, pasted in below. >At first sight you can see, something is wrong, and irrecord had also=20 >complained about " No toggle bit". > >however, restarting lircd with that new config and running irw shows cod= es=20 >like: >000000000000a048 01 5 /root/test4 >000000000000a040 00 Vol-UP /root/test4 >000000000000a040 01 Vol-UP /root/test4 >000000000000a044 00 3 /root/test4 >000000000000a044 01 3 /root/test4 >000000000000a052 00 Power /root/test4 >... looking good, BUT: > >- Chan-UP is recognized as "5" >- Mute, 0 are being recognized as "3" >- TV/AV, Vol-DOWN, Chan-DOWN, 1,4,6,7,8 do not show up AT ALL > >Looking at the below codes (Panasonic), I see why. > >I tried with a different remote, a Pioneer, and all codes are recorded a= s >0x000000000000A0CE (see below) > >I wrote a little programm, that outputs series of ints from the serial p= ort. >Here, the commands are easily distinguished, so the dongle is working (s= ee=20 >capture log below)=20 > > >Now, I dont know, where to go from here. >Is there a setting i can change? >use raw mode, perhaps? >- but i dont like raw... it sounds cpu-intensive compared to LIRC_MODE_C= ODE >Shall i try n hack logitech.c to make it work? >Shall i try n adapt another driver? >Do you want more info? > >thx already, > Alex > >#(Panasonic) >begin remote > bits 8 > eps 30 > aeps 100 > one 0 0 > zero 0 0 > pre_data_bits 8 > pre_data 0xA0 > gap 129983 > min_repeat 27 > toggle_bit 0 > begin codes > 1 0x0000000000000000 > 2 0x0000000000000042 > 3 0x0000000000000044 > 4 0x0000000000000000 > 5 0x0000000000000048 > 6 0x0000000000000000 > 7 0x0000000000000000 > 8 0x0000000000000000 > 9 0x0000000000000050 > 0 0x0000000000000044 > Power 0x0000000000000052 > Vol-UP 0x0000000000000040 > Vol-DOWN 0x0000000000000000 > Chan-UP 0x0000000000000048 > Chan-DOWN 0x0000000000000000 > TV/AV 0x0000000000000000 > Mute 0x0000000000000044 > end codes >end remote > >#(Pioneer) > bits 16 > eps 30 > aeps 100 > one 0 0 > zero 0 0 > gap 109998 > toggle_bit 0 > begin codes > 1 0x000000000000A0CE > 2 0x000000000000A0CE > > ># Capturelog from serial dongle >Typical commands look like (from both remotes): >##Reading on IR-Device >Length of Burst:12 >Int_view: 93 85 85 85 85 85 85 117 85 93 -9 0 -119 -71 10 #Pana 1 >StringView: EUR]UUUUUUuU]=F7 >Length of Burst:12 >Int_view: 93 85 85 85 85 85 -43 -43 -43 -43 117 0 -119 -71 10 #Pana 2 >StringView: EUR]UUUUU=D5=D5=D5=D5u >Length of Burst:12 >Int_view: 93 85 85 85 85 85 85 117 -43 117 -35 0 -119 -71 10 #Pana 3 >StringView: EUR]UUUUUUu=D5u=DD >Length of Burst:12 >Int_view: -53 -21 123 79 79 -53 79 123 79 111 123 0 -119 -71 10 #Pion UP >StringView: >Length of Burst:12 >Int_view: -53 -53 123 79 111 123 -53 123 -21 79 123 0 -119 -71 10 #Pion = Down >StringView: >Length of Burst:12 >Int_view: -21 -53 123 79 111 123 79 123 107 123 -49 0 -119 -71 10 #Pion = Right >StringView: >Length of Burst:12 >Int_view: -53 -53 123 79 79 -53 123 123 79 123 123 0 -119 -71 10 #Pion L= eft >StringView: >NOTE: the first int is always omitted, it is always 0 or -128=20 > >_______________________________________________________________ > >Have big pipes? SourceForge.net is looking for download mirrors. We supp= ly >the hardware. You get the recognition. Email Us: bandwidth@sourceforge.n= et > > |
From: Alex S. <ros...@st...> - 2002-05-12 18:01:42
|
Hi Karl & all On Sunday 12 May 2002 18:28, Karl Bongers wrote: > Hi Alex, > > I did a google on Adaptec IR, but did not find anything on your dongle. Its an Adaptek AIRport 2000, a disconitued product several years old, als= o=20 called the avaXXXX. > It is probably either: > 1.) IRDA SIR dongle. Possible, since: - I did make it speak to my nokia6110 with gnokii=20 - I once made "discovery" of my Acer travelmate possible, using linux=20 "old_belkin" irda driver BUT, "old belkin" only reduces the max baudrate to 9600 and does not do m= uch=20 more. > 2.) IR Control(TV remote) dongle. Could it perhaps be both? I do get reliable data from the serial port. ... I mean, there are no incrementing "sequence" numbers in the output, or=20 anything else that looks like flow control and/or a protocoll. Could it be, that it is in "CIR" mode, until it gets some funky=20 "command-sequence"? OR, the other way round. That may explain the symptom= =20 described in my previous post "Initialisation of dongle required". > > Do you have any doc on this? What is it intended to be use as? No, as I say, discontinued product -> not much info. and that info was no= t=20 very helpfull to me. (looking for a "detailed" feature list ... i was hun= ting=20 for the terms ASKIR and CIR) I think, it was for syncronisation with early generation PDA -like device= s,=20 using propietary protocols, ... as in: Has to be able to deliver raw data. No, I kinda inherited the device, so it came without docs. And I dont think it came with a remote, but i would not know for sure. > Can you provide a link to the manufacturer page? > > If it is #2, then it was probably bundled with a certain remote, and th= e > hardware translates a certain IR control format to pre-processed RS232 > codes. It give replicable signals (length=3D 12 <=3D X <=3D 30) for the remotes = of=20 following devices: - Panasonic VCR NV-SD 350, can also control: - Panasonic TV TC-21L10R2=20 - Conrad IR-Keyboard-Mouse SK-7100 > > If it is #1, then it is translating IRDA style RS232(SIR) to a stream o= f > bytes on the RS232 port. > > Karl. So, do you think, after this information, and the sample IR output at the= end=20 of this mail, that i should=20 - try and do something in lirc_sir or - try to change one of the dongle-modules (logitech,creative, other hw_*.= c=20 files) ?=20 If you need more info, plese ask :) best regards, Alex > > Alex Stragies wrote: > >Hi all, > > > >My serial dongle runs with the logitech driver. I dont have a logitech= , i > >have an adaptek, but that is the driver that works the "best" for my > >hardware. ( i think) > > > >lircd compiles,loads, and lets me record a remote, pasted in below. > >At first sight you can see, something is wrong, and irrecord had also > >complained about " No toggle bit". > > > >however, restarting lircd with that new config and running irw shows c= odes > >like: > >000000000000a048 01 5 /root/test4 > >000000000000a040 00 Vol-UP /root/test4 > >000000000000a040 01 Vol-UP /root/test4 > >000000000000a044 00 3 /root/test4 > >000000000000a044 01 3 /root/test4 > >000000000000a052 00 Power /root/test4 > >... looking good, BUT: > > > >- Chan-UP is recognized as "5" > >- Mute, 0 are being recognized as "3" > >- TV/AV, Vol-DOWN, Chan-DOWN, 1,4,6,7,8 do not show up AT ALL > > > >Looking at the below codes (Panasonic), I see why. > > > >I tried with a different remote, a Pioneer, and all codes are recorded= as > >0x000000000000A0CE (see below) > > > >I wrote a little programm, that outputs series of ints from the serial > > port. Here, the commands are easily distinguished, so the dongle is > > working (see capture log below) > > > > > >Now, I dont know, where to go from here. > >Is there a setting i can change? > >use raw mode, perhaps? > >- but i dont like raw... it sounds cpu-intensive compared to > > LIRC_MODE_CODE Shall i try n hack logitech.c to make it work? > >Shall i try n adapt another driver? > >Do you want more info? > > > >thx already, > > Alex > > > >#(Panasonic) > >begin remote > > bits 8 > > eps 30 > > aeps 100 > > one 0 0 > > zero 0 0 > > pre_data_bits 8 > > pre_data 0xA0 > > gap 129983 > > min_repeat 27 > > toggle_bit 0 > > begin codes > > 1 0x0000000000000000 > > 2 0x0000000000000042 > > 3 0x0000000000000044 > > 4 0x0000000000000000 > > 5 0x0000000000000048 > > 6 0x0000000000000000 > > 7 0x0000000000000000 > > 8 0x0000000000000000 > > 9 0x0000000000000050 > > 0 0x0000000000000044 > > Power 0x0000000000000052 > > Vol-UP 0x0000000000000040 > > Vol-DOWN 0x0000000000000000 > > Chan-UP 0x0000000000000048 > > Chan-DOWN 0x0000000000000000 > > TV/AV 0x0000000000000000 > > Mute 0x0000000000000044 > > end codes > >end remote > > > >#(Pioneer) > > bits 16 > > eps 30 > > aeps 100 > > one 0 0 > > zero 0 0 > > gap 109998 > > toggle_bit 0 > > begin codes > > 1 0x000000000000A0CE > > 2 0x000000000000A0CE > > > > > ># Capturelog from serial dongle > >Typical commands look like (from both remotes): > >##Reading on IR-Device > >Length of Burst:12 > >Int_view: 93 85 85 85 85 85 85 117 85 93 -9 0 -119 -71 10 #Pana 1 > >StringView: EUR]UUUUUUuU]=F7 > >Length of Burst:12 > >Int_view: 93 85 85 85 85 85 -43 -43 -43 -43 117 0 -119 -71 10 #Pana 2 > >StringView: EUR]UUUUU=D5=D5=D5=D5u > >Length of Burst:12 > >Int_view: 93 85 85 85 85 85 85 117 -43 117 -35 0 -119 -71 10 #Pana 3 > >StringView: EUR]UUUUUUu=D5u=DD > >Length of Burst:12 > >Int_view: -53 -21 123 79 79 -53 79 123 79 111 123 0 -119 -71 10 #Pion = UP > >StringView: > >Length of Burst:12 > >Int_view: -53 -53 123 79 111 123 -53 123 -21 79 123 0 -119 -71 10 #Pio= n > > Down StringView: > >Length of Burst:12 > >Int_view: -21 -53 123 79 111 123 79 123 107 123 -49 0 -119 -71 10 #Pio= n > > Right StringView: > >Length of Burst:12 > >Int_view: -53 -53 123 79 79 -53 123 123 79 123 123 0 -119 -71 10 #Pion > > Left StringView: > >NOTE: the first int is always omitted, it is always 0 or -128 > > |
From: Karl B. <ka...@tu...> - 2002-05-13 05:28:19
|
Hi Alex, I've just started learning about some of this IR stuff, so please keep that in mind. Some IRDA SIR dongles use escape sequences to configure. For example, I'm looking at a Rohm RPM-800CB datasheet, also see linux/drivers/net/irda/girbil.c SIR runs off of RS232 protocol, but the physical bit is transformed into shorter pulses(3/16 of normal bit time). Also note that serial dongles may use the DTR & RTS signals to reset and provide power. It is possible that it could be set into CIR mode, but I doubt it. It's probably just for IRDA SIR and/or ASKIR. You are probably reading in Rx data from the SIR receiver. This data could appear as a repeatable data stream. You will get different results depending on the baudrate set. A number of LIRC drivers(not really drivers, see daemon/hw_*) just open the tty port and expect a sequence of pre-processed codes to appear. LIRC daemon does not try to do the low level timing. The lirc_sir driver opens the serial port hardware at 115200 and uses this fast rate to oversample the raw data. So it uses the RS232 rx & tx stream as a raw digital input/output. I suppose both methods could be made to function. It's all guess work unless you know whats in the dongle. If you want to try and make a driver based on the serial data received, then look at daemons/hw_pixelview.c, hw_silitek.c, hw_pinsys.c (three examples). You might want to try the lirc_sir driver. Alex Stragies wrote: >Hi Karl & all > >On Sunday 12 May 2002 18:28, Karl Bongers wrote: > >>Hi Alex, >> >>I did a google on Adaptec IR, but did not find anything on your dongle. >> >Its an Adaptek AIRport 2000, a disconitued product several years old, al= so=20 >called the avaXXXX. > >>It is probably either: >>1.) IRDA SIR dongle. >> > >Possible, since: >- I did make it speak to my nokia6110 with gnokii=20 >- I once made "discovery" of my Acer travelmate possible, using linux=20 >"old_belkin" irda driver >BUT, "old belkin" only reduces the max baudrate to 9600 and does not do = much=20 >more. > >>2.) IR Control(TV remote) dongle. >> > >Could it perhaps be both? I do get reliable data from the serial port. .= .. >I mean, there are no incrementing "sequence" numbers in the output, or=20 >anything else that looks like flow control and/or a protocoll. > >Could it be, that it is in "CIR" mode, until it gets some funky=20 >"command-sequence"? OR, the other way round. That may explain the sympto= m=20 >described in my previous post "Initialisation of dongle required". > >>Do you have any doc on this? What is it intended to be use as? >> > >No, as I say, discontinued product -> not much info. and that info was n= ot=20 >very helpfull to me. (looking for a "detailed" feature list ... i was hu= nting=20 >for the terms ASKIR and CIR) >I think, it was for syncronisation with early generation PDA -like devic= es,=20 >using propietary protocols, ... as in: Has to be able to deliver raw dat= a. > >No, I kinda inherited the device, so it came without docs. >And I dont think it came with a remote, but i would not know for sure. > >>Can you provide a link to the manufacturer page? >> >>If it is #2, then it was probably bundled with a certain remote, and th= e >>hardware translates a certain IR control format to pre-processed RS232 >>codes. >> > >It give replicable signals (length=3D 12 <=3D X <=3D 30) for the remotes= of=20 >following devices: >- Panasonic VCR NV-SD 350, can also control: >- Panasonic TV TC-21L10R2=20 >- Conrad IR-Keyboard-Mouse SK-7100 > >>If it is #1, then it is translating IRDA style RS232(SIR) to a stream o= f >>bytes on the RS232 port. >> >>Karl. >> > >So, do you think, after this information, and the sample IR output at th= e end=20 >of this mail, that i should=20 > >- try and do something in lirc_sir >or >- try to change one of the dongle-modules (logitech,creative, other hw_*= .c=20 >files) ?=20 > >If you need more info, plese ask :) > >best regards, > Alex > > >>Alex Stragies wrote: >> >>>Hi all, >>> >>>My serial dongle runs with the logitech driver. I dont have a logitech= , i >>>have an adaptek, but that is the driver that works the "best" for my >>>hardware. ( i think) >>> >>>lircd compiles,loads, and lets me record a remote, pasted in below. >>>At first sight you can see, something is wrong, and irrecord had also >>>complained about " No toggle bit". >>> >>>however, restarting lircd with that new config and running irw shows c= odes >>>like: >>>000000000000a048 01 5 /root/test4 >>>000000000000a040 00 Vol-UP /root/test4 >>>000000000000a040 01 Vol-UP /root/test4 >>>000000000000a044 00 3 /root/test4 >>>000000000000a044 01 3 /root/test4 >>>000000000000a052 00 Power /root/test4 >>>... looking good, BUT: >>> >>>- Chan-UP is recognized as "5" >>>- Mute, 0 are being recognized as "3" >>>- TV/AV, Vol-DOWN, Chan-DOWN, 1,4,6,7,8 do not show up AT ALL >>> >>>Looking at the below codes (Panasonic), I see why. >>> >>>I tried with a different remote, a Pioneer, and all codes are recorded= as >>>0x000000000000A0CE (see below) >>> >>>I wrote a little programm, that outputs series of ints from the serial >>>port. Here, the commands are easily distinguished, so the dongle is >>>working (see capture log below) >>> >>> >>>Now, I dont know, where to go from here. >>>Is there a setting i can change? >>>use raw mode, perhaps? >>>- but i dont like raw... it sounds cpu-intensive compared to >>>LIRC_MODE_CODE Shall i try n hack logitech.c to make it work? >>>Shall i try n adapt another driver? >>>Do you want more info? >>> >>>thx already, >>> Alex >>> >>>#(Panasonic) >>>begin remote >>> bits 8 >>> eps 30 >>> aeps 100 >>> one 0 0 >>> zero 0 0 >>> pre_data_bits 8 >>> pre_data 0xA0 >>> gap 129983 >>> min_repeat 27 >>> toggle_bit 0 >>> begin codes >>> 1 0x0000000000000000 >>> 2 0x0000000000000042 >>> 3 0x0000000000000044 >>> 4 0x0000000000000000 >>> 5 0x0000000000000048 >>> 6 0x0000000000000000 >>> 7 0x0000000000000000 >>> 8 0x0000000000000000 >>> 9 0x0000000000000050 >>> 0 0x0000000000000044 >>> Power 0x0000000000000052 >>> Vol-UP 0x0000000000000040 >>> Vol-DOWN 0x0000000000000000 >>> Chan-UP 0x0000000000000048 >>> Chan-DOWN 0x0000000000000000 >>> TV/AV 0x0000000000000000 >>> Mute 0x0000000000000044 >>> end codes >>>end remote >>> >>>#(Pioneer) >>> bits 16 >>> eps 30 >>> aeps 100 >>> one 0 0 >>> zero 0 0 >>> gap 109998 >>> toggle_bit 0 >>> begin codes >>> 1 0x000000000000A0CE >>> 2 0x000000000000A0CE >>> >>> >>># Capturelog from serial dongle >>>Typical commands look like (from both remotes): >>>##Reading on IR-Device >>>Length of Burst:12 >>>Int_view: 93 85 85 85 85 85 85 117 85 93 -9 0 -119 -71 10 #Pana 1 >>>StringView: EUR]UUUUUUuU]=F7 >>>Length of Burst:12 >>>Int_view: 93 85 85 85 85 85 -43 -43 -43 -43 117 0 -119 -71 10 #Pana 2 >>>StringView: EUR]UUUUU=D5=D5=D5=D5u >>>Length of Burst:12 >>>Int_view: 93 85 85 85 85 85 85 117 -43 117 -35 0 -119 -71 10 #Pana 3 >>>StringView: EUR]UUUUUUu=D5u=DD >>>Length of Burst:12 >>>Int_view: -53 -21 123 79 79 -53 79 123 79 111 123 0 -119 -71 10 #Pion = UP >>>StringView: >>>Length of Burst:12 >>>Int_view: -53 -53 123 79 111 123 -53 123 -21 79 123 0 -119 -71 10 #Pio= n >>>Down StringView: >>>Length of Burst:12 >>>Int_view: -21 -53 123 79 111 123 79 123 107 123 -49 0 -119 -71 10 #Pio= n >>>Right StringView: >>>Length of Burst:12 >>>Int_view: -53 -53 123 79 79 -53 123 123 79 123 123 0 -119 -71 10 #Pion >>>Left StringView: >>>NOTE: the first int is always omitted, it is always 0 or -128 >>> > >_______________________________________________________________ > >Have big pipes? SourceForge.net is looking for download mirrors. We supp= ly >the hardware. You get the recognition. Email Us: bandwidth@sourceforge.n= et > > |
From: Alex S. <ros...@st...> - 2002-05-13 10:07:08
|
Hi Karl & all On Monday 13 May 2002 07:31, you wrote: > Hi Alex, > > Some IRDA SIR dongles use escape sequences to configure. How would i find out about these? > also see linux/drivers/net/irda/girbil.c > SIR runs off of RS232 protocol, but the physical > bit is transformed into shorter pulses(3/16 of normal bit time). So it not the acurate representation of the signal, that i get. But, why should this *3/16* represention not be usable for recognition of= the=20 signals? OK, nobody will be able to use my config file for my remotes... > Also note that serial dongles may use the DTR & RTS signals to > reset and provide power. PcRemote.exe had them both ticked in the config. but i have not tried=20 anything else. > > It is possible that it could be set into CIR mode, but I doubt it. > It's probably just for IRDA SIR and/or ASKIR. the thing is, It cannot do more than 9600, (i think), so , using lirc_sir= ,=20 which emulates 38khz by using 115000 is not an option for me... > > You are probably reading in Rx data from the SIR receiver. Yes, with a normal read(fd,buf,255); > This data could appear as a repeatable data stream. REALLY, it does!. I have a paper table with all the codes now, and they a= re=20 *always* the same. > You will get different results depending on the baudrate set. That is true. But recognition and distance are the best with 2400 baud, a= nd=20 at 9600 my pioneer multiremote, that came with a VSX 409 RDS receiver, on= ly=20 prints out "-32 -32 -32 -32 -32 ..." Up to now, i have only tried 2400 and 9600. Do you think, i should try 1200, 4800 too? > > A number of LIRC drivers(not really drivers, see > daemon/hw_*) just open the tty port and expect > a sequence of pre-processed codes to appear. =20 like the hw_logitech. That one even works with my dongle and lirc, but, a= s i=20 say, "Not all keys are found and some are "confused"". I had a look at hw_logitech, and i can +- see, what it is doing, but i=20 thought, i may just have to broaden the "recognition-window", to make it = take=20 into account the bytes after the 8th. > > The lirc_sir driver opens the serial port hardware at 115200 > and uses this fast rate to oversample the raw data. So it > uses the RS232 rx & tx stream as a raw digital input/output. with a dongle-top-speed of 9600, this is not possible, no? And will i not get MUCH less distance, if i use lirc_sir (incase it works= )? > > I suppose both methods could be made to function. > It's all guess work unless you know whats in the dongle. > If you deem it usefull info, i can open the dongle, and see, what's in it. Any other info, help? best regards, Alex > > > Alex Stragies wrote: > >Hi Karl & all > > > >On Sunday 12 May 2002 18:28, Karl Bongers wrote: > >>Hi Alex, > >> > >>I did a google on Adaptec IR, but did not find anything on your dongl= e. > > > >Its an Adaptek AIRport 2000, a disconitued product several years old, = also > >called the avaXXXX. > > > >>It is probably either: > >>1.) IRDA SIR dongle. > > > >Possible, since: > >- I did make it speak to my nokia6110 with gnokii > >- I once made "discovery" of my Acer travelmate possible, using linux > >"old_belkin" irda driver > >BUT, "old belkin" only reduces the max baudrate to 9600 and does not d= o > > much more. > > > >>2.) IR Control(TV remote) dongle. > > > >Could it perhaps be both? I do get reliable data from the serial port.= ... > >I mean, there are no incrementing "sequence" numbers in the output, or > >anything else that looks like flow control and/or a protocoll. > > > >Could it be, that it is in "CIR" mode, until it gets some funky > >"command-sequence"? OR, the other way round. That may explain the symp= tom > >described in my previous post "Initialisation of dongle required". > > > >>Do you have any doc on this? What is it intended to be use as? > > > >No, as I say, discontinued product -> not much info. and that info was= not > >very helpfull to me. (looking for a "detailed" feature list ... i was > > hunting for the terms ASKIR and CIR) > >I think, it was for syncronisation with early generation PDA -like > > devices, using propietary protocols, ... as in: Has to be able to del= iver > > raw data. > > > >No, I kinda inherited the device, so it came without docs. > >And I dont think it came with a remote, but i would not know for sure. > > > >>Can you provide a link to the manufacturer page? > >> > >>If it is #2, then it was probably bundled with a certain remote, and = the > >>hardware translates a certain IR control format to pre-processed RS23= 2 > >>codes. > > > >It give replicable signals (length=3D 12 <=3D X <=3D 30) for the remot= es of > >following devices: > >- Panasonic VCR NV-SD 350, can also control: > >- Panasonic TV TC-21L10R2 > >- Conrad IR-Keyboard-Mouse SK-7100 > >- Pioneer VSX-409RDS receiver > > > >>If it is #1, then it is translating IRDA style RS232(SIR) to a stream= of > >>bytes on the RS232 port. > >> > >>Karl. > > > >So, do you think, after this information, and the sample IR output at = the > > end of this mail, that i should > > > >- try and do something in lirc_sir > >or > >- try to change one of the dongle-modules (logitech,creative, other hw= _*.c > >files) ? > > > >If you need more info, plese ask :) > > > >best regards, > > Alex > > > >>Alex Stragies wrote: > >>>Hi all, > >>> > >>>My serial dongle runs with the logitech driver. I dont have a logite= ch, > >>> i have an adaptek, but that is the driver that works the "best" for= my > >>> hardware. ( i think) > >>> > >>>lircd compiles,loads, and lets me record a remote, pasted in below. > >>>At first sight you can see, something is wrong, and irrecord had als= o > >>>complained about " No toggle bit". > >>> > >>>however, restarting lircd with that new config and running irw shows > >>> codes like: > >>>000000000000a048 01 5 /root/test4 > >>>000000000000a040 00 Vol-UP /root/test4 > >>>000000000000a040 01 Vol-UP /root/test4 > >>>000000000000a044 00 3 /root/test4 > >>>000000000000a044 01 3 /root/test4 > >>>000000000000a052 00 Power /root/test4 > >>>... looking good, BUT: > >>> > >>>- Chan-UP is recognized as "5" > >>>- Mute, 0 are being recognized as "3" > >>>- TV/AV, Vol-DOWN, Chan-DOWN, 1,4,6,7,8 do not show up AT ALL > >>> > >>>Looking at the below codes (Panasonic), I see why. > >>> > >>>I tried with a different remote, a Pioneer, and all codes are record= ed > >>> as 0x000000000000A0CE (see below) > >>> > >>>I wrote a little programm, that outputs series of ints from the seri= al > >>>port. Here, the commands are easily distinguished, so the dongle is > >>>working (see capture log below) > >>> > >>> > >>>Now, I dont know, where to go from here. > >>>Is there a setting i can change? > >>>use raw mode, perhaps? > >>>- but i dont like raw... it sounds cpu-intensive compared to > >>>LIRC_MODE_CODE Shall i try n hack logitech.c to make it work? > >>>Shall i try n adapt another driver? > >>>Do you want more info? > >>> > >>>thx already, > >>> Alex > >>> > >>>#(Panasonic) > >>>begin remote > >>> bits 8 > >>> eps 30 > >>> aeps 100 > >>> one 0 0 > >>> zero 0 0 > >>> pre_data_bits 8 > >>> pre_data 0xA0 > >>> gap 129983 > >>> min_repeat 27 > >>> toggle_bit 0 > >>> begin codes > >>> 1 0x0000000000000000 > >>> 2 0x0000000000000042 > >>> 3 0x0000000000000044 > >>> 4 0x0000000000000000 > >>> 5 0x0000000000000048 > >>> 6 0x0000000000000000 > >>> 7 0x0000000000000000 > >>> 8 0x0000000000000000 > >>> 9 0x0000000000000050 > >>> 0 0x0000000000000044 > >>> Power 0x0000000000000052 > >>> Vol-UP 0x0000000000000040 > >>> Vol-DOWN 0x0000000000000000 > >>> Chan-UP 0x0000000000000048 > >>> Chan-DOWN 0x0000000000000000 > >>> TV/AV 0x0000000000000000 > >>> Mute 0x0000000000000044 > >>> end codes > >>>end remote > >>> > >>>#(Pioneer) > >>> bits 16 > >>> eps 30 > >>> aeps 100 > >>> one 0 0 > >>> zero 0 0 > >>> gap 109998 > >>> toggle_bit 0 > >>> begin codes > >>> 1 0x000000000000A0CE > >>> 2 0x000000000000A0CE > >>> > >>> > >>># Capturelog from serial dongle > >>>Typical commands look like (from both remotes): > >>>##Reading on IR-Device > >>>Length of Burst:12 > >>>Int_view: 93 85 85 85 85 85 85 117 85 93 -9 0 -119 -71 10 #Pana = 1 > >>>StringView: EUR]UUUUUUuU]=F7 > >>>Length of Burst:12 > >>>Int_view: 93 85 85 85 85 85 -43 -43 -43 -43 117 0 -119 -71 10 #Pana = 2 > >>>StringView: EUR]UUUUU=D5=D5=D5=D5u > >>>Length of Burst:12 > >>>Int_view: 93 85 85 85 85 85 85 117 -43 117 -35 0 -119 -71 10 #Pana = 3 > >>>StringView: EUR]UUUUUUu=D5u=DD > >>>Length of Burst:12 > >>>Int_view: -53 -21 123 79 79 -53 79 123 79 111 123 0 -119 -71 10 #Pio= n UP > >>>StringView: > >>>Length of Burst:12 > >>>Int_view: -53 -53 123 79 111 123 -53 123 -21 79 123 0 -119 -71 10 #P= ion > >>>Down StringView: > >>>Length of Burst:12 > >>>Int_view: -21 -53 123 79 111 123 79 123 107 123 -49 0 -119 -71 10 #P= ion > >>>Right StringView: > >>>Length of Burst:12 > >>>Int_view: -53 -53 123 79 79 -53 123 123 79 123 123 0 -119 -71 10 #Pi= on > >>>Left StringView: > >>>NOTE: the first int is always omitted, it is always 0 or -128 |
From: Karl B. <ka...@tu...> - 2002-05-14 04:23:55
|
Hi Alex, I'd recommend building or buying some other hardware that is supported. There are some links on the LIRC page. It's tough to say what your hardware is doing. If it really does give you consistent codes you could write a LIRC driver for it but that will take some work. Or you could finish your simple serial port program(hey, whatever works!). Karl. Alex Stragies wrote: >Hi Karl & all > >On Monday 13 May 2002 07:31, you wrote: > >>Hi Alex, >> >>Some IRDA SIR dongles use escape sequences to configure. >> > >How would i find out about these? > >>also see linux/drivers/net/irda/girbil.c >>SIR runs off of RS232 protocol, but the physical >>bit is transformed into shorter pulses(3/16 of normal bit time). >> > >So it not the acurate representation of the signal, that i get. >But, why should this *3/16* represention not be usable for recognition o= f the=20 >signals? >OK, nobody will be able to use my config file for my remotes... > >>Also note that serial dongles may use the DTR & RTS signals to >>reset and provide power. >> > >PcRemote.exe had them both ticked in the config. but i have not tried=20 >anything else. > >>It is possible that it could be set into CIR mode, but I doubt it. >>It's probably just for IRDA SIR and/or ASKIR. >> > >the thing is, It cannot do more than 9600, (i think), so , using lirc_si= r,=20 >which emulates 38khz by using 115000 is not an option for me... > >>You are probably reading in Rx data from the SIR receiver. >> > >Yes, with a normal read(fd,buf,255); > >>This data could appear as a repeatable data stream. >> > >REALLY, it does!. I have a paper table with all the codes now, and they = are=20 >*always* the same. > >>You will get different results depending on the baudrate set. >> > >That is true. But recognition and distance are the best with 2400 baud, = and=20 >at 9600 my pioneer multiremote, that came with a VSX 409 RDS receiver, o= nly=20 >prints out "-32 -32 -32 -32 -32 ..." >Up to now, i have only tried 2400 and 9600. >Do you think, i should try 1200, 4800 too? > >>A number of LIRC drivers(not really drivers, see >>daemon/hw_*) just open the tty port and expect >>a sequence of pre-processed codes to appear. =20 >> > >like the hw_logitech. That one even works with my dongle and lirc, but, = as i=20 >say, "Not all keys are found and some are "confused"". > >I had a look at hw_logitech, and i can +- see, what it is doing, but i=20 >thought, i may just have to broaden the "recognition-window", to make it= take=20 >into account the bytes after the 8th. > >>The lirc_sir driver opens the serial port hardware at 115200 >>and uses this fast rate to oversample the raw data. So it >>uses the RS232 rx & tx stream as a raw digital input/output. >> > >with a dongle-top-speed of 9600, this is not possible, no? >And will i not get MUCH less distance, if i use lirc_sir (incase it work= s)? > >>I suppose both methods could be made to function. >>It's all guess work unless you know whats in the dongle. >> > >If you deem it usefull info, i can open the dongle, and see, what's in i= t. > >Any other info, help? > >best regards, > Alex > > >> >>Alex Stragies wrote: >> >>>Hi Karl & all >>> >>>On Sunday 12 May 2002 18:28, Karl Bongers wrote: >>> >>>>Hi Alex, >>>> >>>>I did a google on Adaptec IR, but did not find anything on your dongl= e. >>>> >>>Its an Adaptek AIRport 2000, a disconitued product several years old, = also >>>called the avaXXXX. >>> >>>>It is probably either: >>>>1.) IRDA SIR dongle. >>>> >>>Possible, since: >>>- I did make it speak to my nokia6110 with gnokii >>>- I once made "discovery" of my Acer travelmate possible, using linux >>>"old_belkin" irda driver >>>BUT, "old belkin" only reduces the max baudrate to 9600 and does not d= o >>>much more. >>> >>>>2.) IR Control(TV remote) dongle. >>>> >>>Could it perhaps be both? I do get reliable data from the serial port.= ... >>>I mean, there are no incrementing "sequence" numbers in the output, or >>>anything else that looks like flow control and/or a protocoll. >>> >>>Could it be, that it is in "CIR" mode, until it gets some funky >>>"command-sequence"? OR, the other way round. That may explain the symp= tom >>>described in my previous post "Initialisation of dongle required". >>> >>>>Do you have any doc on this? What is it intended to be use as? >>>> >>>No, as I say, discontinued product -> not much info. and that info was= not >>>very helpfull to me. (looking for a "detailed" feature list ... i was >>>hunting for the terms ASKIR and CIR) >>>I think, it was for syncronisation with early generation PDA -like >>>devices, using propietary protocols, ... as in: Has to be able to deli= ver >>>raw data. >>> >>>No, I kinda inherited the device, so it came without docs. >>>And I dont think it came with a remote, but i would not know for sure. >>> >>>>Can you provide a link to the manufacturer page? >>>> >>>>If it is #2, then it was probably bundled with a certain remote, and = the >>>>hardware translates a certain IR control format to pre-processed RS23= 2 >>>>codes. >>>> >>>It give replicable signals (length=3D 12 <=3D X <=3D 30) for the remot= es of >>>following devices: >>>- Panasonic VCR NV-SD 350, can also control: >>>- Panasonic TV TC-21L10R2 >>>- Conrad IR-Keyboard-Mouse SK-7100 >>>- Pioneer VSX-409RDS receiver >>> >>>>If it is #1, then it is translating IRDA style RS232(SIR) to a stream= of >>>>bytes on the RS232 port. >>>> >>>>Karl. >>>> >>>So, do you think, after this information, and the sample IR output at = the >>>end of this mail, that i should >>> >>>- try and do something in lirc_sir >>>or >>>- try to change one of the dongle-modules (logitech,creative, other hw= _*.c >>>files) ? >>> >>>If you need more info, plese ask :) >>> >>>best regards, >>> Alex >>> >>>>Alex Stragies wrote: >>>> >>>>>Hi all, >>>>> >>>>>My serial dongle runs with the logitech driver. I dont have a logite= ch, >>>>>i have an adaptek, but that is the driver that works the "best" for = my >>>>>hardware. ( i think) >>>>> >>>>>lircd compiles,loads, and lets me record a remote, pasted in below. >>>>>At first sight you can see, something is wrong, and irrecord had als= o >>>>>complained about " No toggle bit". >>>>> >>>>>however, restarting lircd with that new config and running irw shows >>>>>codes like: >>>>>000000000000a048 01 5 /root/test4 >>>>>000000000000a040 00 Vol-UP /root/test4 >>>>>000000000000a040 01 Vol-UP /root/test4 >>>>>000000000000a044 00 3 /root/test4 >>>>>000000000000a044 01 3 /root/test4 >>>>>000000000000a052 00 Power /root/test4 >>>>>... looking good, BUT: >>>>> >>>>>- Chan-UP is recognized as "5" >>>>>- Mute, 0 are being recognized as "3" >>>>>- TV/AV, Vol-DOWN, Chan-DOWN, 1,4,6,7,8 do not show up AT ALL >>>>> >>>>>Looking at the below codes (Panasonic), I see why. >>>>> >>>>>I tried with a different remote, a Pioneer, and all codes are record= ed >>>>>as 0x000000000000A0CE (see below) >>>>> >>>>>I wrote a little programm, that outputs series of ints from the seri= al >>>>>port. Here, the commands are easily distinguished, so the dongle is >>>>>working (see capture log below) >>>>> >>>>> >>>>>Now, I dont know, where to go from here. >>>>>Is there a setting i can change? >>>>>use raw mode, perhaps? >>>>>- but i dont like raw... it sounds cpu-intensive compared to >>>>>LIRC_MODE_CODE Shall i try n hack logitech.c to make it work? >>>>>Shall i try n adapt another driver? >>>>>Do you want more info? >>>>> >>>>>thx already, >>>>> Alex >>>>> >>>>>#(Panasonic) >>>>>begin remote >>>>>bits 8 >>>>>eps 30 >>>>>aeps 100 >>>>>one 0 0 >>>>>zero 0 0 >>>>>pre_data_bits 8 >>>>>pre_data 0xA0 >>>>>gap 129983 >>>>>min_repeat 27 >>>>>toggle_bit 0 >>>>> begin codes >>>>> 1 0x0000000000000000 >>>>> 2 0x0000000000000042 >>>>> 3 0x0000000000000044 >>>>> 4 0x0000000000000000 >>>>> 5 0x0000000000000048 >>>>> 6 0x0000000000000000 >>>>> 7 0x0000000000000000 >>>>> 8 0x0000000000000000 >>>>> 9 0x0000000000000050 >>>>> 0 0x0000000000000044 >>>>> Power 0x0000000000000052 >>>>> Vol-UP 0x0000000000000040 >>>>> Vol-DOWN 0x0000000000000000 >>>>> Chan-UP 0x0000000000000048 >>>>> Chan-DOWN 0x0000000000000000 >>>>> TV/AV 0x0000000000000000 >>>>> Mute 0x0000000000000044 >>>>> end codes >>>>>end remote >>>>> >>>>>#(Pioneer) >>>>>bits 16 >>>>>eps 30 >>>>>aeps 100 >>>>>one 0 0 >>>>>zero 0 0 >>>>>gap 109998 >>>>>toggle_bit 0 >>>>> begin codes >>>>> 1 0x000000000000A0CE >>>>> 2 0x000000000000A0CE >>>>> >>>>> >>>>># Capturelog from serial dongle >>>>>Typical commands look like (from both remotes): >>>>>##Reading on IR-Device >>>>>Length of Burst:12 >>>>>Int_view: 93 85 85 85 85 85 85 117 85 93 -9 0 -119 -71 10 #Pana = 1 >>>>>StringView: EUR]UUUUUUuU]=F7 >>>>>Length of Burst:12 >>>>>Int_view: 93 85 85 85 85 85 -43 -43 -43 -43 117 0 -119 -71 10 #Pana = 2 >>>>>StringView: EUR]UUUUU=D5=D5=D5=D5u >>>>>Length of Burst:12 >>>>>Int_view: 93 85 85 85 85 85 85 117 -43 117 -35 0 -119 -71 10 #Pana = 3 >>>>>StringView: EUR]UUUUUUu=D5u=DD >>>>>Length of Burst:12 >>>>>Int_view: -53 -21 123 79 79 -53 79 123 79 111 123 0 -119 -71 10 #Pio= n UP >>>>>StringView: >>>>>Length of Burst:12 >>>>>Int_view: -53 -53 123 79 111 123 -53 123 -21 79 123 0 -119 -71 10 #P= ion >>>>>Down StringView: >>>>>Length of Burst:12 >>>>>Int_view: -21 -53 123 79 111 123 79 123 107 123 -49 0 -119 -71 10 #P= ion >>>>>Right StringView: >>>>>Length of Burst:12 >>>>>Int_view: -53 -53 123 79 79 -53 123 123 79 123 123 0 -119 -71 10 #Pi= on >>>>>Left StringView: >>>>>NOTE: the first int is always omitted, it is always 0 or -128 >>>>> > >_______________________________________________________________ > >Have big pipes? SourceForge.net is looking for download mirrors. We supp= ly >the hardware. You get the recognition. Email Us: bandwidth@sourceforge.n= et > > |