Windows Based Signage Publishing Server
Budget: $15 – $25 USD
Introduction:
We are building a local windows-based server application for publishing to a Novastar Taurus player. We will be using the existing API/SDK for the Taurus system. All communications will go through a windows server application that users can connect to by local IP. Users will need an interface to create schedules of content and export to the existing network connected player.
The primary use is for digital message centers.
Taurus Series Player:
The primary test device is the TB40 player/controller. SDK information is available in the link below.
https://docapi-us.vnnox.com/web/#/4?page_id=286
User Interface:
Local web address supported by Google Chrome. IP to be set in settings of server. Fit/finish to be similar to ViPlex express.
Local Server:
To be installed on Windows Server 2022. Provide an interface for up to 10 users at a time to create schedules and manipulate content as similar to ViPlex.
a. Build platform to be QT, Flutter, or Visual Studio
b. C+++ is the preferred language
c. System must support up to 50 unique connected devices (i.e. 50 TB40 players)
d. Each user is prompted for username/password at login. Each instance is unique and user device login is
e. Up to 10 users logged in simultaneously and 50 unique users
f. Each user can store up to 10 schedules/solutions. Content will be stored on server.
Dev Structure:
Github will be the basis for tracking progress with daily commits. Pay will be set based on time worked at a pre negotiated rate.
A remote PC with local connection to a TB40 will be setup with remote access as a testing and development sandbox.
We are building a local windows-based server application for publishing to a Novastar Taurus player. We will be using the existing API/SDK for the Taurus system. All communications will go through a windows server application that users can connect to by local IP. Users will need an interface to create schedules of content and export to the existing network connected player.
The primary use is for digital message centers.
Taurus Series Player:
The primary test device is the TB40 player/controller. SDK information is available in the link below.
https://docapi-us.vnnox.com/web/#/4?page_id=286
User Interface:
Local web address supported by Google Chrome. IP to be set in settings of server. Fit/finish to be similar to ViPlex express.
Local Server:
To be installed on Windows Server 2022. Provide an interface for up to 10 users at a time to create schedules and manipulate content as similar to ViPlex.
a. Build platform to be QT, Flutter, or Visual Studio
b. C+++ is the preferred language
c. System must support up to 50 unique connected devices (i.e. 50 TB40 players)
d. Each user is prompted for username/password at login. Each instance is unique and user device login is
e. Up to 10 users logged in simultaneously and 50 unique users
f. Each user can store up to 10 schedules/solutions. Content will be stored on server.
Dev Structure:
Github will be the basis for tracking progress with daily commits. Pay will be set based on time worked at a pre negotiated rate.
A remote PC with local connection to a TB40 will be setup with remote access as a testing and development sandbox.