Raspbery Pi DMP issue and general question

Hi Rongzhong, Great! Now it's working! I had wondered about that switch. I am attaching some pictures - I used a stacking header and some standoffs to mount the RPi a little more apart from the Nyboard. Without the separation, the heatsink on the Pi was hitting the Nyboard, plus the Pi4 runs a little hot so I wanted to give some space for heat dissipation. Cheers, Chris

Hi Li,

I made the same mistake by switching to Pi on Bittle, now I have stumbled upon this I realised it's not necessary, suggest adding that extra line "do not switch to Pi" under Bittle manual section 4.4.

Having said that, you said "It will change the I2C master to Pi, and you will need to write a complete Pi code to control the devices", can you please elaborate on this part? I understand how to communicate between Pi and Arduino with USB or Bluetooth, but what do you mean here? Any simple example to illustrate?

Say I got a bare bone code below for controlling Arduino via Pi, by switching the Bittle to Pi, is it what this switch is for?

import RPi.GPIO as GPIO

import time

GPIO.setmode(GPIO.BOARD)

GPIO.setup(2, GPIO.OUT)

panServo = GPIO.PWM(2,50)

panServo.start(0)

duty = 2

while duty <= 12:

panServo.ChangeDutyCycle(duty)

time.sleep(1)

duty += 1

@R T After you dial the switch to Pi, the master of the I2C network becomes the Pi. The servo pins are not connected to the Arduino or the Pi, but a servo driver PCA9685. It communicates with the master through I2C. So you need to use the Adafruit PCA9685 PWM library on the Pi to drive the servos.