Digital Input doesn't work with RaspBerry

Lucifer06 commented 4 months ago

Relays confirm to work with RaspBerry, but Digital Input won't. It will require additional work for making Digital Inputs working with RaspBerry. This was tested with Venus 3.40-2 and RemoteGPIO 3.2.2

cbelcher commented 4 months ago

You're free France email address has been sending me NDR's for days now. Hit me with a real email. I'm so close to having this working. Have one question.

Been searching what creates the directory, for example: /data/RemoteGPIO/sys/devices/platform/soc/1c20800.pinctrl/gpiochip0/gpio/gpio205

Answer me that and I'm sure it'll work :)

Hope you enjoyed Vegas! Cheers

Lucifer06 commented 4 months ago

Hello Craig, don't see any issue from my side with my free.fr email. Anyway here is an alternate one if needed: @. The /data/RemoteGPIO/sys/devices/platform/soc/1c20800.pinctrl/gpiochip0/gpio/gpio205 is coming from the package itself. I created these folders manually and are downloaded as a zip with the package (see in the install script). Then I creates links from these to the /dev/GPIo, depending on GUI configuration. These links are created with the /etc/rcS.d/S90rgpio scriptHope it helped,FreD. Excuse possible typo: swallowed by my iPhoneLe 16 avr. 2024 à 03:21, Craig Belcher @.> a écrit : You're free France email address has been sending me NDR's for days now. Hit me with a real email. I'm so close to having this working. Have one question. Been searching what creates the directory, for example: /data/RemoteGPIO/sys/devices/platform/soc/1c20800.pinctrl/gpiochip0/gpio/gpio205 Answer me that and I'm sure it'll work :) Hope you enjoyed Vegas! Cheers

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

cbelcher commented 4 months ago

Oh there's something wrong :) GitHub Stripped your address and mine, thank goodness. Send me one from your alternate address.

cbelcher commented 4 months ago

Now that I have this thing working on the Pi, noticed that dbus_digitalinputs.py, is throwing an exception. Not often, 5 times in 1 hour and 10 minutes of uptime.

Traceback output:

@40000000661fd8230c4843a4 File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 614, in poll @40000000661fd8230c48572c for inp, level in pulses(): @40000000661fd8230c4862e4 File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 169, in call @40000000661fd8230c486e9c v = int(fp.read()) @40000000661fd8230c496c84 ValueError: invalid literal for int() with base 10: b'' @40000000661fd823120de12c starting dbus-digitalinputs

trace give you any clues what's going on?

Looks like it has something to do with the DT-R008 and its Input registration status? Been trying to catch it with dbus-monitor, but I don't see anything that is not an integer being returned. I must have my filter set incorrectly to catch it.

Other than that, it works perfectly. I'll find it eventually, if your busy.

Having fun learning all this new stuff.

Lucifer06 commented 4 months ago

Well-done!We will chat when I'm back so I can put your rpi specific modifications in the main release. For the error I have no clue...Excuse possible typo: swallowed by my iPhoneLe 17 avr. 2024 à 09:49, Craig Belcher @.> a écrit : Now that I have this thing working on the Pi, noticed that dbus_digitalinputs.py, is throwing an exception. Not often, 5 times in 1 hour and 10 minutes of uptime. Traceback output: @40000000661fd8230c4843a4 File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 614, in poll @40000000661fd8230c48572c for inp, level in pulses(): @40000000661fd8230c4862e4 File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 169, in call @40000000661fd8230c486e9c v = int(fp.read()) @40000000661fd8230c496c84 ValueError: invalid literal for int() with base 10: b'' @40000000661fd823120de12c starting dbus-digitalinputs *** trace give you any clues what's going on? Looks like it has something to do with the DT-R008 and its Input registration status? Been trying to catch it with dbus-monitor, but I don't see anything that is not an integer being returned. I must have my filter set incorrectly to catch it. Other than that, it works perfectly. I'll find it eventually, if your busy. Having fun learning all this new stuff.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

cbelcher commented 4 months ago

Can either of you check the value of com.victronenergy.packageManager/Platform on your Cerbo GX's? I'm assuming you have MK1's. I've got a MK2 and has a value of "einstein". Is that also the same for both variants? I've got my dealer checking on what an Ekrano has this value set to. Figured if I'm dealing with checking on the platform to address the RPi DI issue, might as well deal with them all.

drtinaz commented 4 months ago

If you look in Kevin's package manager helper resources he has code in there for checking what platform is being used. His code covers all platforms.

cbelcher commented 4 months ago

Thank you, sir,

I’ve forked your project, cloned it, I need to read about this commit business. There’s nothing I can break, can I? Got me a little worried, that I might.

From: Derrick @.> Sent: Wednesday, April 24, 2024 8:04 AM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Comment @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

If you look in Kevin's package manager helper resources he has code in there for checking what platform is being used. His code covers all platforms.

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2074784597, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNJ2NZFOFRKIEZACCY3Y66NSFAVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZUG44DINJZG4. You are receiving this because you commented.Message ID: @.**@.>>

cbelcher commented 4 months ago

If found where he looks at /etc/venus/machine for the platform in CommonResources, but he’s just looking to see if it’s a RPi or not. I’ll keep hunting for an actual list. But sure is a better way to check the platform, then my elaborate d-bus call.

From: Derrick @.> Sent: Wednesday, April 24, 2024 8:04 AM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Comment @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

If you look in Kevin's package manager helper resources he has code in there for checking what platform is being used. His code covers all platforms.

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2074784597, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNJ2NZFOFRKIEZACCY3Y66NSFAVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZUG44DINJZG4. You are receiving this because you commented.Message ID: @.**@.>>

drtinaz commented 4 months ago

I can't remember exactly where it is but I did see it in there just day before yesterday when I was looking for something else. There is a section where he checks for every platform old and new.

cbelcher commented 4 months ago

I’ll find it.

Sent from my iPhone

On Apr 25, 2024, at 10:37 AM, Derrick @.***> wrote:

I can't remember exactly where it is but I did see it in there just day before yesterday when I was looking for something else. There is a section where he checks for every platform old and new.

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2077366049, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNIM2YB36XPJNLZQZQ3Y7EIL5AVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXGM3DMMBUHE. You are receiving this because you commented.Message ID: @.***>

cbelcher commented 4 months ago

I found this some time ago. Bug…? Not consistent, for sure.

It’s in the S90rgpio_pins.sh script.

In the Create conf files , Handle Module 1 section.

You deal with Relay’s correctly, since in starts at 3. But DI’s start at 5, on Cerbo's. You handle DI - 10 correctly and set to “a”. DI 11 & 12 not so much.

Output of the Digital_Inputs_unit1.conf.

Goes: 9, a, 11, 12.

/dev/gpio/digital_input_5/value /dev/gpio/digital_input_6/value /dev/gpio/digital_input_7/value /dev/gpio/digital_input_8/value /dev/gpio/digital_input_9/value /dev/gpio/digital_input_a/value /dev/gpio/digital_input_11/value <- b? I’ve updated my script, and it works fine as a b. /dev/gpio/digital_input_12/value < - c Same deal here.

I’ve got to figure out how to get my S90 on GitHub. It’s code or figure out this dang Microsoft GitHub, not a big MS fanboy.

Works like a champ on RPI 3, 4B and Cerbo.

But all my work is in vein, if I can't get it to you guys.

drtinaz commented 4 months ago

Good catch. I'll get that fixed straight away.

drtinaz commented 4 months ago

@cbelcher I have made the changes to S90 and issued a PR. @Lucifer06 can merge and create a new release.

cbelcher commented 4 months ago

Nice!

From: Derrick @.> Sent: Thursday, April 25, 2024 6:56 PM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Mention @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

@cbelcherhttps://github.com/cbelcher I have made the changes to S90 and issued a PR. @Lucifer06https://github.com/Lucifer06 can merge and create a new release.

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2078300906, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNJYNQ26QQ4E73MXS7TY7GCXTAVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZYGMYDAOJQGY. You are receiving this because you were mentioned.Message ID: @.**@.>>

Lucifer06 commented 4 months ago

Well-done guys! PR applied on v3.3.2

Lucifer06 commented 4 months ago

@cbelcher can you confirm that on the shelf version 3.3.2 is working on your Raspberry (both relays and Digital Inputs), with no further modification?

cbelcher commented 4 months ago

You bet; I’m coding as I type this. Keep you posted.

From: Lucifer06 @.> Sent: Friday, April 26, 2024 2:34 AM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Mention @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

@cbelcherhttps://github.com/cbelcher can you confirm that on the shelf version 3.3.2 is working on your Raspberry (both relays and Digital Inputs), with no further modification?

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2078720594, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNNLXT5GORL4XBX4U3DY7HYOZAVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZYG4ZDANJZGQ. You are receiving this because you were mentioned.Message ID: @.**@.>>

cbelcher commented 4 months ago

No it does not. RemoteGPIO v3.3.2 has killed my RPi fix. Been trying to tack it down. I see the changes to S90 and moving it to the rcS.d directory. I've dealt with them, just nothing not even my Relays work any more. Firing up the Cerbo and see what's different.
Where do I look for all the modified files from 3.2.2 I'm sure I'll find them if I look hard enough. With that I can narrow down my target.

Lucifer06 commented 4 months ago

The changes was on S90Let me know what the changes you are making for having the rpi working and I will add it to the standard repo so you will enjoy any new updates with no pain...Excuse possible typo: swallowed by my iPhoneLe 26 avr. 2024 à 20:23, Craig Belcher @.***> a écrit : No it does not. RemoteGPIO v3.3.2 has killed my RPi fix. Been trying to tack it down. I see the changes to S90 and moving it to the rcS.d directory. I've dealt with them, just nothing not even my Relays work any more. Firing up the Cerbo and see what's different. Where do I look for all the modified files from 3.2.2 I'm sure I'll find them if I look hard enough. With that I can narrow down my target.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

cbelcher commented 4 months ago

Maybe I missed something, I’m on it.

From: Lucifer06 @.> Sent: Friday, April 26, 2024 5:35 PM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Mention @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

The changes was on S90Let me know what the changes you are making for having the rpi working and I will add it to the standard repo so you will enjoy any new updates with no pain...Excuse possible typo: swallowed by my iPhoneLe 26 avr. 2024 à 20:23, Craig Belcher @.<mailto:@.>> a écrit : No it does not. RemoteGPIO v3.3.2 has killed my RPi fix. Been trying to tack it down. I see the changes to S90 and moving it to the rcS.d directory. I've dealt with them, just nothing not even my Relays work any more. Firing up the Cerbo and see what's different. Where do I look for all the modified files from 3.2.2 I'm sure I'll find them if I look hard enough. With that I can narrow down my target.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2080149019, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNN6UY6SR5HKDP2CIS3Y7LCBBAVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGE2DSMBRHE. You are receiving this because you were mentioned.Message ID: @.**@.>>

cbelcher commented 4 months ago

It's the same thing I've been fighting all day, everything seems to work from the Remote Console configuration standpoint. Define the Digital input, it shows up in the Device List. But when I short the input the status does not register.

I watch the dbus-monitor and no longer do I see the messages like I use too. Like this is from the last working version 3.2.1.

Neither 3.2.2 or 3.3.2, work. I see nothing on the bus.

signal time=1713282122.199821 sender=:1.49410 -> destination=(null destination) serial=26186 path=/; interface=com.victronenergy.BusItem; member=ItemsChanged array [ dict entry( string "/InputState" array [ dict entry( string "Value" variant int32 0 ) dict entry( string "Text" variant string "0" ) ] ) dict entry( string "/State" array [ dict entry( string "Value" variant int32 6 ) dict entry( string "Text" variant string "open" ) ] ) ]

The only clue I see is the working v3.2.1 I, have a units.conf in /data/RemoteGPIO/conf. 3.2.2 and 3.3.2, it's missing, only the relays.conf file is in this directory. What am I missing?

I see S90 no longer references it, so has me thinking there is something else?

Thoughts? Need to get a pcap going and see if I see the messages, maybe the RPi just isn't listen to them.

cbelcher commented 4 months ago

My statement that 3.2.2 doesn't work, is simple false. I've got notes and console output that proves that it did. Not much point in dealing with the past. Have to figure out what's wrong with the current release.

Any ideas, toss them out!

drtinaz commented 4 months ago

Have you enabled digital inputs in the 'additional options' menu for each relay module?

cbelcher commented 4 months ago

No Sir, but I have tried it in the past. Need to do anything after I enable it? Reboot, etc?

From: Derrick @.> Sent: Friday, April 26, 2024 9:56 PM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Mention @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

Have you enabled digital inputs in the 'additional options' menu for each relay module?

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2080314970, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNJBDY6R3MI3BXEXONLY7MASTAVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGMYTIOJXGA. You are receiving this because you were mentioned.Message ID: @.**@.>>

cbelcher commented 4 months ago

Working.. What the heck is that option there for, lol.... I tried it earlier this morning and it didn't change anything? Been rebuilt 5 times since then, so who knows.

Okay, we have a fully function RPi 4 Model B running RemoteGPIO v3.3.2. Nice..

Now I just copy my S90 to my git folder then do what, a commit?

drtinaz commented 4 months ago

Yes. Any changes to configuration will require a manual restart of RemoteGPIO from within the menu.

cbelcher commented 4 months ago

You are correct.

drtinaz commented 4 months ago

Working.. What the heck is that option there for, lol.... I tried it earlier this morning and it didn't change anything? Been rebuilt 5 times since then, so who knows.

Okay, we have a fully function RPi 4 Model B running RemoteGPIO v3.3.2. Nice..

Now I just copy my S90 to my git folder then do what, a commit?

The option is there because not everyone will use the feature, and disabling it saves on system resources. Same reason with reading relays option.

cbelcher commented 4 months ago

Makes sense. With the PoS Cerbo you need every clock cycle you can get. I’m still in shock my 5 year old, $45 RPi has just over twice the MIPS score.

I think I’ll hang it on the wall for the final install and hide the RPi behind the battery racks 😊

From: Derrick @.> Sent: Friday, April 26, 2024 10:10 PM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Mention @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

Working.. What the heck is that option there for, lol.... I tried it earlier this morning and it didn't change anything? Been rebuilt 5 times since then, so who knows.

Okay, we have a fully function RPi 4 Model B running RemoteGPIO v3.3.2. Nice..

Now I just copy my S90 to my git folder then do what, a commit?

The option is there because not everyone will use the feature, and disabling it saves on system resources. Same reason with reading relays option.

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2080320428, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNPGNRLS4QCIO3ZOZITY7MCF7AVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGMZDANBSHA. You are receiving this because you were mentioned.Message ID: @.**@.>>

Lucifer06 commented 4 months ago

@cbelcher then, did you had to tweak S90 script (or anything else) or the latest v3.3.2 is working fine on a stock rPI? Cheers, FreD.

cbelcher commented 4 months ago

Only changes to S90 are needed to get the rPI working.

Going to spend the morning, trying to get the code to my GitHub fork.

From: Lucifer06 @.> Sent: Saturday, April 27, 2024 3:34 AM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Mention @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

@cbelcherhttps://github.com/cbelcher then, did you had to tweak S90 script (or anything else) or the latest v3.3.2 is working fine on a stock rPI? Cheers, FreD.

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2080400586, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNIPLV2V226W6ATF73TY7NIGNAVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGQYDANJYGY. You are receiving this because you were mentioned.Message ID: @.**@.>>

cbelcher commented 4 months ago

Just ran through a complete, from a blank SD card to a fully functional RPi 4 Model. Running RemoteGPIO v3.3.2, with a single DT-R008. Firmware & Packages Firmware: 3.40~10 SetupHelper: v7.18 GuiMods: v10.24 ShutdownMonitor: v3.2 RpiTemperature: v1.2 RemoteGPIO: v3.3.2

Just have to pause, after installing RemoteGPIO when it's asking you to reboot. Shim in my S90, then select now. Configure RemoteGPIO. Bam! Just works.

Let me get this very old version of my S90 script committed on GitHub, long story why I chose an old version. I'll work on getting the much slicker version published this evening.

The key to getting it working, is that the stock S90 assumes that dbus_digitalinput service is running. Well on any device without native Digital Inputs and that list includes several Victron devices. start-digitalinputs.sh puts a stop to that. It does a test for the existence of /dev/gpio/digital_input_1. Doesn't find it, it takes the service down. For any device without native DI's I bring it up. You'll see when I can figure out how to do a commit, YouTube to the rescue.

Most recent version of the script handles all the devices without native DI's and is a 100 or so lines smaller. This version was just the first that worked, it isn't pretty. Other biggie, this one I only had coded for Module 1. Once I got it working I was off to optimizing it, then I dealt with the other modules.

cbelcher commented 4 months ago

@Lucifer06 @drtinaz

Did you see my commit? Hope I didn't mess anything up.

cbelcher commented 4 months ago

Looks like you guys got it, I see it on both your GitHub pages. I'll clean 90% of it up tomorrow, and we can have the the all the RPi users back online.

cbelcher commented 4 months ago

Just tested on Cerbo and there is an issue. I'll find it quick.

cbelcher commented 4 months ago

I found it, it's my platform detection call. Need change my get_platform_setting sub to awk for $1 not 3.

Please hold.

drtinaz commented 4 months ago

Are you starting with the current S90 script file and making your changes to that? Using a file from an older version may lose some functionality or break something.

cbelcher commented 4 months ago

Fact is I don’t have a dam clue how to use GitHub. I’m trying, but I knew there would be something I would do incorrectly.

Got the relay’s working on my Cerbo GX MK2, but DI’s are not happy. Service dbus-digitalinputs is crashing every 3 seconds. Even after uninstalling and reinstalling. It obviously leaves a trail of changes after uninstalling.

The second I uninstall it, crashes stop, install it they start. Using 3.3.2 S90, does the same thing.

From: Derrick @.> Sent: Sunday, April 28, 2024 11:30 AM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Mention @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

Are you starting with the current S90 script file and making your changes to that? Using a file from an older version may lose some functionality or break something.

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2081521242, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNLR73OIZMKS2CPIQJ3Y7UIY5AVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGUZDCMRUGI. You are receiving this because you were mentioned.Message ID: @.**@.>>

cbelcher commented 4 months ago

I’ve just completed a full reimage of my Cerbo GX MK2, and dbus-digitalinputs service is tracing back just like with my S90.

You sure this is rock solid? It behaves the same way as my modified S90?

Tracebacks every 3-4 seconds. Whatever is going on it’s not my S90…

@.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15503) 2 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15591) 1 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15591) 2 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15591) 3 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15591) 4 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15661) 1 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15661) 1 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15661) 2 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15661) 3 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15661) 3 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15751) 0 seconds @.:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15751) 1 seconds @.***:~# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 15751) 2 seconds

@40000000662ea05829874b54 starting dbus-digitalinputs @40000000662ea05a16c2a70c Registering GPIO 1 for type 0 @40000000662ea05a230a9e84 Registering GPIO 2 for type 0 @40000000662ea05a2f6239e4 Registering GPIO 3 for type 0 @40000000662ea05b000cbfac Registering GPIO 4 for type 0 @40000000662ea05b0fe9ad54 Registering GPIO 5 for type 0 @40000000662ea05b1ce18824 Registering GPIO 6 for type 0 @40000000662ea05b2988399c Registering GPIO 7 for type 0 @40000000662ea05b37eb161c Registering GPIO 8 for type 0 @40000000662ea05c0a4f752c Registering GPIO 9 for type 0 @40000000662ea05c17d6786c Registering GPIO 10 for type 2 @40000000662ea05c18ec071c Traceback (most recent call last): @40000000662ea05c18ee4d24 File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 651, in @40000000662ea05c191bf0bc main() @40000000662ea05c191e59ec File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 607, in main @40000000662ea05c1a3501dc register_gpio(pth, inp, bus, sd) @40000000662ea05c1a3776c4 File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 547, in register_gpio @40000000662ea05c1a61f5ac handler.level = pulses.register(path, gpio) @40000000662ea05c1a64476c File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 111, in register @40000000662ea05c1a7d78a4 self.ob.register(fp, EPOLLPRI) @40000000662ea05c1a7ff174 PermissionError: [Errno 1] Operation not permitted @40000000662ea05c2446c034 starting dbus-digitalinputs @40000000662ea05e02fc3a94 Registering GPIO 1 for type 0 @40000000662ea05e0fd2413c Registering GPIO 2 for type 0

Not code of mine ,is running on the Cerbo GX MK2.

From: Derrick @.> Sent: Sunday, April 28, 2024 11:30 AM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Mention @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

Are you starting with the current S90 script file and making your changes to that? Using a file from an older version may lose some functionality or break something.

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2081521242, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNLR73OIZMKS2CPIQJ3Y7UIY5AVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGUZDCMRUGI. You are receiving this because you were mentioned.Message ID: @.**@.>>

cbelcher commented 4 months ago

These tracebacks indicate some Permissions Error which I don’t see on the RPi. I’ve seen that if you don’t start from a fresh install, it behaves very differently.

I’ll try to find it, but something is very wrong.

Factory fresh Cerbo GX MK2, Firmware 3.40~10 SetupHelper: v7.18 GuiMods: v10.24 ShutdownMontior: v3.2 RemoteGPIO: v3.2.2

Flat out does not work!

Works on my Pi with my shimmed S90.. Sure, I’ve been concentrating on that platform. Just assumed the Cerbo GX was solid. Not so much.

From: Derrick @.> Sent: Sunday, April 28, 2024 11:30 AM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Mention @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

Are you starting with the current S90 script file and making your changes to that? Using a file from an older version may lose some functionality or break something.

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2081521242, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNLR73OIZMKS2CPIQJ3Y7UIY5AVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGUZDCMRUGI. You are receiving this because you were mentioned.Message ID: @.**@.>>

cbelcher commented 4 months ago

Digging deeper on this complete stock v.3.3.2 install on the Cerbo GX MK2. With Unit 1 configured with 8 relays, digitalinput service traces every 3-4 seconds. Set unit 1 to 2 Relays and it no longer traces. Going to try 4 Relays next, betcha it works.

If you watch dbus-spy this input09 is the culprit. It is displayed for a ms in "com.victronenergy.system" and then vanishes.

Like so: I'm scrolling back in dbus-spy to see what was being displayed. `com.victronenergy.digitalinput.input09
com.victronenergy.digitalinput.input09
com.victronenergy.digitalinput.input09
com.victronenergy.digitalinput.input09
com.victronenergy.digitalinput.input09
com.victronenergy.digitalinput.input09
com.victronenergy.system

com.victronenergy.adc com.victronenergy.fronius
com.victronenergy.logger com.victronenergy.modbusclient.tcp com.victronenergy.packageManager Package Manager com.victronenergy.platform Venus com.victronenergy.settings com.victronenergy.shutdown ShutdownMonitor com.victronenergy.system
com.victronenergy.vecan.vecan0 com.victronenergy.vecan.vecan1`

2 Relays the service has not traced a single time `@40000000662f993f14372db4 starting dbus-digitalinputs

@40000000662f994019125f84 starting dbus-digitalinputs @40000000662f994216bede4c Registering GPIO 1 for type 0 @40000000662f99422a62b34c Registering GPIO 2 for type 0 @40000000662f994302b415d4 Registering GPIO 3 for type 0 @40000000662f994315922dbc Registering GPIO 4 for type 0 @40000000662f994329f7e38c Registering GPIO 5 for type 0 @40000000662f99440294d5d4 Registering GPIO 6 for type 0

root@cerbogx-mk2:/etc/rcS.d# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 13036) 6164 seconds`

cbelcher commented 4 months ago

Proved setting Unit 1 to 8 Relays, triggers the tracebacks in dbus_digitalinputs.py. Set to 2 or 4, no issue.

`root@cerbogx-mk2:/etc/rcS.d# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 25932) 459 seconds

root@cerbogx-mk2:/etc/rcS.d# root@cerbogx-mk2:/etc/rcS.d# ############# Above is with Relays = 4, not tracing just about to set back to 8 to prove it's the trigger of the traces ########

root@cerbogx-mk2:/etc/rcS.d# date Mon Apr 29 15:02:38 UTC 2024 root@cerbogx-mk2:/etc/rcS.d# #######changing now to 8 #############

root@cerbogx-mk2:/etc/rcS.d# date Mon Apr 29 15:03:02 UTC 2024

root@cerbogx-mk2:/etc/rcS.d# ########Restarting RemoteGPIO Service #################

root@cerbogx-mk2:/etc/rcS.d# date Mon Apr 29 15:03:40 UTC 2024 root@cerbogx-mk2:/etc/rcS.d# ############Tracing starts immediately #################### root@cerbogx-mk2:/etc/rcS.d# root@cerbogx-mk2:/etc/rcS.d# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 26818) 3 seconds root@cerbogx-mk2:/etc/rcS.d# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 27054) 1 seconds root@cerbogx-mk2:/etc/rcS.d# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 27054) 2 seconds root@cerbogx-mk2:/etc/rcS.d# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 27054) 2 seconds root@cerbogx-mk2:/etc/rcS.d# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 27054) 3 seconds root@cerbogx-mk2:/etc/rcS.d# svstat /service/dbus-digitalinputs /service/dbus-digitalinputs: up (pid 27054) 4 seconds root@cerbogx-mk2:/etc/rcS.d# root@cerbogx-mk2:/etc/rcS.d# ############ Service will not say running ############ root@cerbogx-mk2:/etc/rcS.d# `

Something's up. I'm on a missing to find it.

drtinaz commented 3 months ago

Check the created links in /dev/gpio and the digital input .conf files.

cbelcher commented 3 months ago

I have they look as they should. With 8

@.**@.:/etc/rcS.d#> ls -lah /dev/gpio drwxr-xr-x 2 root root 520 Apr 29 15:03 . drwxr-xr-x 14 root root 2.9K Apr 28 18:56 .. lrwxrwxrwx 1 root root 23 Apr 28 18:55 digital_input_1 -> /sys/class/gpio/gpio226 lrwxrwxrwx 1 root root 23 Apr 28 18:55 digital_input_2 -> /sys/class/gpio/gpio225 lrwxrwxrwx 1 root root 23 Apr 28 18:55 digital_input_3 -> /sys/class/gpio/gpio224 lrwxrwxrwx 1 root root 23 Apr 28 18:55 digital_input_4 -> /sys/class/gpio/gpio227 lrwxrwxrwx 1 root root 39 Apr 29 15:03 digital_input_5 -> /data/RemoteGPIO/sys/class/gpio/gpio205 lrwxrwxrwx 1 root root 39 Apr 29 15:03 digital_input_6 -> /data/RemoteGPIO/sys/class/gpio/gpio206 lrwxrwxrwx 1 root root 39 Apr 29 15:03 digital_input_7 -> /data/RemoteGPIO/sys/class/gpio/gpio207 lrwxrwxrwx 1 root root 39 Apr 29 15:03 digital_input_8 -> /data/RemoteGPIO/sys/class/gpio/gpio208 lrwxrwxrwx 1 root root 39 Apr 29 15:03 digital_input_9 -> /data/RemoteGPIO/sys/class/gpio/gpio209 lrwxrwxrwx 1 root root 39 Apr 29 15:03 digital_input_a -> /data/RemoteGPIO/sys/class/gpio/gpio210 lrwxrwxrwx 1 root root 39 Apr 29 15:03 digital_input_b -> /data/RemoteGPIO/sys/class/gpio/gpio211 lrwxrwxrwx 1 root root 39 Apr 29 15:03 digital_input_c -> /data/RemoteGPIO/sys/class/gpio/gpio212

@.***:/data/RemoteGPIO/FileSets/Conf# cat Digital_Inputs_unit1.conf

/dev/gpio/digital_input_5/value /dev/gpio/digital_input_6/value /dev/gpio/digital_input_7/value /dev/gpio/digital_input_8/value /dev/gpio/digital_input_9/value /dev/gpio/digital_input_a/value /dev/gpio/digital_input_b/value /dev/gpio/digital_input_c/value

And 4 @@.:/data/RemoteGPIO/FileSets/Conf# ls -lah /dev/gpio root 360 Apr 29 15:22 . root 2.9K Apr 28 18:56 .. root 23 Apr 28 18:55 digital_input_1 -> /sys/class/gpio/gpio226 root 23 Apr 28 18:55 digital_input_2 -> /sys/class/gpio/gpio225 root 23 Apr 28 18:55 digital_input_3 -> /sys/class/gpio/gpio224 root 23 Apr 28 18:55 digital_input_4 -> /sys/class/gpio/gpio227 root 39 Apr 29 15:22 digital_input_5 -> /data/RemoteGPIO/sys/class/gpio/gpio205 root 39 Apr 29 15:22 digital_input_6 -> /data/RemoteGPIO/sys/class/gpio/gpio206 root 39 Apr 29 15:22 digital_input_7 -> /data/RemoteGPIO/sys/class/gpio/gpio207 root 39 Apr 29 15:22 digital_input_8 -> /data/RemoteGPIO/sys/class/gpio/gpio208 root 23 Apr 28 18:56 mkx_rst -> /sys/class/gpio/gpio122 root 21 Apr 28 18:55 relay_1 -> /sys/class/gpio/gpio4 root 21 Apr 28 18:55 relay_2 -> /sys/class/gpio/gpio5 root 39 Apr 29 15:22 relay_3 -> /data/RemoteGPIO/sys/class/gpio/gpio103 root 39 Apr 29 15:22 relay_4 -> /data/RemoteGPIO/sys/class/gpio/gpio104 root 39 Apr 29 15:22 relay_5 -> /data/RemoteGPIO/sys/class/gpio/gpio105 root 39 Apr 29 15:22 relay_6 -> /data/RemoteGPIO/sys/class/gpio/gpio106 root 23 Apr 28 18:56 vebus_standby -> /sys/class/gpio/gpio123 ng>.:/data/RemoteGPIO/FileSets/Conf# cat Digital_Inputs_unit1.conf

/dev/gpio/digital_input_5/value /dev/gpio/digital_input_6/value /dev/gpio/digital_input_7/value /dev/gpio/digital_input_8/value

Trace hit when it’s registering GPIO 9, which doesn’t come into play with either Relays set to 2 or 4. 8 Yes. @40000000662fbb350bb27be4 Registering GPIO 9 for type 2 @40000000662fbb350e5f293c Traceback (most recent call last): @40000000662fbb350e619a3c File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 651, in @40000000662fbb350edc63d4 main() @40000000662fbb350edf0f6c File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 607, in main @40000000662fbb350f2fc77c register_gpio(pth, inp, bus, sd) @40000000662fbb350f322cc4 File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 547, in register_gpio @40000000662fbb350f95671c handler.level = pulses.register(path, gpio) @40000000662fbb350f97fb44 File "/opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py", line 111, in register @40000000662fbb350fad82fc self.ob.register(fp, EPOLLPRI) @40000000662fbb350fafb57c PermissionError: [Errno 1] Operation not permitted

From: Derrick @.> Sent: Monday, April 29, 2024 11:26 AM To: Lucifer06/RemoteGPIO @.> Cc: Craig Belcher @.>; Mention @.> Subject: Re: [Lucifer06/RemoteGPIO] Digital Input doesn't work with RaspBerry (Issue #30)

Check the created links in /dev/gpio and the digital input .conf files.

— Reply to this email directly, view it on GitHubhttps://github.com/Lucifer06/RemoteGPIO/issues/30#issuecomment-2083034772, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABB7DNPV57K7DOCHI3VAYPLY7ZRBFAVCNFSM6AAAAABF2PSV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBTGAZTINZXGI. You are receiving this because you were mentioned.Message ID: @.**@.>>

Lucifer06 / RemoteGPIO

Digital Input doesn't work with RaspBerry #30