Difference between revisions of "Language - Swift"

From Phidgets Support
Jump to: navigation, search
Line 115: Line 115:
 
<div class = "source">
 
<div class = "source">
 
<syntaxhighlight lang="swift">
 
<syntaxhighlight lang="swift">
var ch:PhidgetDigitalInput? = nil;
+
var ch:PhidgetDigitalInput? = nil
 
</syntaxhighlight>
 
</syntaxhighlight>
 
</div>
 
</div>
Line 125: Line 125:
 
<div class = "source">
 
<div class = "source">
 
<syntaxhighlight lang="swift">
 
<syntaxhighlight lang="swift">
PhidgetDigitalInput_create(&ch);
+
PhidgetDigitalInput_create(&ch)
 
Phidget_open(ch);
 
Phidget_open(ch);
 
</syntaxhighlight>
 
</syntaxhighlight>
Line 135: Line 135:
 
<div class = "source">
 
<div class = "source">
 
<syntaxhighlight lang="swift">
 
<syntaxhighlight lang="swift">
Phidget_openWaitForAttachment(ch, 5000); //wait for attach for 5 seconds, if not time out
+
Phidget_openWaitForAttachment(ch, 5000) //wait for attach for 5 seconds, if not time out
 
</syntaxhighlight>
 
</syntaxhighlight>
 
</div>
 
</div>
Line 145: Line 145:
 
<div class = "source">
 
<div class = "source">
 
<syntaxhighlight lang="swift">
 
<syntaxhighlight lang="swift">
    let gotAttach: @convention(c)(PhidgetHandle?, UnsafeMutableRawPointer?) -> () = {phid,context in
+
let gotAttach: @convention(c)(PhidgetHandle?, UnsafeMutableRawPointer?) -> () = {phid,context in
        DispatchQueue.main.async(execute: {
+
    DispatchQueue.main.async(execute: {
            let myObject = Unmanaged<YourViewController>.fromOpaque(context!).takeUnretainedValue()
+
        let myObject = Unmanaged<YourViewController>.fromOpaque(context!).takeUnretainedValue()
            myObject.onAttachHandler()
+
        myObject.onAttachHandler()
        })
+
    })
    }
+
}
 
</syntaxhighlight>
 
</syntaxhighlight>
 
</div>
 
</div>
Line 157: Line 157:
 
<div class = "source">
 
<div class = "source">
 
<syntaxhighlight lang="swift">
 
<syntaxhighlight lang="swift">
PhidgetDigitalInput_create(&ch);
+
PhidgetDigitalInput_create(&ch)
Phidget_setOnAttachHandler(ch,gotAttach,bridge(self));
+
Phidget_setOnAttachHandler(ch,gotAttach,bridge(self))
Phidget_open((PhidgetHandle)digout);
+
Phidget_open((PhidgetHandle)digout)
 
</syntaxhighlight>
 
</syntaxhighlight>
 
</div>
 
</div>
Line 166: Line 166:
 
<div class = "source">
 
<div class = "source">
 
<syntaxhighlight lang="swift">
 
<syntaxhighlight lang="swift">
    func bridge<T : AnyObject>(_ obj : T) -> UnsafeMutableRawPointer {
+
func bridge<T : AnyObject>(_ obj : T) -> UnsafeMutableRawPointer {
        return Unmanaged.passUnretained(obj).toOpaque()
+
    return Unmanaged.passUnretained(obj).toOpaque()
    }
+
}
 
</syntaxhighlight>
 
</syntaxhighlight>
 
</div>
 
</div>
Line 177: Line 177:
 
<div class = "source">
 
<div class = "source">
 
<syntaxhighlight lang="swift">
 
<syntaxhighlight lang="swift">
PhidgetDigitalInput_setOnStateChangeHandler(ch, gotStateChange, bridge(self));
+
PhidgetDigitalInput_setOnStateChangeHandler(ch, gotStateChange, bridge(self))
 
</syntaxhighlight>
 
</syntaxhighlight>
 
</div>
 
</div>
Line 185: Line 185:
 
<div class = "source">
 
<div class = "source">
 
<syntaxhighlight lang="swift">
 
<syntaxhighlight lang="swift">
    let gotStateChangeEventData: @convention(c)(PhidgetDigitalInputHandle?, UnsafeMutableRawPointer?, CInt) -> () = {_,context,cState in
+
let gotStateChange: @convention(c)(PhidgetDigitalInputHandle?, UnsafeMutableRawPointer?, CInt) -> () = {_,context,cState in
        var state:Int32 = cState
+
    var state:Int32 = cState
        DispatchQueue.main.async(execute: {
+
    DispatchQueue.main.async(execute: {
            let myObject = Unmanaged<DigitalInputViewController>.fromOpaque(context!).takeUnretainedValue()
+
        let myObject = Unmanaged<YourViewController>.fromOpaque(context!).takeUnretainedValue()
            myObject.onStateChangeHandler(state)
+
        myObject.onStateChangeHandler(state)
        })
+
    })
 +
}
 +
</syntaxhighlight>
 +
</div>
 +
 
 +
Above, the onStateChangeHandler method is invoked on the main thread. Event data is stored as an Int32.
 +
 
 +
The method onStateChangeHandler is defined as follows:
 +
 
 +
<div class = "source">
 +
<syntaxhighlight lang="swift">
 +
func onStateChangeHandler(_ state:Int32){
 +
    if  state == 0{
 +
        stateLabel.text = "False"
 
     }
 
     }
 +
    else{
 +
        stateLabel.text = "True"
 +
    }
 +
}
 +
</syntaxhighlight>
 +
</div>
 +
 +
The example shown above simply changes the text of a UITextField to display whether the input is true or false.
 +
 +
Some events such as the attach or detach events belong to the base Phidget object and are thus common to all Phidgets. Please refer to the {{Phidget22API}} manual and the Swift examples for a list of events and their usage.
 +
 +
If events do not suit your needs, you can also poll the device directly for data using code like this:
 +
 +
<div class = "source">
 +
<syntaxhighlight lang="swift">
 +
var state = 0
 +
PhidgetDigitalOutput_getState(ch, &state)
 +
stateLabel.text = state ? "True" : "False"
 +
</syntaxhighlight>
 +
</div>
 +
 +
Polling code can be used inside a polling loop as an alternative to event driven programming.
 +
 +
==== Step Four: Close and Delete ====
 +
At the end of your program, don't forget to close your device.
 +
 +
<div class = "source">
 +
<syntaxhighlight lang="swift">
 +
Phidget_close(ch)
 +
PhidgetDigitalInput_delete(&digin)
 
</syntaxhighlight>
 
</syntaxhighlight>
 
</div>
 
</div>

Revision as of 18:16, 1 March 2017

Introduction

If this is your first time working with a Phidget, we suggest starting with the Getting Started page for your specific device. This can be found in the user guide for your device. That page will walk you through installing drivers and libraries for your operating system, and will then bring you back here to use Swift specifically. Swift is capable of using the complete Phidget22 API, including events. We also provide example code in Swift for all Phidget devices.

Swift is capable of using the complete Phidget API, including events. When using it on iOS devices, however, Phidgets can only be remotely controlled over a network using the Phidget Network Service because they don't support direct USB connection.

Swift can be developed with Xcode on macOS.

Quick Downloads

List of download links, to be added once files are available

Getting Started with Swift

macOS

Xcode

Use our examples

Write your own code

iOS

Xcode

Use our examples

If Xcode is not already installed on your system, then you will need to install it. You can download it for free from the Mac app store.

Start by ensuring the Phidget Network Service is running on the computer that the Phidget is physically plugged in and connected to. This computer needs to have a USB port and should be running macOS or one of our other supported operating systems. For directions on how to set up and run the Phidget Network Service refer to the page for that operating system.

Then, on the macOS system that will be used for developing the iOS application, download and unpack the Phidget Examples for Swift. The easiest way to confirm that your environment is set up is to compile and the Phidgets app. Start by opening the Phidgets.xcodeproj in Xcode.

Next, select the target you want the application to run on. In order to run the example on a physical device, you must be an Apple Developer, otherwise you can choose to run the example on a simulator.

Ios SelectTarget.png

To run the example, click on the Run button.

Ios RuniOS.png

The program will detect any servers that are currently online and have Phidgets connected. Here is an example output:

Ios PhidgetApp MainScreen.png

After confirming that the Phidgets Example is working, you can proceed to run the example for your specific device. Do this by continuing to navigate through the hierarchy until you reach your device, after tapping your device the example will show automatically. Currently, we have example programs for the following software objects:

  • DigitalInput
  • DigitalOutput
  • VoltageInput
  • VoltageRatioInput

Here is an example of what the DigitalOutput example looks like:

Ios PhidgetApp DigitalOutput.png

Once you have the Swift example running, we have a teaching section below to help you follow them.

Write your own code

Whether you are building a project from scratch, or adding Phidget functionality to an existing project, you will need to configure your development environment to properly link the Phidget library. To begin:

1. Create a new Xcode project

Cocoa CreateProject.png

2. Select an iOS application. For this tutorial's purposes, we will use a Single View Application.

IOS SingleView.png

3. Give the project a descriptive name such as PhidgetTest, select Objective-C as the language, and choose what kind of devices you want to use the app for. For this tutorial we will allow this app to be used universally.

IOS NameProject Swift.png

A .xcodeproj file will be created in the destination folder.

4. Download the Phidget iOS Library and extract it. Inside you will find iphoneos and iphonesimulator folders. Move the two folders as well as the phidget22.h file into the same directory as the newly created .xcodeproj

5. In Xcode, open Project Settings → Build Settings and navigate to the Linking section

6. In Linking → Other Linker Flags, following the following steps:

Select Any iOS Simulator SDK and enter: $(SRCROOT)/iphonesimulator/libPhidget22.a

Select Any iOS SDK and enter: $(SRCROOT)/iphoneos/libPhidget22.a

IOS LinkerFlags.png

7. In Search Paths→Header Search Paths enter $(SRCROOT)

IOS HeaderSearchPaths.png

8. In your header file, add a reference to phidget22.h

#import "phidget22.h"

The project now has access to Phidgets and we are ready to begin coding.

Edit the Examples

By following the instructions for your operating system and compiler above, you probably now have a working example and want to understand it better so you can change it to do what you want. This teaching section has resources for you to learn from the examples and write your own. Your main reference for writing Objective-C code will be the Phidget22 API Manual:

Example Flow

Have to make a new template for this because Template:ExamplePseudocode does not work for Objective-C (no waiting for enter to close program/device)

Code Snippets

Step One: Initialize and Open

First, ensure you have given your program access to Phidgets as described in the Write Your Own Code section, Then, you will need to declare your Phidget variable in your code. For example, we can declare a Phidget Digital Output like this:

var ch:PhidgetDigitalInput? = nil

The object name for any Phidget is listed in the Phidget22 API manual. Every type of Phidget also inherits functionality from the Phidget base class.

Next, the Phidget object needs to be initialized and opened.

PhidgetDigitalInput_create(&ch)
Phidget_open(ch);

Step Two: Wait for Attachment (plugging in) of the Phidget

Simply calling open does not guarantee you can use the Phidget immediately. To use a Phidget, it must be plugged in (attached). We can handle this by using event driven programming and tracking the attach events and detach events. Alternatively, we can call the following function:

Phidget_openWaitForAttachment(ch, 5000) //wait for attach for 5 seconds, if not time out

Waiting for attachment will block indefinitely until a connection is made, or until the timeout value is exceeded.

To use events to handle attachments, we need to first declare the function that will be called when an attach event is fired - in this case we will call the function gotAttach.

let gotAttach: @convention(c)(PhidgetHandle?, UnsafeMutableRawPointer?) -> () = {phid,context in
    DispatchQueue.main.async(execute: {
        let myObject = Unmanaged<YourViewController>.fromOpaque(context!).takeUnretainedValue()
        myObject.onAttachHandler()
    })
}

Next, we have to modify our create/open code to emulate the following:

PhidgetDigitalInput_create(&ch)
Phidget_setOnAttachHandler(ch,gotAttach,bridge(self))
Phidget_open((PhidgetHandle)digout)

The bridge function mentioned above is described here:

func bridge<T : AnyObject>(_ obj : T) -> UnsafeMutableRawPointer {
    return Unmanaged.passUnretained(obj).toOpaque()
}

Step Three: Do Things with the Phidget

We recommend the use of event driven programming when working with Phidgets. In a similar way to handling an attach event as described above, we can add an event handler with the following code:

PhidgetDigitalInput_setOnStateChangeHandler(ch, gotStateChange, bridge(self))

This code will connect a function and an event. In this case, the gotStateChange function will be called when there has been a change to the devices input. Next, we need to create the gotStateChange function.

let gotStateChange: @convention(c)(PhidgetDigitalInputHandle?, UnsafeMutableRawPointer?, CInt) -> () = {_,context,cState in
    var state:Int32 = cState
    DispatchQueue.main.async(execute: {
        let myObject = Unmanaged<YourViewController>.fromOpaque(context!).takeUnretainedValue()
        myObject.onStateChangeHandler(state)
    })
}

Above, the onStateChangeHandler method is invoked on the main thread. Event data is stored as an Int32.

The method onStateChangeHandler is defined as follows:

func onStateChangeHandler(_ state:Int32){
    if  state == 0{
        stateLabel.text = "False"
    }
    else{
        stateLabel.text = "True"
    }
}

The example shown above simply changes the text of a UITextField to display whether the input is true or false.

Some events such as the attach or detach events belong to the base Phidget object and are thus common to all Phidgets. Please refer to the Phidget22 API manual and the Swift examples for a list of events and their usage.

If events do not suit your needs, you can also poll the device directly for data using code like this:

var state = 0
PhidgetDigitalOutput_getState(ch, &state)
stateLabel.text = state ? "True" : "False"

Polling code can be used inside a polling loop as an alternative to event driven programming.

Step Four: Close and Delete

At the end of your program, don't forget to close your device.

Phidget_close(ch)
PhidgetDigitalInput_delete(&digin)

Further Reading

Phidget Programming Basics - Here you can find the basic concepts to help you get started with making your own programs that use Phidgets.

Data Interval/Change Trigger - Learn about these two properties that control how much data comes in from your sensors.

Using Multiple Phidgets - It can be difficult to figure out how to use more than one Phidget in your program. This page will guide you through the steps.

Polling vs. Events - Your program can gather data in either a polling-driven or event-driven manner. Learn the difference to determine which is best for your application.

Logging, Exceptions, and Errors - Learn about all the tools you can use to debug your program.

Phidget Network Service - Phidgets can be controlled and communicated with over your network- either wirelessly or over ethernet.


Common Problems and Solutions / Workarounds

If you know of common problems using this lanaguage (for example, having to create sub-VIs when using multiple phidgets in labview) put them here.