The following is a list of current known issues and their respective work-arounds. This list applies to DT80/81/85 firmware version 7.10 Last updated 17-Sep-2009 ------------------------------------------------------------------------------- 1936 Using the web UI config tool, image files cannot be uploaded to logger when connected via a crossover Ethernet cable or on a network with no DHCP server (169.254.x.x address). WORK-AROUND: Use a static IP address for the logger; alternatively manually upload the images to the logger's b:\user directory using an FTP client. ------------------------------------------------------------------------------- 1933 Realtime data is not returned when the serial sensor port is configured as a command port (PROFILE "SERSEN_PORT" "FUNCTION"="COMMAND"). Unloaded data and other commadn output is returned correctly. WORK-AROUND: Use a different comms port for sending commands. ------------------------------------------------------------------------------- 1855 Incorrect transmit timeout for 2SERIAL channel when HWFC selected. If CTS is inactive then an immediate timeout occurs, rather than after (by default) 10 seconds. WORK-AROUND: Use 1SERIAL port, or use SWFC ------------------------------------------------------------------------------- 1833 DIR/DIRTREE display incorrect (e.g. wrong drive letter in heading) if no drive specified eg. DIR"jobs" WORK-AROUND: Always specify the drive e.g. DIR"b:\jobs" ------------------------------------------------------------------------------- 1778,1779 nSERIAL channel cannot match incoming data that contains a null character (ASCII 00) WORK-AROUND: There is no work-around. ------------------------------------------------------------------------------- 1725 COPYDATA* (copy data for all jobs) does not work. WORK-AROUND: Issue separate COPYDATA commands for each job. ------------------------------------------------------------------------------- 1720 Connect to UDP port 7700 in Detransfer. Command echo and results of eg status command are returned, but no real time data is returned. WORK-AROUND: Use TCP rather than UDP. ------------------------------------------------------------------------------- 1716 P26 flow control timeout is not implemented for serial sensor port. If the port function is set to COMMAND, and HWFC is selected, and the cable is disconnected, then sampling may stop indefinitely (until cable is restored). WORK-AROUND: Set flow control to SWFC or NONE, or use the host RS232 port. ------------------------------------------------------------------------------- 1683 There is no easy way to include commands before a job definition in an oninsert file, and ensure that they complete before the job is loaded, eg: H COPYDATA*; DELALLJOBS; RESET BEGIN"myjob" ... END In this case the DELALLJOBS and RESET will wait for the COPYDATA to complete (because they are entered on the same line), but the job will be entered while the COPYDATA is still running, and will then be deleted by the DELALLJOBS once the COPYDATA completes. WORK-AROUND: Use two separate memory sticks, one to clean up the logger (ie containing COPYDATA*; DELALLJOBS; RESET) and one to load the job. ------------------------------------------------------------------------------- 1660,1661 Possible erratic operation if logger is allowed to sleep with USB memory device connected. If device is removed while the logger is asleep then this may not detected properly, so that on wake, 9SV may be incorrect. Also, the device may not always be read properly on wake, leading to possible errors. WORK-AROUND: Remove memory stick before allowing logger to sleep. ------------------------------------------------------------------------------- 1656 The logger's analog subsystem is powered up when a RESET command is executed, so that it can perform a calibration cycle. However, it is not powered down again until the next time any schedule is executed. This causes power consumption to increase. WORK-AROUND: If power consumption is critical then ensure that if RESET is used then a schedule is executed soon after (can be the immediate schedule, eg just typing 1CV is sufficient). ------------------------------------------------------------------------------- 1636 If an entered expression has invalid parentheses then an error will be returned, which is correct. However, an error may also be returned on the *next* expression entered, even if it is correct. If the correct expression is entered a second time then it will be accepted. WORK-AROUND: Ensure that expressions are correct before entry. ------------------------------------------------------------------------------- 1615 Using the following job with a CEM20 connected: P28=0 RAX 101V RB 1CV=1CV+1 1SSPWR the 12V power output remains on after schedule A completes (it should switch off) WORK-AROUND: Change schedule B to be a non-continuous schedule, eg. RB10T ------------------------------------------------------------------------------- 1602, 1735 Open circuit R or FW channel readings may return random value rather than error. WORK-AROUND: Add a second channel to measure current through the shunt, with excitation enabled - if zero then resistance is open circuit, eg: 3R(4W) IF(3#I(I)<0.1)"Open circuit" ------------------------------------------------------------------------------- 1329 Logger may reset if a time period is used to set size of a schedule's alarm store eg: RA(ALARMS:2D)1S. Note that this is not valid syntax; for ALARMS the size must be specified in records or bytes. WORK-AROUND: Ensure that schedule options are entered correctly. ------------------------------------------------------------------------------- 1254 If you lock a job (using LOCKJOB) that is also the ONRESET job then the job will not be loaded on reset. WORK-AROUND: Do not lock a job if it is the ONRESET job. ------------------------------------------------------------------------------- 1247 If you define a job using a 1SERIAL channel then the serial sensor port is automatically enabled. If you then define a new job which does NOT use the 1SERIAL channel then the serial sensor port should be disabled, but it remains enabled. WORK-AROUND: Use RESET command (or 1SSPORT=0) before entering new job. ------------------------------------------------------------------------------- 1142,1143 Jobs which create large data files and leave only a small amount of free space on the file system may not run properly. WORK-AROUND: Ensure that there is always at least 1MB of free space. ------------------------------------------------------------------------------- 1075 File system errors eg "Media error on drive B:" may occur following triple push reset. These persist until all power is removed from logger, after which it operates normally. WORK-AROUND: When performing a triple push reset wait until the front panel lights flash (approx 3s after releasing reset) before doing the next reset. ------------------------------------------------------------------------------- 1047 LCD bargraph display option (BG:x:y) does not work for integer channel types WORK-AROUND: Assign the value to a CV eg. 1DN(=1CV,W) 1CV(BG:12:15) ------------------------------------------------------------------------------- 1033 If data has been logged to a storefile on the USB memory device (ie the "A:" schedule option is used) then it is not possible to unload or copy/move the data to an FTP server - the DT80 reports "storefile not found". WORK-AROUND: Always log data to the internal (B:) drive if you intend to transfer the data to an FTP server. ------------------------------------------------------------------------------- 1020 Time taken to complete a COPYDATA/MOVEDATA to USB device gradually increases as the number of files on the USB device increases. Once there are 100+ archive files in the one directory on the USB device it can take over a minute before the copy commences. WORK-AROUND: Do not allow large numbers of archive files to accumulate on the USB device. ------------------------------------------------------------------------------- 955 Power loss message clears itself without keypress. - power on reset occurs -> "Power loss" on LCD - onreset job fails to load (eg due to existing non-matching storefiles) - Display reverts back to standard (No current job) screen, ie power loss warning has been cleared, even though no user acknowledgement via keypress. WORK-AROUND: There is no work-around. ------------------------------------------------------------------------------- 920 DT80: When pushing an file to an FTP site, if the file is too large for the site, the FTP fails but a partial file is left on the site. WORK-AROUND: There is no work-around. ------------------------------------------------------------------------------- 919 DT80: When sending data to an FTP site the bar graph showing progress doesn't represent anything close to the actual progress. WORK-AROUND: There is no work-around. In future, the bargraph will not be shown for FTP transfers. ------------------------------------------------------------------------------- 900 Serial triggered schedules not processed in correct order. eg RA1SERIAL("goose") 1SERIAL("\m[goose]:%f[1cv]") RB1SERIAL("duck" 1SERIAL("\m[duck]:%f[1cv]") If the rx buffer contains both "goose" and "duck" msgs at the time that we scan for schedule triggers then both A and B will be triggered at the same time, and A will always run first even if the first msg in the buffer is a "duck" msg. There are also issues with the following example, where the input is either MSGA:1,2,3 or MSGB:1 RC1SERIAL"MSG" 1SERIAL("\m[MSG]%c[9CV]:") IF(9CV><64.5,65.5){XA} IF(9CV><65.5,66.5){XB} RAX 1SERIAL("%f[1cv],%f[2cv],%f[3cv]") RBX 1SERIAL("%f[4cv]") In particular, C schedule is sometimes executed ahead of A/B schedule, causing it to consume the rest of the message. The end result is that when the A/B sched does get to run the rx buffer is pointing at the wrong msg. WORK-AROUND: There is no work-around. ------------------------------------------------------------------------------- 874 Legend 1G mem stick sometimes causes stall error on insertion. WORK-AROUND: Use a different brand of USB storage key device. ------------------------------------------------------------------------------- 872 DT80 - USB stick STALL condition causes reset When a USB memory device is inserted into a device (a DT80 in our case), if it detects a problem as it starts up, it "stalls". This situation is rare, but if it occurs the DT80 will reset. WORK-AROUND: There is no work-around. ------------------------------------------------------------------------------- 868 Alarm delay eg ALARM2(2CV>1/10S) is only applied on rising (false to true) transition; it should also be applied on the falling edge. WORK-AROUND: There is no work-around. ------------------------------------------------------------------------------- 598 Infinite values not returned in a consistent manner WORK-AROUND: Avoid situations in your program (eg division by zero) where infinite values may arise. ------------------------------------------------------------------------------- 555 PE channel factor (wrap value) is not accepted WORK-AROUND: There is no work-around ------------------------------------------------------------------------------- 481 NAMEDCVS output is incorrect in formatted (/H) mode WORK-AROUND: There is no work-around ------------------------------------------------------------------------------- 263 Setting a system timer (eg. 2ST) to a value lower than its nominal value (derived from the actual time) can give an incorrect result when passing midnight. For example, if it's now 23:58 and you set 2ST=56 (ie. you set it 2 minutes behind the current time) then it will return incorrect values during the period between 0:00:00 (midnight) and 0:02:00 (the witching hour). WORK-AROUND: There is no work-around. ------------------------------------------------------------------------------- 175 RTD measurments over 600 Deg C return the resistance value of the RTD rather than the 99999.9 overrange value WORK-AROUND: There is no work-around. ------------------------------------------------------------------------------- 173 Integer channel types suffer from being converted to intermediate floating point values when their values are set, eg 1C=123456789 1C 123456792 Counts 1IV=123456789 1IV 123456800 WORK-AROUND: There is no work-around. --End--