Thank you for the quick response blh64. What you have described in the response is right along with our findings. Based on what we have found, here is our approach thus far:
Reading the RC input signal into Arduino:
a) call out the channel from the RC receiver and the chosen PWM pin in the arduino.
b) define a deadzone value for when we do not want the servo to move.
Communicating the RC signal to Master Bluetooth:
d) initialize a state to read the data from the serial port
e) in the void setup () section we call out the serial baud rate of the master bluetooth module
f) In the void loop, we check and read data from the serial port
g) We read pulse from the receiver, and covert it into a PWM value from -255 to 255.
h) We add a Serial.write command to send the PWM values read from the RC receiver to the servo
Slave Bluetooth signal to servo output:
i) include servo library <Servo.h> and initialize a state command
j) in the void setup (), call out the Serial.begin baud rate to communicate with the master bluetooth
k) in the void loop () check if there is any data coming into the serial port
l) write the servo state condition based on the PWM value received
If our described approach above is somewhat in the right direction, the questions that we now need answer are:
- in order to incorporate a level of security in the communication, how do we code the identified PWM signal by the arduino nano to some sort of message that will be read by the slave bluetooth module and execute a simple high and low servo actuation?
- for anyone that that has done something like it before, will the two bluetooth modules stay connected (say within a range of 10 meters with some level of reliability (understanding that these are cheap devices)? Any stories or information that we should consider are much appreciated. We want to avoid pairing them up manually every time that we power each system (slave & master bluetooth). We are open to suggestions and guidance (especially on the code part…). Thanks!