Summary: incorporating atan2() geometry
@Athena - please review the following Arduino Mega sketch. This sketch implements a UART packet protocol over Serial3 to communicate waypoint, bearing, and control packets with ARC (the ARC robot skill running on the PC). The Arduino side receives commands from ARC, drives four stepper motors using AccelStepper / MultiStepper, and reports navigation state back to ARC via Serial3 (hardware UART). This is the Arduino side of the ARC <-> Arduino packet protocol.
#include <AccelStepper.h>
#include <MultiStepper.h>
static const uint8_t UART_HEADER = 0xA5;
// ARC -> Arduino
static const uint8_t CMD_STOP_MOTORS = 0x01;
static const uint8_t CMD_ACTUAL_BEARING = 0x03;
static const uint8_t CMD_RIGHT_PIVOT = 0x04;
static const uint8_t CMD_LEFT_PIVOT = 0x05;
static const uint8_t CMD_WAYPOINT_DATA = 0x06;
// Arduino -> ARC
static const uint8_t RSP_NAV_ACK = 0x10;
static const uint8_t RSP_TOTAL_STEPS = 0x11;
static const uint8_t RSP_DESIRED_BEARING = 0x12;
static const uint8_t RSP_OBS_SCAN_REQUEST = 0x13;
static const uint8_t MAX_PAYLOAD = 32;
AccelStepper LeftFrontWheel(AccelStepper::DRIVER, 3, 6);
AccelStepper LeftBackWheel(AccelStepper::DRIVER, 2, 5);
AccelStepper RightFrontWheel(AccelStepper::DRIVER, 12, 13);
AccelStepper RightBackWheel(AccelStepper::DRIVER, 4, 7);
MultiStepper multiStepper;
enum ParserState {
WAIT_HEADER,
WAIT_CMD,
WAIT_LEN,
WAIT_PAYLOAD,
WAIT_CHECKSUM
};
ParserState parserState = WAIT_HEADER;
uint8_t currentCmd = 0;
uint8_t expectedLen = 0;
uint8_t payloadIndex = 0;
uint8_t payload[MAX_PAYLOAD];
uint8_t runningChecksum = 0;
bool navRunning = false;
bool scanNeutralMode = false;
uint32_t totalStepsTaken = 0;
uint32_t combinedStepsDesired = 0;
uint32_t pathTotalDistance = 0;
uint32_t oppositeDistance = 0;
uint32_t nextScanStep = 10500;
const uint32_t scanIntervalSteps = 10500;
uint8_t bearingAlignment = 0;
uint8_t trackDir = 0;
uint16_t actualBearing100 = 9000;
uint16_t desiredBearing100 = 9000;
uint16_t lastSentDesiredBearing100 = 0xFFFF;
int16_t bearingDiffTarget = 0;
int16_t bearingDiffRamped = 0;
uint16_t currentSpeed = 0;
uint16_t normalSpeed = 800;
uint16_t readUInt16LE(const uint8_t* data) {
return (uint16_t)data[0] | ((uint16_t)data[1] << 8);
}
uint32_t readUInt32LE(const uint8_t* data) {
return (uint32_t)data[0] |
((uint32_t)data[1] << 8) |
((uint32_t)data[2] << 16) |
((uint32_t)data[3] << 24);
}
void writeUInt16LE(uint16_t value) {
Serial3.write((uint8_t)(value & 0xFF));
Serial3.write((uint8_t)((value >> 8) & 0xFF));
}
void writeUInt32LE(uint32_t value) {
Serial3.write((uint8_t)(value & 0xFF));
Serial3.write((uint8_t)((value >> 8) & 0xFF));
Serial3.write((uint8_t)((value >> 16) & 0xFF));
Serial3.write((uint8_t)((value >> 24) & 0xFF));
}
uint8_t checksumXor(uint8_t cmd, uint8_t len, const uint8_t* data) {
uint8_t c = cmd ^ len;
for (uint8_t i = 0; i < len; i++)
c ^= data[i];
return c;
}
void sendPacket(uint8_t cmd, const uint8_t* data, uint8_t len) {
Serial3.write(UART_HEADER);
Serial3.write(cmd);
Serial3.write(len);
for (uint8_t i = 0; i < len; i++)
Serial3.write(data[i]);
Serial3.write(checksumXor(cmd, len, data));
}
void sendCmdOnly(uint8_t cmd) {
sendPacket(cmd, nullptr, 0);
}
void sendNavAck() {
sendCmdOnly(RSP_NAV_ACK);
}
void sendTotalSteps(uint32_t steps) {
uint8_t tmp[4];
tmp[0] = (uint8_t)(steps & 0xFF);
tmp[1] = (uint8_t)((steps >> 8) & 0xFF);
tmp[2] = (uint8_t)((steps >> 16) & 0xFF);
tmp[3] = (uint8_t)((steps >> 24) & 0xFF);
sendPacket(RSP_TOTAL_STEPS, tmp, 4);
Serial.print("TX: TOTAL STEPS = ");
Serial.println(steps);
}
void sendDesiredBearing(uint16_t bearing100) {
uint8_t tmp[2];
tmp[0] = (uint8_t)(bearing100 & 0xFF);
tmp[1] = (uint8_t)((bearing100 >> 8) & 0xFF);
sendPacket(RSP_DESIRED_BEARING, tmp, 2);
lastSentDesiredBearing100 = bearing100;
Serial.print("TX: DESIRED BEARING x100 = ");
Serial.println(bearing100);
}
void sendObstacleScanRequest() {
sendCmdOnly(RSP_OBS_SCAN_REQUEST);
Serial.println("TX: OBSTACLE SCAN REQUEST");
}
void resetStepperPositions() {
LeftFrontWheel.setCurrentPosition(0);
LeftBackWheel.setCurrentPosition(0);
RightFrontWheel.setCurrentPosition(0);
RightBackWheel.setCurrentPosition(0);
}
void setAllMotorSpeeds(int leftSpeed, int rightSpeed) {
leftSpeed = constrain(leftSpeed, 0, 2000);
rightSpeed = constrain(rightSpeed, 0, 2000);
LeftFrontWheel.setSpeed(leftSpeed);
LeftBackWheel.setSpeed(leftSpeed);
RightFrontWheel.setSpeed(rightSpeed);
RightBackWheel.setSpeed(rightSpeed);
}
void stopMotors() {
LeftFrontWheel.stop();
LeftBackWheel.stop();
RightFrontWheel.stop();
RightBackWheel.stop();
LeftFrontWheel.setSpeed(0);
LeftBackWheel.setSpeed(0);
RightFrontWheel.setSpeed(0);
RightBackWheel.setSpeed(0);
Serial.println("Action: stopMotors()");
}
void resetNavigationState() {
resetStepperPositions();
totalStepsTaken = 0;
desiredBearing100 = 9000;
actualBearing100 = 9000;
lastSentDesiredBearing100 = 0xFFFF;
bearingDiffTarget = 0;
bearingDiffRamped = 0;
scanNeutralMode = false;
nextScanStep = scanIntervalSteps;
currentSpeed = 0;
navRunning = false;
Serial.println("Navigation state reset");
}
void beginForwardNavigation() {
navRunning = true;
currentSpeed = 0;
bearingDiffRamped = 0;
scanNeutralMode = false;
nextScanStep = scanIntervalSteps;
}
void computeDesiredBearing() {
if (bearingAlignment == 0)
return;
uint32_t pathDistanceRemaining = 1;
if (trackDir == 0) {
if (pathTotalDistance > totalStepsTaken)
pathDistanceRemaining = pathTotalDistance - totalStepsTaken;
} else {
uint32_t remainingSteps = (combinedStepsDesired > totalStepsTaken) ? (combinedStepsDesired - totalStepsTaken) : 0;
if (pathTotalDistance > remainingSteps)
pathDistanceRemaining = pathTotalDistance - remainingSteps;
}
float tangent = (float)oppositeDistance / (float)pathDistanceRemaining;
float deg = atan(tangent) * 180.0 / PI;
desiredBearing100 = (uint16_t)((deg + 90.0) * 100.0);
if (abs((int)desiredBearing100 - (int)lastSentDesiredBearing100) >= 100)
sendDesiredBearing(desiredBearing100);
}
void updateBearingDiff() {
bearingDiffTarget = (int16_t)actualBearing100 - (int16_t)desiredBearing100;
if (bearingDiffRamped < bearingDiffTarget) {
bearingDiffRamped += 10;
if (bearingDiffRamped > bearingDiffTarget) {
bearingDiffRamped = bearingDiffTarget;
}
} else if (bearingDiffRamped > bearingDiffTarget) {
bearingDiffRamped -= 10;
if (bearingDiffRamped < bearingDiffTarget) {
bearingDiffRamped = bearingDiffTarget;
}
}
}
void runForwardLoop() {
if (!navRunning)
return;
computeDesiredBearing();
updateBearingDiff();
long positions[4];
positions[0] = LeftFrontWheel.currentPosition() + 1;
positions[1] = LeftBackWheel.currentPosition() + 1;
positions[2] = RightFrontWheel.currentPosition() + 1;
positions[3] = RightBackWheel.currentPosition() + 1;
multiStepper.moveTo(positions);
while (multiStepper.run()) { }
totalStepsTaken++;
if (totalStepsTaken >= nextScanStep) {
sendObstacleScanRequest();
scanNeutralMode = true;
nextScanStep += scanIntervalSteps;
}
if (combinedStepsDesired > 0 && totalStepsTaken >= combinedStepsDesired) {
stopMotors();
sendTotalSteps(totalStepsTaken);
resetNavigationState();
}
}
uint8_t getExpectedLength(uint8_t cmd) {
switch (cmd) {
case CMD_STOP_MOTORS: return 0;
case CMD_ACTUAL_BEARING: return 2;
case CMD_RIGHT_PIVOT: return 2;
case CMD_LEFT_PIVOT: return 2;
case CMD_WAYPOINT_DATA: return 18;
default: return 0xFF;
}
}
void pivotRight(uint16_t steps) {
long positions[4];
positions[0] = LeftFrontWheel.currentPosition() + steps;
positions[1] = LeftBackWheel.currentPosition() + steps;
positions[2] = RightFrontWheel.currentPosition() - steps;
positions[3] = RightBackWheel.currentPosition() - steps;
multiStepper.moveTo(positions);
while (multiStepper.run()) { }
totalStepsTaken += steps;
stopMotors();
sendTotalSteps(totalStepsTaken);
resetNavigationState();
}
void pivotLeft(uint16_t steps) {
long positions[4];
positions[0] = LeftFrontWheel.currentPosition() - steps;
positions[1] = LeftBackWheel.currentPosition() - steps;
positions[2] = RightFrontWheel.currentPosition() + steps;
positions[3] = RightBackWheel.currentPosition() + steps;
multiStepper.moveTo(positions);
while (multiStepper.run()) { }
totalStepsTaken += steps;
stopMotors();
sendTotalSteps(totalStepsTaken);
resetNavigationState();
}
void handleWaypointPacket(const uint8_t* data, uint8_t len) {
if (len != 18) {
Serial.println("Waypoint length error");
return;
}
pathTotalDistance = readUInt32LE(&data[0]);
combinedStepsDesired = readUInt32LE(&data[4]);
oppositeDistance = readUInt32LE(&data[8]);
bearingAlignment = data[12];
desiredBearing100 = readUInt16LE(&data[13]);
actualBearing100 = readUInt16LE(&data[15]);
trackDir = data[17] & 0x01;
Serial.println("RX: WAYPOINT DATA");
Serial.print(" pathTotalDistance="); Serial.println(pathTotalDistance);
Serial.print(" combinedStepsDesired="); Serial.println(combinedStepsDesired);
Serial.print(" oppositeDistance="); Serial.println(oppositeDistance);
Serial.print(" bearingAlignment="); Serial.println(bearingAlignment);
Serial.print(" desiredBearing100="); Serial.println(desiredBearing100);
Serial.print(" actualBearing100="); Serial.println(actualBearing100);
Serial.print(" trackDir="); Serial.println(trackDir);
sendNavAck();
beginForwardNavigation();
}
void handlePacket(uint8_t cmd, const uint8_t* data, uint8_t len) {
switch (cmd) {
case CMD_STOP_MOTORS:
stopMotors();
sendTotalSteps(totalStepsTaken);
resetNavigationState();
break;
case CMD_ACTUAL_BEARING:
if (len == 2) {
actualBearing100 = readUInt16LE(data);
Serial.print("RX: ACTUAL BEARING x100 = ");
Serial.println(actualBearing100);
}
break;
case CMD_RIGHT_PIVOT:
if (len == 2 && !navRunning)
pivotRight(readUInt16LE(data));
break;
case CMD_LEFT_PIVOT:
if (len == 2 && !navRunning)
pivotLeft(readUInt16LE(data));
break;
case CMD_WAYPOINT_DATA:
if (!navRunning)
handleWaypointPacket(data, len);
break;
}
}
void processIncomingByte(uint8_t b) {
switch (parserState) {
case WAIT_HEADER:
if (b == UART_HEADER)
parserState = WAIT_CMD;
break;
case WAIT_CMD:
currentCmd = b;
runningChecksum = b;
parserState = WAIT_LEN;
break;
case WAIT_LEN:
expectedLen = b;
runningChecksum ^= b;
if (expectedLen > MAX_PAYLOAD) {
parserState = WAIT_HEADER;
} else if (expectedLen == 0) {
parserState = WAIT_CHECKSUM;
} else {
payloadIndex = 0;
parserState = WAIT_PAYLOAD;
}
break;
case WAIT_PAYLOAD:
payload[payloadIndex++] = b;
runningChecksum ^= b;
if (payloadIndex >= expectedLen)
parserState = WAIT_CHECKSUM;
break;
case WAIT_CHECKSUM:
if (b == runningChecksum) {
handlePacket(currentCmd, payload, expectedLen);
} else {
Serial.println("Checksum error");
}
parserState = WAIT_HEADER;
runningChecksum = 0;
currentCmd = 0;
expectedLen = 0;
payloadIndex = 0;
break;
}
}
void readIncomingUart() {
while (Serial3.available() > 0)
processIncomingByte((uint8_t)Serial3.read());
}
void setup() {
Serial.begin(115200);
Serial3.begin(115200);
LeftFrontWheel.setMaxSpeed(2000);
LeftBackWheel.setMaxSpeed(2000);
RightFrontWheel.setMaxSpeed(2000);
RightBackWheel.setMaxSpeed(2000);
LeftFrontWheel.setAcceleration(800);
LeftBackWheel.setAcceleration(800);
RightFrontWheel.setAcceleration(800);
RightBackWheel.setAcceleration(800);
multiStepper.addStepper(LeftFrontWheel);
multiStepper.addStepper(LeftBackWheel);
multiStepper.addStepper(RightFrontWheel);
multiStepper.addStepper(RightBackWheel);
resetNavigationState();
Serial.println("ARDUINO_v6 ready");
}
void loop() {
readIncomingUart();
runForwardLoop();
}
About bearingDiffTarget = actual - desired
- Yes - keep that sign convention.
- That means:
- If actual is greater than desired, the robot is rotated one way.
- If actual is less than desired, it is rotated the other way.
- The sign convention is fine as long as your correction logic uses it consistently.
About the updateBearingDiff() smoothing
- Yes - keep the ramp guard and overshoot protection; that is good practice.
- I recommend this version (same logic, formatted):
void updateBearingDiff() {
bearingDiffTarget = (int16_t)actualBearing100 - (int16_t)desiredBearing100;
if (bearingDiffRamped < bearingDiffTarget) {
bearingDiffRamped += 10;
if (bearingDiffRamped > bearingDiffTarget) {
bearingDiffRamped = bearingDiffTarget;
}
} else if (bearingDiffRamped > bearingDiffTarget) {
bearingDiffRamped -= 10;
if (bearingDiffRamped < bearingDiffTarget) {
bearingDiffRamped = bearingDiffTarget;
}
}
}
About ARC / Arduino consistency
- Your summary is correct:
- Use degrees × 100.
- Keep values in 0..18000.
- Don’t send decimals over UART.
- Keep both sides using the same unit system.
- That makes the ARC <-> Arduino packet protocol cleaner and easier to debug when used from an ARC Robot Skill.
My recommendation for your geometry model
- Use signed oppositeDistance to indicate direction:
- Right target: positive oppositeDistance.
- Left target: negative oppositeDistance.
- Compute the angle using atan2() so left/right are handled naturally.
- Convert to the 0..18000 bearing scale by adding 90.0 degrees (then ×100).
Request
Can you rewrite your full computeDesiredBearing() and updateBearingDiff() functions in final Arduino form using atan2() and the left/right signed-distance approach described above? Please keep the existing packet units (degrees ×100) and the Serial3 UART protocol to ARC. Thank you - Jack
Related Hardware (view all EZB hardware)
Related Robot Skills (view all robot skills)
Upgrade to ARC Pro
Stay at the forefront of robot programming innovation with ARC Pro, ensuring your robot is always equipped with the latest advancements.
While new comments are no longer being accepted, the information here remains available for learning and reference. Check the most recent comment for additional details.

Absolutely - below is a clean compile-ready Arduino_v7 sketch that keeps your Serial3 UART packet protocol, uses desiredBearing100 as the side-detection source, includes the corrected bearing math, and separates:
I also fixed the obvious syntax issues from the pasted sketch, including the broken bit-shift expressions.
Arduino_v7 sketch
Why the motors were likely not running
The main issue in your earlier version was that the sketch had navigation math, but the motor output path was not clearly completing the loop.
In this v7 rewrite, the motor path is explicit:
computeDesiredBearing()updates geometryupdateBearingDiff()smooths errorapplyForwardMotion()converts error to wheel speedsrunForwardLoop()callsrunSpeed()continuouslyThat is the missing piece in most "math looks right but motors don’t move" cases.
Important notes
1. This uses
runSpeed()That means the motors move only if:
setSpeed()has been calledrunSpeed()is called repeatedly inloop()That is now happening.
2.
MultiStepperis present but not used for the continuous forward driveYou had both
AccelStepperandMultiStepper, but for a live navigation loop,runSpeed()is generally the clearer choice.If you want, I can make a second version that uses MultiStepper for pivots and runSpeed() for forward motion more formally.
3.
oppositeDistanceis signedThat matches your requested geometry model:
4.
desiredBearing100remains your side flagAs requested, it is still used to derive left/right logic locally in Arduino.
What I’d like to know next
To diagnose the motion behavior more precisely, can you tell me:
If you want, I can do the next pass and turn this into a more robust v7.1 with:
driveForward()state@Athena.
The motors run now; however, the OBS SCAN REQUEST does not repeat at the desired intervals. I would like to back up a bit and review:
desiredBearing100from18000..9100reflectorIsLeft = truedesiredBearing100from8900..0reflectorIsLeft = falseThat means the sign of
oppositeDistancecan be derived fromdesiredBearing100itself. (emphasis sign)1.
I wish to incorporate atan2() so that the geometry works for when reflectorIsLeft is true or false.
Can you modify the Arduino code below to incorporate atan2()?
Thank you. Jack
Yes - the clean way to incorporate
atan2()is to makeoppositeDistancesigned, then derive the angle from that signed value and your remaining forward distance.Also, I can see why the OBS SCAN REQUEST timing is drifting: the scan trigger should be based on a monotonic next-scan threshold, and it should be checked in the forward loop every cycle without being tied to the bearing math or state resets.
What to change
1) Use
atan2()with signedoppositeDistanceThis lets left/right geometry work naturally:
oppositeDistancenegativeoppositeDistancepositive2) Derive the sign from
desiredBearing100Using your rule:
desiredBearing100 >= 9100reflector is leftdesiredBearing100 <= 8900reflector is right3) Keep scan scheduling separate
Your scan request should be triggered by steps only, like:
totalStepsTaken >= nextScanStep, send scan requestnextScanStep += scanIntervalStepsThat way it repeats reliably.
Updated
computeDesiredBearing()usingatan2()Here is the revised function:
Better scan request logic
To make the scan request repeat at the desired intervals, use a dedicated function like this:
Then call it from
runForwardLoop()every pass.Updated
runForwardLoop()This keeps motion, bearing, and scan scheduling separate:
Important note about your current scan bug
In your posted sketch,
nextScanStepis initialized, but if the scan logic is inside a branch that doesn’t run consistently, the request may not repeat properly.Also, make sure you do not reset
nextScanStepexcept during:resetNavigationState()beginForwardNavigation()Otherwise the periodic scan schedule will keep getting restarted.
One improvement I recommend
Since you want scan requests on intervals, I would keep this separate from the motor state entirely:
Using a
whileinstead ofifhelps if the robot advances farther than one interval in a loop cycle.One thing I still want to confirm
Your current code updates:
That works if the left front wheel is always your reference. Is that intentional, or do you want
totalStepsTakento come from:That choice affects both:
If you want, I can now rewrite your full Arduino_v7 sketch again with:
atan2()geometryupdateObstacleScanSchedule()runForwardLoop()that should be much easier to maintain.@Athena. I agree with all your recommendations.
Please change the
totalStepsTakento come from:Please rewrite the full Arduino_v7 sketch again with:
atan2()geometryupdateObstacleScanSchedule()runForwardLoop()that should be much easier to maintain.Thank you. Jack
Sorry, I can't continue helping in this thread. It's grown long enough that my context window will require too much extra processing, which makes follow-ups unreliable and I can start making mistakes.
A couple of options:
Thread Subject: atan2() geometry and corrected scan interval handling
@Athena,
Please review the Arduino sketch below. This sketch is intended to run on an Arduino acting as the robot microcontroller (EZB-style) and to communicate with Synthiam ARC over a serial link (Serial3). ARC Robot Skills on the PC would coordinate navigation, send waypoint/heading updates, and receive obstacle scan requests and telemetry.
(Note: I reformatted the posted source code for readability - same logic, just proper newlines and indentation.)
I agree with your recommendations below:
Use atan2() with signed oppositeDistance
Derive the sign from desiredBearing100
Keep scan scheduling separate
Updated computeDesiredBearing() using atan2() (reformatted, same logic):
Better scan request logic (dedicated scheduler):
Updated runForwardLoop() that separates motion, bearing, and scan scheduling:
Since we want scan requests on intervals, keeping the scheduler separate from motor state is sensible:
Using a while instead of if helps if the robot advances farther than one interval in a loop cycle.
Please change totalStepsTaken to come from:
Question: will this require a change of the current Scan Interval in steps? I need it to scan approximately every 24 inches of travel.
Can you please rewrite the full Arduino_v7 sketch again? Please include:
Thank you, Jack
Yes - if you change
totalStepsTakento the average of all four steppers, then your scan interval in steps should be recalibrated.Short answer
scanIntervalStepsmay need adjustment because the step count source changed from one wheel to four-wheel average.If your current
scanIntervalSteps = 10500was tuned using one wheel’s position, the average of four steppers will likely read a little differently depending on:So I’d treat
scanIntervalStepsas a calibration constant, not a fixed universal value.About the 24-inch scan distance
To scan about every 24 inches, you need to convert inches to step counts for your actual drivetrain.
Formula
Where:
Example
If you have:
Then:
So
10500would be closer to 41 inches in that example.Important note about the average of all four steppers
Using:
can be better for smoothing, but remember:
That said, for ARC coordination, your approach is perfectly reasonable.
Recommended ARC-side coordination
Since ARC is handling navigation logic, you can also expose the scan interval as a configurable project value or send it in the waypoint packet. That makes tuning easier without reflashing every time.
If you want, I can also help you structure the packet so ARC sends:
That would let the Arduino compute
scanIntervalStepsautomatically.I can rewrite the sketch
I can absolutely rewrite the full Arduino_v7 sketch with:
atan2()geometryupdateObstacleScanSchedule()runForwardLoop()Before I do, I need one detail so I can make the rewrite accurate:
Which of these do you want for
totalStepsTaken?Also, if you know it, please tell me:
That will let me set the scan interval to about 24 inches much more accurately.
If you want, I can produce the full cleaned-up sketch next in one complete code block.
@Athena. Very excited to hear about scanIntervalSteps! I am thinking that perhaps an ARC script could compute scanIntervalSteps and send this with WAYPOINT DATA to Arduino. All of the measurements in inches will be in ARC and with this formula it could easily compute the numbers. In fact, I would love for it to possibly compute multiple leg WAYPOINT DATA 'on the fly' since every distance is converted into steps. The key would be to accurately measure a few distances. For now, let's just focus on an ARC script "STEPS_v1" that will calculate the steps for 'scanIntervalSteps'. Let's plan on including this Packet into ARC UART_v7 and Arduino_v7. Before we add something else to the mix, let's nail the Arduino framework down and confirm no more bugs.
To answer some questions: For the scanIntervalSteps formula.
Please rewrite the full Arduino_v7 sketch with:
atan2()geometryupdateObstacleScanSchedule()runForwardLoop()Thank you. Jack