2029 replies to this topic

[mlord]

So the questions are:

 

1. Does the hand-controller still work?

2. Does the HBG3 work (THREE BLUE BLINKS) when no hand-controller or other devices are connected?

 

If the HBG3 does not work in isolation (#2 above), then it would appear that the BUSY line circuit within the mount may now be b0rked.  The hand-controller itself appears to ignore the BUSY line, so it may work regardless.

[cyberduck]

Now, check the voltage on D32 of the ESP32.  It should read +3.3V (HIGH) at idle.   If D32 reads 0.0V (LOW), then it is broken.  We can work around that if need be, re-routing a different GPIO for BUSYOUT, and changing the firmware to match.  Wait for further advice if this appears to be the case!

D32 shows +3.3V at idle, indicating that it works as expected. Not connected to the mount.

 

If D32 correctly shows +3.3V, then something else is wrong.  So measure the voltage on D35 (BUSYIN) now.  This should read +2.7V¹ or higher (HIGH) when idle.  If not, then something is wrong either with the 74HCT125 chip, or in the mount itself.  But if it correctly reads 0V (LOW), then the fault is in the ESP32.  And again, this can be worked around.

 

¹ +2.7V with USB power only; +3.3V when powered from the mount.

D35 also shows +3.3V at idle when powered over USB, i.e. not +2.7V as expected. Not connected to the mount.

 

But if it correctly reads 0V (LOW), then the fault is in the ESP32.  And again, this can be worked around.

I redid the measurements, this time with HBG3 connected to the mount (no external power), and got +3.3V for D32 and 0V for D35.

 

Same results for both the #1 and  #2 assemblies.

[cyberduck]

So you could now try that test (powered from the mount, no accessories, no HC) and post the results here.

This may explain how both HBG3 devices suddenly went "bad".

Both #1 and #2 get the following result of the test_auxbus command with the mount CONNECTED to power and ON:

auxbus: Busy  test passed
auxbus: Tx/Rx test passed

[cyberduck]

So the questions are:

 

1. Does the hand-controller still work?

2. Does the HBG3 work (THREE BLUE BLINKS) when no hand-controller or other devices are connected?

 

If the HBG3 does not work in isolation (#2 above), then it would appear that the BUSY line circuit within the mount may now be b0rked.  The hand-controller itself appears to ignore the BUSY line, so it may work regardless.

1. The hand controller works.
2. There is only one blue blink when connecting either of #1 or #2 without any accessories.

However, the BUSY test passes with the mount powered ON (see above)... If the BUSY line circuit on the mount is broken, the test fails to detect it.

Edited by cyberduck, 07 April 2024 - 10:00 AM.

[mlord]

 

1. The hand controller works.

Meaning.. what?  Can it slew the mount?

 

And the HBG3 does NOT get THREE BLUE BLINKS even with the hand-controller not plugged in?

Edited by mlord, 07 April 2024 - 10:26 AM.

[mlord]

(fixed wording in post quoted below):

 

.. measure the voltage on D35 (BUSYIN) now.  This should read +2.7V¹ or higher (HIGH) when idle.  If not, then something is wrong either with the 74HCT125 chip, or in the mount itself.  But if it correctly reads HIGH, then the fault is in the ESP32.  And again, this can be worked around.

 

¹ +2.7V with USB power only; +3.3V when powered from the mount.

So, there's your answer.

Edited by mlord, 07 April 2024 - 10:35 AM.

[mlord]

One can demonstrate that the mount has a fault here, by disconnecting Pin-6 of the AUX bus connection.  The easiest way for me to do it, is to cut off the RJ12 plug from one end of the cable, and then crimp a fresh connector on, but with the 6th wire cut short so that it doesn't get connected.

 

On my cables here, Pin-6 is the right-most pin, when viewed as shown in this photo:

 

 

So, for that cable, I would cut the blue wire, before crimping a new connector onto the other five.  Like this:

 

 

The resulting cable should work with the HBG3.  It does not matter which end of the cable is used where.

Edited by mlord, 07 April 2024 - 10:48 AM.

[mlord]

Another simple thing you should do, is connect it to the mount with the original/unmodified 6-pin cable.

Also connect USB to your computer and open the Serial/Debug monitor.

At the Serial/Debug monitor, hit ENTER, then hit 'v' and ENTER.

It should respond with "verbose=1".

Power-on the mount.

Enter 't' to send a test message.

Now wait a few seconds, and see if there are any "Busy" messages.

Show me what it does.

Edited by mlord, 07 April 2024 - 11:13 AM.

[cyberduck]

Meaning.. what?  Can it slew the mount?

 

And the HBG3 does NOT get THREE BLUE BLINKS even with the hand-controller not plugged in?

I have not done extensive testing, but the HC does not show any error messages, I can go through the alignment and site dialogs, and then yes, the slew controls do work.

 

Yes, the HBG3 does not get THREE BLUE BLINKS only ONE BLUE BLINK with nothing but the HBG3 connected to HC or AUX ports, and nothing connected to the autoguider port.

[mlord]

DO NOT CONNECT THE HBG3 OR ANYTHING ELSE TO ANY PORT LABELLED AS AUTOGUIDER !!!!

 

They are NOT electrically compatible, and that's a great way to fry electronics on both sides!!

Edited by mlord, 07 April 2024 - 11:08 AM.

[cyberduck]

Enter 't' to send a test message.

Now wait a few seconds, and see if there are any "Busy" messages.

Show me what it does.

I do not get any "Busy" messages. The output is:

verbose=1
Sending auxtest
000046772 auxbus_tx: 3b 03 e2 10 fe 0d 					[HBG3   -> AZM   ] GET_VERSION
000046801 auxbus_rx: 00

[cyberduck]

DO NOT CONNECT THE HBG3 OR ANYTHING ELSE TO ANY PORT LABELLED AS AUTOGUIDER !!!!

 

They are NOT electrically compatible, and that's a great way to fry electronics on both sides!!

I know, no worries.

[mlord]

 

I do not get any "Busy" messages.

Ah.  I didn't expect that result.  It doesn't make sense with the other information already gathered.

 

Oh well.

[cyberduck]

Redid the test a couple of times, and if I power on the mount and connect the HBG3 before the automated tests finishes, I do get the BUSY output even after the sequence finishes.

 

Also noticed that if I wait for the test sequence to finish, enter verbose mode, connect the HBG3, and then turn on the mount I get a 

000032010 auxbus_rx: 00

... from the mount without sending a test message.

Edited by cyberduck, 07 April 2024 - 11:43 AM.

[mlord]

Redid the test a couple of times, and if I power on the mount and connect the HBG3 before the automated tests finishes, I do get the BUSY output even after the sequence finishes.

Show me that output?

[mlord]

Don't plug/unplug anything from an HC or AUX port while the mount has power.  It will fry electronics!

 

At this point, my remaining suggestion is this:  https://www.cloudyni...3#entry13375275

If the HBG3 still fails, then the fault is most likely within the HBG3.  Otherwise the mount.

[mlord]

Here is a test version of the firmware source code.  You can use this with the unmodified cable to see if the HBG3 is "seeing" the BUSYIN signal correctly  [removed].  Install it, and before powering on the mount, issue these commands:

 

debug_busy

v

 

See if there's any output once the mount is powered on.  Try a 't' command as well.

Then power-off the mount, plug in the hand-controller (keep the HBG3 plugged in),

and power-on again and see what the output looks like.  Show me.

Edited by mlord, 07 April 2024 - 03:20 PM.

[cyberduck]

Output after booting:

oled.type = Adafruit128x64
focus_set_calibration(0,0): limits=0:60000 focus_calibrated=0
HBG3-v8.43a: AUXRELAY=0 GPS=1 BLOCK_CFM=1 NCHUCK=1 FOCUS=1 OLED=1 DEW=1 FRAM=0 REVERSED=0 ETH=NONE
GPS uart is hwserial1
OLED detected
routing[0]: AZM (10) on auxbus_rx
routing[1]: ALT (11) on auxbus_rx
routing[2]: HBG3 (e2) on auxbus_rx
routing[3]: DUMMY (e3) on auxbus_rx
Stepper driver not detected, Focus Motor emulation disabled.
dew_adc_vref=1.10
SHT3X sensor NOT detected, disabling Dew Heater Control.
000001262 wifi_mode_switch: client_mode
wifi_begin_server_mode
esp32_wifi ON, softAP, ssid=HomeBrew-BB84DC, passkey=
esp32_wifi OFF
GPS detected.
esp32_wifi ON, Client mode
wifi_begin_client_mode:
000002446  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000002453 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000003462  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000003469 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
GPS baud 38400.
agps_send_to_gps: sent 17 bytes
000004478  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000004485 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION

WiFi connected to QMB6-USR, IP address: 192.168.3.129
agps_send_to_gps: sent 32 bytes
000005494  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000005501 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000006510  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000006517 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000007526  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000007533 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000008542  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000008549 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000009558  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000009565 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000010574  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000010581 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000011590  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000011597 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000012606  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000012613 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000013622  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000013629 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000014638  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000014645 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000015654  bus_loop: discard: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION
000015661 auxbus_tx: auxtest: 3b 03 e2 10 fe 0d    [HBG3   -> AZM   ] GET_VERSION

Sending debug_busy and v commands:

debug_busy=1
000024739 auxbus   : Busy
verbose=1

Powering ON the mount:

000036875 auxbus   : Idle

Sending the t command:

Sending auxtest
bus_loop: auxbus_tx is alive
000055004 auxbus_tx: 3b 03 e2 10 fe 0d      [HBG3   -> AZM   ] GET_VERSION
000055033 auxbus_rx: 00

Powering OFF the mount, connecting HC, powering ON again:

000078774 auxbus   : Busy
000078798 auxbus_rx: ff da 08 2b 01 00 00 00 00 00 00 00 00 00 00 00 
                     00 
000084278 auxbus_rx: 00 
000091734 auxbus   : Idle
000098967 auxbus   : Busy
000098971 auxbus   : Idle
000098991 auxbus_rx: 00 
000099320 auxbus   : Busy
000099323 auxbus   : Idle
000099343 auxbus_rx: 00 
000099672 auxbus   : Busy
000099675 auxbus   : Idle
000099695 auxbus_rx: 00 
000100024 auxbus   : Busy
000100028 auxbus   : Idle
000100048 auxbus_rx: 00 
000100376 auxbus   : Busy
000100380 auxbus   : Idle
000100400 auxbus_rx: 00 
ntp_time: 07/04/2024 UTC 17:15:46

EDIT: Corrected output of the 't' test above, it was in the wrong section.

Edited by cyberduck, 07 April 2024 - 12:37 PM.

[cyberduck]

Don't plug/unplug anything from an HC or AUX port while the mount has power.  It will fry electronics!

 

At this point, my remaining suggestion is this:  https://www.cloudyni...3#entry13375275

If the HBG3 still fails, then the fault is most likely within the HBG3.  Otherwise the mount.

Noted.

 

I made a cable with the 6th lead cut short. Tests are... not conclusive. In any case still no THREE BLUE BLINKS.

 

Starting to tire, will make another round a bit later and make sure the output is properly documented. 

Edited by cyberduck, 07 April 2024 - 12:32 PM.

[mlord]

Looks like the UART in the ESP32 is toast.  Not receiving properly.

It should be receiving/displaying all of the stuff from the hand-controller's start-up.

 

Or.. the 74HCT125 chip of the HBG3 is busted on the RX input.  That can happen when hot-plugging things (connecting/disconnecting while the mount is powered on), though usually it's the hand-controller that gets fried.  But the Tx/Rx test would also be failing if the 74HCT125 were the culprit.

Edited by mlord, 07 April 2024 - 12:34 PM.

[mlord]

Looks like the UART in the ESP32 is toast.  Not receiving properly.

Just on the off chance that is true, it may be possible to work around it.

Try this version:    hbg3.ino.txt   308.18KB   11 downloads

 

It swaps the two UARTs for USB and AUX.  Pins remain the same, so no rewiring needed.

See if the THREE BLUE BLINKS happen, and then see if you can get output on the serial/debug port.  Try the "help" command.

[Zoroastro]

Hi Mark,

 

Which pin for the pushbutton on an older HB, instead of the D4?

 

Thanks!

 

 

[mlord]

Which pin for the pushbutton on an older HB, instead of the D4?

The firmware, and wiring, for the HBG3 has remained 100% backward compatible with all PCBs, even the first/second generation ones.  So a push-button switch can be installed between D4 and GND, on any HBG3.

 

The photo above is not a HBG3 though.  But you can use modern HBG3 firmware, and thus an OLED with it, so long as the appropriate settings are used when building the firmware yourself from the hbg3.ino source code.  In which case, the push-button still goes between D4 and GND. 

 

Note that the ESP32 module shown in the photo has "G4", which is another name for D4.

 

The two settings in the source code for older designs are these:

 

#define ORIGINAL_WIFI_PROJECT false  // When true, build firmware for the original WIFI+BT+GPS project, instead of for the HBG3.
#define COOLICK_PCB_PROJECT   false  // When true, build firmware for the Coolick PCB version of the original WIFI+BT+GPS project.

 

Change one of those lines as needed by the hardware you have, and then enjoy the full HBG3 feature set (except for OTA Firmware Updates).

 

Cheers

Edited by mlord, 08 April 2024 - 10:23 AM.

[Zoroastro]

Thanks - indeed I used "HB", not HBG3 . 

 

I can't see the D4 pin, the ESP-WROOM32 pinout is different, hence my doubt about the D4 port. BTW, pity that the OTA doesn't work on the older generations ... ;-)

 

Cheers,

Luca

[mlord]

Thanks - indeed I used "HB", not HBG3 . 

 

I can't see the D4 pin, the ESP-WROOM32 pinout is different, hence my doubt about the D4 port. BTW, pity that the OTA doesn't work on the older generations ... ;-)

See edited post above.  "G4" is "D4". 

 

OTA could work, I'd just have to do regular builds for that variant.