RC Model for Motion Simulation

I'm attaching a video

I checked everything correctly 10 times again but nothing works

Make sure you have clicked the green 'Save' after changing the Interface settings, it should bring up a window saying 'Settings Saved' if it updates correctly.

I've verified the code and your settings with an arduino Uno and servo here and they work for me. You could also try closing down simtools and starting it again and check that the interface settings are showing up correctly. Also try unplugging and replugging the usb to your microcontroller.

Also when the microcontroller is plugged in, your servo should move to centre and resist you manually moving the servo arm even without Simtools running if the code has been uploaded correctly.

Maybe I, of course, uploaded the wrong sketch to the Arduino Uno, Serov drives resist manual movement, what you wrote is what I tried, but nothing changed

Here is the code I used:

Code:

//********************************************************************************************
// RC Model Servo
// Original code By EAOROBBIE (Robert Lindsay)
// Completely mangled by aarondc
// For free use for Sim Tool Motion Software
//********************************************************************************************
#include <Servo.h>
//#define DEBUG 1                                    // comment out this line to remove debuggin Serial.print lines
const int kActuatorCount = 2;                       // how many Actuators we are handling

// the letters ("names") sent from Sim Tools to identify each actuator
// NB: the order of the letters here determines the order of the remaining constants kPins and kActuatorScale
const char kActuatorName[kActuatorCount] = { 'R', 'L' };
const int kPins[kActuatorCount] = {4, 5};                       // pins to which the Actuators are attached
const int kActuatorScale[kActuatorCount][2] = { { 0, 179 } ,    // Right Actuator scaling
                                                { 179, 0 }      // Left side Actuator scaling
                                               };     
const char kEOL = '~';                              // End of Line - the delimiter for our acutator values
const int kMaxCharCount = 3;                        // some insurance...
Servo actuatorSet[kActuatorCount];                  // our array of Actuators
int actuatorPosition[kActuatorCount] = {90, 90};    // current Actuator positions, initialised to 90
int currentActuator;                                // keep track of the current Actuator being read in from serial port
int valueCharCount = 0;                             // how many value characters have we read (must be less than kMaxCharCount!!

// set up some states for our state machine
// psReadActuator = next character from serial port tells us the Actuator
// psReadValue = next 3 characters from serial port tells us the value
enum TPortState { psReadActuator, psReadValue };   
TPortState currentState = psReadActuator;

void setup()
{
    // attach the Actuators to the pins
    for (int i = 0; i < kActuatorCount; i++)
        actuatorSet[i].attach(kPins[i]);
    
    // initialise actuator position
    for (int i = 0; i < kActuatorCount; i++)
        updateActuator(i);
    
    Serial.begin(9600); // opens serial port at a baud rate of 9600
}
 
void loop()
{

}

// this code only runs when we have serial data available. ie (Serial.available() > 0).
void serialEvent() {
    char tmpChar;
    int tmpValue;

    while (Serial.available()) {
        // if we're waiting for a Actuator name, grab it here
        if (currentState == psReadActuator) {
            tmpChar = Serial.read();
            // look for our actuator in the array of actuator names we set up
#ifdef DEBUG           
Serial.print("read in ");           
Serial.println(tmpChar);           
#endif
            for (int i = 0; i < kActuatorCount; i++) {
                if (tmpChar == kActuatorName[i]) {
#ifdef DEBUG           
Serial.print("which is actuator ");           
Serial.println(i);           
#endif
                    currentActuator = i;                        // remember which actuator we found
                    currentState = psReadValue;                 // start looking for the Actuator position
                    actuatorPosition[currentActuator] = 0;      // initialise the new position
                    valueCharCount = 0;                         // initialise number of value chars read in
                    break;
                }
            }
        }
        
        // if we're ready to read in the current Actuator's position data
        if (currentState == psReadValue) {
            while ((valueCharCount < kMaxCharCount) && Serial.available()) {
                tmpValue = Serial.read();
                if (tmpValue != kEOL) {
                    tmpValue = tmpValue - 48;
                    if ((tmpValue < 0) || (tmpValue > 9)) tmpValue = 0;
                    actuatorPosition[currentActuator] = actuatorPosition[currentActuator] * 10 + tmpValue;
                    valueCharCount++;
                }
                else break;
            }
            
            // if we've read the value delimiter, update the Actuator and start looking for the next Actuator name
            if (tmpValue == kEOL || valueCharCount == kMaxCharCount) {
#ifdef DEBUG           
Serial.print("read in ");           
Serial.println(actuatorPosition[currentActuator]);           
#endif
                // scale the new position so the value is between 0 and 179
                actuatorPosition[currentActuator] = map(actuatorPosition[currentActuator], 0, 255, kActuatorScale[currentActuator][0], kActuatorScale[currentActuator][1]);
#ifdef DEBUG           
Serial.print("scaled to ");           
Serial.println(actuatorPosition[currentActuator]);           
#endif
                updateActuator(currentActuator);
                currentState = psReadActuator;
            }
        }
    }
}


// write the current Actuator position to the passed in Actuator
void updateActuator(int thisActuator) {
    actuatorSet[thisActuator].write(actuatorPosition[thisActuator]);
}

Well, it turns out that I also used it, maybe the Arduino ide is not the latest version installed

in the section axis assignmens % set to 100 and dir DOF1 Axis2a set and when testing at 50-60 Roll and Pitch the first servo rotates by 1mm and that’s it

and for some reason I have an Arduino connected to the com port where it is written in sim tools, but next to the cross and DEMO the red indicator is on, but when you turn on the test the blue one turns on, the red one means that there is no connection

what should I do please help me

Hi again Happy new year i return to finish my simrig and add gseat surge effect. I have problem: i add another profile to simtools v3 and config like on pic. I use arduino code for gseat https://www.xsimulator.net/community/threads/007-g-seat-ultra-compact-servo-based.10470/#post-139756
I have movement only with this range like on movie:
Any help
Ehhh decimal solved

maybe someone can help me.

i am using this example code. by the way nice bit of code..thanks

my issue is that i can get only 2 servos working. R, L but not B. or i can get B working but just not the third servo. in Simtool i have R<Axis1a>L<Axis2a>B<Axis3a> i've used the "~" but that make no difference.

what i'm trying to get working is 4 servos but again i can only get 2 to work.

Any ideas?


/ Original code By EAOROBBIE (Robert Lindsay)
// Completely mangled by aarondc
// Modify by Jun
// For free use for Sim Tool Motion Software
//********************************************************************************************
#include <Servo.h>
//#define DEBUG 1 // comment out this line to remove debuggin Serial.print lines
const int kActuatorCount = 3; // how many Actuators we are handling

// the letters ("names") sent from Sim Tools to identify each actuator
// NB: the order of the letters here determines the order of the remaining constants kPins and kActuatorScale
const char kActuatorName[kActuatorCount] = { 'R', 'L', 'B' };
const int kPins[kActuatorCount] = {5, 6, 9}; // pins to which the Actuators are attached
const int kActuatorScale[kActuatorCount][3] = { { 0, 179 } , // Right Actuator scaling
{ 179, 0 } , // Left side Actuator scaling
{ 0, 179 } // Back Actuator scaling
};
const char kEOL = '~'; // End of Line - the delimiter for our acutator values
const int kMaxCharCount = 3; // some insurance...
Servo actuatorSet[kActuatorCount]; // our array of Actuators
int actuatorPosition[kActuatorCount] = {90, 90, 90}; // current Actuator positions, initialised to 90
int currentActuator; // keep track of the current Actuator being read in from serial port
int valueCharCount = 0;

Yes, i followed it in changing the code as shown in my post.
this only difference is that i have different pin outputs ...i'm using pin 10 instead of pin 3

because i already wired and solders things before expanding the code.
Pin 10 is a PWM output so it does not matter (3,5,6,9,10,11) are all PWM and can be used

i can try using different pins tomorrow as a test, however don't see why that would make a difference...but I've been wrong before according to my wife LOL.

Looking over the Arduino Docs they stated you needed to pick a PWM (pulse width modulated) pin for servos hence why i picked pin 9 and 10 which are PWM

the code you show just calls from a list KPins and increments to next value so it should "attach"
pin 5, then 6 then 9 then 10 so that should be working. the loop is derived by the kActuatorCount which is 4 so it should increment all four

const int kActuatorCount = 4;
const int kPins[kActuatorCount] = {5,6,9,10};

for (int i = 0; i < kActuatorCount; i++)
actuatorSet.attach(kPins);

i'll post what i find when changing the pins tomorrow.
any other imput is welcome...thanks

All Right...got to love CHATGPT
looks like the servo library uses a timer on pins 9 and 10 so you cannot use them as PWM

here is chatgpt reply:

The issue where only two of the three PWM signals work could be due to the pins you've chosen to generate PWM signals on. The Arduino Uno has limitations on which pins can generate PWM signals when using the Servo library.

Key Points:

1. Servo Library Conflicts with PWM Pins:
   • The Servo library uses hardware timers to control servos, which can conflict with the PWM functionality on certain pins.
   • On the Arduino Uno, the Servo library uses Timer1, which controls pins 9 and 10.
   • If you're trying to use pins 5, 6, and 9, note that pin 9 will be controlled by Timer1, which the Servo library also uses. This may disable the PWM functionality on that pin.

Suggested Solution:
To avoid conflicts, you can try using different PWM-capable pins that do not conflict with the Servo library, or ensure that you're not using the same timer for both servos and PWM signals.

Adjusted Code Example:
You could try moving the PWM output to pins 3, 5, and 6 instead, as pin 3 is controlled by Timer2, which isn't used by the Servo library: