×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Baader Steeldrive

  • Posts: 49
  • Thank you received: 1
Hello,
Are there plans to develop an integration focuser Baader Steeldrive BA2957150?
www.teleskop-express.de/shop/product_inf...cts_id=4853#zubehoer

Sincerely

Daniel
9 years 8 months ago #1542

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic Baader Steeldrive

Does it have an accessible API?
9 years 4 months ago #2208

Please Log in or Create an account to join the conversation.

  • Posts: 49
  • Thank you received: 1

Replied by Daniel Constantin on topic Baader Steeldrive

No :(
I have since bought another focuser, usb.focus.3 develop and provides the information to develop an Indi driver. So I want to know if someone is going to develop this driver ?
Sincerely
www.usb-foc.us/
Daniel
9 years 4 months ago #2211

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic Baader Steeldrive

What information it provides to develop the INDI driver? Do you have any?
9 years 4 months ago #2214

Please Log in or Create an account to join the conversation.

  • Posts: 158
  • Thank you received: 2
I have a Baader SteelDrive focuser exactly as stated in the first post. I sniffed the protocol - I can give the entire command set. Hope somebody can help with developing the driver ;)
9 years 3 months ago #2230

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic Baader Steeldrive

Sure, what's the protocol? Does the manufacturer provide any official documentation on the protocol as well?
9 years 3 months ago #2235

Please Log in or Create an account to join the conversation.

  • Posts: 158
  • Thank you received: 2


Button UP:
- On press:
:F1MUP00#
- On release:
:F3STOP0#

Button DOWN:
- On press:
:F2MDOW0#
- On release:
:F3STOP0#

Field position:
- Request:
:FASKP0#
- Reply:
:F600000#
- Example: 5 mm will be
:F600500#

Field temperature:
- Request:
:F5ASKT0#
- Reply (if there is probe connected):
:F5+1810#
- Reply (no probe connected):
:F5-----#

Field step:
- Request:
:F8ASKS0#
- Reply:
:F80000000#

Field Sync Absolute (step):
- Request:
:FB0000000#
- Purpose: override current step counter with another step number

Field GoTo Absolute (step):
- Request:
:F90000000#

Field GoTo Incremental (step):
- Request when "+":
:FA2000000#
- Request when "-":
:FA1000000#

Field Sync Absolute (mm):
- See Sync Absolute (step)
- Explanation: We can ask from focuser current position by mm, but we can't ask it to go by mm, only by steps, the application itself is doing the conversion (will be described later)

Field GoTo Absolute (mm):
- See GoTo Absolute (step)
- Explanation: See the one from Sync Absolute (mm)

Field GoTo Incremental (mm):
- See GoTo Incremental (step)
- Explanation: See the one from Sync Absolute (mm)

HW Version and Date:
- Request
:FVERSIO#
- Reply:
:FV2.00812#

FW Version and Date:
- Request:
:FNFIRMW#
- Reply:
:FN2.21012#

The right half is a bit trickier... A will describe it a little bit later :)
Last edit: 9 years 3 months ago by Alexandru Barbovschi.
9 years 3 months ago #2249

Please Log in or Create an account to join the conversation.

  • Posts: 158
  • Thank you received: 2
Button start from T compensation settings:
- By pressing it the SteelGo application memorize the current temperature. After >=0.5 degrees temperature change user can press the calculate button and the app will suggest T Coefficient (there is no description on the algorithm of calculation)

Button Enable T Compensation:
- Request:
:F7ASKC0#
- Reply (if T compensation is disabled):
:F710004#
- Reply (if T compensation is enabled):
:F710024#
- For writing (disabling):
:F041000#
- For writing (enabling):
:F041002#
- Note: the number 4 you can see here is related to Select Focuser model drop-down list. The numbering starts from 0 (total - 5 items). More details later. Number 100 is from the Type T Coefficient field. Numbers 0/2 are working like a switch

Field Number of T Samples:
- Request:
:FLSPCOM#
- Reply:
:FL35000#
- For writing:
:FI35000#
- Explanation: 05000 is 16, 15000 is 32, 25000 is 64 and 35000 is 128 samples per second

Button Position Calibration: start:
- From the User Guide it should move focuser to 25,00 mm position (active only if Custom type of focuser is chosen). In my case it is asking to do it manually with UP and/or DOWN buttons. After that calculate button must be pressed. Honestly, this part in User Guide is not very clear to me, will post it here for your analysis

Field Type MAX Trip (mm):
- Request:
:F8ASKS1#
- Reply:
:F40011577#
- For writing:
:FC0011577#
- Calculation: If MAX Trip is 28,99, when 2899/0,25040 (taken from Gear Ratio, below) = 11577,47. As far as I understood the result is rounded

Field Type Gear Ratio:
- Request:
:FEASKGR#
- Reply:
:FE25040#
- For writing:
:FD25040#

Drop-down menu Select Focuser model:
- There are 5 items in it: SteelTrack NT2, SteelTrack SC2, SteelTrack RT2, SteelTrack RT3 and Custom.
- NT2: MAX Trip 30, Gear Ratio 0,25040
- SC2: MAX Trip 30, Gear Ratio 0,25040
- RT2: MAX Trip 80, Gear Ratio 0,25040
- RT3: MAX Trip 115, Gear Ratio 0,25040
- Custom: It's my case. Why not SC2 if it is designed for my Schmidt-Cassegrain? Don't know for sure, but may be because the focuser I have can't actually reach 30, only 29,49 (on screenshot is a different number because I am playing with it, Gear Ratio seems not to be corresponding to Vernier scale)

Slider Slew Rate:
- Request:
:FGSPMAX#
- Reply:
:FG00350#
- For writing:
:Fg00350#
- The range is in between 350 and 1000

Slider Acceleration Ramp:
- Request:
:FHSPMIN#
- Reply:
:FH01800#
- For writing:
:Fh03000#
- The range is in between 1500 and 3000

Field Description:
- Request:
:FMDESCR#
- Reply:
:FMCelestronEdgeHD#
- For writing:
:FmCelestronEdgeHD#
- Note: it must 15 characters long! If less - space character must be added!

IMPORTANT NOTE: All the parameters what can be written to the focuser are lost after disconnection. There is a way to save permanently - send
:FFPOWER#
command!

If I haven't missed something this is the entire command set. If any questions - just ask!

P.S. There is a hidden command, purpose of which I don't understand at the moment:
:FIDCODE#
Reply:
:FI00w6G130161#
Last edit: 9 years 3 months ago by Alexandru Barbovschi.
9 years 3 months ago #2251

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic Baader Steeldrive

That sounds fairly straight forward, similar to Robofocus command set.
9 years 3 months ago #2257

Please Log in or Create an account to join the conversation.

  • Posts: 158
  • Thank you received: 2
Finished! Hope to see driver soon, without it I can't start using at full Ekos ;)
9 years 3 months ago #2258

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic Baader Steeldrive

Ok, my brain hurts when I read 29,89.. I assume it is 29.89... writing the driver now.

What are the physical units of slew speed and acceleration?

EDIT: One more thing, MAX Trip in steps is a custom value you enter that depends on your focuser model? The minimum is 0 and maximum is MAX TRIP ?

Connection parameters? I'm assuming 9600 8N1
Last edit: 9 years 3 months ago by Jasem Mutlaq.
9 years 3 months ago #2269

Please Log in or Create an account to join the conversation.

  • Posts: 158
  • Thank you received: 2
My brain hurts too. But I am no guilty! ;) Just in different parts of world different standards of decimal and group separators. In US for example for decimal separation is used dot and for group - comma. In Europe (not sure if in all countries) it is vice-versa. It creates headache with different kind of software...
There are no physical units for slew speed and acceleration as far as I can see from SteelGo application.
If the model is NOT custom MAX trip is a fixed number (I gave the list of models and corresponding values). If focuser is custom it can be whatever is the digital limit of the command I suppose :)
9 years 3 months ago #2270

Please Log in or Create an account to join the conversation.

Time to create page: 0.767 seconds