OK, I have a new theory (though, technically it's not my theory).
I had my mate come round yesterday. He's the one I mentioned in the
previous thread who is a bit of an electronics whizz. He looked at the
IR sensor datasheet and the previous thread and doesn't think the
suggested cap and resistor as suggested in the "application" diagram on
the vendor datasheet would have anything to do with this, especially
when IRW is showing single events (mostly).
However, his theory is that it's to do with timing, and button press vs
button release. He spends his day job working with interfaces ("screens
and buttons") for a large car manufactuerer making car radios work, and
this is the kind of thing he spends half his life working on.
I wonder if it's not apparently been seen by very many people (yet) is
because I'm running on a 3B+ and most (or at least many) people up until
now have been using this IR setup on an older/slower Pi?
Anyway, we looked at the config yesterday and whilst playing with it we
realised that if you hold the power button long enough for the
auto-repeat to kick in, it *will* then reliably turn Jive on (or off).
He thinks it's a timing issue, coupled with the fact that there there
might be an event in Jive taking place for both button press and button
hold/release.
His suggestion is, to remove the button press event for power, to be
left with a hold event for power only in
/opt/jivelite/share/jive/jive/InputToActionMap.lua. That would mean you
would have to press and hold the power button to turn it on and off, but
actually I like that idea, to make it a little more deliberate to turn
it on or off.
What would be the "best" (easiest/quickest) way of changing (removing)
the "on press" event for power in
/opt/jivelite/share/jive/jive/InputToActionMap.lua so I could test this
(presumably, if you change this file, you need to restart Jive to
re-read the file?) - is it possible to do this without making the change
permanent, and to avoid having to do a reboot, so I can test this?
Obviously, if it does fix it, I'd make it persistent later.
I am also tempted to replace my 3B+ with a spare 2B I have lying around,
to see if just changing to a slower Pi makes any difference. I have a
pretty much standard piCore setup (just Pi 3B+, + 7" touch screen +
Squeezelite + Jive + lirc, using inbuilt audio out (for now), with the
"standard" IR module on the "default" GPIO pins. I'd expect many more
people to have the same problem as me, but it seems not a common
problem, at least at the moment.
One other quick one, Raplhy, I thought that the Harmony discreet
power-on and power-off were now part of the standard config, but it
seems it's not enabled in my config (piCorePlayer v4.0)?
I need to find time to play further, but any
thoughts/comments/suggestions?
Cheers,
Matt.
------------------------------------------------------------------------
mutant_matt's Profile: http://forums.slimdevices.com/member.php?userid=37288
View this thread: http://forums.slimdevices.com/showthread.php?t=109786
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
