64bit Raspbian beta released too!
Note hardware layout changes - "which doesn't effect anything" - Famous last words - perhaps the USB3/Wifi etc is finally sorted on these boards. Just have to see what the new ones are if any. £24 extra for 4gb isn't that bad !
Cant say I am expecting much improvement until software catches up!
Should also mean 64bit Raspbian is released !
Scottish been around 20+yrs
Alternative to waiting for Sky Watcher prodcuct and as long as you trust the pin outs (which are 99% ok) then you could just but a ready made EQMOD ( name is irrelant in this case it should work with anything) like this $12 inc del to USA
and just splice the mount end and put you own connector wired to the correct pin outs. The spec for EQMOD (e.g. AZEQ6GT) wiring is online on EQMOD so just a case of making sure you have connected to your new pin outs. Plus you of course can get the same cable in the USA
anyway I presume so only a couple of days waiting for delivery!
The SW product is, I am told, a Prolific Chip device where as the above is an FTDI which means no clash on USB ports (FTDI have a unique serial number) an in Linux Udev can be used to make that device a perm mount connection with appropriate name in /dev.
"The AZ-GTI driver was already mentioned in this thread." - yes I know (KNRO * 2,me once) ) but your answer was unclear if you had tried it or not Yes you did say about some annoying bits of Alt-GTI which seems to imply you have but I wasn't clear.
Plus the AZ-GTI is going to be nearer what you are looking for than Synscan or EQMOD especially if you are going to write a "new" Indi driver .
Just saying Last time promise
Just remembered this on SGL -
- no coding involved
Silly question but have you tried the AZ-GTI device which has Wifi support built in and as its based on the EQMOD which will talk to MOST SW mount motors directly so is using the corrent "SW protocol" already. If nothing else its not a bad place to start looking at the coding
Forgive me in saying SW aren't going to create new boards/motor protocols for the newer GoTo Dobs as it doesn't make commercial sense - IMHO.
If nothing else no wiring (get it wrong and its bye bye board - e.g. 12v onto 3.3v = bang) - and do not trust wiring colours (color) - I have found that they dont match across the same cables - the pins do so follow the pin outs IMO.
But if you love "fiddling" thats great and good luck
If you are an ex programmer than an alternative is to use an ESP32/Ardunio sketch to enable serial to UDP convertion (just plug in the ESP32(usb version) creates a serial port and the coding in the ESP32 can pick up the serial data and do transparant convertion to UDP (and visa versa). It works but ESP Wifi signal isn't the strongest IMO - but it works. If you google something like " transparanet serial to UDP arduino " there is a basic sketch out there but it does need mods to enable it to work with SW UDP (mainly port numbers!)
Here's your starter github.com/roboremo/ESP8266-WiFi-UART-Bridge
Just a thought
If you dont know already maybe this will help
And maybe with your device and Astroberry HOTPLUG doesn't work - but it does on std Raspbian. Anyway it appears you might have to edit the devices file.
"Regarding hot-plugging GPS - it works for USB devices but does not work with hardware serial port (/dev/ttyACM0). To use hardware serial port you need to either edit /etc/default/gpsd and set DEVICES or you can leave the file alone and run: sudo gpsdctl add /dev/ttyACM0
To make the second approach persistent you can add gpsdctl add /dev/ttyACM0 to /etc/rc.local "
Tried rebooting a number of time and removing and reinserting Ublox (which normally works) - GPSMON just hangs even though systemctl said gpspanel and gpsd services were active. Noticed that GPSMON in my case showed JSON XXXXXXXXX where hardware device name is normally
So shurdown - disconnect power lead,waited 30 secs ,started PI and see attached. Flaky IMHO hence I just set the things(Time,Location) manually - I dont get enough clear skies time !
Other thing to check is power - Are you fully connected with all your devices and are you using a powered Hub - guessing really!
I would bring it up with @Radek - with logs etc see if he can see anything.
But mine shows - see attached
But agree its flaky - hardware/software or both.
Another possible idea especially for RTC and power management - read this thepihut.com/products/wittypi3-rtc-power...ent-for-raspberry-pi .
No GPS though