-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CM4-IO-WIRELESS-BASE-B configure ports #26
Comments
My VeCanSetup package may be able to help with the CANbus port but you may need to tweak some things. (There are often GPIO conflicts between devices.) Others have found ways to activate an RS485 port on similar modules but I don't know anything about what they did or problems they encountered. |
Hardware and ports are enabled. For Can and. Rs485. But the mapping to the
gpio pins avoid conflicts and add a relay is unclear for me at the moment
Boot Overlay file uart3 and 5 added from raspberry firmware https://github.com/raspberrypi/firmware/tree/master/boot/overlays
CAN is working as per instruction from waveshare
dtparam=spi=on
dtoverlay=mcp2515-can0,oscillator=16000000,interrupt=25
at this moment I would like to add relay options on the waveshare Partial GPIO header these 2x GPIO pins, and power supply to have them available in the venus os interface.
In what way I am able to add pinout configuration to RpiGpioSetup and avoid conflicts?
Configuration of this board
https://files.waveshare.com/wiki/CM4-IO-WIRELESS-BASE-B/CM4-IO-WIRELESS-BASE-B-SchDoc.pdf
UART 2x, GPIO 12 en 13 (?) and GPI 4 and 5 (?)
CAN GPIO 8, 9, 10, 11,25
Partial GPIO header available on this waveshare board::
Relay 4 to connect on GPIO 22
Shutdown possible to reconfigure on 18?
this will result in a custom gpio_list file, gpiolist with only entry for a relay and no? digital input:
# Relay 4 GPIO 22 / header pin 15
22 out relay_4
Is it possible to have only one relay in the Gui of venus, only the one listed in the GPIOlist?
When installing with the gpiolist with only the relay4 in the file:
/data/setupOptions/RpiGpioSetup/gpio_list:
#### LEGACY assignments for Relay 1, 5 and 6 and Dig In 4
#### WILL CONFLICT with second channel on WaveShare dual channel CANbus hats, a>
#### interrupts, chip selects and second SPI bus
#### single channel CANbus hats should be OK with these assignments
#### this includes using only the first channel of the WaveShare dual channe>
#### note that WaveShare sells two different dual channel CANbus hats: the non >
### for use by the RpiGpio package on Raspberry PI platforms ONLY
# This is a list of GPIO pins, set by the script /etc/rcS.d/S90gpio_pins.sh
# They are documented at: https://github.com/victronenergy/venus/wiki/bbb-gpio
# Format: <pin_number> <direction: in/out> <name>
#
# The <name> part is used to create an symlink in /dev/gpio.
# relays are active HIGH
# Relay 4 GPIO 22 / header pin 15
22 out relay_4
when using the gpiolist provided with config above and use this in the configuration.
If you type n to exit, not to reboot, it will reboot.
Op zo 15 sep 2024 01:14 schreef kwindrem ***@***.***>:
… My VeCanSetup package may be able to help with the CANbus port but you may
need to tweak some things. (There are often GPIO conflicts between devices.)
Others have found ways to activate an RS485 port on similar modules but I
don't know anything about what they did or problems they encountered.
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIFPJJTXIIYDUGV5W2NHRZLZWS7NXAVCNFSM6AAAAABOG55G26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJRGIYTCOJWGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm struggle-ing but willing to find out how to make a rpigpio setup for this board.
any way forward to map de UART RS485 and CAN port of this board.
I have found de pdf with pinout on you're side but struggle to match it with this board. Any clues?
The text was updated successfully, but these errors were encountered: