GPIO Pins / Controller Service

[sunilbass]

So now, do the same via relay. Results shall be the same. You should be able to detect change of the state. Does it work?

Yes they are the same but oap isnt responding ie send vol up. to it volume stays the same etc

Again with raspi-gpio get it is showing the gpio are going from low to high to low

And what are the values when you add pull-up resistors to the circut? OpenAuto Pro uses sysfs gpio interface (from Linux kernel) which does not simulate the pull-up.

using piscope when pull up resistors are added, when trigger is applied, it goes high and low once trigger is off

[sunilbass]

So now, do the same via relay. Results shall be the same. You should be able to detect change of the state. Does it work?

Yes they are the same but oap isnt responding ie send vol up. to it volume stays the same etc

Again with raspi-gpio get it is showing the gpio are going from low to high to low

And what are the values when you add pull-up resistors to the circut? OpenAuto Pro uses sysfs gpio interface (from Linux kernel) which does not simulate the pull-up.

using piscope when pull up resistors are added, when trigger is applied, it goes high and low once trigger is off

so today i install oap15 with same issue, no gpio inputs to turn vol up etc

i did test with a keyboard and that works so i guess there's a issue with gpio inputs? this was also a direct connection to the gpio and with pull up resistors.

[BlueWave]

Could you please post pictures of your circuit?

Please also remove instance controller_service from the autostart, run it in the terminal and post the output.

[sunilbass]

Could you please post pictures of your circuit?

Please also remove instance controller_service from the autostart, run it in the terminal and post the output.

I have removed it from autostart.

However i can not get the file to run in the terminal (command not found) Sorry im a newbie to pi, any pointers to get it to run from the terminal?

Thanks

[Daniel_BlueWave]

This is good starting point for Rpi GPIO topic:
https://learn.sparkfun.com/tutorials/raspberry-gpio/all

Based on that try to write a script that will take action (eg print something on the console) after the state will change at your relays board. This should allow to verify your hardware connections.

[Kleekru]

This is good starting point for Rpi GPIO topic:
https://learn.sparkfun.com/tutorials/raspberry-gpio/all

Based on that try to write a script that will take action (eg print something on the console) after the state will change at your relays board. This should allow to verify your hardware connections.

Did this get resolved?  If so, what was the resolution?  I have a simpler issue with a much simpler setup but cannot get it to recognize a button push...  just one pin (25) with a Key stroke = Down to navigate (called openauto_controller_service_navdown.ini and added to autostart) to from the main buttons to the back button at the bottom menu which I cannot get to with the left/right navigation directions of the rotary encoder (which is working fine via the controller service along with a separate instance for volume up/down & mute).  Is there a better way to get to the lower part of the OAP screen without using touch (I have a small single din screen and getting to that part of the screen is challenging without navigation.  I used a pull up resistor... still no go.  This was the last step before my install... super frustrating.  I hope it is something simple.  Is it ok to have 3 instances running?