You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi as I don't know programming I'm no able to make work your control code with i2c-0, as the driver by default use i2c-1. I found this lines in the code of this file https://gitlab.com/bradanlane/ros-i2cpwmboard/-/blob/master/src/i2cpwm_controller.cpp but I have no idea what to do.
` /**
\private method to initialize private internal data structures at startup
@param devicename a string value indicating the linux I2C device
Example _init ("/dev/i2c-1"); // default I2C device on RPi2 and RPi3 = "/dev/i2c-1" /
static void _init (const char filename)
{
int res;
char mode1res;
int i;
/* initialize all of the global data objects */
`
I tried contact with the driver site, but the emails don't work and it looks a abandoned project, not sure, but a similar issue is open from long time and I thought maybe it is a easy thing that can be fixed with a small tip.
thanks and take care!!!!
The text was updated successfully, but these errors were encountered:
Hi as I don't know programming I'm no able to make work your control code with i2c-0, as the driver by default use i2c-1. I found this lines in the code of this file https://gitlab.com/bradanlane/ros-i2cpwmboard/-/blob/master/src/i2cpwm_controller.cpp but I have no idea what to do.
` /**
\private method to initialize private internal data structures at startup
@param devicename a string value indicating the linux I2C device
Example _init ("/dev/i2c-1"); // default I2C device on RPi2 and RPi3 = "/dev/i2c-1"
/
static void _init (const char filename)
{
int res;
char mode1res;
int i;
`
I tried contact with the driver site, but the emails don't work and it looks a abandoned project, not sure, but a similar issue is open from long time and I thought maybe it is a easy thing that can be fixed with a small tip.
thanks and take care!!!!
The text was updated successfully, but these errors were encountered: