Phidget Network Server: Difference between revisions

From Phidgets Support
No edit summary
(36 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[Category:Overview]]
[[Category:Programming]]{{Recommended_Flow_Links|{{Flow Page Number|{{PAGENAME}} }} }}
__TOC__
__NOTOC__
The Phidget Network Server is a feature of Phidgets that makes it possible to control or interact with Phidgets connected to other computers on your local network.


==General Overview==
==General Overview==


- what is the network server
Once the Phidget Network Server is enabled, your computer hosts a '''Phidget Server''' which broadcasts all connected Phidgets to other computers on your network. When another computer tries to open a channel, these Phidgets will be included in the list of channels that can be attached.


- how does it work
Phidgets attached over a Phidget Network server can be addressed, opened, and attached in much the same way as local Phidgets, so long as the program has access to the Network Server hosting the Phidgets.


<picture of normal phidgets setup>
Channels that are attached remotely may be opened by multiple programs simultaneously using the Phidget Network Server. There are some exceptions, such as motor controllers, that will never match more than one channel at a time for safety reasons.


<picture of setup with discovery enabled>
[[Image:NetworkServer_PhidgetServer.jpg|link=|800px]]


- how to set it up
When you open a Phidget, you have the option of opening it '''locally''' or '''remotely'''.


- it can be mobile, too
Opening a Phidget '''locally''' means communicating with it directly. You can only locally open Phidgets that are physically connected to the computer running your program.


==Network Server on a Phidget Single Board Computer==
Opening a Phidget '''remotely''' means communicating with it using the Network Server. You can remotely open any Phidget on your network, even ones that are physically connected to the computer running your program. 
 
The Phidget Single Board Computer (SBC) can provide a compact, inexpensive way to easily run the Network Server. It runs the Network Server in the background automatically from the moment you turn it on, and allows you to read from and control all Phidgets attached to it:
 
<<picture of SBC setup>>


This can allow for a compact, mobile-based system like this:
'''''IsLocal''''' and '''''IsRemote''''' serve as additional Addressing Properties when a Phidget Network Server is used in your application, and are used to specify if a Phidget should be attached locally or remotely. If you are opening a Phidget your computer is physically connected to and your program uses the Phidget Network Server, it is strongly recommended to specify if you intend to connect to it locally or remotely.
 
<<picture of SBC with mobile>>?
 
The SBC runs Linux, which provides a [[OS - Phidget SBC|full operating system]] on which to develop code, {{ARTICLE|WebPageOnSBC|serve web pages}}, and {{ARTICLE|PhidgetsWirelesslyWithSBC|control Phidgets}}.


==Using The Network Server==
==Using The Network Server==
<!--
Each Operating System page has a section on how to use the Network Server on that operating system:


Each Operating System page has a section on how to use the Network Server on that operating system:
Notably, on Windows and Mac OS this can be handled from the '''Phidgets Control Panel''', under the ''Network Server'' tab.


* [[OS - Windows#Phidget Network Server|Windows]]
* [[OS - Windows#Phidget Network Server|Windows]]
Line 38: Line 33:
* [[OS - iOS#Phidget Network Server|iPhone/iPad iOS]]
* [[OS - iOS#Phidget Network Server|iPhone/iPad iOS]]


The operating systems pages have complete examples on how to set up a network server process and using it to remotely control or gather data from Phidgets. The pages also tell you how to start and stop the Network Server on your computer, and how to run it with or without mDNS (Bonjour, avahi, etc).
The operating systems pages will tell you how to start and stop the Network Server on your computer, and how to run it with or without mDNS (Bonjour, avahi, etc).
-->
 
The specifics of running a Phidget Network Server on your machine depends on the operating system it is using. Select your operating system below for instructions:
 
<tabber>
=
===Select an Operating System for Instructions===
|-|
Windows=
{{Tabber_Tab_Title|Windows}}
In order to try the Phidget Network Server out, first download and install [https://www.apple.com/support/downloads/bonjourforwindows.html Bonjour for Windows] on your host computer and your client computer.
*'''Host computer:''' the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
*'''Client computer:''' a computer running a Phidgets application that accesses Phidgets connected to the host computer.
If you only have one computer, don't worry, your machine can act as both a host and a client.
 
 
Next, open the Phidget Control Panel on your host computer. Do this by double-clicking on the [[File:Ph.jpg|link=]] icon in your taskbar, or by searching for ''Phidget Control Panel'' in the start menu.
Navigate to the Network Server tab, you will see something like this:
[[File:windows_networkserver.PNG|link=|center]]
 
 
From here, you can start, stop, or restart the Network Server. You can also decide how and when the Network Server will start.
[[File:windows_networkserver_startuptype.png|link=|center]]
 
 
Select ''Automatic'' as the startup type from the list and press the start button. By enabling automatic startup, the Network Server will run immediately after Windows boots, so you won't have to manually start it again.
 
 
Now that you have the Network Server running on your host computer, the next step will be accessing the Phidgets connected to your host computer from your client computer. Follow the steps below:
 
 
Open the Phidget Control Panel on your client computer. You will see something like this:
[[File:Windows_controlpanel_remote.PNG |link=|center]]
 
 
As you can see from the image above, Phidget servers are listed under the following heading:
*Remote Server: Servername (link local address)
 
 
You now have access to the Phidgets that are connected to your host computer. Try double-clicking one of them to bring up an example:
[[File:Windows_controlpanel_remoteexample.PNG|link=|center]]
 
 
Note the label in the example indicating a remote connection. This means the example is using the Phidget Network Server in order to communicate with the device.
|-|
macOS=
{{Tabber_Tab_Title|macOS}}
In order to try the Phidget Network Server out, you will need a host computer, and a client computer:
*'''Host computer:''' the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
*'''Client computer:''' a computer running a Phidgets application that accesses Phidgets connected to the host computer.
If you only have one computer, don't worry, your machine can act as both a host and a client.
 
 
Next, open the Phidget Control Panel on your host computer. Do this by double-clicking on the [[File:Ph.jpg|link=]] icon in your applications folder. Navigate to the Network Server tab, you will see the following:
[[File:macos_networkserver.png|link=|center]]
 
 
From here, you can start or stop the Network Server. You can also decide when the Network Server will start.
[[File:macos_networkserver_run.png|link=|center]]
 
 
Check the automatic start box and enter a server name. By enabling automatic startup, the Network Server will run immediately after macOS boots, so you won't have to manually start it again. You can verify the Network Server is running by looking at the label beside the start/stop button.
 
 
Now that you have the Network Server running on your host computer, the next step will be accessing the Phidgets connected to your host computer from your client computer. Follow the steps below:
 
 
Open the Phidget Control Panel on your client computer. You will see something like this:
[[File:macos_controlpanel_remote.png|link=|center]]
 
 
As you can see from the image above, Phidget servers are listed under the following heading:
*Remote Server: Servername
 
 
You now have access to the Phidgets that are connected to your host computer. Try double-clicking one of them to bring up an example:
[[File:macos_controlpanel_remoteexample.png|link=|center]]
 
 
Note the label in the example indicating a remote connection. This means the example is using the Network Server in order to communicate with the Phidget.
|-|
Linux=
{{Tabber_Tab_Title|Linux}}
In order to try the Phidget Network Server out, you will need a host computer, and a client computer with the Phidget libraries installed:
*'''Host computer:''' the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
*'''Client computer:''' a computer running a Phidgets application that accesses Phidgets connected to the host computer.
If you only have one computer, don't worry, your machine can act as both a host and a client.
 
 
Next, open the terminal on the host computer and type in the following command to run the Network Server in the terminal:
<syntaxhighlight lang=bash>
phidget22networkserver
</syntaxhighlight>
 
Or, as a daemon:
<syntaxhighlight lang=bash>
phidget22networkserver -D
</syntaxhighlight>
 
 
[[File:Linux_networkserver.PNG|link=|center]]
 
 
The Network Server is now running on your machine with the default configuration. If you would like to change the Network Server configuration, you can do so by modifying the following file:
*/etc/phidgets/phidget22networkserver.pc
 
 
You can also simply point towards your own configuration file with the following command:
<syntaxhighlight lang=bash>
phidget22networkserver -c /path/to/configuration/file
</syntaxhighlight>
 
 
Now that you have the Network Server running on your host computer, the next step will be accessing the Phidgets connected to your host computer from your client computer. Follow the steps below:
 
 
Open the terminal on the client computer and type in the following command (if you are using a single machine, simply open a new terminal session and continue):
<syntaxhighlight lang=bash>
phidget22admin -s
</syntaxhighlight>
[[File:Linux_networkserver_phidgetadmin.PNG|link=|center|850px]]
 
 
This will list all of the Phidget Servers on your network. Confirm that you can see the Network Server running on your host computer.
 
 
After you have confirmed your Network Server is running, type in the following command:
<syntaxhighlight lang=bash>
phidget22admin -R -d
</syntaxhighlight>
 
 
This command will list all remote Phidgets on the network. Confirm that you can see the Phidgets attached to your host computer:
[[File:Linux_networkserver_phidadminlist.PNG|link=|center]]
 
 
===Run Phidget Network Server on Boot===
If you would like the Network Server to run automatically when your computer boots, take a look at [{{SERVER}}/?view=articles&article=Daemon1 this project].
|-|
PhidgetSBC=
{{Tabber_Tab_Title|PhidgetSBC}}
In order to try the Phidget Network Server out, you will need a host computer, and a client computer with the Phidget libraries installed:
*'''Host computer:''' the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
*'''Client computer:''' a computer running a Phidgets application that accesses Phidgets connected to the host computer.
If you only have one computer, don't worry, your machine can act as both a host and a client.
 
 
The Phidget SBC comes with the Phidget Network Server installed, and the SBC automatically starts the Network Server on boot. In order to change any of this default behaviour, navigate to Phidgets->phidget22NetworkServer using the SBC Web Interface:
 
 
[[File:phidgetsbc_networkserver.PNG|link=|alt=|center]]
</tabber>
 
== Connecting to a Network Server ==
 
There are two ways to gain access to a Phidget server that's being hosted on your network. If the server is discoverable, you can simply enable automatic server discovery in your program. Select your programming language below to see a sample of how this is done.
 
<tabber>
Python=<syntaxhighlight lang=python>
Net.enableServerDiscovery(PhidgetServerType.PHIDGETSERVER_DEVICEREMOTE)
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang=java>
Net.enableServerDiscovery(ServerType.DEVICE_REMOTE);
</syntaxhighlight>
|-|
C#=<syntaxhighlight lang=cSharp>
Net.EnableServerDiscovery(ServerType.DeviceRemote);
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=c>
PhidgetNet_enableServerDiscovery(PHIDGETSERVER_DEVICEREMOTE);
</syntaxhighlight>
|-|
JavaScript=
In Javascript, instead of opening a Phidget using the network server, you can open it normally after connecting to the remote server that the Phidget belongs to. (In a sense, JavaScript is always opening Phidgets remotely)
</tabber>
 
'''Net''' is the object that is used for Phidget Networking. You can find a full list of methods and properties available use with the network in the {{Phidget22API}} by selecting '''Networking API''' in the drop-down menu.
 
If the Phidget server is not discoverable, you can connect to it by adding it specifically. This is done using {{code|AddServer}}, which takes a number of parameters that help specify the server to connect to (e.g. IP address, port, password). See below for an an example of adding a specific server, and take a look at the '''Networking API''' in the {{Phidget22API}} for details.
 
<tabber>
Python=<syntaxhighlight lang=python>
Net.addServer("ServerName", "192.168.2.20", 5661, "passwd", 0)
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang=java>
Net.addServer("ServerName", "192.168.2.20", 5661, "passwd", 0);
</syntaxhighlight>
|-|
C#=<syntaxhighlight lang=cSharp>
Net.AddServer("ServerName", "192.168.2.20", 5661, "passwd", 0);
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=c>
PhidgetNet_addServer("ServerName", "192.168.2.20", 5661, "passwd", 0);
</syntaxhighlight>
|-|
JavaScript=
In Javascript, instead of opening a Phidget using the network server, you can open it normally after connecting to the remote server that the Phidget belongs to. (In a sense, JavaScript is always opening Phidgets remotely)
</tabber>
 
==Network Server on a Phidget Single Board Computer==
The [{{SERVER}}/products.php?product_id=SBC3003 Phidget Single Board Computer (SBC)] can provide a compact, inexpensive way to easily run the Network Server.  It runs the Network Server in the background automatically from the moment you turn it on, and allows you to remotely read from and control all Phidgets attached to it:
 
[[Image:network_server_sbc.jpg|link=|900px]]
 
In this example, a Phidget SBC is connected to a VINT Hub, which in turn is connected to a VINT device. By using the Network Server, it makes all of these channels available to any device connected to the same network. The Network Server on the SBC is discoverable by default.
 
This is convenient because it allows the Phidgets and sensors to be in a remote location, like mounted on a wall or inside some kind of assembly, rather than sitting on your computer desk. The channels of this system could be conveniently accessed by a home computer on the network, a phone running some Phidgets code, or even another Phidget SBC in a different location.
 
For more information on controlling Phidgets with your phone, have a look at the mobile section of our [[Operating System Support|operating system support]] page, or read {{ARTICLE|MurvRobotIOS|this article}} where we use [[OS_-_iOS|iOS]] to control a robot full of Phidgets.


== Examples ==
== Examples ==
Below are some quick examples showing how simple it is to open a Phidget remotely over the Network Server:
Below are some quick examples showing how simple it is to open a Phidget remotely over the Network Server. In each example, a light sensor Phidget is being remotely opened on port 0 of a VINT Hub with serial number 37299.
 
<tabber>
Python=<syntaxhighlight lang='python'>
ch = LightSensor()
 
ch.setDeviceSerialNumber(37299)
ch.setHubPort(0)
ch.setIsRemote(1)
 
Net.enableServerDiscovery(PhidgetServerType.PHIDGETSERVER_DEVICEREMOTE)
 
ch.open();
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang='Java'>
LightSensor ch = new LightSensor();
 
ch.setDeviceSerialNumber(37299);
ch.setHubPort(0);
ch.setIsRemote(true);
 
Net.enableServerDiscovery(ServerType.DEVICE_REMOTE);


=== C/C++ ===
ch.open();
</syntaxhighlight>
|-|
C#=<syntaxhighlight lang='CSharp'>
LightSensor ch = new LightSensor();


<syntaxhighlight lang=cpp>
ch.DeviceSerialNumber = 37299;
ch.HubPort = 0;
ch.IsRemote = true;


Phidget_setDeviceSerialNumber((PhidgetHandle) device, 37299);
Net.EnableServerDiscovery(ServerType.DeviceRemote);
Phidget_setIsRemote((PhidgetHandle) device, 1);


Phidget_open((PhidgetHandle) device);
ch.Open();
CPhidget_openRemoteIP ((CPhidgetHandle) device, serial_number, "127.0.0.1", 5001, NULL);
</syntaxhighlight>
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=cpp>
PhidgetLightSensorHandle ch;
PhidgetLightSensor_create(&ch);


=== C# ===
Phidget_setDeviceSerialNumber((PhidgetHandle) ch, 37299);
Phidget_setHubPort((PhidgetHandle) ch, 0);
Phidget_setIsRemote((PhidgetHandle) ch, 1);


=== Java ===
PhidgetNet_enableServerDiscovery(PHIDGETSERVER_DEVICEREMOTE);


=== Python ===
Phidget_open((PhidgetHandle) ch);


== Configuration File ==
</syntaxhighlight>
|-|
JavaScript=
In Javascript, instead of opening a Phidget using the network server, you can open it normally after connecting to the remote server that the Phidget belongs to. (In a sense, JavaScript is always opening Phidgets remotely)
</tabber>


- how to find config file
For more information, have a look at the {{Phidget22API}} and select your language from the drop-down menu. You can learn more about opening Phidgets on the [[Phidget_Programming_Basics#Opening_the_Phidget|Programming Basics]] page.
- explain the options


== Troubleshooting ==
== Troubleshooting ==


When using the Network Server, both the '''client and server should have the ''same version''''' of the Network Server installed.  The easiest way to ensure this is to update your libraries on both ends.
When using the Network Server, '''both the client and server should have the ''same version''''' of the Network Server installed.  The easiest way to ensure this is to update your libraries on both ends.
 
For other troubleshooting tips, try our [[Network Server Troubleshooting]] page.


For other troubleshooting tips, try our General Troubleshooting page, in its [[General_Troubleshooting#Network_Server_Troubleshooting|Network Server section]].
{{Flow_Navigation_Buttons|{{Flow Page Number|{{PAGENAME}} }} }}

Revision as of 19:31, 11 April 2019

 Phidget Programming Basics: Phidget Network ServerTOC Icon.png Table of Contents

Nav Back Arrow.png Nav Back Hover.png WhiteTab1.png HoverTab1.jpg WhiteTab2.png HoverTab2.jpg WhiteTab3.png HoverTab3.jpg WhiteTab4.png HoverTab4.jpg WhiteTab5.png HoverTab5.jpg WhiteTab6.png HoverTab6.jpg WhiteTab7.png HoverTab7.jpg WhiteTab8.png HoverTab8.jpg WhiteTab9.png HoverTab9.jpg WhiteTab10.png HoverTab10.jpg WhiteTab11.png HoverTab11.jpg WhiteTab12.png HoverTab12.jpg WhiteTab13.png HoverTab13.jpg WhiteTab14.png HoverTab14.jpg GreenTab15.png WhiteTab16.png HoverTab16.jpg Nav Next Arrow.png Nav Next Hover.png


15 . Phidget Network Server

The Phidget Network Server is a feature of Phidgets that makes it possible to control or interact with Phidgets connected to other computers on your local network.

General Overview

Once the Phidget Network Server is enabled, your computer hosts a Phidget Server which broadcasts all connected Phidgets to other computers on your network. When another computer tries to open a channel, these Phidgets will be included in the list of channels that can be attached.

Phidgets attached over a Phidget Network server can be addressed, opened, and attached in much the same way as local Phidgets, so long as the program has access to the Network Server hosting the Phidgets.

Channels that are attached remotely may be opened by multiple programs simultaneously using the Phidget Network Server. There are some exceptions, such as motor controllers, that will never match more than one channel at a time for safety reasons.

NetworkServer PhidgetServer.jpg

When you open a Phidget, you have the option of opening it locally or remotely.

Opening a Phidget locally means communicating with it directly. You can only locally open Phidgets that are physically connected to the computer running your program.

Opening a Phidget remotely means communicating with it using the Network Server. You can remotely open any Phidget on your network, even ones that are physically connected to the computer running your program.

IsLocal and IsRemote serve as additional Addressing Properties when a Phidget Network Server is used in your application, and are used to specify if a Phidget should be attached locally or remotely. If you are opening a Phidget your computer is physically connected to and your program uses the Phidget Network Server, it is strongly recommended to specify if you intend to connect to it locally or remotely.

Using The Network Server

The specifics of running a Phidget Network Server on your machine depends on the operating system it is using. Select your operating system below for instructions:

Select an Operating System for Instructions

Windows

In order to try the Phidget Network Server out, first download and install Bonjour for Windows on your host computer and your client computer.

  • Host computer: the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
  • Client computer: a computer running a Phidgets application that accesses Phidgets connected to the host computer.

If you only have one computer, don't worry, your machine can act as both a host and a client.


Next, open the Phidget Control Panel on your host computer. Do this by double-clicking on the Ph.jpg icon in your taskbar, or by searching for Phidget Control Panel in the start menu. Navigate to the Network Server tab, you will see something like this:

Windows networkserver.PNG


From here, you can start, stop, or restart the Network Server. You can also decide how and when the Network Server will start.

Windows networkserver startuptype.png


Select Automatic as the startup type from the list and press the start button. By enabling automatic startup, the Network Server will run immediately after Windows boots, so you won't have to manually start it again.


Now that you have the Network Server running on your host computer, the next step will be accessing the Phidgets connected to your host computer from your client computer. Follow the steps below:


Open the Phidget Control Panel on your client computer. You will see something like this:

Windows controlpanel remote.PNG


As you can see from the image above, Phidget servers are listed under the following heading:

  • Remote Server: Servername (link local address)


You now have access to the Phidgets that are connected to your host computer. Try double-clicking one of them to bring up an example:

Windows controlpanel remoteexample.PNG


Note the label in the example indicating a remote connection. This means the example is using the Phidget Network Server in order to communicate with the device.

macOS

In order to try the Phidget Network Server out, you will need a host computer, and a client computer:

  • Host computer: the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
  • Client computer: a computer running a Phidgets application that accesses Phidgets connected to the host computer.

If you only have one computer, don't worry, your machine can act as both a host and a client.


Next, open the Phidget Control Panel on your host computer. Do this by double-clicking on the Ph.jpg icon in your applications folder. Navigate to the Network Server tab, you will see the following:

Macos networkserver.png


From here, you can start or stop the Network Server. You can also decide when the Network Server will start.

Macos networkserver run.png


Check the automatic start box and enter a server name. By enabling automatic startup, the Network Server will run immediately after macOS boots, so you won't have to manually start it again. You can verify the Network Server is running by looking at the label beside the start/stop button.


Now that you have the Network Server running on your host computer, the next step will be accessing the Phidgets connected to your host computer from your client computer. Follow the steps below:


Open the Phidget Control Panel on your client computer. You will see something like this:

Macos controlpanel remote.png


As you can see from the image above, Phidget servers are listed under the following heading:

  • Remote Server: Servername


You now have access to the Phidgets that are connected to your host computer. Try double-clicking one of them to bring up an example:

Macos controlpanel remoteexample.png


Note the label in the example indicating a remote connection. This means the example is using the Network Server in order to communicate with the Phidget.

Linux

In order to try the Phidget Network Server out, you will need a host computer, and a client computer with the Phidget libraries installed:

  • Host computer: the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
  • Client computer: a computer running a Phidgets application that accesses Phidgets connected to the host computer.

If you only have one computer, don't worry, your machine can act as both a host and a client.


Next, open the terminal on the host computer and type in the following command to run the Network Server in the terminal:

phidget22networkserver

Or, as a daemon:

phidget22networkserver -D


Linux networkserver.PNG


The Network Server is now running on your machine with the default configuration. If you would like to change the Network Server configuration, you can do so by modifying the following file:

  • /etc/phidgets/phidget22networkserver.pc


You can also simply point towards your own configuration file with the following command:

phidget22networkserver -c /path/to/configuration/file


Now that you have the Network Server running on your host computer, the next step will be accessing the Phidgets connected to your host computer from your client computer. Follow the steps below:


Open the terminal on the client computer and type in the following command (if you are using a single machine, simply open a new terminal session and continue):

phidget22admin -s
Linux networkserver phidgetadmin.PNG


This will list all of the Phidget Servers on your network. Confirm that you can see the Network Server running on your host computer.


After you have confirmed your Network Server is running, type in the following command:

phidget22admin -R -d


This command will list all remote Phidgets on the network. Confirm that you can see the Phidgets attached to your host computer:

Linux networkserver phidadminlist.PNG


Run Phidget Network Server on Boot

If you would like the Network Server to run automatically when your computer boots, take a look at this project.

PhidgetSBC

In order to try the Phidget Network Server out, you will need a host computer, and a client computer with the Phidget libraries installed:

  • Host computer: the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
  • Client computer: a computer running a Phidgets application that accesses Phidgets connected to the host computer.

If you only have one computer, don't worry, your machine can act as both a host and a client.


The Phidget SBC comes with the Phidget Network Server installed, and the SBC automatically starts the Network Server on boot. In order to change any of this default behaviour, navigate to Phidgets->phidget22NetworkServer using the SBC Web Interface:


Connecting to a Network Server

There are two ways to gain access to a Phidget server that's being hosted on your network. If the server is discoverable, you can simply enable automatic server discovery in your program. Select your programming language below to see a sample of how this is done.

Net.enableServerDiscovery(PhidgetServerType.PHIDGETSERVER_DEVICEREMOTE)
Net.enableServerDiscovery(ServerType.DEVICE_REMOTE);
Net.EnableServerDiscovery(ServerType.DeviceRemote);
PhidgetNet_enableServerDiscovery(PHIDGETSERVER_DEVICEREMOTE);

In Javascript, instead of opening a Phidget using the network server, you can open it normally after connecting to the remote server that the Phidget belongs to. (In a sense, JavaScript is always opening Phidgets remotely)

Net is the object that is used for Phidget Networking. You can find a full list of methods and properties available use with the network in the Phidget22 API by selecting Networking API in the drop-down menu.

If the Phidget server is not discoverable, you can connect to it by adding it specifically. This is done using AddServer, which takes a number of parameters that help specify the server to connect to (e.g. IP address, port, password). See below for an an example of adding a specific server, and take a look at the Networking API in the Phidget22 API for details.

Net.addServer("ServerName", "192.168.2.20", 5661, "passwd", 0)
Net.addServer("ServerName", "192.168.2.20", 5661, "passwd", 0);
Net.AddServer("ServerName", "192.168.2.20", 5661, "passwd", 0);
PhidgetNet_addServer("ServerName", "192.168.2.20", 5661, "passwd", 0);

In Javascript, instead of opening a Phidget using the network server, you can open it normally after connecting to the remote server that the Phidget belongs to. (In a sense, JavaScript is always opening Phidgets remotely)

Network Server on a Phidget Single Board Computer

The Phidget Single Board Computer (SBC) can provide a compact, inexpensive way to easily run the Network Server. It runs the Network Server in the background automatically from the moment you turn it on, and allows you to remotely read from and control all Phidgets attached to it:

Network server sbc.jpg

In this example, a Phidget SBC is connected to a VINT Hub, which in turn is connected to a VINT device. By using the Network Server, it makes all of these channels available to any device connected to the same network. The Network Server on the SBC is discoverable by default.

This is convenient because it allows the Phidgets and sensors to be in a remote location, like mounted on a wall or inside some kind of assembly, rather than sitting on your computer desk. The channels of this system could be conveniently accessed by a home computer on the network, a phone running some Phidgets code, or even another Phidget SBC in a different location.

For more information on controlling Phidgets with your phone, have a look at the mobile section of our operating system support page, or read this article where we use iOS to control a robot full of Phidgets.

Examples

Below are some quick examples showing how simple it is to open a Phidget remotely over the Network Server. In each example, a light sensor Phidget is being remotely opened on port 0 of a VINT Hub with serial number 37299.

ch = LightSensor()

ch.setDeviceSerialNumber(37299)
ch.setHubPort(0)
ch.setIsRemote(1)

Net.enableServerDiscovery(PhidgetServerType.PHIDGETSERVER_DEVICEREMOTE)

ch.open();
LightSensor ch = new LightSensor();

ch.setDeviceSerialNumber(37299);
ch.setHubPort(0);
ch.setIsRemote(true);

Net.enableServerDiscovery(ServerType.DEVICE_REMOTE);

ch.open();
LightSensor ch = new LightSensor();

ch.DeviceSerialNumber = 37299;
ch.HubPort = 0;
ch.IsRemote = true;

Net.EnableServerDiscovery(ServerType.DeviceRemote);

ch.Open();
PhidgetLightSensorHandle ch;
PhidgetLightSensor_create(&ch);

Phidget_setDeviceSerialNumber((PhidgetHandle) ch, 37299);
Phidget_setHubPort((PhidgetHandle) ch, 0);
Phidget_setIsRemote((PhidgetHandle) ch, 1);

PhidgetNet_enableServerDiscovery(PHIDGETSERVER_DEVICEREMOTE);

Phidget_open((PhidgetHandle) ch);

In Javascript, instead of opening a Phidget using the network server, you can open it normally after connecting to the remote server that the Phidget belongs to. (In a sense, JavaScript is always opening Phidgets remotely)

For more information, have a look at the Phidget22 API and select your language from the drop-down menu. You can learn more about opening Phidgets on the Programming Basics page.

Troubleshooting

When using the Network Server, both the client and server should have the same version of the Network Server installed. The easiest way to ensure this is to update your libraries on both ends.

For other troubleshooting tips, try our Network Server Troubleshooting page.