<xiangfu>
the only problem for me, is the same key give me different value some time.
<xiangfu>
and single press, there are 2~3 values sometimes
<lekernel>
er, what is it supposed to do?
<lekernel>
remove the capture button?
<lekernel>
why?
<lekernel>
if you have inconsistent values, either your remote isn't RC5 or there is a bug somewhere
<lekernel>
concealing the problem by hiding the values is obviously not ok
<xiangfu>
then if there is consistent values. we don't need 'capture' button at all. because you will need that when you open the windows
<lekernel>
?
<lekernel>
the purpose of the "capture" button is to grab the code that is sent from a particular key on the remote
<lekernel>
so you don't have to look up RC5 specs and just press the button you want instead
<lekernel>
ah, sorry, I didn't see you were always enabling capture mode
<xiangfu>
hmm.. I mean. 1. when open the  IR window, we should just add the 'ir input event'  2. press keys in remote controller 3, add file name. 4. press 'add/update'
<lekernel>
uhm, well, ok then
<lekernel>
but do the same for MIDI
<xiangfu>
oh(sorry for bad/slow English)
<xiangfu>
ok. I will commit IR first. then MIDI
<wolfspraul>
we renamed something to 'ssd'
<wolfspraul>
I'm confused about that, I don't think that name is very good.
<wolfspraul>
ssd = solid state drive?
<lekernel>
yes
<lekernel>
it's better than "flash" which people confuse with the macromedia thing
<lekernel>
ssd either means nothing or "solid state drive", which is pretty close to what the flash filesystem is
<wolfspraul>
xiangfu: can you explain more about the inconsistent remote control values you see?
<wolfspraul>
lekernel: OK I understand the 'flash' problem, but ssd...
<wolfspraul>
maybe just data or so?
<wolfspraul>
well, it's a detail
<wolfspraul>
this kind of cryptic thing is bad, generally. people feel they are too stupid to use the product.
<xiangfu>
(inconsistent value) when I press one button many times. it's give me 0c, 08, 2c.
<wolfspraul>
let's do a test. press the same button 20 times, how many 0c, how many 08, how many 2c?
<wolfspraul>
lekernel: fyi - these inconsistencies are with the 'gold standard' rc-5 control Adam is using for testing too, so I'm surprised we see this kind of inconsistencies. Want to find out what's going on.
<xiangfu>
0x0C: 10, 0x2C: 6, 0x08: 4.
<wolfspraul>
how about other buttons?
<xiangfu>
some keys have 4,5 different values.
<wolfspraul>
this looks very random to me. does it work at all?
<wolfspraul>
xiangfu: obviously this is not working right now ;-)
<wolfspraul>
xiangfu: can you press a few more buttons 20 times and tell us what you see?
<wolfspraul>
are you using the remote through the acrylic case? can you try to remove the acrylic on that side? just want to rule out that the acrylic is causing any problem...
<xiangfu>
ok
<lekernel>
what is the value supposed to be, according to the rc5 standard?
<lekernel>
also it works reliably for me (as usual) with the remote I have...
<lekernel>
ssd isn't cryptic, it's all over computer advertisements
<xiangfu>
ok. then the remote controller is not RC5 probability
<wolfspraul>
no way. this is the remote controller Adam sent you months ago for testing. and he uses for testing too.
<wolfspraul>
Adam is off on a public holiday today, we'll ask him tomorrow to test on his end too
<wolfspraul>
xiangfu: how many remote controllers do you have that you think are rc-5?
<wolfspraul>
do all of them show these inconsistencies?
<wolfspraul>
can you try to press the same key 20 times on each of them, and tell us what you get?
<xiangfu>
4. all have inconsistencies
<xiangfu>
there is not same key. all remote controller different
<lekernel>
xiangfu, the rc5 standard specifies a code that is associated to a particular key
<lekernel>
for example keys 0-9 have codes 0x00-0x09
<lekernel>
do you get those codes sometimes, or something totally different?
<wolfspraul>
xiangfu: from now on. if there is an inconsistency, the remote control does not work!
<wolfspraul>
inconsistency obviously is unacceptable to an end user :-)
<wolfspraul>
so you have 0 remote controls right now that work
<wolfspraul>
good point - do you have any control that gives you a value of 0x05 when you press '5'?
<xiangfu>
no
<xiangfu>
lekernel: something totally different
<lekernel>
iirc there is a "dump remote" command in the demo firmware, try that
<lekernel>
if you still get inconsistent values there, it's either a fpga design problem or an incompatible remote
<xiangfu>
where is demo firmare? not in github/flickernoise.git
<wolfspraul>
maybe none of his remote controls are actually rc5?
<lekernel>
in milkymist.git
<lekernel>
software/demo
<xiangfu>
wolfspraul: probability
<wolfspraul>
and Adam also is using a non-rc5 control for his testing, and sent Xiangfu the wrong one too?
<wolfspraul>
well, we have to clear this up fast :-) good that we are focused on this now
<wolfspraul>
xiangfu: from now on - please help us find _WORKING_ remote controls :-)
<wolfspraul>
I will go shopping now, try to find some too.
<wolfspraul>
I have 3 here, none of them work.
<lekernel>
philips brand should be ok
<xiangfu>
the one Adam send to me. not working.
<wolfspraul>
we didn't really focus on this before, but now we do
<wolfspraul>
maybe so far Adam's testing was really just to see _any_ value
<wolfspraul>
I think I vaguely remember seeing 0x2B/2C values in the rc2 testing, let me check the logs...
<xiangfu>
(_any_ value) for me it is. :(
<wolfspraul>
with the 3 controls I have here I also get 0x2A/0x2B values sometimes, but obviously overall the thing is not working for me
<wolfspraul>
xiangfu: can you press the power button on the remote Adam sent you? what value do you get?
<wolfspraul>
if you press the power button 20 times, are there inconsistencies?
<xiangfu>
no power button, only 'standby'
<xiangfu>
I take a picture of the remote controller.
<xiangfu>
one memont.
<wolfspraul>
maybe just press that button...
<xiangfu>
it give. 0C, 26, 0E
<wolfspraul>
do you have the acrylic on or removed?
<xiangfu>
removed.
<wolfspraul>
xiangfu: which image are you running? can you try to go back to some older images, or the msd ones from Sebastien, to see whether some of them work?
<wolfspraul>
maybe focus on that power (standby?) button, and try to get a consistent 0x0c
<wolfspraul>
you can also try the testing images, we probably still have them somewhere
<wolfspraul>
when testing the 40 boards from rc2, I don't remember ever running into this test failing
<wolfspraul>
so if we had the 0x0c check back then, there shouldn't be a way that an inconsistency slipped through somehow, I should have seen that at least a few times on those 40 boards (which were tested several times too)
<xiangfu>
wolfspraul: I amd using test image now.
<xiangfu>
wolfspraul: some keys give [PASSWD]. mute keys always give [PASSED]
<xiangfu>
mute keys. 10 times, 9 times give [PASSED].
<xiangfu>
I never got a [FAILED], most keys have no raction.
<xiangfu>
once test image raction, it give [PASSED]
<xiangfu>
ok. there is no [FAILED] in source code. :_
<xiangfu>
:)
<wolfspraul>
wait wait wait
<wolfspraul>
I don't understand
<wolfspraul>
10 times, 9 times pass is also not enough. it needs to be 100%
<wolfspraul>
why do 'some other' keys pass as well?
<lekernel>
because the RC5 decoder gets some random garbage
<wolfspraul>
so you are saying with the test software at least in 90% you get a 0x0c value?
<lekernel>
and this garbage happens to contain 0x0c
<lekernel>
period
<wolfspraul>
lekernel: you think none of those controls are rc5, and that explains the problems?
<lekernel>
do you have a logic analyzer? check at the output of the IR sensor that you get RC5 frames
<lekernel>
maybe
<xiangfu>
I don't have that. :(
<lekernel>
you can try xilinx chipscope, if you dare ...
<lekernel>
but I never got it to work
<lekernel>
maybe Adam has a proper one?
<wolfspraul>
xiangfu: when you bought some of your remotes, did they specifically say 'rc-5'?
<lekernel>
or just a digital oscilloscope should be ok ...
<xiangfu>
wolfspraul: no specifical say 'rc-5'
<xiangfu>
wolfspraul: now. I just order three. all them specitical rc-5. just it's not the small one. all big remote controllers
<wolfspraul>
ok
<wolfspraul>
you mean you just ordered them?
<wolfspraul>
so they arrive in a few days?
<xiangfu>
yes. I just ordered them on taobao. should be arrive in 2~3 days.
<xiangfu>
I don't have a device that can test MIDI. :(, I found there is a Channel 0~15, is that also from MIDI? or must input by user?
<wpwrak>
(rc5) why rc5 ? there's a gazillion different protocols. may be easier to just work with general patterns after AM demodulation.
<roh>
wpwrak: why rc5? i think because its 'a standard' not 'none' .)
<wpwrak>
roh: well, it's a bit like setting up an international web shop that accepts only payments in uruguayan pesos. sure, it's a well-enough established "standard", but ...
<roh>
comeon... rc5 isnt at all 'seldomly'
<roh>
its rather like 'euro' or 'us$' compared to stuff avail
<wpwrak>
roh: some time ago, i experimented a bit with IR remotes. they basically all exhibited wildly different patterns. i didn't even bother to try to figure out what higher layers could be there, just treat this as a stream on on/off intervals.
<roh>
sure. just makes for more ugly decoders. stuff ends up looking like lirc (detecting on-off pattern times ;)
<wpwrak>
roh: maybe 1-2 in ten were rc5. maybe 1-2 in then "sony". the bottom line is that there's not really any standard.
<wpwrak>
(ugly decoders) yes, ugly decoders that work ;-)
<roh>
wpwrak: true. there are multiple ones. get one from philips and it will work
<wpwrak>
vs. theoretically perfect decoders that will work with a perfect remote control. if xiangfu buys a batch of "rc5" remotes and none of them works, does that suggest something about the fun prospective end users will have ? ;-)
<roh>
eh. simple: dont buy batches of untested stuff ;)
<lekernel>
wpwrak, then maybe you'd like to port your wonderful remote control recognition software to MM? :)
<wpwrak>
lekernel: hihi, it's actually just record and playback. and runs on a PIC. one of my very first experiments with an MCU ;-)
<lekernel>
there are tons of stuff in MM which are "actually just xxx" :)
<wpwrak>
maybe LIRC already has what you need in terms of remote control recognition ? they ought to be quite flexible on the driver side
<roh>
wpwrak: they detect space and mark, and do patterns from there.
<roh>
flexible yes. but pain to confiugure. in the end it doesnt matter. deliver a remote that works.
<roh>
compat. with 10-20% of the market is already more than usual for ir-stuff.
<wpwrak>
roh: space/mark. yup, i think that's about the lowest common denominator. well, besides fun with the carrier frequency. (there are all sorts of carriers, several in 30-39 kHz, 56 kHz, and i'm sure there's more)
<wpwrak>
roh: picking one "standard" remote to ship with the device is an entirely different story. there you're free to put whatever requirements you fancy.
<roh>
anyhow. need to run now. but thats a 'enough battles, this one isnt worth it' issue ;)
<roh>
you can make anything better. sometimes it doesnt matter. its good enough for now (and doesnt need any changing) .. btw.. the 38khz or what filter is already in the ir-reciever usually, so that is the only thing fixed by hw
<wpwrak>
(38 kHz filter) yeah. usually not much choice there, if you use a fully integrated receiver.
<wpwrak>
"roh withdraws from battle without admission of defeat" so it shall be recorded ;-)
<wpwrak>
the nice thing about patents is that they're not elitist at all. even the dullest engineer will have a dozen ideas every day that would be worth a patent or two ;-)
<lekernel>
looks ok
<lekernel>
well, you need a significant sum of money to have patents
<lekernel>
the application itself costs, plus the lawyers you need to speak legalese and get the necessary amount of red tape
<wpwrak>
lekernel: i was trying to be sarcastic :) attacking the aspect of "an idea worth excessive amounts of privilege"
<lekernel>
patents aren't even that, they're just yet another tool that bureaucrats use to get power
<terpstra>
lekernel, is it possible you took the wrong power supply with you?
<lekernel>
mh, probably not... back home, unpacked everything and didn't find anything that wasn't mine
<lekernel>
what does yours look like?
<terpstra>
it's 12v +center
<terpstra>
and i have an unknown power supply on my desk
<terpstra>
16v +center ... that isn't mine
<terpstra>
but, anyway, maybe one of my colleagues borrowed it. nevermind.
<lekernel>
I don't have anything 16V
<wpwrak>
i think i'll keep that quote for my "famous last words / self-fulfilling prophecy" collection ;-)