LoggerNet Patch (Large) 3.4
Updated: 17-07-2007

  1. Support for Windows NT has been removed.
  2. Enhancement: Applications have been updated to run on Windows Vista (including a new help file format).
  3. Enhancement: New diagnostic window displays error messages when there is a communication failure.
  4. Enhancement: The Troubleshooter can now be customized in regard to the types of warnings that are displayed.
  5. Enhancement: Code has been added to restart the server if an unhandled exception is caught while processing windows events.
  6. Enhancement: The network map is now saved in an XML format, which makes it more robust. NOTE: Network maps from LoggerNet 3.4 are not compatible with previous versions of LoggerNet.
  7. Enhancement: Improved the algorithm for setting datalogger clocks over slower communications links.
  8. Enhancement: Added support for long file names for CR5000 and CR9000X dataloggers.
  9. Enhancement: Added support in the server for BOOL8 variable types.
  10. Enhancement: Increased intrinsic time-out for phone modems to 2 seconds.
  11. Enhancement: New transaction log message that is produced when the server renames an existing data file rather than append to it.
  12. Enhancement: Increased the minimum time between PakBus Serial Packet ring packets from two seconds to 10 seconds.
  13. Bug Fix: Translation string files were missing for Security Manager, ServiceManager, and HoleMonitor.
  14. Bug Fix: If RTMC (or RTMC Pro) was open when you closed LoggerNet, the next time you open LoggerNet you received the message: "The system cannot find the file specified".
  15. Bug Fix: With some monitor configurations, the right-click Move would not work to move an application window.
  16. Bug Fix: If the Toolbar was placed on a secondary monitor, its position on the monitor was not remembered.
  17. Bug Fix: If a network with security enabled was backed up, security might not be enabled when the network was restored.
  18. Bug Fix: A mixed array CSV file was being falsely detected as a binary file when it began with a comma rather than a number.
  19. Bug Fix: If the file format was changed during scheduled data collection, mixed data file formats could end up in one file.
  20. Bug Fix: LoggerNet was converting 7999 to INF for the TOACI1 file formats.
  21. Bug Fix: If a schedule is enabled for a datalogger and LoggerNet is unable to retrieve its table definitions, LoggerNet will only attempt to retrieve the definitions in accordance with the specified schedule and retry intervals.
  22. Bug Fix: The strictest Data Execution Prevention setting in Microsoft Windows was causing access violations in LoggerNet and its clients.
  23. Bug Fix: Several improvements to callback over TCP/IP.
  24. Bug Fix: The server was hanging up a serial link with a CR9000X during a program file send.
  25. Bug Fix: With one-way data collection, when you first sent a program to the datalogger and you had hole collection enabled, the logs showed a very large record number which indicated holes in the data.
  26. Bug Fix: If a PakBus port was bridged while retrieving table definitions, the server could crash.
  27. Bug Fix: When Maximum Time On Line was exceeded for a phone to RF link, the RF modem and the datalogger should be left in an on-line state until they timed out.
  28. Bug Fix: A PakBus port no longer sends a "Goodbye" message to the datalogger when hanging up the link.
  29. Bug Fix: With table-based CR10X/CR23X/CR510 dataloggers doing data advise, if a table came in with no records, any tables after that which did have records were ignored.
  30. Bug Fix: Link failures were not handled properly for some operations including the program file receive and the program file send operations.
  31. Bug Fix: There was an issue where the datalogger would send a beacon followed by a one way message. Over a cell link, the one way message could be delayed. The server had started to close the link when the one way data message finally made it. At this point, the one way message was ignored.
  32. Bug Fix: Fixed a problem that could cause the server to crash when a CRXXX-TD datalogger was configured in the network map as a descendant of an RF95T-PB device type
  33. Bug Fix: Extended the time that the server will wait to check for overwriting its configuration file from one minute to five minutes since this check uses processing time.
  34. Bug Fix: Addressed a communication failure reported through PakBus Graph when the Linux server was polled for PakBus settings.
  35. Bug Fix: Fixed an issue where the server could crash if it tried to write to a log file that was locked by some other process, such as a virus scan program.
  36. Bug Fix: Added a timer to monitor the server's shut-down process.
  37. Bug Fix: Added code to prevent the server from dialing links merely to collect lost holes.
  38. Bug Fix: Added time for file send and file control transactions so that the datalogger has time to finish rebooting before LoggerNet tries to communicate.
  39. Known Issue: Table Fill Times information (Datalogger Status window) is not correct for CR800 series dataloggers.
  40. Known Issue: When running LoggerNet as a service, you cannot write to network drives.
  41. Known Issue: If you ping a device that cannot be reached, the ping window will close.
  42. Known Issue: The timestamps on input locations for mixed array dataloggers are a combination of the time retrieved from the datalogger and LoggerNet's date. With even a slight difference between the LoggerNet clock and the datalogger clock, data can be incorrectly time stamped for data points close to midnight. This incorrect timestamp can cause the graphical display to stop, because the timestamp of subsequent data is older than the timestamp of the last data provided. To remedy this, adjust the datalogger clock to be equal to or slightly ahead of the PC clock. There is no other known resolution, since mixed array dataloggers do not store a complete timestamp.
  43. Known Issue: When upgrading from a previous version of LoggerNet, if the numeric monitor was set to a size other than the default, when the monitor is opened in LoggerNet 3.4 the fonts may be very large. Resizing the window will resize the fonts.
  44. Known Issue: Data Export has been removed from LoggerNet Admin. Use LDEP or LDMP.
  45. Known Issue: Saving a file using Save As in the CRBasic Editor when the instruction panel is closed will result in the error "Cannot focus a disabled or invisible window".
  46. Setup Window Enhancement: Three modems added to Modem Database - Lucent WinModem, Conexant, US Robotics 56K USB.
  47. Setup Window Enhancement: The default setting for PakBus Port Always Open (Setup window) is now disabled (so the PakBus Port is closed unless LoggerNet specifically opens it).
  48. Setup Window Bug Fix: Get Device Type would fail sometimes.
  49. Setup Window Bug Fix: Collapsing a section of the network tree would move the cursor focus to the topmost device in the network.
  50. Setup Window Bug Fix: There were odd characters at the end of lines in the final screen of the Backup Network wizard.
  51. EZSetup Enhancement: Improvements made so it can be navigated without a mouse.
  52. EZSetup Enhancement: Added Data File Output options for mixed array dataloggers.
  53. Connect Window Enhancement: Double-clicking a file in the summary window that is displayed after collecting data opens the file in View.
  54. Connect Window Enhancement: Right-clicking a table name in the Custom Collect window after data collection will open the file in View.
  55. Connect Window Enhancement: Ports and Flags dialog no longer minimizes when the Connect window is minimized.
  56. Connect Window Enhancement: File Control has been moved to the Datalogger menu item.
  57. Connect Window Enhancement: Program name has been added to the Send Program message box.
  58. Connect Window Enhancement: Added a Start/Stop button to the Numeric Displays and Graphs.
  59. Connect Window Enhancement: Improved algorithm for displaying data on Numeric Monitors and Graphs - only the data values being shown on the display are collected, rather than the entire table.
  60. Connect Window Enhancement: Data displays now show fractions of a second for timestamps.
  61. Connect Window Enhancement: When one-way data is being sent by the datalogger, the graphs will now attempt to populate using a formula of the current time - the width of the graph. Previously, one-way data would only be graphed as it was received when the graph was enabled.
  62. Connect Window Enhancement: Added a vertical line marker on graphs that can be enabled by double-clicking the graph.
  63. Connect Window Enhancement: Graphical displays will now be backfilled with data from the data cache (as available) if the graph width is changed to cover a longer period of time.
  64. Connect Window Enhancement: Added Y axis title to the graphical displays.
  65. Connect Window Enhancement: Changed the graphical displays so a graph is still updated when it is minimized.
  66. Connect Window Enhancement: Added a Time of Fill column to Datalogger Status window that shows the estimated time each table will fill.
  67. Connect Window Enhancement: If table definitions were not current, Custom Collect would not collect data.
  68. Connect Window Enhancement: Reset Tables button for table-based dataloggers has been moved from the Custom Collect window to the Datalogger Status window.
  69. Connect Window Enhancement: Pause button added to Terminal Emulator.
  70. Connect Window Enhancement: Terminal Emulator window can be resized.
  71. Connect Window Enhancement: Support added for backspace character in Terminal Emulator.
  72. Connect Window Bug Fix: Cosmetic issues when resizing the window.
  73. Connect Window Bug Fix: Messages from Custom Data Collections were not being stored in the Transaction log.
  74. Connect Window Bug Fix: Improved error messages from Custom Data Collections.
  75. Connect Window Bug Fix: Modifying a value in the Numeric Monitor would cause the monitor to go behind the Connect window.
  76. Connect Window Bug Fix: Displaying a very large array on the Numeric Monitor could cause the monitor to crash.
  77. Connect Window Bug Fix: NAN values for Long integers are now displayed as -2147483648.
  78. Connect Window Bug Fix: Data displays no longer truncate Long integers.
  79. Connect Window Bug Fix: Setting a value in a multi-dimensional array for CR5000 and CR9000(x) dataloggers was setting the wrong element of the array.
  80. Connect Window Bug Fix: If displaying both Public/Input Location and Final Storage Data on the same graph with a large graph width interval, the Y axis could be unreadable.
  81. Connect Window Bug Fix: On a dual processor Windows 2000 PC, if you stopped/started a graph the window moved an inch or so.
  82. Calibration Wizard Enhancement: Updated Calibration Wizard for performing field calibrations on CRBasic programmed dataloggers.
  83. Calibration Wizard Bug Fix: Using a FieldCal instruction that is scalar based (single-valued variables) with KnownVar variable as a particular array element resulted in the error, "The array subscript was incorrect".
  84. File Control Bug Fix: In some instances the CRD would appear to be the selected device, but the directory displayed would be for the CPU (or vice versa).
  85. File Control Bug Fix: The ability to download an OS via File Control has been removed.
  86. Status Monitor Enhancement: Pause Schedule button has been moved so it is not inadvertently clicked when selecting a Status Monitor View.
  87. Status Monitor Enhancement: Added a new Line State statistic to indicate an IP port is waiting for an incoming connection.
  88. Status Monitor Bug Fix: GUI elements (buttons, check boxes, text fields) behave better when window is resized to a very small size.
  89. Status Monitor Bug Fix: An incorrect message was being displayed when collecting data from a datalogger via the Status window and Max Time On Line was reached.
  90. Status Monitor Bug Fix: Communication History window now updates when it is being viewed and new data becomes available.
  91. Status Monitor Bug Fix: The Datalogger Network Views dialog box displayed a red slash circle for the CR800 datalogger.
  92. Hole Monitor 1.3.10 Bug Fix: The application would crash if the LoggerNet server was shut down and certain controls in Hole Monitor were clicked.
  93. Card Convert Version 1.3 Enhancement: Updated to support translation to other languages.
  94. Card Convert Version 1.3 Enhancement: Added ability to save a day of year for table-based timestamps.
  95. Card Convert Version 1.3 Bug fix: Repairing an empty table yielded an error.
  96. Card Convert Version 1.3 Bug fix: In certain instances changes to the Destination File Name dialog were not saved.
  97. Card Convert Version 1.3 Bug fix: Processing data based on date/time with 0 for the time intervals would lock up Card Convert.
  98. Card Convert Version 1.3 Bug fix: Appending data would use last file name instead of Destination File Name.
  99. CRBasic Editor Version 2.8 Enhancement: Added a Save and Send option which allows you to send a program to a datalogger from the Editor.
  100. CRBasic Editor Version 2.8 Enhancement: Added the option to save a compressed file (stripped of remarks and spaces).
  101. CRBasic Editor Version 2.8 Enhancement: New F9 functionality inserts a variable at the cursor location (existing F10 functionality would overwrite existing variable).
  102. CRBasic Editor Version 2.8 Enhancement: Added the ability to turn off syntax checking.
  103. CRBasic Editor Version 2.8 Enhancement: Options | Show Labels will show the table name, output interval, and field names for the Public table and all output tables.
  104. CRBasic Editor Version 2.8 Enhancement: Improved precompiler messages.
  105. CRBasic Editor Version 2.8 Bug Fix: Files with an ampersand in the file name could not be opened from the Recent Files List.
  106. CRBasic Editor Version 2.8 Bug Fix: Cleared bookmarks would return after inserting a variable.
  107. CRBasic Editor Version 2.8 Bug Fix: Next/Previous Bookmark would move to bookmarks in the order they were declared, not in the order they appeared in the program.
  108. CRBasic Editor Version 2.8 Bug Fix: Print Preview would set margins to .01 less than the value entered.
  109. CRBasic Editor Version 2.8 Bug Fix: If no program was opened, the Editor always defaulted to files with a .CR2 extension. The default is now .CR*.
  110. CRBasic Editor Version 2.8 Bug Fix: The Editor always tried to save "Save As" files with uppercase letters.
  111. CRBasic Editor Version 2.8 Bug Fix: Printing in Landscape mode was not repaginating the file.
  112. CRBasic Editor Version 2.8 Bug Fix: Subroutine arguments were showing up in variable list.
  113. DevConfig 1.8 Enhancement: File | Browse Config Files will let you view the saved configuration file for a device.
  114. DevConfig 1.8 Enhancement: More time added to the end of the operating system download process to help avoid the user removing power from the device before the OS load finishes.
  115. DevConfig 1.8 Bug Fix: Problem with the XML configuration file header which would cause it not to render properly in a browser.
  116. DevConfig 1.8 Bug Fix: Screen redraw algorithm could result in black boxes on the application window.
  117. DevConfig 1.8 Bug Fix: Improved OS download for CR9000X.
  118. Edlog 2.6 Bug Fix: Compiler didn't warn of a Table 2 that had instructions but an execution interval of 0.
  119. Edlog 2.6 Bug Fix: Disallow spaces in P84 table names.
  120. Edlog 2.6 Bug Fix: Screen was repositioning when setting reps to a value greater than 1 and pressing Enter.
  121. Edlog 2.6 Bug Fix: In some instances, the Edlog window would not close.
  122. PakBus Graph 1.8 Enhancement: In the (right click) Edit Settings mode, the current settings of the device can be viewed and printed (Summary button), or a new configuration can be loaded in to the datalogger (Read File button).
  123. PakBus Graph 1.8 Enhancement: Now functions as a shared component in CSI's software. This means any time a newer version of the software is installed (with LoggerNet, PC200W, PC400), the old version will be updated (rather than having two different copies on the PC).
  124. PakBus Graph 1.8 Bug Fix: If you edited a setting in the datalogger, that setting would not be applied unless you clicked a field other than the one being set to the new value before pressing Apply.
  125. PakBus Graph 1.8 Bug Fix: When making changes using Edit Settings, there was no warning if the changes were not applied.
  126. PakBus Graph 1.8 Bug Fix: If you resized the window to a very small state, it did not redraw correctly when it was resized larger.
  127. RTMC 2.5.24 Bug Fix: If a time offset was applied in LoggerNet's Setup window, attempting to display station time values in RTMC would cause RTMC to crash.
  128. RTMC 2.5.24 Bug Fix: Time component was limited to 14 characters. It is now unlimited.
  129. RTMC 2.5.24 Bug Fix: The use of parentheses in a datalogger station name would cause set point and switch components to fail.
  130. RTMC 2.5.24 Bug Fix: The number of digits for values in tables were not limited so there were times when a very large number could be displayed in a table cell.
  131. RTMC 2.5.24 Bug Fix: Fixed an issue where a 0 byte project file could be saved.
  132. Split 2.6 Enhancement: Can process larger files.
  133. Split 2.6 Enhancement: The "bad data" indicator will flag bad data, even if there is no screen display.
  134. Split 2.6 Enhancement: Screen display indicates how long it took the file to process.
  135. Split 2.6 Bug Fix: Record numbers greater than 14 characters could not be formatted.
  136. Split 2.6 Bug Fix: Subsecond data now truncates rather than rounding.
  137. Other Applications: The size and maximum number of files can now be set for the CQR log (RF communication quality log). Note: The change must be made using CoraScript.