Resource Center
RTDAQ Patch
Software applications, data logger operating systems, firmware, and drivers for Campbell Scientific products
RTDAQ Patch
v1.4.1This patch will upgrade RTDAQ version 1.0, 1.1, 1.2, 1.3 or 1.4 to 1.4.1. RTDAQ 1.x must be installed on the computer.
Note: This application requires the Microsoft .Net 4.0 Framework. If it is not already installed on your computer, it can be obtained from the Microsoft Download Center.
Revision History
v1.4.1March 13, 2020
- Fixed an issue with language support on non-English Windows operating systems.
v1.4February 28, 2020
- Enhancement - Added support for the GRANITE 6, GRANITE 9, and GRANITE 10 dataloggers.
- Enhancement - Fixed an integer overflow error when calculating the expectedRecs by making it an Int64 and catching the exception if it is thrown.
- Enhancement - Added the ability for the user to control the visibility of the symbol and line of their traces individually. This only affects the normal graph and xy plotter.
- Enhancement - Fixed synchronizing the colors between the complex and normal series.
- Enhancement - Custom and normal data collection has been improved.
- CRBasic Editor - Added the ability to use CAN .dbc file for use with new CAN-FD read and write instructions
- CRBasic Editor - Added support for CRB files and programs.
- CRBasic Editor - Made it so that the parameter check for conditional parameter is not case sensitive.
- CRBasic Editor - Fixed a problem with instruction search and last item in list (XOR).
- CRBasic Editor - Changed the CRBasic editor to no longer try to write to HKEY_LOCAL_MACHINE hive when associating files which can require admin privileges.
- CRBasic Editor - Added the ability to select a .DBC file and fill out parameters for CANRead and CANWrite on the GRANITE 10. This is similar to how the SDMCAN allows selecting of a .PCK file but it uses DBC2PCK.exe for the user.
- CRBasic Editor - Added a small change to make the parsing of datalogger type on the first line more flexible.
- CRBasic Editor - Optimized loading of the default template files to speed up the process.
- CRBasic Editor - Fixed a bug where Compile, Save, and Send was not showing any loggers to send to with a dld extension. Now it shows a filtered list based on CRB or DLD extension.
- CRBasic Editor - Fixed an MDI bug where part of MDI child form was hidden behind toolbar when the main form started maximized.
- CRBasic Editor - Fixed an issue with editing an instruction with the insert edit dialog when using the insert instruction edit box. If a parameter has options, a selected option could show the comment for a previous option if the selected option does not have a comment.
- CRBasic Editor - Modified the code to allow the "&" operator to be syntax highlighted.
- CRBasic Editor - Fixed a problem where the instruction edit box would not show the comment for a parameter if that parameter used the rg#DefaultName? The look up for the comment needed the actual name to work.
- CRBasic Editor - Modified to now allow the "File Save As" to set the correct extension. Fixed by setting the default extension.
- Device Configuration Utility 2.23 - Add support for TX326.
- Device Configuration Utility 2.23 - New settings added to the CR1000X, CR6, GRANITE 6, GRANITE 9, and GRANITE 10 dataloggers that allow the user to edit IPv6 domain name servers.
- Device Configuration Utility 2.23 - Help for various settings in the ALERT205 have been updated.
- Device Configuration Utility 2.23 - Added tooltips for labels in left panel controls.
- Device Configuration Utility 2.22 - Added support for the GRANITE 6, GRANITE 9, and GRANITE 10 Measurement and Control Data-Acquisition Systems.
- Device Configuration Utility 2.22 - Added support for the LevelVUE B10.
- Device Configuration Utility 2.22 - Added support for the TX325 GOES transmitter.
- Device Configuration Utility 2.22 - Updated AL200 settings and help.
- Device Configuration Utility 2.22 - Moved some retired dataloggers to the ‘Datalogger (other)’ category.
- Device Configuration Utility 2.22 - Minor bug fixes and help changes needed to improve the customer experience.
- Device Configuration Utility 2.21 - Added support for the GRANITE series VOLT 108, VOLT 116 and TEMP 120.
- Device Configuration Utility 2.21 - Reorganized the left panel so that an IP address is kept separate from a serial port name and so that you can specify the PakBus address of the datalogger that might be connected through a PakBus router.
- Device Configuration Utility 2.21 - AL200 Alert and Alert 2 bug fixes.
- Device Configuration Utility 2.19 - Added new baud rates for the RS-232 port that are faster than the 115,200 KBaud rate for the CR1000, CR3000, CR800 Series, CR6, and CR1000X. These baud rates will only be available with an OS update and can only be used with a very short cable.
- Device Configuration Utility 2.19 - Added new settings for the CR300 series dataloggers including "Trusted Hosts", "NTP Server", and "PCAP".
- Device Configuration Utility 2.19 - Added settings for external CELL2xx connected to a datalogger that cover roaming and over the air update pending.
- Device Configuration Utility 2.19 - Added support in the deployment panel for the CR300, CR6, and CR1000X dataloggers so that external modem parameters can be edited through the datalogger.
- Device Configuration Utility 2.19 - Added support in the deployment panel for the CR1000X, CR6, and CR300 datalogger types for settings that configure an optionally attached CELL-200 series modem.
- Device Configuration Utility 2.19 - Extended the baud rates available for the CR300 Series RS-232 port so that rates of 230400 and 460800 can be specified.
- Device Configuration Utility 2.19 - Added a "Trusted Host" setting for the CR1000X and CR6 dataloggers.
- Device Configuration Utility 2.19 - Added a dialog that can be used for testing serial port connections with loop-back adapters. This can be accessed from the Help menu.
- Device Configuration Utility 2.19 - Various minor bug fixes and help changes needed to improve the customer experience.
- Device Configuration Utility 2.18 - Added auto-update capability for DevConfig software.
- Device Configuration Utility 2.18 - Added "Manage OS" panel to facilitate datalogger operating system updates (CR300, CR1000X, CR6 dataloggers).
- Device Configuration Utility 2.18 - Added a new setting for the CR6 to specify the behavior of the Wi-Fi configuration button (Join a Network/Create a Network/Disable).
- Device Configuration Utility 2.18 - Added new settings for the CR6 and CR1000X that specify verify and beacon interval values for PakBus/TCP connections.
- Device Configuration Utility 2.18 - Added a "Maximum TCP Segment Size" setting for the CRx000 families of dataloggers.
- Device Configuration Utility 2.18 - Assigned a maximum value of 10 Amps to the current limit setting for the charge rate for the CH201.
- Device Configuration Utility 2.18 - Removed the "factory-write" attribute from the serial number setting for the CS475A.
- Device Configuration Utility 2.18 - Edited the setting help files for the CR300 and CR6 so that the help looks better on the settings web page.
- Device Configuration Utility 2.18 - Increased the size limit for the CR300 setting that reports cellular state.
- Device Configuration Utility 2.18 - Updated the graphics in the about box header.
- Device Configuration Utility 2.18 - Removed enable expressions for the HTTP service port and the FTP service port settings. The position of the enabling values is not the same across all device types that use this file.
- Device Configuration Utility 2.18 - Updated the help for the CRx000 setting that controls PCAP output.
- Device Configuration Utility 2.18 - Added a warning in the instructions for the data recovery wizard that identifies the requirement for OS25 or newer for the CR1000, CR3000, and CR800 datalogger types.
- Device Configuration Utility 2.18 - Added a custom version string parser for the CR300 that will ignore anything beyond the dash in the model. This resolves an issue where the CR300 reported its daughter board as a part of the OS version model.
- Device Configuration Utility 2.18 - Updated the connect and OS send instructions for the MD485 to change references to the word "modem".
- Device Configuration Utility 2.18 - Updated the wiring table in the connect instructions for the CS240DM.
- Device Configuration Utility 2.18 - Updated mbed-tls to version 2.9.0
- Device Configuration Utility 2.18 - Added key filters for the edit control used for floating point components so that the control will only accept characters associated with floating point values.
- Device Configuration Utility 2.18 - Updated the certificate used for signing applications and USB drivers.
- Device Configuration Utility 2.18 - Corrected grammar errors in connected and off-line modes for various device types.
- Device Configuration Utility 2.18 - Disabled Configuration setting for control port-based com ports (e.g., COMC1, COMC3).
- Device Configuration Utility 2.18 - Updated settings help for the NL240.
- Device Configuration Utility 2.18 - Removed a reference to the CS I/O port for CR300 baud rate settings.
- Device Configuration Utility 2.17 - Added support for CR300-CELL2XX internal cellular modems.
- Device Configuration Utility 2.17 - Made numerous device setting changes, cosmetic improvements, and added other new minor capabilities and optimizations.
- LoggerNet Server - Fixed a bug where the broadcast option of a Linux UDP socket was not set on the socket when it was opened.
- LoggerNet Server - Changed the function that retrieves the IP interface addresses so that it can use the getifaddr() under posix implementations. This provides a better list of local interfaces than does the previous method.
- LoggerNet Server - Added command line options for the loggernet daemon that will enable IPv6 service. (LNLinux)
- LoggerNet Server - Changed the post install script so that the -U option is specified along with the useradd command that creates the loggernet user.
- LoggerNet Server - Added a try/catch block in the posix TCP client component around the code that attempts connections on various resolved addresses. If a connection fails, the catch will ensure that the socket is closed and will allow us to attempt the next connection.
- LoggerNet Server - Added a new value for to the respCode parameter of the Device Send File Status Notification and Device Send Program File Status Notification messages that will indicate that the logger reported that the file was incompatible. Added an optional parameter, explanation, that report the datalogger string that explains the reason for this incompatibility.
- LoggerNet Server - Fixed a bug in the BMP5 file send operation where the datalogger explanation string was not read from the datalogger's response because the code was not reading the file offset from the body first. Also added code to ensure that the comms log messages recognize the incompatible file response code.
- LoggerNet Server - Added a new collect area setting for ALERT2 sensor report areas that will control the data type that is used for the raw and processed values stored in the cache table.
- LoggerNet Server - Changed the persistence values assigned to alert station sensor report collect areas so that they are all marked as user-defined. This will allow the user to rename or delete default areas.
- LoggerNet Server - Changed the implementation of the device rename collect area transaction so that the notification for the collect area deletion is sent out before the new name is applied to the collect area.
- LoggerNet Server - Changed the code that creates alert2 report areas so that, if the report value type is specified as an integer, the cache data type will be specified as an int4 rather than an int8.
- LoggerNet Server - Fixed a bug in the alert2 report area where the table would not get recreated after the client had changed the report value data type setting.
- LoggerNet Server - Changed the BMP5 enumerate files operation so that, if the client does not specify a preceding slash when it needs to limit the files sent, that slash will be provided automatically.
- LoggerNet Server - Added code to log comms messages for the alert2 base when there is a communications failure
- LoggerNet Server - Added code in the restore snapshot handler to work around a bug where, in older versions of backup files, files lengths were encoded as size_t (64 bits on 64 bit machines) instead of the expected uint4. The result was that, when attempting to restore the older file, the newer server would report it as corrupt. The validation code will now check the length encoding for the first file by reading eight bytes for the length and, if the least significant four bytes are zero, will expect all string lengths to be encoded with 64 bits instead of 32 bits.
- LoggerNet Server - Fixed an oversight where the connection rules did not allow a CR1000X to be configured as a child to a CR800 router.
- LoggerNet Server - Changed the current focus object state log messages produced so that they will include the destination address and transaction ids in the message. This will hopefully make it easier to track down problems with frozen focus.
- LoggerNet Server - Fixed a bug where the alert2 base monitor command was not being removed when communications were disabled. This resulted in any attempt to delete the base while it was on-line getting stuck waiting for the base to go off-line.
- LoggerNet Server - Changed the base PakBus router code so that, when a link is reported deleted and there are pending transactions that appear to use that link, a failure will be reported for those transactions. This may be of some use to customers who are experiencing problems with transactions getting stuck in the queue after a hello message timed out.
- LoggerNet Server - Added code in the periodic save device handler for PakBus/TCP routers that will check the routes for any unrouted messages that have been enqueued for longer than one minute, require a static route, and there is a route for that static route's neighbour. When these conditions are satisfied, a delivery failure will be reported for that neighbour and port.
- LoggerNet Server - Changed the log baler component to use the Csi::move_file() function to rename log files rather than the "C" run time version. The move_file() function can work with unicode file names while, apparently, the ::rename() expects multi-byte format.
- LoggerNet Server - Changed the method that calculates the time stamp for an alert2 sensor report value so that, if the sensor report does not have a reported time stamp, the received time less any specified time offset will be used as the time stamp for the value.
- LoggerNet Server - Fixed a bug where, if a table based collect area was renamed, the transactions that enumerate tables for data brokers and devices were not being updated.
- LoggerNet Server - Removed the code that generates a default set of sensor reports when a new alert2 station is added. It is much simpler to allow the client to perform this as that leaves only one place where we have to worry about what those defaults should be.
- LoggerNet Server - Changed the file control operation for BMP5 dataloggers so that, if an OS is being started, we will force the server to wait a minimum of 2.5 minutes (150 seconds) before attempting to restart the link to the datalogger.
- LoggerNet Server - Added a watch dog timer for the communication command used to communicate with an ALERT2 base so that a beacon (\r\n) will be sent on the link if more than two minutes elapse without receiving any data on the link.
- LoggerNet Server - Changed the rename() method for the base TableArea class for collect areas so that the tables written setting gets updated with the new name. This will ensure that the enabled state will be correctly reported to the table collator.
- LoggerNet Server - Added an optional parameter to the LgrNet Restore Snapshot command that allows the client to specify the state of the LgrNet commEnabled state when the restoration is complete.
- LoggerNet Server - Removed support for the NTCIP-RWIS version 1 and version 2 type stations. These relied on increasingly antiquated libraries that were difficult to update and rebuild for static linking and were not used by our customers.
- LoggerNet Server - Fixed a bug in the windows version of TCP clients where socket handles could be leaked when trying more than one address to reach a named host. This manifested as a server lock-up on large networks where some sites failed to connect.
- LoggerNet Server - Changed the PakBus/TCP server so that the max time on-line setting is ignored.
- LoggerNet Server - Changed the parser for newer BMP5 datalogger table definitions so that, if only the table size has been changed, the new size is larger than the existing table.
- LoggerNet Server - Overloaded the comm disabled handler for the BMP5 hangup delay operation as well as for the clock check/set operation in order to ensure that these operations are closed when communication becomes disabled.
- LoggerNet Server - Added a new message that will be broadcast to all LgrNet session clients when a snapshot has been restored.
- LoggerNet Server - Fixed a bug where the pakbus encryption key settings was not reported for any of the granite series loggers.
- LoggerNet Server - Changed the way that IPv6 broadcasts are done when performing a UDP search. The behavior should match that of Device Configuration Utility.
- LoggerNet Server - Changed the BMP5 implementation for the program file send transaction so that the program is not stopped when sending an OS to a CR300, CR6, CR1000X, GRANITE 9, GRANITE 6, or GRANITE 10 dataloggers.
- LoggerNet Server - Changed the file synch so that the history now tracks when a file should be deleted but wasn't able to because of comm failures. This addresses a problem that was found on Mount Everest where the link was timing out before we had retrieved all of the files and none of the files that should have been deleted were ever deleted.
- LoggerNet Server - Changed the file synch so that pending deletes take precedence over pending retrievals.
- LoggerNet Server - Fixed a bug in the BMP5 set variable implementation that prevented the server from setting string variables that were declared with a size greater than or equal to 995. The implementation was producing a PakBus message that was unrouteable due to its size. The fix is to avoid attempting to fill all bytes of the variable with trailing nulls but to set the variable to the client specified value with at least one trailing null. If the result is too large, the transaction will be reported as a failure. Eventually, we will need to create a new transaction that can be used to transfer large objects for variable values.
- LoggerNet Server - Removed the code that set the lastComPortId setting when handling an incoming socket for callback.
- LoggerNet Server - Implemented the code that creates the new data file import collect area as well as settings to support that area type. Also implemented the code that parses data files and attempts to import their data into new or existing broker tables.
- LoggerNet Server - Implemented support for the logger query EX transaction for BMP1, BMP3, and BMP5 (all table based) dataloggers.
- LoggerNet Server - Fixed a bug in the LgrNet delete branch transaction where the incorrect outcome code was reported if the client specified an invalid device name.
- LoggerNet Server - Fixed a bug that was introduced into the formatted data advise where the record number, file mark number, and time stamp were not being written to the notification message.
- LoggerNet Server - Added code in the BMP5 implementation of the logger query ex transaction that will ensure that records are not repeated.
- LoggerNet Server - Fixed a bug in the logger query ex transaction where the client specified station name was not applied.
- LoggerNet Server - Changed the mechanism to track expected records within the logger query ex transaction.
- LoggerNet Server - Fixed a bug in the BMP5 implementation of Logger Query EX that could result in collecting the entire table while collecting record range if the client's end record number was not in the table.
- LoggerNet Server - Fixed a bug where received bytes from the cc proxy conn provider were not transmitted to the root level device. This only has impact on LoggerNet operating within the Campbell Cloud.
- LoggerNet Server - Fixed a bug where the socket close method for the cc proxy conn provider got confused with the provider close method. As a result, the state of the provider was wrong when the connection to the proxy service was made.
- LoggerNet Server - Fixed a bug in the default value of the CCProxyConnInfo setting where the datalogger IP address property was misnamed.
- LoggerNet Server - Removed quotes from the timestamp pattern when formatting records for collected data.
- LoggerNet Server - Added missing BMP3 implementation of the LoggerQueryEx transaction for linux.
- LoggerNet Server - Fixed a bug in the LgrNet udp discover transaction where the serial number was being misreported as the OS version.
- LoggerNet Server - Added code to print the table name in transaction log events that mark the receipt of records from logger query.
- LoggerNet Server - Added code to ensure that the ranges of expected record numbers are ordered before sending the request to the datalogger. Also added code to clear the newest record if it happened to be reported by the datalogger.
- LoggerNet Server - Changed the BMP5 implementation of logger query ex with the start-at-record option so that the calculated oldest record number for the table is used in place of the client's when the client's is determined not to be in the table.
- LoggerNet Server - Changed the CCProxyConn device type so that it applies a five minute timeout while it is waiting for the proxy server to make a connection back to LoggerNet. It will advertise this interval in the connection request and also will advertise the current GMT epoch of when the timer was set.
- LoggerNet Server - Added code to look for 'GRANITE9", "GRANITE10", and "GRANITE6" identifying strings in the terminal output when attempting to identify the protocol and model using terminal commands.
- LoggerNet Server - Fixed a bug in the BMP5 implementation of logger query ex handling record fragments where the begin record number was not being specified for the p1 parameter.
- LoggerNet Server - Added code in the CCProxyConn provider so that messages associated with listening for incoming connections from the loggernet proxy are logged in the communications log.
- LoggerNet Server - Fixed a bug where the error handler for the CCProxyConn provider listener was not reporting any problems to the application.
- LoggerNet Server - Changed the CCProxyConn device type so that it only binds to IPv4 interfaces while waiting for a connection from the proxy.
- LoggerNet Server - Changed the CCProxyConn device so that it will look for a "failed" report from service-campbellsci-proxy as well as a "queued" message. Also added code that will set the watchdog timer after the connection request has been transmitted. This will allow us to work around the case where service-loggernet-proxy is not responding.
- LoggerNet Server - Fixed a bug where the LoggerNet monitor view transaction would not fail if the client specified an invalid view ID.
- Short Cut - Added support for GRANITE 6, GRANITE 9, GRANITE 10, GRANITE TEMP 120, GRANITE VOLT 108, and GRANITE VOLT 116
- Short Cut - CDM and GRANITE modules now show the user-defined “Module Name” throughout Short Cut, including on the corresponding module tab, measurement grids, wiring diagram, wiring text, summary, and so forth.
- Short Cut - Added the following new or updated sensor files: SkyVUE8 Ceilometer,SkyVUEPro (rebranded CS135),GPS16X-HVS GPS Receiver (Added support for the CR6, CR1000X, GRANITE 6, GRANITE 9, and GRANITE 10 dataloggers.),LevelVUEB10 Water-Level Continuous Flow Bubbler,CS547A Conductivity and Temperature Probe (Added support for the CR6 and CR1000X),TS100SS Aspirated Radiation Shield,Type B, E, J, K, N, R, S, and T thermocouples on the GRANITE TEMP 120,TS100SS Aspirated Radiation Shield,CS241 (2-wire) Class A RTD Back of PV Module Temperature Sensor,CS241 (4-wire) Class A RTD Back of PV Module Temperature Sensor, [CAN] - CAN Port Configuration, - DBC Read Signal, - DBC Write Signal, - Generic Read Signal, - Generic Write Signal, [CAN FD] -CAN FD Port Configuration, - DBC Read FD Signal, - DBC Write FD Signal, - Generic Read FD Signal, - Generic Write FD Signal
- Short Cut - Replaced SC115 with USB was only done for the GRANITE 6,9,10. Other loggers are unchanged.
- Short Cut - Added a search (filter) to the DBC display form to help find the specific signal. Added a display of the number of signals.
- Short Cut - Fixed a bug where a double click to edit was locking the cursor and tool tip in drag mode.
- Short Cut - Fixed a bug where the table name was not displayed for TD loggers.
- Short Cut - Fixed some issues when mapping the datalogger integration for use in a mux file. For example the CDM may use different integration than the datalogger.
- Short Cut - !!Note!!: Beginning with this version of Short Cut, CDM modules are no longer supported for the CR1000, CR3000, and CR800 series. CDM modules are still supported for the CR6 series and CR1000X series. However, the way the modules are programmed in CRBasic is handled differently. Therefore, for existing Short Cut program files, the modules will need to be removed and then added again.
- RTMC - Fixed an issue where the fill and clear of scope was creating an out of bounds scale condition.
- RTMC - Added a check to prevent out of bounds values from locking the application up.
- RTMC - Added a console log that allows users and support to have more info when a data failure occurs.
- RTMC - Resolved an issue where the graph would not refresh in QuickReports upon completing its' data acquisition.
- RTMC - Fixed an issue if the series was not available an OleException was thrown. This happens in an extremely rare circumstance.
- RTMC - Modified the code to make sure that the table uri is persisted, for QuickReports, to make it available for the dialogs and also the error given if no data is available.
- RTMC - Added PostgreSQL and Oracle types to be populated as datasources.
- View Pro - Fixed a problem with reading binary files containing values stored using IEEE8B.
- View Pro - Fixed an issue when indexing TOB2 and TOB3 files that was skipping records when encountering an empty frame footer.
- View Pro - Added the missing IEEE8L data type.
- View Pro - Modified the main window to open in the maximized state if it was in that state before it was closed.
- View Pro - Fixed an issue where IEEE8 values were not being added to the graph for TOB files.
- View Pro - Fixed and Error parsing files that contrained commas withing quotes.
- View Pro - Fixed and Error parsing files that contained commas within quotes.
v1.3November 9, 2017
- RTDAQ is no longer supported on Windows XP and Windows Vista.
- Added support for the CR1000X datalogger.
v1.2March 9, 2015
- Requirement - .Net 4.0 framework (full profile) is required for this application to run in its entirety. The .Net 4.5 framework may also be installed on the system as it is an upgrade to the 4.0 .Net framework and will allow the application to run in its entirety.
- RTDAQ Enhancements - Added support for CR6 Series dataloggers.
- RTDAQ Enhancements - Added support for dragging and dropping files from Windows Explorer onto the File Control dialog.
- RTDAQ Enhancements - Added support for modifying Station Status
- Status Table values via the double click.
- RTDAQ Enhancements - Added ability to use MD9 connection.
- RTDAQ Enhancements - Added PakBus Encryption Key setting to the CR1000/CR3000/CR800 Series/CR6.
- RTDAQ Enhancements - Added the ability to view a file from File Control.
- RTDAQ Bug Fix - Changed Max Time On-Line maximum to 23 h 59 m 59 s.
- RTDAQ Bug Fix - Changed default Beacon Interval to 0.
- RTDAQ Bug Fix - Time zone offset is now applied when finish is clicked as well as when the user sets the clock.
- RTDAQ Bug Fix - Trying to send an OS to a 2 Meg CR1000 now gives the correct error message.
- RTDAQ Bug Fix - Removed the Time of Fill column from the Station Status because the information was not always correct.
- RTDAQ Bug Fix - Fixed a bug when dealing with very large records.
- RTDAQ Bug Fix - Long table names and long variable names are now supported.
- RTDAQ Bug Fix - Changed the Minimum Graph Width on a Fast Graph to 1 ms.
- RTDAQ Bug Fix - Fixed a scaling problem when zooming in on a Histogram when in "Show Values" mode.
- RTDAQ Bug Fix - Fixed a problem where the Y-axis label would sometimes overwrite a scale value.
- RTDAQ Bug Fix - Fixed a problem where when Collect Mode was set to "Fill Graph Width", data was not displayed smoothly over time. It would scroll for a short time, displaying data, and then stop. It would then go and stop perpetually.
- RTDAQ Bug Fix - Fixed a problem where you would get a different Graph configuration when reopening a graph from the Monitor Data tab depending on whether the graph was configured manually or by using File
- Load Configuration.
- RTDAQ Bug Fix - Fixed a problem in the Fast Graph, where a line was occasionally drawn through an existing curve.
- RTDAQ Bug Fix - Fixed a problem with a stopped Fast Graph and historical buffer active, where the prompt was inaccurate (i.e., Page 8 of 2 or Page 13 of 7).
- RTDAQ Bug Fix - Fixed a problem where the labels in RTDAQ real-time FFTs were not correct for the case of logarithmic binning.
- RTDAQ Bug Fix - Fixed an issue where if a maximum time on-line event is reached, forcing a disconnect on a datalogger while it is collecting records (data since last) that the latest record collected (just before the forced disconnect) does not get written into the csilgrnet.xml file (the last record collected pointer isn't updated there for collection purposes).
- RTDAQ Bug Fix - Fixed an issue where when tables were reset, data collected using "Data Since Last Collection" did not collect the correct records.
- RTDAQ Bug Fix - Fixed an overlapping problem in the FFT viewer when looking at dual-valued FFTs (real/imag or amp/phase).
- RTDAQ Bug Fix - Fixed a problem where the directory dialog would crash when an invalid path was specified.
- RTDAQ Bug Fix - Fixed a bug where the FFT graph was not handling INF values properly.
- RTDAQ Bug Fix - Fixed a problem where the behavior between the Trace Options dialog box and the Trace Options in the Graph dialog box was not the same.
- Short Cut Enhancement - Added support for CR6 Series dataloggers.
- Short Cut Enhancement - Added new or updated sensor files for the Switched 12 Volt Timed Control, CS475/CS476/CS477 Radar Water Level Sensor, GPS16X-HVS GPS Receiver, CS140 Luminance Sensor, CS120 Visibility Sensor, PWS100 Present Weather Sensor, CS125 Present Weather and Visibility Sensor, CS135 Ceilometer, Jewell Instruments 904-T Clinometer Pak, DGSI Vibrating Wire Strain Gage, DGSI Vibrating Wire Piezometer, Generic Thermistor (CR6), CS11 Current Transformer, CS11 Current Transformer with Potential Transformer, Geo-Instruments Electrolevel Tiltmeter, VTI ECI-1 Embedded Corrosion Instrument, Modbus Master, Modbus Slave, BS-3+/OBS300 Turbidity Sensor, HC2S3 Temperature and Relative Humidity Sensor, OBS500 Smart Turbidity Meter (SDI-12), Device for Analog Input from SDM-AO4A, 52202 Rain Gauge (CSI), CMP3/CMP6/CMP11 Pyranometer, CS526/CS525 ISFET pH Probe, 020C Wind Direction Sensor, A100LK Wind Speed Sensor, 092 Barometric Pressure Sensor, 61302V Barometric Pressure Sensor, P2546A Wind Speed Sensor, 110PV Surface Temperature Probe, and a Wind Vane Installation Offset Correction (calculation)
- CRBasic Editor Enhancement - Added support for CR6 Series dataloggers.
- CRBasic Editor Enhancement - Added support for optional parameters (for instructions that have them) in parameter dialog box.
- CRBasic Editor Enhancement - Added ability to copy compile results to clipboard.
- CRBasic Editor Enhancement - The CRBasic Editor now allows you to Save and Open Display Settings. Display settings affect the look and feel of the CRBasic Editor. This includes font and background, as well as syntax highlighting.
- CRBasic Editor Enhancement - Added Unicode support.
- CRBasic Editor Enhancement - To support Unicode, an Insert Symbol dialog box has been added to the CRBasic Editor. This allows you to insert Unicode symbols into your CRBasic program for use in Strings and Units declarations.
- CRBasic Editor Enhancement - Added the Shift+Insert hotkey to perform the paste function.
- CRBasic Editor Bug Fix - Fixed a problem with the Undo list using up a large amount of memory.
- CRBasic Editor Bug Fix - Fixed an error when attempting to compile a program when the previous program was saved in a folder that no longer exists.
- CRBasic Editor Bug Fix - Fixed an access violation that occurred when clicking the red x in the Confirm dialog box. It is to be noted that the access violation only happened if the cursor was on a blank line.
- CRBasic Editor Bug Fix - Fixed a problem when attempting to replace the baud rate parameter in the SerialOpen command, by using right-click to choose from the variable list. Rather than replacing the previous baud rate, it inserted a second baud rate.
- CRBasic Editor Bug Fix - Fixed a bug where the Undo/Redo could be very slow (up to 6 seconds for one redo) for very large files.
- CRBasic Editor Bug Fix - Fixed so that when a line is selected and you scroll down or up it will scroll nicely at the extremes of top and bottom.
- CRBasic Editor Bug Fix - Fixed a problem with deleting templates.
- CRBasic Editor Bug Fix - Fixed a problem where the insert key was not toggling between insert and overwrite.
- CRBasic Editor Bug Fix - Made the editor's screen position and window size persistent even in a dual monitor environment.
- CRBasic Editor Bug Fix - Files opened with a double click will now cause the editor to open in the last window size used by the editor.
- CRBasic Editor Bug Fix - Cursor doesn't go to end of line when enter is pressed splitting a line
- CRBasic Editor Bug Fix - Fixed a problem where the Save As dialog appended an extra extension when you replaced the default extension with .dld.
- CRBasic Editor Bug Fix - Fixed a problem during a switch from the find dialog to the replace dialog, the state was confused and it did not see the search word had changed.
- CRBasic Editor Bug Fix - With the Find dialog box open, you can now use the Paste functionality to paste into the program.
- CRBasic Editor Bug Fix - Fixed an issue where the cursor was sometimes misplaced after an F10 variable insert/replace.
- CRBasic Editor Bug Fix - Fixed an issue where an extra set of parenthesis was added when using the F10 (Replace Variable) feature to replace an array variable.
- RTMC Enhancement - Added RESET_WEEKLY and RESET_CUSTOM options for functions with state that reset. RESET_CUSTOM allows for an optional expression to control the state of when the function will reset.
- RTMC Enhancement - Added a flag to tabs with active alarms on them.
- RTMC Enhancement - Added support for Unicode.
- RTMC Enhancement - Added support for IPv6 addresses.
- RTMC Enhancement - Added the ability to change fonts for tables. Header and contents individually in Pro.
- RTMC Enhancement - Added a feature to allow copying an entire screen at a time.
- RTMC Enhancement - Changed the Configure Workspace to behave the same way as RTMC Pro.
- RTMC Enhancement - Added the functions AvgSpa, MinSpa, and MaxSpa to the expressions engine.
- RTMC Enhancement - When browsing for data that needs to be read/write, the R icon turns red to indicate it is a read only value.
- RTMC Enhancement - Added new z-order options for a single step forward or backward.
- RTMC Enhancement - Added option to undo multiple groups.
- RTMC Enhancement - Component naming is now more dynamic and tracks the data it is associated with. Chart titles are used in the name if it is one word. Labels also use the title. Images pull out the image name.
- RTMC Enhancement - Added a paste menu item to the component menu.
- RTMC Enhancement - Added a new function, SelectSwitch(), that can be used to select from multiple case predicate and value combinations. The behavior of this function is similar to that of nested IIF statements.
- RTMC Enhancement - Locale is now used when formatting numbers. Instead of 1234567 you see 1,234,567.
- RTMC Bug Fix - Changed the expressions as well as alarm comparators to round the values down to 7 decimals and then do the comparisons. This cleans up all of the artifacts that show up in the floating point operations.
- RTMC Bug Fix - Change 'Set Point' and 'Digital' to display timestamps recorded within data tables (time of maximum) as timestamps by default instead of nanoseconds.
- RTMC Bug Fix - Fixed a bug where the chart series was using the current locale to format time stamp values. If this value was then interpreted again as a date, the PM of the date portion was lost.
- View Pro Enhancement - Fixed FSL file loading and a range check error in the Array Definitions dialog.
- View Pro Enhancement - The XY Plot now supports multiple XY series. A series selection panel has been added, along with a "New" button that creates new XY series.
- View Pro Enhancement - Added ability to import CSV files.
- View Pro Enhancement - All of the dialogs in View Pro are now translatable.
- View Pro Enhancement - Added a search function to the main grid accessible using ctrl-f, or Edit/Find.
- View Pro Enhancement - Added the record view dialog to address the requirements for displaying a status table record. The record view dialog will work for any CSI file type displayed in a grid.
- View Pro Enhancement - Added cancel button to Selection Properties under line graph, FFT, Histogram, Rainflow Histogram, and XY Plot. Also added cancel buttons to Graph Options screens associated with the listed graph types. This change will change back the on-screen live changes.
- View Pro Enhancement - Extensively revised the print preview code so only one page preview is shown at a time. Also redid the print code. Print Preview will no longer "count pages". Switching from portrait to landscape or back now happens instantaneously without showing a dialog.
- View Pro Enhancement - Added two decimal places to the selection data on the graph.
- View Pro Enhancement - Multiple large FFTs in the same file are now supported.
- View Pro Enhancement - Changed page up/page down functionality to match Excel rather than open office calc.
- View Pro Enhancement - Bool8 is now supported for TOB(X) data files
- View Pro Enhancement - Added support for the Rainflow Histogram Sample process strings.
- View Pro Bug Fix - Fixed a problem with the view grid mouse state missing the mouse up event allowing the data grid to scroll with the mouse when the mouse pointer is off of the application.
- View Pro Bug Fix - Trying to copy data from an empty column no longer causes an access violation
- View Pro Bug Fix - Fixed a problem where the last record was missing in the graph when an entire column was graphed
- View Pro Bug Fix - Fixed a problem where the number of points displayed in a line graph was one less than the number reported.
- View Pro Bug Fix - The values in the statistics dialog are now correct when panning.
- View Pro Bug Fix - Scrolling one line graph associated with a view file will no longer update the position of the scroll bars on other line graphs associated with the same file
- View Pro Bug Fix - Fixed an unzoom/unpan issue that put the Y axis on a line graph in custom axis mode.
- View Pro Bug Fix - When scrolling in the graph the data grid view no longer scrolls when there is less than a page of data
- View Pro Bug Fix - Changed the file parser to be more tolerant of extra lines at the end of a file.
- View Pro Bug Fix - Opening an empty DAT file from the data collection results dialog will no longer lock view from opening subsequent files.
- View Pro Bug Fix - TOA5 files with no time stamp or record number will now open.
- View Pro Bug Fix - Fixed a binary file parsing issue where the record size for some files was being calculated incorrectly, resulting in erroneous offsets.
- View Pro Bug Fix - No longer showing erroneous message about too many records when column selections don't match up in the XY Plot.
- View Pro Bug Fix - Fixed an issue where the y-axis didn't clear after removing a selection that was graphed using record numbers on the x-axis.
- View Pro Bug Fix - Closing View Pro after viewing a binary file as text will now work.
- View Pro Bug Fix - Fixed panning then clearing line graph access violation.
- View Pro Bug Fix - Fixed time stamp comparison code that wasn't precise enough for some files.
- View Pro Bug Fix - When the database connection fails to connect an error dialog will now appear.
- View Pro Bug Fix - Changed the method for calculating the standard deviation to match the method found in the data logger operating systems.
- View Pro Bug Fix - View Pro will no longer fail to terminate a string when a null value was encountered. Non-string data in strings will no longer show up when null values are contained therein.
- View Pro Bug Fix - Boolean values will now show as -1 and 0 rather than true and false.
- Split Enhancement - Added 'qq' to format string. Acts like hh except gives 24 at midnight.
- Split Enhancement - Added two more custom date format strings TOA5 and 24TOA5. The former produces a TOA5 formatted timestamp. The latter does the same except with midnight set to 24:00:00.
- Split Enhancement - Unicode support added.
- Split Enhancement - Enhanced -time offset crossing year boundary. So on first day of the year, a negative offset can back up to previous year.
- Split Bug Fix - Fixed HourArray and dayofyear format strings so that they work properly when a time offset is used. Also these fields were not properly quoted when Date vs Edate was used. Fixing this may break existing .PAR files. These (and the "Serial" format string) are intended to be used as the entire format string e.g. edate("dayofyear";4;3;2).
- CardConvert Enhancement - Added 2400 hours at midnight support.
- CardConvert Enhancement - Added Unicode support.
- CardConvert Bug Fix - Fixed some issues with TOB1 files that grow over 4 Gb.
- CardConvert Bug Fix - Fixed 'headers do not match' error displays.
- PakBus Graph Enhancement - Added support for IPv6 addresses.
- PakBus Graph Enhancement - Added Unicode support.
- PakBus Graph Bug Fix - Fixed a bug where settings editor sub-panels were getting deleted twice if the settings were reloaded.
- LogTool Enhancement - When the LogTool is running remotely and zip all log files is selected, files are now zipped up to a specific file on the server's machine, and then transferred to the client's machine to the location that the user selected.
- LogTool Enhancement - When retrieving a zipped file from a remote server, the percentage of the file retrieved so far is now displayed.
- LogTool Bug Fix - Delete Log Files and Zip Log Files are now only enabled if security level is Full Administrator.
- LogTool Bug Fix - Fixed an issue where you could not Save/Copy/Print the text of a Low Level Log window after its internal buffer had been "filled".
- Device Configuration Utility Enhancement - Added support for the CR6 Series, CRS451, CRVW, VSC100, CS125, CS140, RavenXT, RF401A, LS300, CSAT3B, NL200, CC5MPX, CDM-VW300 Series, TX312/TX320, NL240, AL200, CRS450 Series, SC-CPI, OBS500, EC120.
- Device Configuration Utility Enhancement - Added wizards to back up a datalogger's settings and files to a zip file and to restore these from a zip file.
- Device Configuration Utility Enhancement - Added a data recovery wizard.
- Device Configuration Utility Enhancement - Updated support for the CRX000 dataloggers, AL200, CC5MPX.
- Device Configuration Utility Enhancement - Added a context menu option to the terminal emulator that will allow the user to toggle whether new lines are time stamped as they are added.
- Device Configuration Utility Enhancement - Changed the file control panel so that, if the user attempts to send an operating system to the datalogger, an operation will be included that will start that operating system using the file control transaction.
- Device Configuration Utility Enhancement - Added ability for some devices to be configured over the network (using IP).
- Device Configuration Utility Enhancement - The device type can now be categorized. This is controlled from the Options menu.
- Device Configuration Utility Enhancement - Added an optional button to the Logger Control panel that will allow the user to retrieve the currently running program from any datalogger that supports retrieval (CR1000, CR3000, CR8xx, CR10X-XX, CR23X-XX, CR510-XX, CR5000, and CR9032).
- Device Configuration Utility Enhancement - Added new settings for the CR1000, CR3000, and CR800 to configure the NL240 bridged network stack
- Device Configuration Utility Enhancement - Added code to the datalogger passwd file editor dialogue that will allow the file, when written to the datalogger, to optionally be marked as hidden on the datalogger. This has been done in order to avoid having the file read by the web or FTP server since doing so could assist in breaking the datalogger security.
- Device Configuration Utility Enhancement - Added support for a Bluetooth serial port.
- Device Configuration Utility Enhancement - Enabled the SDI-12 option for the CWB100.
- Device Configuration Utility Enhancement - Increased the length limit on the "PPP User Name" component of the "PPP Configuration" setting for the CR1000, CR3000, and CR8xx from 31 to 63 characters.
- Device Configuration Utility Enhancement - Added ability to copy from help/description area. Also added copy and paste support to terminal.
- Device Configuration Utility Enhancement - Changed the file selection controls in the browse configuration summaries dialogue so that a directory picker is used in conjunction with a list box that shows the possible files in the chosen directory. The directory picker has a browse button that brings up a standard directory browse dialogue.
- Device Configuration Utility Enhancement - Added options for 300 fixed for the baud rate settings for the COM1-COM4 devices for the CR1000, CR800, and CR3000 dataloggers.
- Device Configuration Utility Enhancement - Added IPv6 support.
- Device Configuration Utility Enhancement - Added a file control panel for PakBus dataloggers that support file systems.
- Device Configuration Utility Enhancement - Added support for a new setting, PakBus Encryption Key for the CR1000, CR3000, and CR8xx device types.
- Device Configuration Utility Enhancement - Added Unicode support.
- Device Configuration Utility Enhancement - Added store log files to the Options menu. The default value is off and when this is off, only minimal logging occurs. When this is on, normal logging occurs (including logging the PakBus password).
- Device Configuration Utility Enhancement - Added support for new functionality in the CWS900 implemented with version 2 of the CWS900 operating system.
- Device Configuration Utility Bug Fix - The AL200 Slot Offset setting will now be interpreted as an unsigned four byte integer rather than as an unsigned two byte integer.
- Device Configuration Utility Bug Fix - Fixed a bug in the settings editor panel where a poll attempt could take place after a session failure. This could lead to a crash due to an unhandled exception.
- Device Configuration Utility Bug Fix - Made the code that checks the length of the telnet password conditional on that setting being reported. This addresses an issue where a special version of the OS didn't support the deployment panel.
- Device Configuration Utility Bug Fix - Added code in the handler for command completion that will check to make sure that the transaction queue is not empty before handling the command outcome. This addresses a bug that could lead to a crash when power was pulled on the TX320 while polling transactions were under way.
- Device Configuration Utility Bug Fix - Fixed a bug where the NL2xx deployment panel was attempting to unconditionally poll the IPv6 address regardless of whether the device reported the setting. This could lead to an unhandled exception when connecting to an NL200 with an older OS.
- Device Configuration Utility Bug Fix - Added code to stop automatic updates of settings such as IPv6 status when settings are changed in the NL2xx deployment panel.
- Device Configuration Utility Bug Fix - Fixed a bug where the settings manager component was returning true to the query of whether settings needed to be committed when there was a cancel or commit operation under way. The result was that DevConfig would post a modal dialogue confirming close if the user tried to close the application while a cancel or commit operation was under way and could result in an unhandled exception.
- Device Configuration Utility Bug Fix - Fixed a bug in the RF430 deployment where, when settings were loaded from the radio, the radio address control was initialized with the value of the network address.
- Device Configuration Utility Bug Fix - Changed the code that compares formatted setting values in the configuration summary comparison dialogue so that the comparison is performed in a case-sensitive fashion.
- Device Configuration Utility Bug Fix - Increased the maximum security code (when connecting) from 65535 to 99999.
- Device Configuration Utility Bug Fix - Changed the behavior of the "Edit .csipasswd File" button in the deployment panel for the CR1000, CR800, and CR3000 so that the value of the hide check box is preserved in the application configuration and restored when the dialog is created afresh.
- Device Configuration Utility Bug Fix - Fixed a bug where a *.a43 pattern was used to search for SDM-SIO1 instead of *.hex
- Device Configuration Utility Bug Fix - Fixed copy and paste.
- Device Configuration Utility Bug Fix - Fixed a bug with the PakBus routes setting where the port number was not large enough to handle all of the values that the datalogger could use.
- Device Configuration Utility Bug Fix - Now correctly report the European variant of the serial number.
- Server Enhancement - Added support for the CRVW and CRS500 datalogger types.
- Server Enhancement - Added code in the serial port thread so that, if the simplified I/O is enabled, the thread will use a timer that will get reset whenever data is transmitted or received. If this timer expires, the thread will call SetCommState() in an attempt to force communication over a USB serial port in order to test if the driver connection is still valid.
- Server Enhancement - Added support for an optional parameter to the device files enumerate command message that will allow the client to specify a pattern that will be used by BMP5 dataloggers to restrict the set of files that are reported.
- Server Enhancement - Implemented the device force link offline transaction.
- Server Enhancement - Changed the BMP5 implementation of the device set variable transaction so that it recognizes when the datalogger sends the response code indicating that it needs to reboot. The server will now shut down the link and wait for the specified amount of time before reporting the outcome and launching the poll.
- Server Enhancement - Added a new coralib function, cora_on_device_change(), that can be called to inform the server that a potential device remove device has been detected. Added code in the serial port class and its associated provider that will conduct a test to determine whether the serial port handle is still valid as a result of that method. Doing this gives the server a chance to detect USB serial port failures more reliably.
- Server Enhancement - Changed the behavior of the BMP5 file control command so that, if the original command specified that the data should be left in the datalogger tables, the server will preserve the data in its own cache table as well. This should provide a means to change the program without losing data from the cache.
- Server Enhancement - Changed the parent/child configuration rules to allow a PakBusPortHD device type to be added as a child to an MD9 Passive device type.
- Server Enhancement - Added IPv6 support.
- Server Enhancement - Changed the code that parses table names, column names, unit strings, and process strings for BMP3 and BMP5 dataloggers so that these strings are assumed to be encoded as utf-8 rather than using the local code page. If these strings fail to convert as UTF-8, the local code page will be used to convert the strings to Unicode.
- Server Enhancement - Added a timer to delay the automatic retrieval of table definitions by fifteen seconds
- Server Enhancement - Added support for the new option for the server to send the "extended" version of the data broker data advise start acknowledgement message. This extended version allows whole arrays to be described with one entry instead of an entry for each array element. This is to support increased efficiency when dealing with large data records.
- Server Enhancement - Added support for PakBus Encryption (AES-128).
- Server Enhancement - Changed the device file enumeration transaction so that it can send a longFileSize attribute as well as a fileSize attribute. This change was made to support large (> 2 GB) file system capacities on the datalogger.
- Server Enhancement - Added a code in the device file control transaction implementation to deal with the new compile, pause, and mark tables as full control option that is available for the CR1000 and cousins. This is a mechanism to allow recovery of data that has been lost on the datalogger after a power loss (the user forgot to set the run on power up bit) or after the user inadvertently sent a program to the datalogger.
- Server Enhancement - Changed the BMP5 get compile results and get table definitions transactions to alter the compile results with a warning if there is a program running but there is no power up program running
- Server Enhancement - Changed functions and classes that deal with file names and directory names so that they assume the use of Unicode encoding.
- Server Enhancement - xtended the time that the PakBus/TCP Server will wait on a new connection before hanging it up from five seconds to forty seconds. Also added code so that this device will broadcast a hello request on new connections if no activity has occurred within five seconds of the initial connection.
- Server Enhancement - dded a transaction log message that gets posted each time that the next time to poll gets calculated.
- Server Bug Fix - Changed the BMP1 operation/transaction relation so that the on_message_being_sent() operation method has the ability to prevent the message from being sent by its return value. This should prevent the BMP5 tunnel carrier operation from sending an empty message when the router has nothing to send.
- Server Bug Fix - Fixed a bug in the code that unregisters a static route where we could use the wrong address to access the child list under certain configurations. This resulted in an unhandled exception that forced the server to reset.
- Server Bug Fix - Added an optional flag to the device startUp() method so that setting changed flags will be cleared only if that flag is set. Changed the rename and move network map modifiers so that this flag is not set when the newly renamed or moved devices are started. This will allow any pending changes to be written when the device configuration is written
- Server Bug Fix - Added code for the BMP1 table poll operation that will prevent the server from sending a hole collection command to the datalogger that is larger than the logger can handle. (This was already being done for the hole collection operation but was not for the table polling version.)
- Server Bug Fix - Fixed a bug that could crash the server when multiple set value commands were queued for a mixed-array datalogger while the datalogger was in an off-line state. This could set up the conditions where an infinite recursion took place until the program stack was exhausted and the server crashed.
- Server Bug Fix - Modified the code in the cache manager thread that adds records for a table so that older records will be eliminated if a set of records is larger than the size of the cache table. Failure to do this could result in inconsistent information for table blocks because too few records were "released".
- Server Bug Fix - Fixed a bug that could crash the server if it was trying to open the link on a TCP serial port and the address look-up failed for the specified address.
- Server Bug Fix - Fixed a bug where, if an exception was thrown when an incoming TCP messaging connection was handled, that exception would wind up crashing the LoggerNet server.
- Server Bug Fix - Added code to handle the case when a communication error is reported by another operation in order to ensure that the logger lock was released.
- Server Bug Fix - Added code to ensure that any reports associated with a device are removed when that device gets shut down. Failure to do this could lead to a crash if the device was deleted after being shut down
- Server Bug Fix - Fixed a bug in the shut down code where the device was removed from the network map structure before its shutdown() method was called. On some networks, this could lead the server to throw an unhandled exception when it was being shut down.