Firmware version v8.31 of the Arduino ESP32 source code for this project is now available:
hbg3.ino.v8.31.txt
Cheers
with this version Focus is only increasing.
Cheers
Martin
Posted 01 January 2024 - 08:59 AM
Firmware version v8.31 of the Arduino ESP32 source code for this project is now available:
hbg3.ino.v8.31.txt
Cheers
with this version Focus is only increasing.
Cheers
Martin
Posted 01 January 2024 - 10:06 AM
Version v8.32 of the Arduino ESP32 firmware is now available:
hbg3.ino.v8.32.txt 295.05KB
26 downloads
Anyone using a Stepper Motor with v8.31 will want to update immediately to fix a one-direction-only bug there.
Cheers
Posted 01 January 2024 - 10:10 AM
There are now test binaries available for both the HBG3 and AIO projects, using (much) faster I2C speeds for the OLED and FRAM modules. To help us all and try out the test release, change one setting on the HBG3:
set ota.update.path /hbg3/testing.bin
save
reset
ota_update
Or on the AIO, use this instead:
set ota.update.path /hbg3/aio-testing.bin
save
reset
ota_update
Please give it a whirl and post your findings here. And don't forget to restore the original update path afterwards:
set ota.update.path
save
I'm still awaiting feedback on how that change works (or not) for everyone. Otherwise I'll just blindly release it. So please give it a try ASAP if you can. That's how this "Open Source" stuff works -- everyone pitching in to do their bit!
Edited by mlord, 01 January 2024 - 10:11 AM.
Posted 01 January 2024 - 12:46 PM
Downloading v8.32+ now...done.
OLED only on mine and I can't tell the difference. Have filmed to compare.
Posted 01 January 2024 - 12:47 PM
set ota.update.path /hbg3/testing.bin
can you share the sourcecode, having some issues withh OTA Update, loosing connection inbetween
Posted 01 January 2024 - 01:16 PM
can you share the sourcecode, having some issues withh OTA Update, loosing connection inbetween
The full source code is (always) on https://rtr.ca/hbg3/ as well as in the HBG3_Arduino archives there too.
https://rtr.ca/hbg3/hbg3.ino.txt
Posted 01 January 2024 - 01:18 PM
Downloading v8.32+ now...done.
OLED only on mine and I can't tell the difference. Have filmed to compare.
I'm mostly interested in WiFi and/or Bluetooth stability. It's fine here for me, but then.. most things usually are!
Posted 01 January 2024 - 02:24 PM
The full source code is (always) on https://rtr.ca/hbg3/ as well as in the HBG3_Arduino archives there too.
sorry my bad, I was reffering to the testing source code, I tried with .ino and .txt but no succes
Posted 01 January 2024 - 02:40 PM
I'm mostly interested in WiFi and/or Bluetooth stability. It's fine here for me, but then.. most things usually are!
Sorry, I didn't see the request for comms testing. Is there a list for the testers to run through, as well as finding their own items to add to the list?
Posted 01 January 2024 - 02:45 PM
See the original post here: https://www.cloudyni...5#entry13164086
"One thing I would like to someday figure out, is why running the I2C at 400KHz causes WiFi/Bluetooth to stop working.."
So I am mainly interested in whether the WiFi or Bluetooth actually still work normally with the new faster I2C speeds. So whatever way one normally would use WiFi/Bluetooth is what would be good to do.
Because.. I am going to release this blindly in the near future, after which my hope is that WiFi/BT will continue working for others as well as it does for me here. If simply releasing it is the only way to get people to help with testing, then so be it.
Edited by mlord, 01 January 2024 - 02:47 PM.
Posted 01 January 2024 - 05:55 PM
Update: working in both Direct and 'Use Access Point' mode this morning, after reseating the RJ12 cable.
Edited by Astro Andy, 02 January 2024 - 03:21 AM.
Posted 01 January 2024 - 06:41 PM
Edited by Distant Dust, 01 January 2024 - 06:41 PM.
Posted 01 January 2024 - 08:36 PM
Failed connection
- v8.32 and v8.32+ in WiFi client mode (up)
Direct connection works. This is probably a my scope thing but it is odd the Direct works.
Mmm.. Odd one. I'll call that report "inconclusive", because so many people report those symptoms which can mean all sorts of things, or nothing at all. I find it somewhat common for a first-connect attempt to fail like that. Just clicking on "Connect" again normally works, sometimes a third attempt is needed.
I think this has to do with the delays in establishing the connection, and the app times out early before things are ready.
Cheers
Posted 01 January 2024 - 10:24 PM
Posted 03 January 2024 - 06:12 AM
Please give it a whirl and post your findings here. And don't forget to restore the original update path afterwards:
set ota.update.path
save
Hi Mark, I have tested the 8.32+:
CPWI (Access Point): OK
CPWI (Direct Connect): OK
SkyPortal on Android (tablet) - WiFi - Direct Connect: OK
SkySafari on Android (tablet) - WiFi - Direct Connect: OK
SkyPortal on Android (tablet) - BT - Communication Bridge Pro: OK
SkySafari on Android (tablet) - BT - Communication Bridge Pro: OK
SkyPortal on Android (tablet) - WiFi - AP: OK
SkySafari on Android (tablet) - WiFi - AP: OK
Cheers
Posted 03 January 2024 - 09:58 AM
Firmware version v8.33 is now available for this project:
Main file:
hbg3.ino.v8.33.txt 295.66KB
25 downloads
Ethernet:
eth.h.txt 17.75KB
14 downloads (optional)
The cheap and plentiful EJC28J60 Ethernet modules can now be used with the HBG3, and also again now with the All-In-One (AIO) project. These have the advantage of NOT jamming GPS signals, but have smaller buffers and place more of a burden on the CPUs -- fine for most purposes with the ESP32 though.
The I2C speeds for OLED and FRAM are now much faster, giving quicker updates, and freeing up CPU time for other tasks.
The Ethernet and EthernetENC libraries have been further patched to return the detected chip revisions. So if building from source code, please re-download the newly updated pre-patched / pre-configured HBG3_Arduino archives from the links near the bottom of https://rtr.ca/hbg3/
Binaries are also available for both projects in all of the usual places.
Go forth and update!
Edited by mlord, 03 January 2024 - 02:31 PM.
Posted 03 January 2024 - 02:20 PM
To help us all and try out the test release, change one setting on the HBG3:
set ota.update.path /hbg3/testing.bin
save
reset
ota_update
Please give it a whirl and post your findings here. And don't forget to restore the original update path afterwards:
tested and the result is:
18:50:20.583 -> WiFi connected to access@16, IP address: 192.168.1.140
18:50:20.637 -> 000005500 auxbus_rx: auxtest: 3b 05 10 e2 fe 05 0e f8 [AZM -> HBG3 ] Version: 5.14
18:50:21.802 -> 000006688 w2000 Connected
18:50:22.442 -> routing[4]: SW (20) on w2000_rx
18:50:54.611 -> w2000 Timed-out
18:50:54.611 -> routing[4]: SW (20) removed from w2000_rx
18:50:54.611 -> 000039486 w2000 Disconnected
18:51:02.577 -> 000047465 w2000 Connected
18:51:02.624 -> routing[4]: SW (20) on w2000_rx
18:51:36.015 -> w2000 Timed-out
18:51:36.015 -> routing[4]: SW (20) removed from w2000_rx
18:51:36.015 -> 000080897 w2000 Disconnected
18:51:59.052 -> 000103941 w2000 Connected
18:51:59.052 -> routing[4]: SW (20) on w2000_rx
if my mobile turns out its display, scope ist immediatly disconnected. I wake up my mobile and wifi ist connected again
that doesn't influence skyportal...
Edited by SieglindeFestkochend, 03 January 2024 - 02:28 PM.
Posted 03 January 2024 - 03:17 PM
Yes, that's how mobile phones work with SkyPortal. Best to tell your phone to NOT try to power-save while running SkyPortal. And enable running it in "The Background" too.
Cheers
Okay, thanks for this info.
Posted 04 January 2024 - 01:27 AM
Hello,
On firmware 8.32 and 8.33, I'm getting the following.
001884332 w2000_rx: 3b 04 17 20 1a 00 ab [DEW -> SW ]
evo_wifi OFF
001887716 auxbus_tx: 3b 04 e2 b5 10 00 55 [HBG3 -> EVWIFI] SET_EVO_WIFI
001887732 auxbus_rx: 3b 03 b5 e2 10 56 [EVWIFI -> HBG3 ]
w2000 Timed-out
routing[4]: SW (20) removed from w2000_rx
001888352 w2000 Disconnected
001889667 w2000 Connected
routing[4]: SW (20) on w2000_rx
001889671 dew_rx: 3b 03 20 17 10 b6 [SW -> DEW ] DEW_GET_NUM_PORTS
When connected to CPWI, I loose connection to the mount while retaining connection to focus and dew control. I finished assembling my hbg3 a few days ago so I don't know if this is hardware or firmware related. It appears evo_wifi is repeatedly switched ON and OFF and w2000 is disconnected afterwards.
Edited by eleven, 04 January 2024 - 01:28 AM.
Posted 04 January 2024 - 05:35 AM
When connected to CPWI, I loose connection to the mount while retaining connection to focus and dew control. I finished assembling my hbg3 a few days ago so I don't know if this is hardware or firmware related.
Not enough information to do anything with.
Posted 04 January 2024 - 10:45 AM
mlord, how can I get a copy firmware version 8.3?
Posted 04 January 2024 - 12:08 PM
mlord, how can I get a copy firmware version 8.3?
Do you mean v8.3 or v8.33 (the current)?
V8.3 would be in the full sketch archive in the portable Arduino IDE on mlords rtr.ca/hbg3 site.
Posted 04 January 2024 - 05:27 PM
Hi Astro Andy,
I meant the older v8.3 from back in August 2023, and thank you for the info.
Posted 04 January 2024 - 05:37 PM
Firmware version v8.34 is now available for this project:
hbg3.ino.v8.34.txt 295.94KB
23 downloads
The HBG3 already included protocol tweaks to enable the latest firmware of the Nexstar-GPS mount to work over WiFi/BT with SkyPortal/SkySafari, but older firmware on that mount needs a slightly different tweak. So.. here it is! Thanks to Carson H. for helping with this.
Binaries and stuff are available now in all of the usual places.
Cheers
Posted 05 January 2024 - 07:59 AM
When connected to CPWI, I loose connection to the mount while retaining connection to focus and dew control.
You provided nearly no information to go on. If "focus" means a Celestron Focus Motor, and/or "Dew" means a Celestron 2X/4X Dew controller, then most likely this is an issue with the mount's AUX ports not coping with many things connected. Eg. see this almost identical situation posted on CN just a few days ago: https://www.cloudyni...er-connections/
So try rearranging which items are connected to which AUX ports.
Or add a Relay PCB to your HBG3, converting it into an HBG3-Relay, and use the Relay ports for Celestron accessories instead of plugging them into the mount's AUX ports. That usually cures any problems like this.
I am out of regular HBG3 PCBs at the moment, but do still have lots of Relay PCBs.
Edited by mlord, 05 January 2024 - 08:01 AM.
![]() Cloudy Nights LLC Cloudy Nights Sponsor: Astronomics |