About the SCADAR.NET web application
The SCADAR.NET web application is a dedicated software product used by designers, specifiers, installers, and users of compressed air equipment.
The SCADAR.NET web application is used in conjunction with SCADAR equipment to audit the use of compressed air equipment. Use this link to learn about SCADAR equipment CLICK HERE
SCADAR.NET features a variety of graphing, charting, simulation and reporting tools.
Visit the SCADAR.NET site and create an account. There's a sample audit included with new accounts that can be used to learn more about the web application. Use this link to open SCADAR.NET in a new tab... CLICK HERE
SCADAR.NET web application 'browser' compatibility
SCADAR.NET is a web application. Consequently it requires a compatible PC 'web browser'. The following web browsers are supported... Google Chrome Mizilla Firefox Internet Explorer SCADAR.NET may operate on other web browser products. SCADAR.NET ...
SCADAR.NET web application 'platform' compatibility
SCADAR.NET is a web application. To operate the SCADAR.NET App users will need an appropriate platform device and web browser. Platform devices are widely catagorised as 'PC's', 'Tablets' and 'Smartphones. Although SCADAR.NET may operate on many ...
What is SCADAR.NET
SCADAR.NET is a web application. A web application is a client-server software application in which the client (or user interface) runs in a web browser. In simple terms, this means the SCADAR.NET application software is hosted elsewhere (on a ...
What is SCADAR
SCADAR is an advanced data logging (equipment) and web application (software) solution that enables compressed air equipment and systems to be easily audited. The SCADAR name is an acronym for 'Structured Compressed Air Data Analysis & Reporting'.
How does the Base Station communicate with SCADAR.NET? What IP address does it use? And other network related questions...
If you think you're experiencing a network related issue which is preventing your Base Station from connecting to the Cloud, here are the first two things you should try: Try running the B2C or C2B step from a different location using a different ...