LoggerNet Patch (Large) 3.0
Updated: 11-19-2004

  1. Toolbar Enhancement: The new EZSetup client has been added to LoggerNet and can be launched from the Toolbar. The EZSetup wizard will be displayed the first time LoggerNet is launched instead of the Setup Screen.
  2. Toolbar Enhancement: The new Troubleshooter client has been added to LoggerNet and can be launched either via a Toolbar button or from the Tools | Troubleshooter menu item.
  3. Toolbar Enhancement: Toolbar can now launch PakBus Graph, RTMC Run-time, and Task Master clients.
  4. Toolbar Enhancement: The Options | Allow Remote Connections menu item allows the user to configure the Server to allow or disallow remote connections dynamically. The user will no longer have to reinstall LoggerNet to allow or disallow remote connections. LoggerNet must be restarted for the new setting to take effect.
  5. EZSetup Enhancement: The new EZSetup client first introduced in PC400 has been added to LoggerNet to provide a simple, datalogger oriented method to set up communications to dataloggers. Users upgrading from PC400 to LoggerNet in order to use scheduled collection or other LoggerNet features will find that EZSetup eases their transition from PC400.
  6. EZSetup Enhancement: EZSetup allows for setting up and maintaining multiple dataloggers, but the communications devices in the traditional tree-like display are hidden for simplicity.
  7. EZSetup Enhancement: EZSetup allows setting up one level of communications (phone modem or RF or MD9, etc.).
  8. EZSetup Enhancement: EZSetup will not allow for editing loggers that have been setup with multiple levels of communication (e.g. Phone to RF). Text is displayed in the summary window noting that the datalogger must be edited using the Setup Screen.
  9. EZSetup Enhancement: Scheduled collection can be setup in the wizard.
  10. Setup Screen Enhancement: Settings have been segregated on the screen into standard and advanced groups. Standard settings typically must be set, as the defaults won't necessarily be applicable. Advanced settings are settings that rarely need changing.
  11. Setup and EZSetup Enhancement: The Setup and EZ-Setup Screens and CoraScript use the new Locking feature of the server. This means that only one client is allowed to make changes to the network map or device settings at a time. The Setup Screen obtains the lock when an edit has been made. If the apply button is enabled, the Setup Screen has the lock. Edits to the network map using EZ-Setup or Cora Script, or even another Setup Screen (in a future LoggerNetAdmin) can be viewed in the Setup Screen as they are made.
  12. Setup Enhancement: Settings have been added to configure LoggerNet for receiving incoming transmissions from an AirLink modem (Raven or PinPoint) with a dynamic IP Address by accepting a UDP packet from the modem announcing the new IP address. Note that the modem must be configured with LoggerNet's IP address. This makes it possible to use these IP modems without a fixed IP address from the service provider.
  13. Setup Enhancement: The new server supports independent PakBus addresses for individual PakBusPorts, effectively allowing you to isolate subnetworks from each other. The Setup screen offers a pull-down menu item to set the LoggerNet PakBus settings and bridge or not bridge the individual ports to create PakBus 'subnets' or to allow the server to route packets from dataloggers in one PakBus subnetwork to dataloggers in a separate PakBus subnetwork.
  14. Setup Enhancement: Users can now check and set the clock as well as send programs to dataloggers from tabs on the Setup Screen.
  15. Setup Enhancement: A new tab was added to the PakBus device setup to display a list of nodes available in the PakBus Network that are not yet represented in the LoggerNet network map. The purpose of this tab will be to assist in adding PakBus devices to the LoggerNet network map. Once the new node is displayed, clicking the 'Get Device Type' button will query the device for its type. If a recognized device type is returned then the 'Add to Network Map' button will be enabled and the selected node can then be added to the PakBus port selected in the network map. The user can initiate a search for PakBus nodes by clicking the 'Start Search' button. Only nodes from which the user wants to collect data should be added to the network map.
  16. Connect Screen Enhancement: All functionality is accessible to the user without having to 'connect' to the logger first. If not connected the server will connect to the datalogger to accomplish the action requested (e.g., send program or check clock), and then hang up the link.
  17. Connect Screen Enhancement: A 'Check Clocks' button has been added. This feature is enabled whenever the automatic clock update is not on.
  18. Connect Screen Enhancement: The advanced custom collection options for classic dataloggers contain more information about the modem pointer values. They show both the value of the pointer being used by scheduled collection and the pointer being used for custom collection. The user is only allowed to adjust the custom collection modem pointer.
  19. Connect Screen Enhancement: The Status Table is available from table- based dataloggers by clicking the Tools | Status Table menu item. To view data that extends beyond the width of the field or is multi-line data (such as strings from a CR1000 or the PakBus routing table), use the right-click option, View Value. The user may attempt to set values for Status table fields. This is done by using the right- click option, Modify Value. The user can then enter the new value for this field and press Enter to apply. The user will be notified if the value cannot be changed. The Refresh Values button prompts LoggerNet to query the datalogger and update the values again. A subset of status values can be displayed by clicking the Select Fields button. This will display a list of the status data available in the datalogger. Select one or more of the fields and then press OK. The current values will be displayed in the table.
  20. Connect Screen Enhancement: Numeric and Graph Screens. When open with the Connect Screen in a 'Connected' state, the Numeric and Graph Screens will update the display for input locations and public variables at the interval selected on that screen. Final storage values will not be updated for mixed-array dataloggers unless collected manually via the Collect Now button or automatically via scheduled retrieval. Final storage values for table- based dataloggers will be updated, but only for the display ' they will not be added to PC final storage data files unless explicitly collected manually or via scheduled retrieval. When in a 'Disconnected' state, only final storage values will be updated, and then only if final storage is explicitly collected manually or via scheduled retrieval. Ports and Flags pop-up: When the Connect Screen is in a 'Connected' state, this display will update once per second. When 'Disconnected' this display will only be updated when the ports and flags table is included in an explicit manual or scheduled data collection.
  21. Connect Screen Enhancement: New Options in Graph Screen: The printing, copying, and saving options are now accessible only through the popup menu. The user can view a print preview of their graph. The user can select the color of the X-axis grid lines just like they could the Y-Axis grid lines. The update interval has been moved to the main window. The user can choose the data precision they wish to use. This is done on the 'Options' dialog on the 'Data Display' tab. The user has the option of showing the label for each data point for a selected trace. This is done via the 'Trace Options' window using the 'Show Values' check box.
  22. File Control Enhancement: The properties button has been removed. A delete button has been added. The user can now pause and resume a program.
  23. Status Monitor Enhancement: The network map is indented to match the view in the setup screen.
  24. Status Monitor Enhancement: A communications history is available to the user for each device. The Historical Graph in the StatGrid has 72 records (vertical bars). Each record represents 10 minutes for a total of 12 hours. The height of each bar is calculated by the following equation: Height = (Failures + Retries) / Attempts.
  25. Status Monitor Enhancement: The Color of each bar is determined by the following rules: Green: No Retries, No Failures Blue: Retries, No Failures Red: Failures Gray: No Attempts
  26. Status Monitor Enhancement: Every device has an image of that device type next to it.
  27. Status Monitor Enhancement: A trouble shooter image (graphic exclamation point symbol) can appear next to a device that is having some type of trouble.
  28. Status Monitor Enhancement: The user cannot launch the Task Master from the Status Monitor.
  29. Status Monitor Enhancement: The user can launch the Trouble Shooter from via the right-click menu option.
  30. Status Monitor Enhancement: The low level logs are accessible from the Status Monitor through the LogTool.
  31. Status Monitor Enhancement: The user can sort the statistics by column.
  32. Troubleshooter Enhancement: The Troubleshooter is a new screen in Version 3.0 and offers a quick snapshot of the network health. Any device having problems is shown with an exclamation mark next to it. Text about each device is shown in a text window to the right of the network. Any warnings or errors are shown in blue or red.
  33. Troubleshooter Enhancement: The following errors are monitored and displayed: Network schedule is paused. Scheduled collection is disabled for a datalogger. Table definitions are invalid. Table definitions are empty. TAPI Line is not selected. Phone number is blank. IP address is not set. MD9 switch ID is 0 (still the default). RF95 switch ID is 0 (still the default). PakBus ID is not unique. RF400 Network Id is 0 (still the default). RF400 Radio Id is 1 (still the default). Communication status is marginal. Communication status is critical. Average error rate (>5% shown in blue, >20% shown in red).
  34. Troubleshooter Enhancement: The information text given is updated automatically although the automatic update can be paused. The user can then manually update the information using the Manual Update button.
  35. Troubleshooter Enhancement: Other information about devices such as PakBus ID, phone Number, etc., is also given. A Show Potential Problems Only check box can make it so only warnings and errors are only shown.
  36. Troubleshooter Enhancement: The user can identify a datalogger on a communication link. This reveals the protocol used in the datalogger and display the model and PakBus ID, if found.
  37. Troubleshooter Enhancement: The user can launch the LogTool and PakBus Graph clients.
  38. Communication Test: The Communication Test button has been moved to the Troubleshooter.
  39. Communication Test: If a communication test fails, an attempt is made to find a datalogger on the communication link. If a logger is found, the protocol is displayed along with the model and PakBus ID, if available.
  40. Communication Test: The legend can be toggled on or off using the Show Legend checkbox.
  41. Task Master: A button is available from the LoggerNet toolbar to launch the Task Master screen. The Task Master does not run in the background as a separate application. It is part of the toolbar and runs invisibly to the user. The TaskMaster.exe program is an interface for this 'Task Engine'. Closing the Task Master will not stop the task engine from running tasks. The user can check Pause Tasks on the Status tab of this screen or disable tasks from the Options menu item on the Toolbar.
  42. Task Master: New station event types available: After Failed Retry: A primary retry collection attempt has failed. After Primary Retries Failed: All primary retry collection attempts have failed.
  43. PakBus Graph: A search feature has been added to search for new nodes on LoggerNet PakBus port.
  44. PakBus Graph: The setting dialog (accessed via a right- click on a device) provides an editable list of the PakBus settings for the device. When a setting is selected, a description of the setting is provided. Setting PakBus settings has been simplified by providing enumerations and spin buttons.
  45. PakBus Graph: Nodes can once again be moved using the mouse. Node positions are temporary, however, and will be reset the next time the nodes are laid out.
  46. LogTool: All server log monitoring and settings have been moved into the LogTool client.
  47. LogTool: Specific log windows can be shown or hidden using their respective toolbar buttons or the Options->Logs to Show menu.
  48. LogTool: Warning and Error Communication Log messages are colored Blue and Red respectively.
  49. LogTool: Warning, Error, and Status Communication Log messages can be toggled on/off, so that only those log messages selected will be shown.
  50. LogTool: Logs messages for specific devices can be parsed from the logs by selecting 'Show All Msgs', 'Select by Device' and 'Select by Station' using the combo box at the top of the window.
  51. LogTool: Text from each Log window can be copied to the clipboard, saved to file, or printed via a right click menu on each log window. Saving to file and printing can also be accomplished via the File menu.
  52. LogTool: Timestamps for log messages can be set to: Date, military time, and ms Resolution from a menu item, Options->TimeStamp Options.
  53. LogTool: Clear All and Pause All buttons were added.
  54. LogTool: I/O (Low Level Log) windows can be shown using the View I/O toolbar button or the Options->View I/O menu. They also can be shown via a popup menu shown by right clicking a device in the network view.
  55. LogTool: Individual Log toolbars and the parse window (network view window) can be shown/hidden via their respective toolbar buttons.
  56. RTMC: Auto tabbing can now be enabled on a project along with specifying a tab interval. When the project is loaded in the RTMC Run-time, each tab will be displayed on the specified interval.
  57. RTMC: The time, graph, and table display components now have a timestamp format option that will use the system default based off system settings and locale
  58. DevConfig: The device configuration utility (DevConfig) allows users to set up dataloggers and intelligent peripherals before those devices are deployed in a customer's application and before these devices are set up in applications like LoggerNet. This utility is particularly suited to setting up PakBus devices.
  59. DevConfig: Direct RS-232 serial connection to the device is required.
  60. DevConfig: The Deployment screen can set datalogger clocks and send programs.
  61. DevConfig: A separate tab sends operating systems to supported devices.
  62. DevConfig: DevConfig can determine a datalogger's type. This is particularly useful with dataloggers like the CR10X where the operating system version in the datalogger is not known.
  63. DevConfig: A generic settings editor similar allows the user to view and/or edit all of the settings defined for that device.
  64. DevConfig: The utility provides a configuration reporting facility where a summary of the current configuration of a device can be shown on the screen and printed.
  65. DevConfig: DevConfig can save the configuration of a device into a file for restoring that configuration to the same device or copying it to similar device.
  66. DevConfig: A terminal emulation screen is provided for a connected device where this is appropriate.
  67. DevConfig: The utility will ship with applications like LoggerNet and PC400 and will also be available as a free download from Campbell Scientific's web site.
  68. CRBasicEditor: When a user opens a new program, a template on the screen gives the user the structure of a CRBasic program with sample instructions. This template can be modified and saved as the new default.
  69. CRBasicEditor: The user can now select the CR200 compiler to be used from the CR200 compilers available on his/her machine.
  70. CRBasicEditor: CRBasicEditor detects duplicate variable names with a message at the bottom of the screen. Double-clicking on the message line will cause the error line to be highlighted in red.
  71. CRBasicEditor: CRBasicEditor detects embedded blank characters in variable declarations with a message at the bottom of the screen. Double- clicking on the message line will cause the error line to be highlighted in red.
  72. CRBasicEditor: Several changes have been made to support the CR1000. The Boolean, float, long, and string data types with new instruction boxes have been added to support the Public and Dim statements. The new instruction boxes use the F2 shortcut key to popup the list of data types for those who prefer using the keyboard to the mouse.
  73. CRBasicEditor: The Call statement instruction box gives a list of subroutines to call. Right-clicking the SubName in the Call instruction will also give a list of subroutines.
  74. CRBasicEditor: Similarly, the CallTable instruction gives lists of table names in both the CallTable instruction box and when right-clicking the table name in the instruction.
  75. CRBasicEditor: The behavior of instruction insertion has been modified such that an instruction inserting at the beginning of an empty line will have the cursor moved to the start of the next line while an instruction inserted at the middle or end of a line will have the cursor placed at the end of the instruction line where the instruction was inserted.
  76. CRBasicEditor: Indentation and vertical spacing features can be triggered from the Options | Editor Preferences' menu item. Options include using tabs or spaces for the indentation, the tab width or number of spaces to indent, and vertical spacing parameters. Once the user has set up the indentation/vertical spacing parameters, the Edit | Rebuild Indentation menu item (CTRL-I) is used to reformat the program.
  77. CRBasicEditor: CRBasicEditor will now show whether parentheses are matched in instructions and equations. Whenever the cursor is placed immediately inside a left or right parenthesis, the CRBasic Editor will check to see if there is a matching opposite parenthesis in the line. If a matching parenthesis is found, both are highlighted in the color and style specified by the user in the Options | Editor Preferences' | Editor Options - Syntax Highlighting.
  78. Short Cut: Advanced Output can be enabled (disabled by default) on the Output screen. If more than one condition is enabled they are ANDed together.
  79. Short Cut: Users can select multiple (contiguous) measurements for output on the Output screen. Only outputs allowed for all selected measurements will be enabled.
  80. Short Cut: Drag-and-drop now works to reorder outputs on Output screen.
  81. Short Cut: Individual members of rep blocks can be renamed on the Sensors screen.
  82. Short Cut: Users can override allowed (recommended) outputs on Output screen with a right-click.
  83. Short Cut: A 50 or 60 Hz noise rejection option in available from the Settings pull-down menu.
  84. Short Cut: Alternative compilers can be selected for the CR200 Series dataloggers from the Settings pull-down menu.
  85. Transformer: Transformer is a new tool to convert CR10X (mixed-array OS only) Edlog program (.dld or .csi) to a CR1000 CRBasic program (.CR1). This tool was designed for customers who are familiar with Edlog and / or have existing .dld or .csi files and need some help in moving to the CRBasic.
  86. Transformer: Transformer may not be able to convert all of the instructions and features in an Edlog CR10X program into a CR1000 CRBasic program, and the result may not be the best way to accomplish the functionality in CRBasic.
  87. Transformer: Transformer does imports and display a CR10X .dld (automatically documents a dld file) or .csi file in theleft frame ('Source') of the window and 'transforms' CR10X instructions to comparable CR1000 instructions. It then creates a .CR1 file including transformation metadata in the right frame ('Program') and creates a separate file containing 'problem' and / or 'information' messages ('Action Log') which is also displayed in the bottom frame. References to problems or missing instructions are noted as comments in the CRBasic code. Transformer can then launch the CRBasicEditor to open with the newly created CRBasic program.
  88. LoggerNet Server: Created new settings that will apply to table datalogger collect areas that will govern what data is collected when a "first poll" condition is detected, i.e., when the area has not been polled since it was created or when an "uncollectable hole" is detected at the start of polling an area. New settings are also available for each time the table is polled.
  89. LoggerNet Server: Reintroduced support for RF95T base and remote devices for BMP1 networks. This support originally existed in LoggerNet 1.x but was removed from LoggerNet 2.x due to complications of supporting it under PC208W's polling and batch processing model. Data advise is supported by the server and can be enabled via CoraScript, but settings to govern it are not exposed in the LoggerNet 3.0 Setup screen.
  90. LoggerNet Server: Users can send .CR2 files through the program file send transaction. The server's implementation of that transaction for CR2xx dataloggers would invoke the compiler appropriate for the datalogger OS version and send the resulting .BIN file to the datalogger. This operation would be transparent to the user.
  91. LoggerNet Server: When detecting a call-back event, the server can 'auto baud detect'. The initial port baud rate is the lowest of the max baud rates for all devices attached to that port that are enabled for call-back. As framing errors occur, the baud rate will be automatically adjusted downward until it reaches 300 baud. If framing errors continue, the baud rate would start again as it was at the beginning.
  92. LoggerNet Server: While collecting 'last X arrays' from classic datalogger final storage areas, the modem pointer is set to the datalogger's reference pointer if it isn't already equal before the server issues the "B" command.
  93. LoggerNet Server: The server architecture now has a different PakBus router assigned to each PakBus port object as the default. A new device setting for PakBus port objects was also created to set the PakBus address for that port. If two or more PakBus port objects share the same value for this setting, then they will be part of the same PakBus network and share the same router. The LgrNet setting that currently identifies the computer PakBus address was made obsolete. As long as two PakBus port objects have different router address setting values, the nodes that belong to them can have duplicate PakBus addresses.
  94. LoggerNet Server: A new setting, "hangUpDelay", was created and applies to all devices. This setting specifies an interval, in milliseconds, that the server waits before hanging up the link after the "last command" has been executed. The effect of the setting would be that the device will stay in an "on-line" state for up the specified period in case anything else needs to be done with that link. By setting this interval to a value greater than the normal polling interval for a station, the user can effectively specify that LoggerNet should keep the link open to the station all of the time, just as if there was a client that had a 'manage comm' resources transaction going with that device.
  95. LoggerNet Server: A new LgrNet transaction was created that allows a client to obtain a 'lock' on the entire network. Once this lock is obtained by a client, any other attempts to lock the network by other clients will be rejected until the owning client releases the lock or the lock times out. This lock also prevents any of the following transactions from being performed from any other connection than that on which the lock was obtained: LgrNet Add Device, LgrNet Rename Device, LgrNet Move Branch, LgrNet Delete Branch, LgrNet Set Settings, LgrNet Modem Change, LgrNet Modem Add,LgrNet Modem Delete, Device Set Settings, Device Set Collect Area Settings (for permanent areas), Device Program File Send, Device File Send, Device File Control. These transactions were changed so that their response codes reflect this condition and report when transactions are not allowed due to a lock. The lock transaction will expire if the server loses the session that started the lock. The transaction locks the program file send, file send, and file control transactions because these can cause the server to create and/or destroy collect areas.
  96. LoggerNet Server: A collection mode was implemented for table based collect areas where the table interval and the time stamp of the newest record collected from the datalogger is considered before attempting to collect from a table. The server projects what the datalogger time would be based upon the computer clock and the difference of the two clocks the last time the datalogger clock was read. If the time stamp of the last record read from the datalogger plus the table interval is greater than the projected datalogger clock value, that area would not be collected.
  97. LoggerNet Server: The server accepts one way data notifications from PakBus dataloggers.
  98. LoggerNet Server: The server accepts UDP packets from an AirLink modem (Raven or PinPoint) containing a new dynamic IP address.
  99. LoggerNet Server: A new invalid table definitions policy allows the user to determine whether all data collection should be stopped if table definitions are thought to be invalid or whether the server should merge the changes in and continue with collection.