This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Wind sensor not connecting to OP4 after upgrade
#1
Hi there! I hope you are all good.
I migrated to OP4 on my Rasp v4 and after applying the same settings I had on OP3, the GPS connects flawlessly to the OP4 AP, but the wind sensor doesn't. AP settings (SSID/pwd) are identical to the one on OP3 so GPS connects instantly, but wind sensor can't.
I would deeply appreciate any hint here, because I tried all I know trying to troubleshoot this issue.
thanks a lot!!!
Max
Reply
#2
How is the GPS connecting to the AP? What type of GPS is it?
Reply
#3
Hi Baltika! Thanks for the prompt answer!
It is a GPS that connects over WiFi to the AP of the Raspberry, similar to the wind sensor. Is there any way to see any log from the raspberry AP to identify if somehow the connection from the wind sensor gets rejected?
Thanks in advance,
Max
Reply
#4
The log in OPv4 is different from that in earlier versions. Instead of syslog the data is written to a journal.

Firstly it is worth enabling debugging, Openplotter>Settings>General Settings and click Debugging. you'll see a message saying information will be saved in the system log. Do remember to disable this afterwards or your logs will become very large. You then look at the log data with the journalctl command. Assuming your AP is wlan9 (default) then this command will show any log data for that interface:

Code:
journalctl | grep wlan9


 Here is the result when I try to connect to the AP deliberately using the wrong password:

Code:
Dec 05 12:10:03 openplotter wpa_supplicant[692]: wlan9: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB
Dec 05 12:16:19 openplotter wpa_supplicant[692]: wlan9: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Dec 05 12:16:19 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:16:20 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:16:21 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:16:22 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:25:19 openplotter wpa_supplicant[692]: wlan9: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Dec 05 12:25:19 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:25:20 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:25:21 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:25:22 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:28:41 openplotter wpa_supplicant[692]: wlan9: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Dec 05 12:28:41 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:28:42 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:28:43 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0
Dec 05 12:28:44 openplotter wpa_supplicant[692]: wlan9: AP-STA-POSSIBLE-PSK-MISMATCH 2a:32:66:eb:18:c0

You can see that POSSIBLE-PSK-MISMATCH, this is saying wrong password. Your error messages will be different depending on why the connection failed.

If I try using the correct password the response I get is:

Code:
Dec 05 12:30:54 openplotter wpa_supplicant[692]: wlan9: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Dec 05 12:30:54 openplotter wpa_supplicant[692]: wlan9: AP-STA-CONNECTED 2a:32:66:eb:18:c0
Dec 05 12:30:54 openplotter wpa_supplicant[692]: wlan9: EAPOL-4WAY-HS-COMPLETED 2a:32:66:eb:18:c0
Dec 05 12:30:57 openplotter dnsmasq-dhcp[875]: DHCPDISCOVER(wlan9) 2a:32:66:eb:18:c0
Dec 05 12:30:57 openplotter dnsmasq-dhcp[875]: DHCPOFFER(wlan9) 10.42.0.43 2a:32:66:eb:18:c0
Dec 05 12:30:57 openplotter dnsmasq-dhcp[875]: DHCPDISCOVER(wlan9) 2a:32:66:eb:18:c0
Dec 05 12:30:57 openplotter dnsmasq-dhcp[875]: DHCPOFFER(wlan9) 10.42.0.43 2a:32:66:eb:18:c0
Dec 05 12:30:58 openplotter dnsmasq-dhcp[875]: DHCPDISCOVER(wlan9) 2a:32:66:eb:18:c0
Dec 05 12:30:58 openplotter dnsmasq-dhcp[875]: DHCPOFFER(wlan9) 10.42.0.43 2a:32:66:eb:18:c0
Dec 05 12:30:59 openplotter dnsmasq-dhcp[875]: DHCPREQUEST(wlan9) 10.42.0.43 2a:32:66:eb:18:c0
Dec 05 12:30:59 openplotter dnsmasq-dhcp[875]: DHCPACK(wlan9) 10.42.0.43 2a:32:66:eb:18:c0

Connection has completed successfully and the device I am connecting to the AP has been given the IP address 10.42.0.43
Reply
#5
Thanks mate! I will be performing the tests tomorrow since I will be traveling with the boat and I will come back to you ASAP.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)