2111 replies to this topic

[fdboucher]

Here is v8.25 of the firmware for this project: hbg3.ino.v8.25.txt

• Fix Nunchuck to use appropriate speeds when talking to a Celestron Focus Motor vs a local stepper motor.

I am disappointed.  Very disappointed.

 

This has been broken for a very long time, and until today nobody bothered to point it out.  The way this stuff should happen, is I need you to try new firmware releases and tell me what doesn't work!!!  I'm just one guy, without Celestron's hardware inventory and other resources.  This needs your help to keep it better than what they offer!

 

Flashable binaries are in the usual places, including the OTA Firmware Update mechanism.

Off to Amazon now to purchase a Celestron Focus Motor that I'll never use myself, needed for testing.

 

Blah.

I am very sorry Mark. I understand your frustration.

I thought that something might be an issue with the CFM speed control…

Sadly, the sky around here has been so rotten for the past few weeks that I never got to test it thoroughly.

My last night of observation was November 4. Last week the sky was clear one night, but the temperature outside was -14°C (felt like -18°C).

I only eyed Jupiter through my binos, for a few minutes… 

 

Another thing is: the discussions around here are at such an elevated technical level, that I would have to be very very certain that I did not muck up something myself before I posted on this thread with a newb' question about some issue with the G3PCB… 

 

Thanks for fixing that issue. I hope I can try it out soon…   

Edited by fdboucher, 10 December 2023 - 10:11 PM.

[mlord]

Yeah, I'm hoping for clear skies maybe on Wednesday night here.

[Rac19]

Powering HBG3 from 12 VDC. I want to do this for reasons explained below.

 

I am thinking of purchasing a an RJ 12 "breakout" terminal connector and connecting 12 VDC to the appropriate pins as per the two images attached. Obviously care would need to be taken to connect 12 VDC to the correct pins.

 

As to why I want to do this? It's a little embarrassing. Somehow, I have broken the connector tongue inside the micro USB socket. I am aware of the need to careful, but it happened. Because my permanently mounted scope is at a marginal distance from my WiFi router for 2.6 GHz WiFi, I need to bring the HBG3 inside and power it standalone to perform OTA upgrades. I have done this once on USB power, but that will no longer be possible. The loss of USB communications is not of particular concern but I would like to be able to perform OTA upgrades.

 

EDIT: A simple way test which screw terminals should be used for 12 VDC would be to plug it into the Evolution mount and check with a multimeter, taking note of polarity.

Attached Thumbnails

• 
• 

Edited by Rac19, 11 December 2023 - 07:09 AM.

[Astro Andy]

You could use a mobile phone as a HotSpot (replicating your home WiFi) and run the ota_update that way. Let the HBG3 connect then use the LCD and button to trigger the update.

 

If you don't have the LCD then using JuiceSSH set to Telnet, port 3000 @ whatever IP your phone gives it. 

[Astro Andy]

I've just built a replacement HBG3 (after a USB port failure on the ESP32) and had a 6" reversed cable made with RJ12 instead of using the RJ11 I had to hand. The RJ11 worked when USB power was supplied to the ESP32.

 

As my new build also didn't power up with the reverse wired cable I checked and the cable required is actually 'straight' wiring. The connectors are reversed.

 

Waiting for fresh RJ12 heads...RJ11 and USB still works a treat.

 

 

Attached Thumbnails

• 
• 
• 

[mlord]

The top diagram on the left, which you have circled, is a "/R" cable, which is correct for this application.  Wired exactly the same as the cable that would have been in the HBG3 kit.

 

It is widely and incorrectly called a "straight through" (which it most definitely is NOT).  So I don't use those labels, since the internet mostly seems to be getting them backwards.  Instead, I always say to hold up the two connectors side-by-side, and ensure the wire colour order is the same on each, left to right.

 

It's called a "/R", because if you lay the cable down flat, one connector/tab is on the Reverse side of the cable compared to the other.  This has the effect of swapping the wire order from end to end (twisted, not straight through!!), which is exactly what is needed here.  The larger and better-known manufacturers of such cables label them as "/R", as does the Telecom industry which invented them.

 

Do NOT use the device with a 4-wire "/R" ("RJ11") cable, even if it appears to be working.  It is missing the "BUSY" line that mitigates bus collisions, and could result in permanent electrical failures.  The HBG3 is safe in this regard, but other Celestron gear is not.

 

Cheers

Edited by mlord, 11 December 2023 - 10:06 AM.

[mlord]

I am thinking of purchasing a an RJ 12 "breakout" terminal connector and connecting 12 VDC to the appropriate pins as per the two images attached. Obviously care would need to be taken to connect 12 VDC to the correct pins.

..

The loss of USB communications is not of particular concern but I would like to be able to perform OTA upgrades.

Sure you can do that.  The diagram you posted for that device is labelled correctly.

 

But Note that OTA updates are easier done using just the OLED display and integrated push-button of newer HBG3 units.  Still needs power though, which can come from a mount or from USB.

 

Cheers

Edited by mlord, 11 December 2023 - 10:55 AM.

[dlwmacgregor]

Sure you can do that.  The diagram you posted for that device is labelled correctly.

 

But Note that OTA updates are easier done using just the OLED display and integrated push-button of newer HBG3 units.  Still needs power though, which can come from a mount or from USB.

 

Cheers

I didn't realize that I could do an "OTA Update" with just a USB connection. I thought I had to haul my Mount out and do an AUX connection.

[Rac19]

The top diagram on the left, which you have circled, is a "/R" cable, which is correct for this application.  Wired exactly the same as the cable that would have been in the HBG3 kit.

 

It is widely and incorrectly called a "straight through" (which it most definitely is NOT).  So I don't use those labels, since the internet mostly seems to be getting them backwards.  Instead, I always say to hold up the two connectors side-by-side, and ensure the wire colour order is the same on each, left to right.

 

It's called a "/R", because if you lay the cable down flat, one connector/tab is on the Reverse side of the cable compared to the other.  This has the effect of swapping the wire order from end to end (twisted, not straight through!!), which is exactly what is needed here.  The larger and better-known manufacturers of such cables label them as "/R", as does the Telecom industry which invented them.

 

Do NOT use the device with a 4-wire "/R" ("RJ11") cable, even if it appears to be working.  It is missing the "BUSY" line that mitigates bus collisions, and could result in permanent electrical failures.  The HBG3 is safe in this regard, but other Celestron gear is not.

 

Cheers

Yep, terms such as "straight through", "reversed" etc cause endless confusion and no doubt many mishaps. "pin for pin" or "one to one" might be a better descriptions than "straight through".

 

I agree also that holding the two connectors side by side is the best way to check. The "tag up", "tag down" check is also valid.

Attached Thumbnails

• 

Edited by Rac19, 11 December 2023 - 04:44 PM.

[Rac19]

You could use a mobile phone as a HotSpot (replicating your home WiFi) and run the ota_update that way. Let the HBG3 connect then use the LCD and button to trigger the update.

 

If you don't have the LCD then using JuiceSSH set to Telnet, port 3000 @ whatever IP your phone gives it. 

Thanks, that is an option that I had considered.

[Rac19]

I didn't realize that I could do an "OTA Update" with just a USB connection. I thought I had to haul my Mount out and do an AUX connection.

This can be very handy. My 'scope is permanently mounted with a very marginal 2.6 GHz WiFi signal. I have a 5 GHz mesh repeater but the HBG3 is  2.6 GHz only. Also, the OLED isn't legible in daylight so I really need to perform OTA upgrades indoors, during daylight hours at least.

[Frapeno]

Hi folks, some else could inform whether focus motor function built in HGB3, can be controlled by which astronomy software ?
Or focus motor function only can works by using Skyportal app or by Hand controller ?

[mlord]

Hi folks, some else could inform whether focus motor function built in HGB3, can be controlled by which astronomy software ?
Or focus motor function only can works by using Skyportal app or by Hand controller ?

The Focus Motor functionality in the HBG3 emulates the Celestron Focus Motor.  So any software that can control a Celestron Focus Motor can also be used with a stepper motor connected to the HBG3.  I'm pretty sure there are ASCOM drivers or something for that out there, in addition to CPWI which works.

[Frapeno]

The Focus Motor functionality in the HBG3 emulates the Celestron Focus Motor.  So any software that can control a Celestron Focus Motor can also be used with a stepper motor connected to the HBG3.  I'm pretty sure there are ASCOM drivers or something for that out there, in addition to CPWI which works.

I am trying to control it by Kstars/Indi, I choose the option DIY MyfocuserPro2, but not success yet.
I will check CPWI soon 

 

Thanks Mlord

[Frapeno]

I am trying to control it by Kstars/Indi, I choose the option DIY MyfocuserPro2, but not success yet.
I will check CPWI soon 

 

Thanks Mlord

Just did a quick test with CPWI and works fine 

So, I will try again with Kstars/Indi options, if some else has done it before, give some tips pls, 

[eleven]

Hello,

 

I have 2 questions that I'd like to ask.

 

1.  I purchased a fram module cannot find a schematic or hook up diagram in the forum threads.  Perhaps I overlooked it.  Mark, if you or someone can help/point me in the right direction I'd appreciate it.

 

2. In the attached picture, I'd like to 3d print this focuser bracket.  Is the stl or obj file available for this print?

 

Kind Regards,

 

 

[Rac19]

Windows Bluetooth, this may be of interest.

 

The attached image shows the mysterious two Com ports. I am not at all sure if the "Incoming" or "Outgoing" is best suited for HBG3, probably Outgoing.

 

Going by the log, CPWI connects to Com 7 (Outgoing) but fails to detect any Celestron devices on the Aux bus. The HBG3 is definitely connected to the Aux bus and the USB connection worked for a while until the micro USB receptacle was broken.

With Com 8 CPWI connects and waits forever. I gave up after 25 minutes. I had to block Com 7 in order to get CPWI to try Com 8

 

EDIT: The HomeBrew Bluetooth device shows as paired but never connected. By contrast Bluetooth game controller changed from paired to connected when in use.

 

Com 7

log begins... C:\Users\xxxxx\OneDrive\Documents\Celestron\CPWI\Logs\CPWI_log_2023_12_12.txt 0
2023-12-12 19:21:35.425 +11:00 [#1] (LogUtil) CPWI version: 2.5.2.99
2023-12-12 19:21:35.539 +11:00 [#1] (Cpwi) Starting CPWI...
2023-12-12 19:21:35.539 +11:00 [#1] (Cpwi) Starting ASCOM HTTP server...
2023-12-12 19:21:36.758 +11:00 [#1] (Cpwi) Server running on http://localhost:5555/
2023-12-12 19:21:36.758 +11:00 [#1] (Cpwi) Loading settings...
2023-12-12 19:21:36.766 +11:00 [#1] (Cpwi) Starting Gamepad service...
2023-12-12 19:21:36.792 +11:00 [#1] (Cpwi) Starting Connection service...
2023-12-12 19:21:51.339 +11:00 [#1] (Connection) Disconnection requested
2023-12-12 19:21:51.354 +11:00 [Connection_Tasks1#5] (Connection) Disconnecting all devices
2023-12-12 19:21:51.358 +11:00 [Connection_Tasks1#5] (Connection) Closing all ports
2023-12-12 19:21:51.658 +11:00 [Connection_Tasks1#5] (Connection) Attempting to connect via USB
2023-12-12 19:21:51.713 +11:00 [Connection_Tasks1#5] (Connection) Attempting to connect by USB
2023-12-12 19:21:51.713 +11:00 [Connection_Tasks1#5] (Connection) Searching for serial over TCP
2023-12-12 19:21:53.719 +11:00 [Connection_Tasks1#5] (Connection) Searching for serial over COM
2023-12-12 19:21:53.719 +11:00 [Connection_Tasks1#5] (Connection) Available COM ports: [COM8, COM7]
2023-12-12 19:21:53.719 +11:00 [Connection_Tasks1#5] (Connection) Last successfully connected COM ports: [COM3]
2023-12-12 19:21:53.719 +11:00 [Connection_Tasks1#5] (Connection) Currently blocked COM ports: [COM8]
2023-12-12 19:21:53.719 +11:00 [Connection_Tasks1#5] (Connection) Filtered COM port list: [COM7]
2023-12-12 19:21:53.719 +11:00 [Connection_Tasks1#5] (Connection) Attempting to open port COM7
2023-12-12 19:21:53.719 +11:00 [Connection_Tasks1#5] (Connection) If a hand-controller is present on port COM7, putting it into passthrough mode now.
2023-12-12 19:21:53.719 +11:00 [Connection_Tasks1#5] (Connection) Opening COM7 to attempt version command
2023-12-12 19:21:53.719 +11:00 [Connection_Tasks1#5] (ComPort) Opening COM port...
2023-12-12 19:21:54.780 +11:00 [Connection_Tasks1#5] (ComPort) Opened COM port successfully.
2023-12-12 19:21:56.319 +11:00 [Connection_Tasks1#5] (ComPort) Closing COM port...
2023-12-12 19:21:56.319 +11:00 [Connection_Tasks1#5] (ComPort) Closed COM port successfully.
2023-12-12 19:21:56.319 +11:00 [Connection_Tasks1#5] (Connection) Closed COM7 after attempting version command
2023-12-12 19:21:56.319 +11:00 [Connection_Tasks1#5] (Connection) Opening COM7 to attempt enabling passthrough
2023-12-12 19:21:56.319 +11:00 [Connection_Tasks1#5] (ComPort) Opening COM port...
2023-12-12 19:21:56.364 +11:00 [Connection_Tasks1#5] (ComPort) Closing COM port...
2023-12-12 19:21:56.364 +11:00 [Connection_Tasks1#5] (ComPort) Closed COM port successfully.
2023-12-12 19:21:56.364 +11:00 [Connection_Tasks1#5] (ComPort) Opening COM port...
2023-12-12 19:21:56.532 +11:00 [Connection_Tasks1#5] (Connection) Found no Celestron devices on port COM7
2023-12-12 19:21:56.549 +11:00 [Connection_Tasks1#5] (Connection) Failed to connect via USB
2023-12-12 19:21:56.549 +11:00 [Connection_Tasks1#5] (Connection) FAILED to connect
2023-12-12 19:22:31.247 +11:00 [#1] (MainForm) Main form attempting to close
2023-12-12 19:22:31.247 +11:00 [#1] (Connection) Connection shutdown scheduled
2023-12-12 19:22:31.251 +11:00 [#1] (Connection) Disconnecting all devices
2023-12-12 19:22:31.251 +11:00 [#1] (Connection) Disconnecting Mount
2023-12-12 19:22:31.251 +11:00 [#1] (Connection) Already disconnected
2023-12-12 19:22:31.251 +11:00 [#1] (Connection) Closing all ports

 

Com 8

log begins... C:\Users\xxxxx\OneDrive\Documents\Celestron\CPWI\Logs\CPWI_log_2023_12_12.txt 0
2023-12-12 18:46:13.670 +11:00 [#1] (LogUtil) CPWI version: 2.5.2.99
2023-12-12 18:46:13.787 +11:00 [#1] (Cpwi) Starting CPWI...
2023-12-12 18:46:13.787 +11:00 [#1] (Cpwi) Starting ASCOM HTTP server...
2023-12-12 18:46:14.981 +11:00 [#1] (Cpwi) Server running on http://localhost:5555/
2023-12-12 18:46:14.981 +11:00 [#1] (Cpwi) Loading settings...
2023-12-12 18:46:14.990 +11:00 [#1] (Cpwi) Starting Gamepad service...
2023-12-12 18:46:15.017 +11:00 [#1] (Cpwi) Starting Connection service...
2023-12-12 18:51:40.876 +11:00 [#1] (Connection) Disconnection requested
2023-12-12 18:51:40.876 +11:00 [Connection_Tasks1#5] (Connection) Disconnecting all devices
2023-12-12 18:51:40.890 +11:00 [Connection_Tasks1#5] (Connection) Closing all ports
2023-12-12 18:51:41.196 +11:00 [Connection_Tasks1#5] (Connection) Attempting to connect via USB
2023-12-12 18:51:41.225 +11:00 [Connection_Tasks1#5] (Connection) Attempting to connect by USB
2023-12-12 18:51:41.225 +11:00 [Connection_Tasks1#5] (Connection) Searching for serial over TCP
2023-12-12 18:51:43.236 +11:00 [Connection_Tasks1#5] (Connection) Searching for serial over COM
2023-12-12 18:51:43.236 +11:00 [Connection_Tasks1#5] (Connection) Available COM ports: [COM8, COM7]
2023-12-12 18:51:43.236 +11:00 [Connection_Tasks1#5] (Connection) Last successfully connected COM ports: [COM3]
2023-12-12 18:51:43.236 +11:00 [Connection_Tasks1#5] (Connection) Currently blocked COM ports: [COM7]
2023-12-12 18:51:43.236 +11:00 [Connection_Tasks1#5] (Connection) Filtered COM port list: [COM8]
2023-12-12 18:51:43.236 +11:00 [Connection_Tasks1#5] (Connection) Attempting to open port COM8
2023-12-12 18:51:43.386 +11:00 [Connection_Tasks1#5] (Connection) If a hand-controller is present on port COM8, putting it into passthrough mode now.
2023-12-12 18:51:43.386 +11:00 [Connection_Tasks1#5] (Connection) Opening COM8 to attempt version command
2023-12-12 18:51:43.386 +11:00 [Connection_Tasks1#5] (ComPort) Opening COM port...
2023-12-12 18:51:43.386 +11:00 [Connection_Tasks1#5] (ComPort) Opened COM port successfully.

Note: 25 minute gap before ending task in Task Manager
2023-12-12 19:15:35.259 +11:00 [#1] (MainForm) Main form attempting to close
2023-12-12 19:15:35.259 +11:00 [#1] (Connection) Connection shutdown scheduled
2023-12-12 19:15:35.259 +11:00 [Connection_Tasks1#5] (ComPort) Closing COM port...
2023-12-12 19:21:35.392 +11:00 [#1] (LogUtil)

Attached Thumbnails

• 

Edited by Rac19, 12 December 2023 - 05:28 AM.

[tjay]

Just did a quick test with CPWI and works fine
So, I will try again with Kstars/Indi options, if some else has done it before, give some tips pls,

It looks like the celestron focuser is supported by indi: https://www.indilib....ct-focuser.html

[Rac19]

You could use a mobile phone as a HotSpot (replicating your home WiFi) and run the ota_update that way. Let the HBG3 connect then use the LCD and button to trigger the update.

 

If you don't have the LCD then using JuiceSSH set to Telnet, port 3000 @ whatever IP your phone gives it. 

I just had success with this.

 

Switch the HBG3 to Direct mode (red switch down), power down the HBG3 and power up, connect you PC or iPad to the HBG3 Direct, use SkyPortal or CPWI to connect to it (via WiFi), configure the  phone's hotspot SSID and pass-phrase (SkyPortal, CPWI settings) and send them to HBG3. Next, power down the HBG3, move the red switch to the Access Point position (up) and power up. The HBG3 will get an IP from the phone hotspot giving it internet access for an OTA update.

Edited by Rac19, 12 December 2023 - 08:46 AM.

[mlord]

No need to power cycle the HBG3 when configuring and switching WiFi modes.

[mlord]

CPWI and HBG3 Bluetooth:

 

Windows Bluetooth, this may be of interest.

CPWI connecting over Bluetooth used to work fine, even earlier this fall.  But I have tried it recently, with the current version of CPWI on MS-Win11, and it no longer works for me.  Once in a while perhaps, but hardly ever now.  When it fails, no connection is even attempted to the HBG3, so this is not something that I can do anything about.  It's a CPWI and/or MS-Windows bug.  It may still work fine for others with different PC hardware, perhaps.

 

I can connect successfully every time from PuTTY on Ms-Windows to the Bluetooth COM ports though, and see the binary AUX bus packets flowing.  Ditto for connecting with my more usual systems that all run Linux.  So it all still works from the HBG3 end.  Just not from CPWI.

 

Cheers
 

Edited by mlord, 12 December 2023 - 02:29 PM.

[mlord]

How to Hook Up an FRAM Module:

 

I purchased a fram module cannot find a schematic or hook up diagram in the forum threads.

At the top right of the desktop version of this web page, is a "Search... this Topic" box.  I just now typed "fram" into that box, and clicked on the search icon there.  It returned LOTS of results.  So try to use the Search, please.  It's not that difficult.

 

The results returned there tell us that the FRAM devices supported with the HBG3 use the I2C bus for connection.  Google I2C if unfamiliar with it.  It stands for Inter Integrated-circuit Communications bus, and is normally shortened to IIC, or the unfortunately more common/geeky name:  I2C (meaning, two "I" followed by "C").

 

On the HBG3 purple PCB, there is at least one set of four connection holes for I2C.  The newest PCB revisions have three sets of those four holes, including a set designated for the I2C OLED display. 

 

I2C is a 4-wire BUS.  Meaning that everything that uses I2C is wired to the exact same four connections, wired together in parallel with everything else.  Just like how the Celestron AUX BUS works.   I2C has Ground (GND), VCC (3.3V), Serial-Clock (SCL), and Serial-Data (SDA).  Those are the four connections.  Every I2C device has the same four connections.  Just hook them up.

 

 

Each I2C device has a unique bus "address".   The HBG3 expects FRAM to use 0x50 as the address.  So if the device has jumpers or pins for selecting an address, set it for 0x50, which is normally the default for FRAM, and is the default for the module pictured above.  The A0,A1,A2 lines on that module could be pulled up/down to change the address, but that is not needed here.  The WP (Write-Protect) line is also not used here.

 

On the HBG3, there are already at least two I2C devices wired up in most cases:  The Nunchuck, and the OLED display.  More can be added, up to a point.  The Search results will also find a discussion of that.

 

When an FRAM module is added to the HBG3 set-up, it currently gets used (only) for saving the Stepper Motor (Focus) position in near real-time, so that it can be remembered from session to session.  This enables proper use of "Calibration" limits on the motor, something that is essential for remote unattended use of a Focus Motor.

 

Cheers

Edited by mlord, 12 December 2023 - 02:01 PM.

[mlord]

3D-Printable Stepper Motor Focuser Designs:

 

In the attached picture, I'd like to 3d print this focuser bracket.  Is the stl or obj file available for this print?

That was also my question at one point.  So I sent a message to user dewo , the person who originally posted that photo earlier in this very thread.  After a few months, he eventually replied to me with a link to his design files.

 

Here's the link dewo sent me:  https://www.tinkerca...BE32jSeLv42VshM

You'll have to have/create a (free) TinkerCAD account to view/use the files.

 

I believe someone else here has taken those files and improved upon them, but not posted their improved version here (yet).

 

There is another similarly good version here though:  https://www.thingive...m/thing:3607326  I think I might even like that one better, because it is so simple, and allows for easy switch back to manual focus.

Edited by mlord, 12 December 2023 - 01:28 PM.

[scopewizard]

CPWI and HBG3 Bluetooth:

 

CPWI connecting over Bluetooth used to work fine, even earlier this fall.  But I have tried it recently, with the current version of CPWI on MS-Win11, and it no longer works for me.  Once in a while perhaps, but hardly ever now.  When it fails, no connection is even attempted to the HBG3, so this is not something that I can do anything about.  It's a CPWI and/or MS-Windows bug.

 

I can connect successfully every time from PuTTY on Ms-Windows to the Bluetooth COM ports though, and see the binary AUX bus packets flowing.  Ditto for connecting with my more usual systems that all run Linux.  So it all still works from the HBG3 end.  Just not from CPWI.

 

Cheers
 

I have 3 x HBG3 with 8.13. All connect just fine with CPWI 2.5.4.

I have just installed CPWI 2.5.5 beta on my minipc Win11 which is up to date. I will try with HBG3 8.13 and 8.25.

I will report if any issue connecting with BT.

 

I use HBG3 BT to connect my CGX mount to my minipc (CPWI) which sit on my scope.

The minipc wifi (5ghz) is used to RDP to my laptop via home router.

 

I have never had an issue with this setup.

[mlord]

I have 3 x HBG3 with 8.13. All connect just fine with CPWI 2.5.4.

I have just installed CPWI 2.5.5 beta on my minipc Win11 which is up to date. I will try with HBG3 8.13 and 8.25.

..

I have never had an issue with this setup.

Great to hear!  So not a complete write-off of my efforts to provide it.

 

Perhaps it has something to do with the type/version of Bluetooth transceiver in the PC, then.  My 2023 AMD Ryzen Mini-PC here with up-to-date Win11-Pro only gets CPWI connecting once in a blue moon or so now.  Very modern Bluetooth chip there though.

 

My older Win10 Dell laptop used to work fine with it, but didn't when I briefly tried it the other day.  Will try again.  I also have an older USB Bluetooth transceiver, which Win11 does not support.  Win10 supports it, so perhaps I'll try that too.

 

EDIT: No luck for me with v8.13, or with the beta versions of CPWI up to 2.5.5-beta4.  They DO actually "connect", send two bytes for a Nexstar+ hand-controller, and then disconnect again..  I'll play with that handshake and see if anything can be done.

 

The Celestron Focuser Utility connects just fine over the Bluetooth connection though, and works the focus motor without issue.
 

Edited by mlord, 12 December 2023 - 02:55 PM.