Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect DDU version #4

Open
cboulay opened this issue Apr 1, 2021 · 1 comment
Open

Detect DDU version #4

cboulay opened this issue Apr 1, 2021 · 1 comment

Comments

@cboulay
Copy link
Member

cboulay commented Apr 1, 2021

The different DDU versions scale the value read from the serial port (or USB2Serial port) differently. Here are some notes I have from the DDU serial interface documentation:

CLICK ME
AXON+:
AXON+ will enable Axon communication

AXON-:
AXON- will disable Axon communications

BOUNCE:
The bounce command is used to cause the motor to continuously move the motor
between 0 and the forward limit.
Sending bounce while in bounce mode will exit the bounce procedure.

C:
This will report whether the motor/encoder and remote are detected.

E will display any text that follow is on the lead. Ex: 'ETesting'

DX:
This will set the display to Distance to Target mode.

DZ:
This will set the display to Distance to Zero mode.

L:
L by itself will report which language number is selected.
L followed by a number will set the language number to the specified number.

MM:
MM will set the display to use millimeters for units.

MODE:
MODE by itself will report the current emulation mode.
MODE followed by a space and a version number will set the emulation mode
to that version. E.g. MODE 2.20 will cause the mT Controller to emulate
operation of firmware version 2.20.

Versions 2.12 and 2.20 are currently supported.

O:
O by itself will report the current offset position.
Offset is used to specify the starting position of the drive.
It can be set as many times before or after the drive is zeroed.
Automatically reverts to zero on power up.

R:
R will report the position of the drive.

UM:
UM will set the display to use microns for units.

V:
V will print out the current software version.

X followed by a number will set the target value to the specified number.

Z:
Z by itself will report the current limit value.
Z followed by a number will set the limit value to the specified number.

Additionally, when in 2.20 mode only...

GO:
GO will force the mTController to start advancing towards the next stop point if the last one has been reached, without having to turn the remote to stop or retract and then back to advance.

SP will report the next stop point value.
If the fixed step advancing option is disabled, SP will report 0.

SS by itself will report the fixed step size value.
SS followed by a number between 100 microns and drive limit will set the fixed step advance size. Entering zero disables the fixed step advance functionality.
Automatically reverts to zero on power up.
@cboulay
Copy link
Member Author

cboulay commented Apr 28, 2023

Also:

  • Automatically calculate drive DTT when provided with the plan DTT
    • StarDrive needs -60 (assumes zeroes at 0)
    • NexDrive requires knowing the secondary stage setting when zeroing the drive.

This should probably be in a config file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant