Version : 4.7
LoggerNet distant (Remote) vous permet de gérer un réseau existant de centrales de mesure à partir d'un emplacement distant sans avoir à investir dans un logiciel LoggerNet Admin complet.
Lire la suiteLoggerNet distant (Remote) vous permet de gérer un réseau existant de centrales de mesure à partir d'un emplacement distant sans avoir à investir dans un autre logiciel LoggerNet Admin complet.
LoggerNet distant ne comprend que les applications "clients" de LoggerNet Admin, qui sont utilisées pour se connecter à un serveur LoggerNet existant sur un PC distant. Il ne comprend pas le serveur LoggerNet.
Veuillez noter : Ce qui suit montre des informations de compatibilité générales. Ce n'est pas une liste complète de tous les produits compatibles.
Produits | Compatibilité | Note |
---|---|---|
CR1000 (obsolète) | ||
CR1000X | ||
CR200X (obsolète) | ||
CR216X (obsolète) | ||
CR300 (obsolète) | ||
CR3000 (obsolète) | ||
CR310 | ||
CR350 | ||
CR5000 (obsolète) | ||
CR6 | ||
CR800 (obsolète) | ||
CR850 (obsolète) | ||
CR9000X (obsolète) |
LoggerNetRem est une collection de programmes 32 bits conçu pour fonctionner sur les ordinateurs équipés de composants Intel, fonctionnant sous les systèmes d'exploitation Microsoft Windows. La configuration de l'ordinateur minimale recommandée pour l'exécution de LoggerNetRem est Windows 7. LoggerNetRem fonctionne également sur Windows 7,8, 11 et 10. LoggerNet Remote fonctionne à la fois avec des systèmes d'exploitation 32 et 64 bits.
Notes:
*Pour nos centrales de mesure CR510, CR10X et CR23X, LoggerNet est compatible avec les systèmes d'exploitation ; mixed array, PakBus® et TD.
**La 21X requiert trois PROM; une 21X équipée seulement de deux PROM n'est pas compatible.
Version disponible | 4.7 |
Système d'exploitation | Windows 11, 10, 8 ou 7 (les système d'exploitation 32- et 64-bit sont compatibles.) |
Exigence | .NET 4.6.2 |
This is a fully functional 30 day trial of the remote version of LoggerNet.
Current LoggerNet users: It is recommended that you install the trial on a computer other than the one running your existing LoggerNet. If that is not practical, we strongly recommend you back up the LoggerNet working directory to prevent backward compatibility issues if you revert to a previous version. To revert you must re-install LoggerNet using the original disk and software key.
Note: 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.
This patch will upgrade LoggerNet, LoggerNet Remote or LoggerNet Admin version 4.0 and newer to 4.9. 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.1. If you are using RTMC Pro 4.3.3 or older or CSI Web Server 1.6 or older and plan to continue creating RTMC projects, we recommend that you opt out on updating RTMC during the install or upgrade to RTMC Pro v5.0.1.
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 11 or 10.
Nombre de FAQ au sujet de(s) LoggerNet Remote: 16
Développer toutRéduire tout
Yes. The download for the trial version is available in the Downloads section of the LoggerNet Remote Product Information page.
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:
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. 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.
No. However, LoggerNet can be upgraded to LoggerNet Admin, which has the same features as LoggerNet Remote.
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.
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.
To connect to a remote computer, either LoggerNet Remote or another copy of LoggerNet Admin is needed. The standard LoggerNet software does not have the ability to log in to a server other than localhost.