LoggerNet Patch (Large)

Enhancements: The auto-reconnect interval for the Connect window was changed to 2 seconds.

Bug Fix: Fixed setting ports & flags for CR9000 datalogger.

Bug Fix: Collecting a sample of a Boolean True value would be stored in the data file as a 1. Changed to -1.

Bug Fix: If the All Caps mode option was selected in the Terminal Emulator when not connected to a device an error would occur.

Bug Fix: The Select Device list in the Terminal Emulator has been changed so that it cannot be edited manually.

Bug Fix: If a connection was attempted with a datalogger connected via RF and the connection to the RF remote failed, in some instances LoggerNet would connect to the RF base.

Bug Fix: Made changes so that LoggerNet can work properly with a last modified date string returned by the datalogger for files.

Known Issue: If a backup of the network is performed and a filename is not specified for the backup file, the file will be saved as year-month-day_hour-minute-seconds.snapshot. This *.snapshot file can be loaded into LoggerNet by renaming the file with a *.bkp extension.

Known Issue: When doing a Custom Collection from the Connect window, if you select the CSV file format and apply formatting changes (such as removing the time and date stamp), and then return the file format option to TOA5 or Binary, the settings for the CSV file are incorrectly applied to the new file format.

Setup Window: Made some changes to the behavior of the File dialog box for the Backup/Restore option when a file name is not specified.

Setup Window: Added an hour glass cursor to indicate LoggerNet is "busy" when saving changes to large networks.

Connect Window: In some instances, once the ports and flags dialog box was opened for a datalogger it would always open when the Connect window was opened.

Connect Window: If a program file was sent from the network and then the computer was disconnected from the network, the Send (program) button could get into a state so that nothing would happen when Send was pressed.

Connect Window: Pressing the Connect button to bring it to the front of other application windows would change the original position of the window on the screen if it had been moved.

Connect Window: Reimplemented the ability to plot Boolean values on a graph.

Connect Window: Under certain conditions, the Numeric Display would stop updating.

Connect Window: If the Override the Autoupdate option was chosen for a Numeric Display, there were instances where the update rate would be set to 5 seconds if you stopped and then restarted a display.

Connect Window: The Numeric Displays were updating only when the record number updated for the datalogger. Thus, if values were being updated in a loop, the user would never see this update.

Connect Window: Choosing Restore Default Configuration in a Numeric Display could cause text in a cell to be right-aligned.

Connect Window: Resolved an error that appeared in the Custom Collection window when trying to apply a directory choice to all tables.

Connect Window: In certain circumstances a cancelled data collection in the Custom Collection window would not abort.

Connect Window: When doing a Custom Collection, the file name would be incorrect for the "Create New File" option if a period was used in the directory name.

Connect Window: If a data table had only two records (record 0 & 1), only the second record (1) would be collected with a Custom Collection.

File Control: Canceling a send operation would not always stop the file send.

File Control: Could not send files to a datalogger using File Control.

File Control: Fixed some problems with the behavior of the Run Options dialog box.

File Control: If a card was full when trying to send a file, the error message erroneously indicated that the CPU was full instead of the card full.

CRBasic Editor 2.9 Enhancement: New support files for all CRBasic dataloggers have been added to the CRBasic Editor.

CRBasic Editor 2.9 Enhancement: New Editor Options (Options | Editor Preferences) - Added the ability to turn off case auto correction of key words (Enable Keyword Capitalization check box). - Added the option to use spaces or tabs when the tab key is pressed or when auto indenting is performed, and the ability set the number of spaces used when spaces is chosen.

CRBasic Editor 2.9 Enhancement: A list of all CRBasic short cut keys can be displayed from the Options | Show Keyboard Shortcuts menu item or by using CTRL+K.

CRBasic Editor 2.9 Enhancement: If a word is highlighted and the Replace function is chosen, the highlighted word will be placed in the Search box for the replace.

CRBasic Editor 2.9 Enhancement: Added the ability to associate program file extensions with the CRBasic Editor in the Windows operating system (Options | Associate Files) so they are automatically opened in the CRBasic Editor when double-clicked in Windows Explorer.

CRBasic Editor 2.9 Enhancement: The Save & Send dialog now remembers the last datalogger to which a program was sent.

CRBasic Editor 2.9 Enhancement: Programs are now precompiled prior to sending the file when Save & Send is used.

CRBasic Editor 2.9 Bug fix: When using the up or down bookmark arrows to go to the next or previous bookmark, the bookmarks were visited in the order added to the Editor, not in the order they appeared in the program.

CRBasic Editor 2.9 Bug fix: In the parameter dialog box for adding variables (Public or Dim), adding new variables and pressing Next would incorrectly add parenthesis around the variables.

CRBasic Editor 2.9 Bug fix: The Replace function was replacing the first instance twice.

CRBasic Editor 2.9 Bug fix: Fixed several issues with opening the CRBasic Editor if a network printer was selected as the default printer, but the computer was not connected to the network.

CRBasic Editor 2.9 Bug fix: If LoggerNet was closed with the CRBasic Editor maximized, it would not return to a maximized state when LoggerNet was restarted.

CRBasic Editor 2.9 Bug fix: Fixed instances where the Search & Replace dialog box was covering other windows or losing focus when it shouldn't have.

CRBasic Editor 2.9 Bug fix: A CR9000 datalogger would not show up in the list of dataloggers for the Save & Send dialog box.

CRBasic Editor 2.9 Bug fix: The compiler message was being omitted when you saved and compiled a compressed file.

CRBasic Editor 2.9 Bug fix: If a specific compiler was chosen for the CR200 datalogger prior to saving the program to a file name, the program would always be compiled with the default compiler.

CRBasic Editor 2.9 Bug fix: An access violation would be displayed if help were chosen from the menu and no file was opened.

PakBus Graph 1.8: Unlocking the position of a node did not have any affect.

Support for Windows NT has been removed.

Enhancement: Applications have been updated to run on Windows Vista (including a new help file format).

Enhancement: New diagnostic window displays error messages when there is a communication failure.

Enhancement: The Troubleshooter can now be customized in regard to the types of warnings that are displayed.

Enhancement: Code has been added to restart the server if an unhandled exception is caught while processing windows events.

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.

Enhancement: Improved the algorithm for setting datalogger clocks over slower communications links.

Enhancement: Added support for long file names for CR5000 and CR9000X dataloggers.

Enhancement: Added support in the server for BOOL8 variable types.

Enhancement: Increased intrinsic time-out for phone modems to 2 seconds.

Enhancement: New transaction log message that is produced when the server renames an existing data file rather than append to it.

Enhancement: Increased the minimum time between PakBus Serial Packet ring packets from two seconds to 10 seconds.

Bug Fix: Translation string files were missing for Security Manager, ServiceManager, and HoleMonitor.

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".

Bug Fix: With some monitor configurations, the right-click Move would not work to move an application window.

Bug Fix: If the Toolbar was placed on a secondary monitor, its position on the monitor was not remembered.

Bug Fix: If a network with security enabled was backed up, security might not be enabled when the network was restored.

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.

Bug Fix: If the file format was changed during scheduled data collection, mixed data file formats could end up in one file.

Bug Fix: LoggerNet was converting 7999 to INF for the TOACI1 file formats.

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.

Bug Fix: The strictest Data Execution Prevention setting in Microsoft Windows was causing access violations in LoggerNet and its clients.

Bug Fix: Several improvements to callback over TCP/IP.

Bug Fix: The server was hanging up a serial link with a CR9000X during a program file send.

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.

Bug Fix: If a PakBus port was bridged while retrieving table definitions, the server could crash.

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.

Bug Fix: A PakBus port no longer sends a "Goodbye" message to the datalogger when hanging up the link.

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.

Bug Fix: Link failures were not handled properly for some operations including the program file receive and the program file send operations.

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.

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

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.

Bug Fix: Addressed a communication failure reported through PakBus Graph when the Linux server was polled for PakBus settings.

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.

Bug Fix: Added a timer to monitor the server's shut-down process.

Bug Fix: Added code to prevent the server from dialing links merely to collect lost holes.

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.

Known Issue: Table Fill Times information (Datalogger Status window) is not correct for CR800 series dataloggers.

Known Issue: When running LoggerNet as a service, you cannot write to network drives.

Known Issue: If you ping a device that cannot be reached, the ping window will close.

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.

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.

Known Issue: Data Export has been removed from LoggerNet Admin. Use LDEP or LDMP.

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".

Setup Window Enhancement: Three modems added to Modem Database - Lucent WinModem, Conexant, US Robotics 56K USB.

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).

Setup Window Bug Fix: Get Device Type would fail sometimes.

Setup Window Bug Fix: Collapsing a section of the network tree would move the cursor focus to the topmost device in the network.

Setup Window Bug Fix: There were odd characters at the end of lines in the final screen of the Backup Network wizard.

EZSetup Enhancement: Improvements made so it can be navigated without a mouse.

EZSetup Enhancement: Added Data File Output options for mixed array dataloggers.

Connect Window Enhancement: Double-clicking a file in the summary window that is displayed after collecting data opens the file in View.

Connect Window Enhancement: Right-clicking a table name in the Custom Collect window after data collection will open the file in View.

Connect Window Enhancement: Ports and Flags dialog no longer minimizes when the Connect window is minimized.

Connect Window Enhancement: File Control has been moved to the Datalogger menu item.

Connect Window Enhancement: Program name has been added to the Send Program message box.

Connect Window Enhancement: Added a Start/Stop button to the Numeric Displays and Graphs.

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.

Connect Window Enhancement: Data displays now show fractions of a second for timestamps.

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.

Connect Window Enhancement: Added a vertical line marker on graphs that can be enabled by double-clicking the graph.

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.

Connect Window Enhancement: Added Y axis title to the graphical displays.

Connect Window Enhancement: Changed the graphical displays so a graph is still updated when it is minimized.

Connect Window Enhancement: Added a Time of Fill column to Datalogger Status window that shows the estimated time each table will fill.

Connect Window Enhancement: If table definitions were not current, Custom Collect would not collect data.

Connect Window Enhancement: Reset Tables button for table-based dataloggers has been moved from the Custom Collect window to the Datalogger Status window.

Connect Window Enhancement: Pause button added to Terminal Emulator.

Connect Window Enhancement: Terminal Emulator window can be resized.

Connect Window Enhancement: Support added for backspace character in Terminal Emulator.

Connect Window Bug Fix: Cosmetic issues when resizing the window.

Connect Window Bug Fix: Messages from Custom Data Collections were not being stored in the Transaction log.

Connect Window Bug Fix: Improved error messages from Custom Data Collections.

Connect Window Bug Fix: Modifying a value in the Numeric Monitor would cause the monitor to go behind the Connect window.

Connect Window Bug Fix: Displaying a very large array on the Numeric Monitor could cause the monitor to crash.

Connect Window Bug Fix: NAN values for Long integers are now displayed as -2147483648.

Connect Window Bug Fix: Data displays no longer truncate Long integers.

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.

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.

Connect Window Bug Fix: On a dual processor Windows 2000 PC, if you stopped/started a graph the window moved an inch or so.

Calibration Wizard Enhancement: Updated Calibration Wizard for performing field calibrations on CRBasic programmed dataloggers.

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".

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).

File Control Bug Fix: The ability to download an OS via File Control has been removed.

Status Monitor Enhancement: Pause Schedule button has been moved so it is not inadvertently clicked when selecting a Status Monitor View.

Status Monitor Enhancement: Added a new Line State statistic to indicate an IP port is waiting for an incoming connection.

Status Monitor Bug Fix: GUI elements (buttons, check boxes, text fields) behave better when window is resized to a very small size.

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.

Status Monitor Bug Fix: Communication History window now updates when it is being viewed and new data becomes available.

Status Monitor Bug Fix: The Datalogger Network Views dialog box displayed a red slash circle for the CR800 datalogger.

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.

Card Convert Version 1.3 Enhancement: Updated to support translation to other languages.

Card Convert Version 1.3 Enhancement: Added ability to save a day of year for table-based timestamps.

Card Convert Version 1.3 Bug fix: Repairing an empty table yielded an error.

Card Convert Version 1.3 Bug fix: In certain instances changes to the Destination File Name dialog were not saved.

Card Convert Version 1.3 Bug fix: Processing data based on date/time with 0 for the time intervals would lock up Card Convert.

Card Convert Version 1.3 Bug fix: Appending data would use last file name instead of Destination File Name.

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.

CRBasic Editor Version 2.8 Enhancement: Added the option to save a compressed file (stripped of remarks and spaces).

CRBasic Editor Version 2.8 Enhancement: New F9 functionality inserts a variable at the cursor location (existing F10 functionality would overwrite existing variable).

CRBasic Editor Version 2.8 Enhancement: Added the ability to turn off syntax checking.

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.

CRBasic Editor Version 2.8 Enhancement: Improved precompiler messages.

CRBasic Editor Version 2.8 Bug Fix: Files with an ampersand in the file name could not be opened from the Recent Files List.

CRBasic Editor Version 2.8 Bug Fix: Cleared bookmarks would return after inserting a variable.

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.

CRBasic Editor Version 2.8 Bug Fix: Print Preview would set margins to .01 less than the value entered.

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*.

CRBasic Editor Version 2.8 Bug Fix: The Editor always tried to save "Save As" files with uppercase letters.

CRBasic Editor Version 2.8 Bug Fix: Printing in Landscape mode was not repaginating the file.

CRBasic Editor Version 2.8 Bug Fix: Subroutine arguments were showing up in variable list.

DevConfig 1.8 Enhancement: File | Browse Config Files will let you view the saved configuration file for a device.

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.

DevConfig 1.8 Bug Fix: Problem with the XML configuration file header which would cause it not to render properly in a browser.

DevConfig 1.8 Bug Fix: Screen redraw algorithm could result in black boxes on the application window.

DevConfig 1.8 Bug Fix: Improved OS download for CR9000X.

Edlog 2.6 Bug Fix: Compiler didn't warn of a Table 2 that had instructions but an execution interval of 0.

Edlog 2.6 Bug Fix: Disallow spaces in P84 table names.

Edlog 2.6 Bug Fix: Screen was repositioning when setting reps to a value greater than 1 and pressing Enter.

Edlog 2.6 Bug Fix: In some instances, the Edlog window would not close.

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).

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).

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.

PakBus Graph 1.8 Bug Fix: When making changes using Edit Settings, there was no warning if the changes were not applied.

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.

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.

RTMC 2.5.24 Bug Fix: Time component was limited to 14 characters. It is now unlimited.

RTMC 2.5.24 Bug Fix: The use of parentheses in a datalogger station name would cause set point and switch components to fail.

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.

RTMC 2.5.24 Bug Fix: Fixed an issue where a 0 byte project file could be saved.

Split 2.6 Enhancement: Can process larger files.

Split 2.6 Enhancement: The "bad data" indicator will flag bad data, even if there is no screen display.

Split 2.6 Enhancement: Screen display indicates how long it took the file to process.

Split 2.6 Bug Fix: Record numbers greater than 14 characters could not be formatted.

Split 2.6 Bug Fix: Subsecond data now truncates rather than rounding.

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.

Resolved issues: When a new mixed array datalogger was added to the network map, scheduled data collection for that station would not start until LoggerNet was closed and restarted.

Resolved issues: The Service Manager was creating and using an alternate key in the Windows registry, which had the effect that in some instances the working directory used by the service was incorrect. The symptom of this was that the network map would be blank after starting/stopping the service with the Service Manager.

Resolved issues: In some instances server transactions were hanging, which would result in scheduled data collection stopping.

Resolved issues: A change was made to the algorithm used for checking/setting clocks. The change improves the synchronization of clocks over slower communication links and resolves an issue where scheduled data collection would be delayed if a negative Time Zone Offset was being used and a station's clock was set using the CoraCmd clock-set. Note that a result of this change is that the Server Date/ Time reported on the Connect window and the Setup window's Clock tab will now include the offset.

Enhancement: Support for the CR800 datalogger.

Enhancement: New CSV custom file format added as a file output option in the Setup window and in CardConvert. This new format, available only for table-based dataloggers, stores the data to a comma separated format that is similar to that of mixed array dataloggers.

Enhancement: Improvements to the Ports and Flags window for all datalogger types.

Enhancement: Field Calibration wizard for measurement calibration in the CRX000 dataloggers.

Hole Monitor Enhancement: Added ability to purge or collect all or specific holes.

Backup Wizard Enhancement: When running the network Backup wizard, now get a warning that the file will be overwritten if a backup file with the same name exists.

Backup Wizard Enhancement: When running the Backup utility as a Task, you now have the option to create unique file names based on date/time of backup.

EZSetup Enhancement: Can now type in a COM port number in EZSetup, if it is not displayed in the list of available ports.

CRBasic Editor Enhancement: Allows printing select pages.

CRBasic Editor Enhancement: Added "library file" support to CRBasic editor.

CRBasic Editor Enhancement: Added scroll bar to message window for CRBasic Editor.

CRBasic Editor Enhancement: Support for new instructions in the CR1000, CR3000, CR9000X, and CR5000 datalogger operating systems was added to the CRBasic Editor.

CardConvert Enhancement: Added ability to store processed files in uniform sized packets based on time.

CardConvert Enhancement: Now supports a file naming scheme based on timestamp of data.

CardConvert Enhancement: Improved user interface.

Resolved issues: When custom labels were entered for Ports/Flags dialog, these labels were not maintained when the dialog was closed.

Resolved issues: LoggerNet Admin: Launch Multiple Clients option was inadvertly left off of the Toolbar's Options menu.

Resolved issues: Fixed an issue with LNBackup when running LoggerNet as a service.

Resolved issues: Transformer could only open CRBasic once per session.

Resolved issues: Multiple changes made to Spanish language files.

Resolved issues: Troubleshooter "Show Stations Only" menu option was not working.

Resolved issues: TAPIRemote "Country Code" list box now in alphabetical order.

Resolved issues: With a certain series of keystrokes, the CRBasic Editor would return an error when Save was pressed.

Resolved issues: DevConfig would return an "unhandled exception" error when trying to connect to a storage module.

Resolved issues: Improved display of multi-lines strings in Numeric Monitor.

Resolved issues: Connect window was requesting table definitions from all dataloggers in a network, instead of just the datalogger to which it was connected. This could result in very slow response if connecting over a slow communication link with a large datalogger network.

Resolved issues: CardConvert output file directory no longer defaults to card.

Resolved issues: CardConvert: Creating a new output directory off of the root directory sometimes created the directory in the wrong place.

Resolved issues: Resolved a Range Check error in Split when using a Starting Offset and the Date function.

Resolved issues: Fixed a problem with Split's WDQS(n) function when wind direction was 360 degrees or greater.

EZSetup Bug Fix: If your first action is to edit a previously configured mixed-array datalogger, and you jump to the data files tab, the EZSetup client may show the data file name fields as blank. Clicking Finish at this point saves blank fields in the server, which prevents data files from actually being saved. (Problem was introduced in LoggerNet 3.2.)

Setup Screen Bug Fix: 1. If you make any change to a setting on the Final Storage Area 1 or Final Storage Area 2 tabs for mixed-array dataloggers, that change is duplicated on the other tab. If you make any changes to a setting you cannot have different settings - including the path and name of the data file or whether to collect or not - on these two tabs. This means users cannot choose to collect just one Final Storage Area and any data they collect from either Final Storage Area will be put into the same file - an even more serious problem if they have duplicate Array IDs in both Final Storage Areas. (Problem was introduced in LoggerNet 3.2.1.)

LoggerNet Server Bug Fix: Reverted to the behavior of LoggerNet 3.1.x where we don't look for the DSR line to be high before attempting to use a device on a COM port. We attempted to use this to make sure a USB serial port cable was actually attached to resolve a problem with FTDI drivers. However, it presented problems for many internal phone modems that didn't support the DSR line. USB COM port users may have to add a Generic modem between COM port and the PhoneBase and set the Generic modem to igonore the DSR by choosing "The RTS line will be raised" on the modem tab.

CRBasic Editor 2.6 Bug Fix: Now creates a binary (*.BIN) program file for sending to CR2xx dataloggers when compiling the program.

Setup Screen Bug Fix: When run remotely displays the wrong default working directory. It used variables for the server's and the application's working directory on the remote PC rather than those on the server PC.

Short Cut 2.5.1 Bug Fix: Short Cut 2.5 created illegal 21X programs when instructions used integration.

TaskMaster Engine Bug Fix: When LoggerNet is closed, it sends a message to the TaskMaster Engine to close, but the TMEngine closes before it writes all of its tasks to its ini file. The next time it comes up, it has no knowledge of tasks. TaskMaster Fixed so it only writes to its ini file when the Apply button is clicked.

Transformer 1.3 Bug Fix: Now searches for the CRBasic Editor in its own application directory first.

Bug Fix: On loss of and restoring power to the PC, the Task Master now comes back up as it was before power loss instead of always coming up paused.

Enhancement: Added support for new CR3000 datalogger throughout the application.

Enhancement: Added LoggerNet Remote and LoggerNet Admin products to support remote data distribution and remote network management. New client applications include: Security Manager, Hole Monitor, Data Export, and LoggerNet Server Monitor. Install asks for CD key and evaluates it against the current install to determine what product to put on the PC.

Enhancement: Added capability in LoggeNet Admin product to run LoggerNet server as a Windows service, with new Service Manager utility to manage it.

Enhancement: Easier to use backup and restore functions for the network map, accessible from Setup Screen.

Enhancement: Added LoggerNet Server Monitor for remote administration, to monitor one or more LoggerNet servers. Status of servers indicated by color of icon in the Windows task bar.

Enhancement: More flexible Ports and Flags dialog box in Connect Screen that now displays Boolean variables for dataloggers that support that variable type.

Enhancement: Updated Status Table dialog box in Connect Screen for more statistics for datalogger and program tables. Added tab to show graphically when the datalogger will start overwriting final storage tables.

Enhancement: Fully customizable Status Monitor window with capability to save different network views in the Status Monitor client in LoggerNet Remote and LoggerNet Admin.

Enhancement: Redesigned RTMC data display client (see below).

Enhancement: Added alternative language support for main LoggerNet clients (Toolbar, EZSetup, Setup, Connect, Status Monitor, LogTool, Task Master, Troubleshooter, PakBus Graph, DevConfig) by downloading language files from Campbell Scientific web site (www.campbellsci.com/downloads).

Enhancement: Added a new feature in the server to "delay hangup" for devices to replace the "managecomm" utility, to keep devices on line for an extra period so that other devices can be dialed without having to shut down the entire link.

Enhancement: No longer support LoggerNet installations on Windows 95, Windows 98, or Windows ME platforms because they're inconsistent with some of the new functionality in the server, such as running the server as a Windows service. Also removed the Resource Monitor utility, as it was only used for these 16-bit platforms.

Short Cut 2.5 Enhancement: Added wizard-like user interface.

Short Cut 2.5 Enhancement: Added support for new CR3000 datalogger.

Short Cut 2.5 Enhancement: Added images for most sensors to help select the correct sensor.

Short Cut 2.5 Enhancement: Support for additional colors on the wiring diagram (e.g., brown and orange).

Short Cut 2.5 Enhancement: New sensor files: CS300 Apogee PYR-P Pyranometer and (for the CR2xx dataloggers only) the CS15 Current Transformer.

Short Cut 2.5 Enhancement: User selectable print options (Results, Summary, Wiring Diagram, Wiring Text) added to the last step.

Short Cut 2.5 Enhancement: Improved Advanced Outputs, including Ring and Fill and Stop table options, store Filemark when a flag is toggled by the user, option to set a flag high when a table becomes full, Data Event output option.

Short Cut 2.5 Enhancement: Use control ports for tipping buckets, freeing up pulse ports for higher frequency measurements.

RTMC 2.0 Enhancement: New, more sophisticated graphical components.

RTMC 2.0 Enhancement: Graphs now allow zooming in on smaller section and autoscaling on chart's y-axis.

RTMC 2.0 Enhancement: Adds wind gauge component.

CRBasic Editor 2.5 Enhancement: Added Back/Next buttons to parameter editing pop-up.

CRBasic Editor 2.5 Enhancement: New GoTo function and Bookmarks for navigating in larger programs.

CRBasic Editor 2.5 Enhancement: Faster repainting of the screen on very large programs.

Transformer 1.1 Enhancement: Support for converting CR23X mixed-array programs to CR3000 CRBasic programs.

Transformer 1.1 Enhancement: Support for converting CR510 mixed-array programs to CR1000 CRBasic programs.

CardConvert 1.1 Enhancement: Added a "repair" option for corrupted TOB2 and TOB3 files from PC Cards or compact flash cards.

LoggerNet Server 1.3.6.42 Bug Fix: A bug in server would not allow data collection from a 21X or CR7 datalogger.

LoggerNet Server 1.3.6.41 Bug Fix: A bug in the server caused it to crash (external exception) if a Numeric or Graphic Display launched from the Connect Screen tried to display any values from a table (inlocs, public, or final storage) in a table-based datalogger (Edlog or CRBasic datalogger) that had more than 227 fields.

LoggerNet Server 1.3.6.41 Bug Fix: Fixed a bug in the server that prevented it from collecting "most recently stored records" from a table-based datalogger if the datalogger had not stored at least that many records since LoggerNet's last collection.

Short Cut 2.4 Bug Fix: Reverted to default.plt and table.plt sensor files similar to those in Short Cut 2.0-2.2 for measuring the program signature in order to preserve forward compatibility so that Short Cut can edit programs created in those earlier verisons. Programs created in Version 2.3.x will have to be recreated to be used in this and subsequent versions.

LoggerNet Server 1.3.6.40 Enhancement: Added support for sending programs to CR1000s with newer operating systems (>=CR1000.Std.04.obj).

File Control Enhancement: Improved functionality in File Control screen (from Connect Screen) when working with compact flash cards in a CR1000 (CFM100).

Enhancement: Added capability to abort the program send command for all dataloggers.

Enhancement: Implemented a new CoraScript command ("create-backup-file") to back up the server's network as well as the data cache and collect areas (and other files as stipulated by the user, including use of wildcard "*" and "?" characters) while the server is running. This makes backing up the full state of the LoggerNet server more practical. This command can be run from within a batch file with other CoraScript commands on a schedule using the Task Master. Along with this, also implemented the command to restore the network from that backup file ("lgrnet-restore-snapshot").

Enhancement: Added WinSock error codes to the Comms log for troubleshooting IP connections.

Enhancement: Increased the minimum time out for an Edlog datalogger to compile its program from 90 seconds to 180 seconds (three minutes).

Enhancement: Changed handling of FP2 formatted data to recognize INF and -INF values.

Enhancement: Can now change the case on device names in the Setup Screen without upsetting the other settings for the device.

Enhancement: Added code for the RF400 series of radios to make call-back functional when the radios are in "transparent" mode (i.e., dialed, not in PakBus mode). This is accomplished by setting the base radio mask to 0xFC00 (ATMK FC00 ) when the link is being hung up or when the link is being set up to receive call-back so that it's a predictable address for the remotes to dial.

Bug Fix: Related to processing table definitions from BMP3 dataloggers (CR5000 and CR9000) that prevented data collection when a table contained boolean variable types.

Bug Fix: Fixed a problem where, if scheduled collection from a CR1000 exhausted all primary retries but secondary retries was not enabled, the Last Data Coll looked as if it had succeeded.

PakBus Graph 1.5 Enhancement: Allows users to "lock" PakBus devices to a fixed location on the screen to make viewing the network easier.

CardConvert 1.0 Enhancement: Replaced the TOBConvert utility with CardConvert to support binary data types and files from CR1000 compact flash cards.

CardConvert Enhancement: Can increment file names to prevent mistakenly overwriting files; remembers settings and directories; better feedback about conversion progress and results, optionally will select unused filenames for output filenames; simple help; launched from toolbar rather than Start menu; allows you to open View from its main screen to view the data files; creates new files when encountering filemarks and (new) "removemarks."

DevConfig 1.3 Enhancement: Added several devices, including the RF401 spread spectrum radio w/ PakBus capability, CC640 camera, CD295 DataView Display, and TGA100.

DevConfig 1.3 Enhancement: Added new settings for other devices, including the CR1000, NL100, and SC105.

Short Cut 2.3 and 2.3.1 Enchancement: Added support for alternative groups of sensor files, specifically to support sensor files developed for sensors specific to European users. The SCWin.EXE was modified to read new settings in the sensor files and display a menu item under the Settings menu to offer options for viewing "Campbell Scientific Inc" or "Campbell Scientific Ltd" sensor groups. Short Cut 2.3 and 2.3.1 Enchancement: Added support for interfaces requiring special wiring between the datalogger and sensors: LLAC4 (4 channel device for reading low level AC signals on digital control ports), SW12V (standalone switched 12V relay cable for HMP45C sensors), Terminal Input Modules for the AGS Level Sensor and CNR1 Net Radiometer, A547 interface for the CS547A Conductivity and Temperature Probe, QD1 interface for quadrature shaft encoders, SDM-AO4 4-Channel Analog Output Module, and SDM-CVO4 4-Channel Current/Voltage Output Module. Short Cut 2.3 and 2.3.1 Enchancement: Added support for outputting data to the CR1000's compact flash (CFM100). Short Cut 2.3 and 2.3.1 Enchancement: Added new CSI sensor files: 107 Temperature Probe (4-wire version) for multiplexors 108 Temperature Probe (3-wire) for multiplexors 108 Temperature Probe (4-wire) for multiplexors AGS Level Sensor (Metritape) CNR1 Net Radiometer CS100 Barometric Pressure Sensor CS205-LC Fuel Temperature Sensor for the MetData1 and ET106 CS215 Temperature & Relative Humidity Sensor CS505-LC Fuel Moisture Sensor for the MetData1 and ET106 CS512 Dissolved Oxygen Probe HMP45C (6-wire) Temperature & Relative Humidity Sensor on the SW12V NRG #200P Wind Direction Sensor NRG #40 Wind Speed Sensor Device for Analog Input from SDM-AO4 Device for Current/Voltage Input from SDM- CVO4 WindSonic-LC 2-D Sonic Wind Sensor for the MetData1 Wind Run Calculation

Short Cut 2.3 and 2.3.1 Bug Fix: Fixed a bug that prevented workable DLD files for 21X dataloggers for sensors that used 50/60 Hz rejection options for analog voltage integration.

SMS 4.9 Bug Fix: Fixed a problem with collecting data from SM16M modules set for fill & stop. Data collection would proceed as expected, almost until the last "chunk" and then would either fail with a "too many errors message" or just get in a loop where it tried over and over and over to collect that last chunk.

Miscellaneous: Updated instruction definition files and help for CRBasic dataloggers.

Bug Fix: Fixed several problems in the server when LoggerNet was collecting from storage modules. These included: files were always stored in binary format which also caused a backup file to be created on every collection; we were allowing the operating system to insert extra bytes in the files that threw off the byte pairing which made the data appear to be corrupt; we were not retaining the correct pointer when storage modules were full (rung around) and collections were aborted; we were not processing retries as well as we should when the maximum time on line was triggered during a scheduled collection; we were timing out too soon when users had set the collection option for a very large number of the most recent arrays; and the Status Monitor was showing a decreasing number of values to collect during the data collection. These problems did not affect collections when using the SMS (Storage Module Software) program.

Bug Fix: Fixed a minor bug in the server that prevented it from collecting tables from CR5000 or CR9032 dataloggers that contained Boolean variables.

Bug Fix: Used a different sequence for closing sockets and threads during shutdown by several clients, including Setup, Connect, Status, EZSetup, CRBasicEditor, TroubleShooter, Task Master, and LogTool to resolve a problem with the Windows' WSACleanup routine that was revealed by a third party antivirus software.

Enhancement: Made it possible to use regional settings with alternative separator characters (e.g., commas for decimal separators and periods for thousands separators), particularly noticeable in the Connect Screen's Numeric Monitor.

Bug Fix: Fixed a bug during the install when upgrading from LN 2.1c. It didn't use the working directory if the path didn't end in "loggernet". It updated the SCWin, RTMC, DevConfig, etc. directories, but then forgot to use the previous old working directory. Instead, not finding a "LoggerNet" directory, it makes a fresh one, so thatit shows a blank network map. 2. Fixed a bug in the Connect Screen when upgrading froma LoggerNet 2.x network that included table-based Edlog dataloggers (TD and PB) in the Numeric Monitor. Inloc fields in the Numeric Monitors would appear but no values would ever be displayed.

Bug Fix: Fixed a bug in the Setup Screen when upgrading froma LoggerNet 2.x network that caused the Output File Name field on the Data Files tab for any table-based datalogger to show the wrong path to the datafile. The actual path used was correct, but this could lead to a wrongly named data file if the user clicks the browse button, fails to notice that the file name offered has "bin" at the front of it and clicks OK.

CRBasic Editor Enhancement: Improved the performance of the CRBasic Editor when using the keyboard cursor keys to scroll left-right or up-down. This was very noticeable on slow PCs (~350 MHz).

LoggerNet Server Bug Fix: Fixed a very obscure bug in the server, probably there since Version 2.0, that was exposed during very rapid scheduled data collection from PakBus dataloggers.

LoggerNet Server Bug Fix: Fixed a bug collecting multiple holes from a PakBus datalogger in response to one-way- data packets having been received.

Setup, Collect, Status Monitor Bug Fix: Fixed memory leak exposed in the event that the LoggerNet server were to crash. Not considered serious, since the server should never crash.

TroubleShooter Enhancement: Folded help into the Toolbar help to make it easier to access.

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.

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.

Toolbar Enhancement: Toolbar can now launch PakBus Graph, RTMC Run-time, and Task Master clients.

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.

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.

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.

EZSetup Enhancement: EZSetup allows setting up one level of communications (phone modem or RF or MD9, etc.).

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.

EZSetup Enhancement: Scheduled collection can be setup in the wizard.

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.

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.

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.

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.

Setup Enhancement: Users can now check and set the clock as well as send programs to dataloggers from tabs on the Setup Screen.

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.

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.

Connect Screen Enhancement: A 'Check Clocks' button has been added. This feature is enabled whenever the automatic clock update is not on.

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.

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.

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.

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.

File Control Enhancement: The properties button has been removed. A delete button has been added. The user can now pause and resume a program.

Status Monitor Enhancement: The network map is indented to match the view in the setup screen.

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.

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

Status Monitor Enhancement: Every device has an image of that device type next to it.

Status Monitor Enhancement: A trouble shooter image (graphic exclamation point symbol) can appear next to a device that is having some type of trouble.

Status Monitor Enhancement: The user cannot launch the Task Master from the Status Monitor.

Status Monitor Enhancement: The user can launch the Trouble Shooter from via the right-click menu option.

Status Monitor Enhancement: The low level logs are accessible from the Status Monitor through the LogTool.

Status Monitor Enhancement: The user can sort the statistics by column.

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.

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).

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.

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.

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.

Troubleshooter Enhancement: The user can launch the LogTool and PakBus Graph clients.

Communication Test: The Communication Test button has been moved to the Troubleshooter.

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.

Communication Test: The legend can be toggled on or off using the Show Legend checkbox.

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.

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.

PakBus Graph: A search feature has been added to search for new nodes on LoggerNet PakBus port.

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.

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.

LogTool: All server log monitoring and settings have been moved into the LogTool client.

LogTool: Specific log windows can be shown or hidden using their respective toolbar buttons or the Options->Logs to Show menu.

LogTool: Warning and Error Communication Log messages are colored Blue and Red respectively.

LogTool: Warning, Error, and Status Communication Log messages can be toggled on/off, so that only those log messages selected will be shown.

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.

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.

LogTool: Timestamps for log messages can be set to: Date, military time, and ms Resolution from a menu item, Options->TimeStamp Options.

LogTool: Clear All and Pause All buttons were added.

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.

LogTool: Individual Log toolbars and the parse window (network view window) can be shown/hidden via their respective toolbar buttons.

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.

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

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.

DevConfig: Direct RS-232 serial connection to the device is required.

DevConfig: The Deployment screen can set datalogger clocks and send programs.

DevConfig: A separate tab sends operating systems to supported devices.

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.

DevConfig: A generic settings editor similar allows the user to view and/or edit all of the settings defined for that device.

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.

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.

DevConfig: A terminal emulation screen is provided for a connected device where this is appropriate.

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.

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.

CRBasicEditor: The user can now select the CR200 compiler to be used from the CR200 compilers available on his/her machine.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Short Cut: Users can select multiple (contiguous) measurements for output on the Output screen. Only outputs allowed for all selected measurements will be enabled.

Short Cut: Drag-and-drop now works to reorder outputs on Output screen.

Short Cut: Individual members of rep blocks can be renamed on the Sensors screen.

Short Cut: Users can override allowed (recommended) outputs on Output screen with a right-click.

Short Cut: A 50 or 60 Hz noise rejection option in available from the Settings pull-down menu.

Short Cut: Alternative compilers can be selected for the CR200 Series dataloggers from the Settings pull-down menu.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

LoggerNet Server: The server accepts one way data notifications from PakBus dataloggers.

LoggerNet Server: The server accepts UDP packets from an AirLink modem (Raven or PinPoint) containing a new dynamic IP address.

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.