tinypilot beta image

[hreuver]

as a client you have to specify the correct ssid and key..   How did you change it to client mode?

Are you sure the remote won't switch back even if you select defaults?

You can also edit the networking file instead of rewriting the image.

Sean

Yes I used the webapp to switch to Client mode and specified the correct ssid and key
defaults is not showing up in that menu it just states no wifi detected

I also edited the networking file but I am not sure exactly how it should look. 
The SSID and key were correct in the network.txt but I am not sure what the settings above should say. Currently at the top of the file it says SSID pypilot and then below that it says managed. 

Then the client ssid and key and static IP address are listed.

But the biggest issue is even leaving TP as the AP and connecting OP2 to the TP wifi access point, Opencpn pypilot plugin is not connecting

I'm answering to the old message in this thread:
I tried changing the Wifi to AP myself and it works by setting up de SID and password for me.


Questions:
If the TP does not provide the AP what does?
Can you check if the AP receives a correct DHCP request? (There should be logging of provided IP adresses?)
It is obvious that the TP does not get a DHCP address from the AP.

---

Thanks Sean
The plugin was originally installed from git.
Yesterday I updated the openCPN installer and reinstalled the plugin using the openCPN installer.   It is reported as .05 in the installer and there is only one option listed.

Edit: I found the spot where you can choose to install version .22. but when I do update the plugin to .22 it no longer connects to localhost pypilot ... guessing that is by design, it seems I can install .22 and uninstall it at will?
I will attempt to connect the beta tinypilot to the plugin version .22 next
thank you

Edit#2. Okay so I got it working with the wifi as managed connection to openplotter with a static IP. The only thing I am having difficulty with now is there is no access request in signal K for that device? Is there a way to force tinypilot to request access?
All the data is getting to where it needs to be but it is not going through signalk (I guess?)

If you are using OpenCPN, the TP is obvious another computer.
Localhost will connect to the OpenCPN computer, why don't you try to connect to the static IP you earlier put into the TP?

Using SIgnalK I setup a NMEA0183 connection  (labelled tinypilot):
- TCP client
- IP address from TP (default 192.168.14.1, but you have a different static IP)
- output events nmea0183out
- sentence events pypilot

That way I get access to:
- tinypilot.AP (RSA)
- tinypilot.AP (HDM)


The tinypilot gets access to the Wind sources.