This article assumes you’re already familiar with Tulip. If you haven’t read "The Essentials - A brief overview of Tulip" and “Welcome to your Tulip Account”, we recommend taking a couple minutes to do so.
Now, let’s setup the Tulip Player, which is the platform used to run Tulip Apps and collect data from the production floor.
The Tulip Player can be used in two ways:
- Via Google Chrome browser at https://your-account.tulip.co/player
- Via downloadable application
Please note: We generally recommend that you download the Player because that is the best way to use the Player to test apps in real-time as you work on them in the App Editor.
Downloading the Player
The Tulip Player can be downloaded within your Tulip account by opening the Help Menu (click on the question mark in the Menu Bar in the top right of every screen) and selecting ‘Download Player’.
From here, select the appropriate download based on your operating system (Mac or Windows). The download should begin automatically.
Alternatively, you can visit download.tulip.co.
When the download is finished, if the Player does not start automatically, navigate to your download directory and run the ‘Tulip Player’ file.
The Player is installed to C:\Users\<username>\AppData\Local\tulip-player-desktop
In addition, Player uses C:\ProgramData\tulip folder to store global configuration. All users on the PC using Tulip must have Read, Write and Modify permissions on that folder and all files within that folder
After a brief loading screen you will see a prompt to register the Tulip Player to your Tulip account.
Registering the Tulip Player
Now that you’ve successfully downloaded and run the Tulip Player it needs to be registered to your Tulip account.
On the Device Registration screen enter the name of your Tulip account in the box next to ‘.tulip.co’.
The name of your account is part of the URL that precedes ".tulip.co" in your address bar when you navigate to Tulip in your browser. For example, the name of the Tulip account below is acme.
Click Register, then login using your Tulip username and password. (Note: this was created when you first logged into Tulip.)
Next, you’ll be prompted to register the device where you are running the Tulip Player.
Enter a name for the device.
Note: We recommend establishing a standard naming convention for all of the devices running Tulip in your operation. It will make it easy to see which devices correspond to the physical shop floor. This will simplify things later on when you’re managing many devices across your instance.
If you are installing Tulip on your computer to test the apps that you are building, you could name it something simple like, “John’s Laptop”
The next step is to create a "Station", or choose a pre-existing Station where you would like to assign the device. Stations allow you to control apps and devices that are running on your production floor. Read more about them here.
Most likely, you will want to create a new station if you are using the computer to test apps.
To create a new station, enter the new station name (could be "My Name Test" if you are testing apps), and assign the station to a group or leave it "Ungrouped".
The last step is to enter a Badge ID to log into this device.
Badge IDs are managed in User Settings in Tulip. Factory. To get started, you can simply log in to Tulip as a generic user by entering “0000” in the Badge ID field.
Now you’re all set to begin running apps on your local computer or Mac.
Running Apps in the Player
To open a specific app in the Player, hit the "Run" button in the top right of the App Editor to open the "development version" of the app. This will allow you to test the app in real-time as you make changes.
Now you are ready to start building apps! Head over to the "Build Your First Frontline Operations App" to get started.
Did you find what you were looking for?
You can also head to community.tulip.co to post your question or see if others have faced a similar question!