Compare commits

...

3 Commits

Author SHA1 Message Date
mathis_s 9098a932fa Fixed bug in response parsing
Test And Build / Lint (push) Failing after 4s
Test And Build / Build (push) Successful in 8s
If the byte 15 is encountered in the message, the parseResponse function
must return asynDisconnected (instead of asynSuccess) so the state of
the axis is accounted for properly.
2026-04-09 10:47:27 +02:00
mathis_s b96605916f Rolled back to motorBase 7.3.2 because 7.4.0 is bugged
Test And Build / Lint (push) Failing after 5s
Test And Build / Build (push) Successful in 8s
In particular, the following problem can happen (shown for a TurboPMAC,
but MasterMACS will run into the same issue):

2026/03/31 11:45:04.698 asynPortDriver:getDoubleParam: port=turboPmac1 error getting parameter 42 MOTOR_STATUS_HOMED, in list 1, wrong type
2026/03/31 11:45:04.698 Controller "turboPmac1", axis 1 => virtual asynStatus turboPmacAxis::init(), line 168:
Accessing the parameter library failed for parameter motorRecResolution_ with error wrong type.

This is definitely because of 7.4.0, because forcing 7.3.2 fixes it.
2026-04-01 10:37:06 +02:00
mathis_s 4d65dd238d Incremented required motorBase version to match upstream (7.3.2 was a local patch version which doesn't exist upstream)
Test And Build / Lint (push) Failing after 4s
Test And Build / Build (push) Successful in 8s
2026-03-24 14:26:25 +01:00
+1 -1
View File
@@ -493,7 +493,7 @@ asynStatus masterMacsController::parseResponse(
}
}
}
break;
return asynDisconnected;
} else if (fullResponse[i] == '\x18') {
// CAN
snprintf(drvMessageText, MAXBUF_,