John Robison replied to the topic 'Polar Alignment issue with EKOS and Astrometry' in the forum. 6 hours 41 minutes ago

Hello El Corazon,

I noticed errors in INDI with the QHY driver for PoleMaster. I an thinking something is up with either a rule or the driver.

Read More...

John Robison replied to the topic 'Polar Alignment issue with EKOS and Astrometry' in the forum. 6 hours 44 minutes ago

Hello,

Thank you for your reply. Yes, I have ensured that Astrometry zone files are downloaded. Astrometry confirms their presence. I have no missing files. I have install ASTAP. Setting the Pole is my biggest problem. I am going to seek the issue with the package update for QHY. The rules file looks to be part of the problem. I looking for the correlation. At the present, log files appear to be lost lately. I cannot find my logs from last night. I created CCD and INDI logs.

Read More...

John Robison replied to the topic 'Polar Alignment issue with EKOS and Astrometry' in the forum. 18 hours 15 minutes ago

Hello,

Thank you for this reply. In this thread, it was said, the FOV is calculated. Ok. EKOS says 88’ x 70’.

I went to the offered FOV calculator and plotted three options specific to my equipment. All where significantly less than the lower limits of FOV in EKOS. I accepted the provided EKOS value

This leaves me with do I pick a band in Astrometry of guess at a FOV? The PoleMaster is fixed and explicitly stated by QHY. This value is not accepted by EKOS. PoleMaster_qt has no problems with the PoleMaster device. If only, PoleMaster_qt and EKOS were aware of each other then polar Alignment is one issue.

I am then thinking about plate solving there after. I think the INDI driver might not be getting updated by Nightly Builds. I saw an error message about 85_camera_qhy.rules the last update. Clear sky events are a long shot for a while. These errors generated during solving with the PoleMaster are the root of the problem, possibly? ERROR getframe -1 is many during the session.

I am looking at ASTAP as an alternative.

Read More...

John Robison replied to the topic 'Polar Alignment issue with EKOS and Astrometry' in the forum. yesterday

Hello,

Finally, a clear night was in my area. I ensured the nightly build was installed on my PI for ZWO and QHY products. All systems were a go. EKOS was communicating well with all of the devices. I went to polar alignment and this error started popping up in KSTARS bar. ERROR GETFRAME -1 with Polemaster. Mutilple errors showed up in the console of PoleMaster.

Now, the kicker... I set up Astrometry to be Offline. I had the PoleMaster to be the tool of choice. Capture to Solving was 3 secs and a beautiful shot of Polaris. 3 minutes later, Solver timed out. Second attempt. Same result. Astro was the plate solver. I am puzzled. What is preventing Plate Solver for Polar Alignment from not resolving. Every Astrometry file is installed on this system. It should find where it is. GPSD is working. INDI is working. But, Polar Alignment is not.

Read More...

John Robison replied to the topic 'Polar Alignment issue with EKOS and Astrometry' in the forum. 2 weeks ago

Hello,

Finally, a clear night has occurred and I was ready. Unfortunately, PolarAlign with EKOS failed. This time the issue is with the QHYCCD driver. I can confirm the QHYCCD driver for PoleMaster is aborting Solver. There is a direct correlation between the -1 messages and aborted Solver messages. I will send a portion of INDI session with the error. I aborted the session as I could not set the alignment.

PoleMaster works fine outside of EKOS With PoleMaster QT. Under EKOS the QHYCCD driver immediately throws an error when getting an image.

Read More...

John Robison replied to the topic 'vap0 and 19.04.2' in the forum. 4 weeks ago

Update

After multiple effort attempts, I have come to the conclusion that vap0 is a shim created by some process. Hostapd is a version 3.9. IEEE80211N optioon is no longer required.

I have wlan0 working. I am seeking the process used to create AstroBerry as a VPN server. The inferface vap0 has to be installed with the Wireless to get VNC to communicate with Astroberry. I have openVPN installed. I am looking for the script to create the vap0 interface.

Thank you.

Read More...

John Robison replied to the topic 'vap0 and 19.04.2' in the forum. 1 month ago

Hello,

Finally, I have the smoking gun. Unmasking hostapd, allowed me to look under the covers. It is a mess.

Oct 18 17:04:09 astroberry.local systemd[1]: hostapd.service: Service RestartSec=2s expired, scheduling restart.
Oct 18 17:04:09 astroberry.local systemd[1]: hostapd.service: Scheduled restart job, restart counter is at 20.
-- Automatic restarting of the unit hostapd.service has been scheduled, as the result for
-- Subject: A stop job for unit hostapd.service has finished
-- A stop job for unit hostapd.service has finished.
-- Subject: A start job for unit hostapd.service has begun execution
-- A start job for unit hostapd.service has begun execution.
Oct 18 17:04:09 astroberry.local hostapd[7987]: Configuration file: /etc/hostapd/hostapd.conf
Oct 18 17:04:09 astroberry.local hostapd[7987]: Could not read interface vap0 flags: No such device
Oct 18 17:04:09 astroberry.local hostapd[7987]: nl80211: Driver does not support authentication/association or connect commands
Oct 18 17:04:09 astroberry.local hostapd[7987]: nl80211: deinit ifname=vap0 disabled_11b_rates=0
Oct 18 17:04:09 astroberry.local hostapd[7987]: Could not read interface vap0 flags: No such device
Oct 18 17:04:09 astroberry.local hostapd[7987]: nl80211 driver initialization failed.
Oct 18 17:04:09 astroberry.local hostapd[7987]: vap0: interface state UNINITIALIZED->DISABLED
Oct 18 17:04:09 astroberry.local hostapd[7987]: vap0: AP-DISABLED
Oct 18 17:04:09 astroberry.local hostapd[7987]: hostapd_free_hapd_data: Interface vap0 wasn't started
Oct 18 17:04:09 astroberry.local systemd[1]: hostapd.service: Control process exited, code=exited, status=1/FAILURE
-- An ExecStart= process belonging to unit hostapd.service has exited.
Oct 18 17:04:09 astroberry.local systemd[1]: hostapd.service: Failed with result 'exit-code'.
-- The unit hostapd.service has entered the 'failed' state with result 'exit-code'.
-- Subject: A start job for unit hostapd.service has failed
-- A start job for unit hostapd.service has finished with a failure.


Using the tool scripts does not change this issue.

Read More...

John Robison replied to the topic 'vap0 and 19.04.2' in the forum. 1 month ago

Hello,

Apparently, the wireless device appears down. Here is an excerpt from "journalctl -e".

astroberry@astroberry:~$ journalctl -e | grep "vap0"
Oct 18 16:00:42 astroberry.local ifup[597]: Cannot find device "vap0"
Oct 18 16:00:42 astroberry.local ifup[597]: ifup: failed to bring up vap0
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1409] ifupdown: guessed connection type (vap0) = 802-3-ethernet
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1411] ifupdown: update_connection_setting_from_if_block: name:vap0, type:802-3-ethernet, id:Ifupdown (vap0), uuid: b77903f0-c28d-8b04-0e87-b3cba551dbae
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1475] ifupdown: guessed connection type (vap0) = 802-11-wireless
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1477] ifupdown: update_connection_setting_from_if_block: name:vap0, type:802-11-wireless, id:Ifupdown (vap0), uuid: b77903f0-c28d-8b04-0e87-b3cba551dbae
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1477] ifupdown: update wireless settings (vap0).
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1483] ifupdown: update wireless security settings (vap0).

This has me stumped. To me vap0 is not tied to a hardware device. The hardware device tie-in is defined in hostapd. So, vap0 is not getting linked to a device. Syslog and journalctl are not finding an hostapd messages. More digging to come.

Read More...

John Robison replied to the topic 'EKOS is missing buttons in the lastest release' in the forum. 1 month ago

Hello,

In this thread, alacant’s picture of EKOS shows the same thing as what I see. In the upper right corner of the Child Window is a red X. No accompanying _ or [] as part of Linux window dressings are there. Clicking on the Title bar with a mouse shows the window functions minimize and maximize are disabled.

One final data point to consider is VNC. The mouse in VNC is just a one button mouse. The problems were compounded trying the juggle the INDI equipment and getting EKOS to polar align. Cameras and INDI appeared to be fighting. I wanted to see the fight to fix it. I could not get past EKOS in VNC.

Read More...

John Robison replied to the topic 'vap0 and 19.04.2' in the forum. 1 month ago

Hello,

Nearing an end. Which, we will see tomorrow.

-- An ExecStart= process belonging to unit dnsmasq.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 2.
Oct 17 22:23:35 astroberry.local dnsmasq[2435]: FAILED to start up
Oct 17 22:23:35 astroberry.local systemd[1]: dnsmasq.service: Failed with result
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: www.ubuntu.com/support
--
-- The unit dnsmasq.service has entered the 'failed' state with result 'exit-cod
Oct 17 22:23:35 astroberry.local systemd[1]: Failed to start dnsmasq - A lightwe
-- Subject: A start job for unit dnsmasq.service has failed
-- Defined-By: systemd
-- Support: www.ubuntu.com/support
--
-- A start job for unit dnsmasq.service has finished with a failure.
--
-- The job identifier is 1366 and the job result is failed.
Oct 17 22:23:35 astroberry.local sudo[2297]: pam_unix(sudo:session): session clo

Read More...

John Robison replied to the topic 'vap0 and 19.04.2' in the forum. 1 month ago

Hello,

Unwrapping an onion is tough. Ok. Now, wpa _supplicant is showing up in the logs. However, interfaces has some problems.

Oct 17 19:41:46 astroberry wpa_supplicant[480]: Successfully initialized wpa_supplicant
Oct 17 20:16:25 astroberry wpa_supplicant[480]: Successfully initialized wpa_supplicant
Oct 17 20:47:37 astroberry wpa_supplicant[506]: Successfully initialized wpa_supplicant
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: Successfully initialized wpa_supplicant
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: Could not read interface wlan0 flags: No such device
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: nl80211: Driver does not support authentication/association or connect commands
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: Could not read interface wlan0 flags: No such device
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: rfkill: Cannot get wiphy information
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: Could not read interface wlan0 flags: No such device
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: WEXT: Could not set interface 'wlan0' UP
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: wlan0: Failed to initialize driver interface
Oct 17 21:23:37 astroberry wpa_supplicant[458]: Successfully initialized wpa_supplicant
Oct 17 21:23:37 astroberry wpa_supplicant[478]: Successfully initialized wpa_supplicant

I removed wlan0 as the device is not on my RPI3B+. I will see if this clears up these errors. I jost copied what as verified as working Now it isn't.

Read More...

John Robison replied to the topic 'vap0 and 19.04.2' in the forum. 1 month ago

Hello,

With the syntax error corrected, the dnsmasq still has problems with vap0.

stroberry@astroberry:~$ systemctl status dnsmasq.service
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset:
Active: failed (Result: exit-code) since Thu 2019-10-17 20:48:38 EDT; 10s ago
Process: 1643 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUC
Process: 1644 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=

Oct 17 20:48:56 astroberry dnsmasq[1798]: dnsmasq: syntax check OK.
Oct 17 20:48:56 astroberry dnsmasq[1799]: dnsmasq: unknown interface vap0
Oct 17 20:48:56 astroberry dnsmasq[1799]: unknown interface vap0
Oct 17 20:48:56 astroberry dnsmasq[1799]: FAILED to start up
Oct 17 20:48:56 astroberry systemd[1]: dnsmasq.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Oct 17 20:48:56 astroberry systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Oct 17 20:48:56 astroberry systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.

ok, This might be the smoking gun.

Oct 17 20:47:38 astroberry NetworkManager[505]: <info> [1571359658.0063] ifupdown: interface-parser: parsing file /etc/network/interfaces
Oct 17 20:47:38 astroberry NetworkManager[505]: <info> [1571359658.0065] ifupdown: interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d
Oct 17 20:47:38 astroberry NetworkManager[505]: <info> [1571359658.0067] ifupdown: interface-parser: finished parsing file /etc/network/interfaces
Oct 17 20:47:38 astroberry NetworkManager[505]: <info> [1571359658.0156] ifupdown: No dns-nameserver configured in /etc/network/interfaces
Oct 17 20:47:38 astroberry NetworkManager[505]: <warn> [1571359658.0172] ifupdown: invalid connection read from /etc/network/interfaces: 802-11-wireless.ssid: property is missing

Something must be explicitly stated. This would mean some of the stated solutions will need to be updated to 19.04.2 standards. However, the wpaconf file has those details in it. Somehow the conf file may not be parsed properly. This has specific details about vlan0. Uggh. change happens to all good things.

This says that wpa_supplicant was initiated. However, /var/run/wpa_supplicant no longer exists. I guess something got whacked during an upgrade.

astroberry wpa_supplicant[506]: Successfully initialized wpa_supplicant

astroberry@astroberry:~$ sudo /var/run/wpa_supplicant GROUP=netdev
[sudo] password for astroberry:
env: '/var/run/wpa_supplicant': No such file or directory
astroberry@astroberry:~$ ls /var/run/wpa_supplicant
ls: cannot access '/var/run/wpa_supplicant': No such file or directory
astroberry@astroberry:~$ ls /var/run/
NetworkManager dhcpcd.unpriv.sock openvpn-client sshd
agetty.reload dnsmasq openvpn-server sshd.pid
alsa gpsd.sock plymouth sudo
avahi-daemon initctl resolvconf systemd
avahi-dnsconfd.pid lightdm rsyslogd.pid thd.socket
console-setup lightdm.pid samba tmpfiles.d
crond.pid lock sendsigs.omit.d udev
crond.reboot log shm udisks2
cups mount snapd-snap.socket user
dbus network snapd.socket utmp
dhcpcd.pid nginx.pid speech-dispatcher uuidd
dhcpcd.sock openvpn spice-vdagentd xtables.lock
astroberry@astroberry:~$

Where would someone get the wpa_supplicant?

Read More...

John Robison created a new topic ' vap0 and 19.04.2' in the forum. 1 month ago

Hello,

Looks vap0 is no longer working. I started from check-wlanconn.

Virtual Access Point STARTED
astroberry@astroberry:~$ sudo /usr/local/bin/astroberry_wireless
Checking if connected to AP.......... Not connected
Trying to connect to known AP
command failed: No such device (-19)
Starting Virtual Access Point
command failed: No such device (-19)
SIOCSIFADDR: No such device
vap0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
vap0: ERROR while getting interface flags: No such device
vap0: ERROR while getting interface flags: No such device
Configuration file: /etc/hostapd/hostapd.conf
Could not read interface vap0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=vap0 disabled_11b_rates=0
Could not read interface vap0 flags: No such device
nl80211 driver initialization failed.
vap0: interface state UNINITIALIZED->DISABLED
vap0: AP-DISABLED
hostapd_free_hapd_data: Interface vap0 wasn't started
Job for dnsmasq.service failed because the control process exited with error code.
See "systemctl status dnsmasq.service" and "journalctl -xe" for details.
Virtual Access Point READY

I was just starting to use new settings. I normalized all conf files and noting changed except for dnsmasq.conf. The interface=vap0 was missing after an update. I added it back and restarted. I still do not have wireless.

astroberry@astroberry:~$ systemctl status dnsmasq.service
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset:
Active: failed (Result: exit-code) since Thu 2019-10-17 20:34:50 EDT; 7min ag
Process: 2199 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=1/FAI

Oct 17 20:34:50 astroberry.local systemd[1]: Starting dnsmasq - A lightweight DH
Oct 17 20:34:50 astroberry.local dnsmasq[2199]: dnsmasq: bad option at line 667
Oct 17 20:34:50 astroberry.local dnsmasq[2199]: bad option at line 667 of /etc/d
Oct 17 20:34:50 astroberry.local dnsmasq[2199]: FAILED to start up
Oct 17 20:34:50 astroberry.local systemd[1]: dnsmasq.service: Control process ex
Oct 17 20:34:50 astroberry.local systemd[1]: dnsmasq.service: Failed with result
Oct 17 20:34:50 astroberry.local systemd[1]: Failed to start dnsmasq - A lightwe

I am still investigating the mashup of the latest Ubuntu-mate update. I forgot to add the "=" sign.

Read More...

John Robison replied to the topic 'EKOS is missing buttons in the lastest release' in the forum. 1 month ago

Hello Ihoujin,

Thank you for your gracious offer. Remote access is not possible. However, I never lost the INDI option. I have an RPI 3B with AstroBerry installed. This was my first platform with RPI. It is fixated on 16.04, The EKOS applet window does not have access to Minimize and Maximize. I must have been mistaken to think that EKOS did have Minimize and Mazimize buttons. Apparently, EKOS for Pi and AstroBerry never did.

Comparing the 3B and 3B+ with each other, I see a difference. Under the 3B, EKOS opens INDI infront of EKOS with the option checked or unchecked. Under 3B+, EKOS opens INDI behind itself. This is the rub. In fact, if I minimize INDI and then Mazimize, EKOS is on top. I could not check INDI for errors or messages on hardware. IF EKOS had minimize and maximiize controls then I would never had the problem. What option turns off EKOS always on top?

Read More...

John Robison replied to the topic 'Polar Alignment issue with EKOS and Astrometry' in the forum. 1 month ago

Hello,

I went back to the FOV calculator and looked up my equipment for to calculate some FOV values. The PoleMaster is always 11 x 8. The ZWO and QHY 5L-IIC are roughly the same in between the QHY Mini scope and the ZWO 60mm F/4.,6. I will try these values next clear night.

Read More...