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
TinyPilot as client instead of Access Point
#1
Has anyone tried to run TP as a client to OP instead of an Access point? 

I can see there are settings that can be adjusted for this but I just cannot seem to get my head around what it means and how it works...


Once TP is a client that would mean it would join the OpenPlotter network ( I would set a static IP for TP)
Then in OpenCPN under the pypilot plugin config I would change the IP address to the new TPs address
Then in settings I would change the 20220 to point to the new TP address

Is that all there is to it?

Am I missing some glaringly obvious reason why it should not work?

Also, if Openplotter is connected as a client to my main home network, and TP is connected as a client to OpenPlotter, would that mean that I can connect to TP from any computer that is on either network via ssh or via opencpn pypilot plugin? 
This would certainly make testing much easier?!
Reply


Messages In This Thread
TinyPilot as client instead of Access Point - by rastam4n - 2019-09-10, 02:06 PM

Forum Jump:


Users browsing this thread: 2 Guest(s)