Replies: 1 comment
-
|
Did u solved? https://meshtastic.org/docs/configuration/module/remote-hardware/#requirements I followed the entire procedure as described, until I received: XXXXXXXXXX ~ % meshtastic --gpio-wrb 5 1 --dest !9e9XXXXX Connected to radio Writing GPIO mask 0x20 with value 0x20 to !9e9XXXXX So the software works... The problem is that the pin the system is connected to (I'm currently testing with an LED as per the instructions) isn't turning on the LED. I'm currently using a Heltec V3 flashed to 2.7.15.567b8eaBETA Any help? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
First time posting, hope this is in the right place. Kindly re-direct me as appropriate.
I've been working on a new Meshtastic system which is relaying telemetry from remote sites and I've recently started on a feature to control some external hardware at those sites. Currently, the design is using the remote hardware module, though is only controlling things locally from a Pi via USB/serial. My node is an nRF based WisMesh Pocket V2. I am planning to use IO3, IO4, IO6, IO8 (mapped to firmware IO 21, 04, 10, 02 respectively). I'm using IO7 (FW GPIO 28) for the motion detector module. I have successfully re-compiled the firmware to enable the feature and I've been able to access these IO -- but only after setting "allowUndefinedPinAccess" to true. I'm anxious about this, of course.
meshtastic --port COM10 --set remote_hardware.allow_undefined_pin_access true
(from --info)
--- snip ---
"remoteHardware": {
"enabled": true,
"allowUndefinedPinAccess": true,
"availablePins": []
--- /snip ---
Has anyone been able to write a Python script to set these available pins? I admit my only exposure to Python has been via AI coding bots (VS Code using GitHub's CoPilot, specifically). It wrote the attached script which didn't work. Because I can't seem to find any working examples, I've given up on this for now but would love to be able to figure this out.
As a side-note, the documentation for the remote hardware module suggests that we don't need to set --dest to point to the local node if we are talking to the local node, but the firmware disagrees. I formed my IO writes on my windows machine with:
meshtastic --port COM10 --dest '!xxxxxxxx' --gpio-wrb 2 0
...where xxxxxx was my node ID in hex
Many thanks in advance,
Brian.
configure_gpio_pins.py
Beta Was this translation helpful? Give feedback.
All reactions