Current Version: 4.7
LoggerNet Remote lets you manage an existing LoggerNet data logger network from a remote location without investing in another complete LoggerNet Admin software package.Leer más
LoggerNet Remote lets you manage an existing LoggerNet datalogger network from a remote location without investing in another complete LoggerNet Admin software package.
LoggerNet Remote includes only the LoggerNet Admin clients that are used to connect with an existing LoggerNet server on a remote PC. It does not include the LoggerNet server.
|Operating System||Windows 10, 8, or 7 (Both 32- and 64-bit operating systems are supported.)|
Nota: lo siguiente muestra información de compatibilidad notable. No es una lista de todos los productos compatibles.
|21X (retired)||The 21X requires three PROMs; two PROM 21X Microloggers are not compatible.|
|CR10X (retired)||Compatible with the mixed array, PakBus, and TD data logger operating systems.|
|CR23X (retired)||Compatible with the mixed array, PakBus, and TD data logger operating systems.|
|CR510 (retired)||Compatible with the mixed array, PakBus, and TD data logger operating systems.|
LoggerNet Remote is a collection of 32-bit programs designed to run on Intel-based computers running Microsoft Windows operating systems. The recommended minimum computer configuration for running LoggerNet Remote is Windows 7. LoggerNet Remote also runs on Windows 8 and Windows 10. LoggerNet Remote runs on both 32-bit and 64-bit versions of these operating systems.
This patch will upgrade LoggerNet, LoggerNet Remote or LoggerNet Admin version 4.0 and newer to 4.7. A version of LoggerNet 4.x must be installed on the computer.
Note: This patch includes RTMC Run-time and the RTMC Standard Development v5.0. If you are using RTMC Pro 4.3.3 or older and plan to continue creating RTMC projects, we recommend that you upgrade to RTMC Pro 5.0.
LoggerNet Admin and Remote:
A change was made in the way the LoggerNet 4.6 Server performs "Custom Data Collection". A corresponding change was made in the Connect Screen 4.6 client "Custom Data Collection" functionality.
If you require "Custom Data Collection" functionality with the Connect Screen client, assure that the LoggerNet Servers and Connect Screen clients are 4.6 or higher.
This application requires the Microsoft .Net 4.6.2 Framework. If it is not already installed on your computer, it can be obtained from the Microsoft Download Center.
Supported Operating Systems: (32 and 64 bit) Windows 10, 8.1, 8 or 7.
Número de FAQs relacionadas con LoggerNet Remote: 16
Expandir todoDesplegar todo
LoggerNet doesn’t know which tables are available in mixed-array dataloggers unless the program is identified by associating it. If no tables show up in the Data Filer table selection window, check that there is a program associated with the datalogger in LoggerNet. This can be done on the Program tab of the LoggerNet Setup screen. Also, verify these two things:
Yes. This combination will result in a LoggerNet Admin installation with all of its features. However, Campbell Scientific does not recommend this process because installing different versions of LoggerNet and LoggerNet Remote can result in inconsistent software behavior.
On the LoggerNet Setup screen, on the Data Files tab, select Create Unique File Name as a File Output Option. The Create Unique File Name option is not available for storage modules or mixed-array dataloggers. In these situations, use Split or a batch file to accomplish the same results.
LoggerNet Remote (LOGGERNETREM) is a separate product available for purchase.
Yes. All of the standard LoggerNet clients that are capable of accessing remote servers (such as Setup, Connect, or Status) include a Select Server dialog box under the application’s File menu.
LoggerNet Admin contains all of the capabilities of LoggerNet Remote. Additional copies of LoggerNet Remote are purchased separately. Because using different versions of LoggerNet and LoggerNet Remote can result in issues, Campbell Scientific recommends purchasing the LoggerNet Admin Upgrade.
LoggerNet Remote does not include the LoggerNet communication server. It was designed to connect to a LoggerNet communication server that is running elsewhere and can be accessed over TCP/IP. LoggerNet Remote cannot be used to connect directly to a datalogger because there is no communication server running. LoggerNet Remote does not have the files necessary to connect to a datalogger directly.
Yes. To install LoggerNet on a centralized server and run it as a service, LoggerNet Admin needs to be installed on the server. Assuming there are open communications paths, LoggerNet Admin can be set up to control/access two or more datalogger networks. However, if users would like to control two networks on separate PCs, a copy of LoggerNet Remote is needed for each PC accessing LoggerNet Admin on the servers.