OS - macOS: Difference between revisions

From Phidgets Support
No edit summary
No edit summary
Line 101: Line 101:


[[File:macOS_ControlPanel_NetworkService_Disconnected.PNG|link=|alt=macOS Control Panel Network Server Stopped]]
[[File:macOS_ControlPanel_NetworkService_Disconnected.PNG|link=|alt=macOS Control Panel Network Server Stopped]]
===Debugging the Network Service===
===Debugging the Network Server===


In addition to enabling [[General Phidget Programming#Logging|logging]] in your Phidget code, you can get additional debugging information from the Network Service itself.  This additional debugging can be found in the log file.
In addition to enabling [[General Phidget Programming#Logging|logging]] in your Phidget code, you can get additional debugging information from the Network Server itself.  This additional debugging can be found in the log file.


You can find the Network Service log file at {{Code|/Library/Logs/}}. The easiest way to view this file is to run the Console, which you can launch by searching for it in spotlight. Click the magnifying glass in the top right corner of the screen or hit Command+Space and search for Console.
You can find the Network Server log file at {{Code|/Library/Logs/}}. The easiest way to view this file is to run the Console, which you can launch by searching for it in spotlight. Click the magnifying glass in the top right corner of the screen or hit Command+Space and search for Console.


[[File:macOS_Console_log.PNG|link=|900px|alt=MacOS Console]]
[[File:macOS_Console_log.PNG|link=|900px|alt=MacOS Console]]
Line 111: Line 111:
Under {{Code|/Library/Logs/}}, you can find {{Code|phidgetNetworkService22.log}}. Errors related to the Control Panel can instead be found in {{Code|phidgetcontrolpanel22.log}} in {{Code|~/Library/Logs/}}.
Under {{Code|/Library/Logs/}}, you can find {{Code|phidgetNetworkService22.log}}. Errors related to the Control Panel can instead be found in {{Code|phidgetcontrolpanel22.log}} in {{Code|~/Library/Logs/}}.


Each message in the log file will list the type of the message, the time and date, the place in the libraries the message came from, and a description. This can be very useful for figuring out why certain parts of one of the examples or the Network Service are not working properly.
Each message in the log file will list the type of the message, the time and date, the place in the libraries the message came from, and a description. This can be very useful for figuring out why certain parts of one of the examples or the Network Server are not working properly.


==Advanced Information==
==Advanced Information==

Revision as of 18:40, 1 May 2017

Quick Downloads

Already know what you're doing? Here you go:

Getting Started with macOS

Welcome to using Phidgets with macOS. If you haven't already, check out the user guide for your device. If you are ready to go, the first step in creating macOS applications with Phidgets is installing the Phidget libraries!

Install

To install the core Phidget files onto your system, follow these steps:


1. Download the Phidget installer for your system:


2. Open up the installer, and double click on Phidgets.pkg to install the libraries.

macOS Install

3. Continue with the installation.

macOS Install

Success! You have finished installing the Phidgets software on your machine. Before you begin coding, let's verify that your Phidget is able to communicate with your machine.

Verify

The best way to verify that your libraries are installed and your Phidget is working is to use the Phidget Control Panel. The Phidget Control Panel is a powerful tool that will help you develop your Phidgets applications. Get started by following the instructions below:


1. Open Finder and navigate to the Phidget Control Panel in the Applications list.

macOS Finder Apps

2. Double click on the Phidgets icon to bring up the Phidget Control Panel. You can now see all the Phidgets that are plugged into your machine, as well as any Phidgets that are on the network.

macOS Control Panel General

3. Click on the arrow beside a device to expand it so that you can see all available channels. Double click on one of these channels to open up a window that lets you interact with it. macOS Control Panel Channel


The Phidget Control Panel can be used for testing devices, updating firmware, enabling a network server, and more! Visit the Phidget Control Panel page if you want to delve a little deeper.

Your Phidget is now able to communicate with your development machine. The next step is selecting a programming language so you can start to write some code!

If you do not see your device in the Phidget Control Panel, visit the general troubleshooting page.

Programming

Ready to write some code? Select one of the programming languages below:

Great choices for beginners:

Also supported:

Phidget Network Server

The Phidget Network Server allows you to remotely control Phidgets over a network. For more information, please see the Phidget Network Server page.

Drivers for the Phidget Network Server on macOS are already included in the Drivers above. If you have the Phidget Control Panel app installed, you already have the Network Server installed.

There are two ways that you can connect to a Phidget hosted on another computer. The first method is by using the IP address/host name and port of the host computer. The second method makes the use of mDNS, which allows Phidgets to be found and opened on the network by a server id instead of an IP address/host name. When using a server id, both the client and server will need to be running an implementation of zero configuration networking. The Phidget Network Server takes advantage of the Bonjour software, which is built-in to macOS. It is a tool developed by Apple to locate devices, such as Phidgets, on a network.

This section helps you install, check, and use the Network Server on macOS, but we also have an overview of the Phidget Network Server in general.

Using the Network Server

To use a Phidget over the Network Server, you'll want to:

  1. Have two different computers connected to the same network. We will call the computer that has the Phidget directly connected to the USB port the host. The client will be the computer that runs a Phidget application to connect to the Phidget attached to the host. Please note that if you only have a single computer, you can also connect to the Phidget over the Network Server. The computer will simply act as both a host and client. This will allow you to bypass the one application per Phidget limitation.
  2. Start the Network Server on the computer that directly connects to the Phidget
  3. Run your program on the remote computer that will control the Phidget over the network

First ensure that the Phidget drivers have been installed on both the host and client computers. Next, we will set up the Network Server and run the Phidget example program on the client. Please follow these steps:

1. On the host computer, double click on the Ph.jpg icon in the Apps list to bring up the Control Panel. In the Network Server tab, you can start, restart or stop the Network Server. You can also choose to have the Network Server start up automatically upon boot up by checking the box beside Start automatically on boot. Otherwise, you will have to manually turn the Network Server on everytime you wish to use it. You'll need administrator privileges in order to make changes to these settings. You can see the status of the Network Server at the top of the window beside the Start/Stop button, where it will say "Network Server is running" or "Network Server is stopped".

macOS Control Panel Network Server Setup

macOS Control Panel Network Server Setup

2. Ensure that the Phidget is plugged in to the host.

3. On the client computer, open up the Phidget Control Panel. On the Phidgets tab you will see the Phidget that is plugged into the host as one of the entries listed under the heading of Remote Server: <Hostname>. Double click on one of the Phidget's objects to open the example application.

macOS Control Panel Network Server

4. The example application will open up, and you will be able to communicate with the Phidget over the Network Server.

macOS Control Panel Example

5. You can confirm that this Phidget is truly being used of the Network Server by stopping the Network Server while the example application is still open. On the host's Phidget Control Panel, go to the Network Server tab and hit Stop Network Server to terminate the Network Server. Now, take a look at the example application on the client. Since the application can no longer find this Phidget over the Network Server, all of the information disappears and the window says that "Nothing" is attached to this channel.

macOS Control Panel Network Server Stopped

Debugging the Network Server

In addition to enabling logging in your Phidget code, you can get additional debugging information from the Network Server itself. This additional debugging can be found in the log file.

You can find the Network Server log file at /Library/Logs/. The easiest way to view this file is to run the Console, which you can launch by searching for it in spotlight. Click the magnifying glass in the top right corner of the screen or hit Command+Space and search for Console.

MacOS Console

Under /Library/Logs/, you can find phidgetNetworkService22.log. Errors related to the Control Panel can instead be found in phidgetcontrolpanel22.log in ~/Library/Logs/.

Each message in the log file will list the type of the message, the time and date, the place in the libraries the message came from, and a description. This can be very useful for figuring out why certain parts of one of the examples or the Network Server are not working properly.

Advanced Information

These files that were placed onto your system as part of the installation process:

  • Phidget22.framework contains the actual Phidget library, which is used at run-time. It is placed into /Library/Frameworks.
  • Phidget.kext is the kernel extension. It is placed into /System/Library/Extensions.
  • phidgetnetworkserver22 is the Phidget Network Server. It is placed into /usr/local/bin.