The following is a list of current known issues and their respective work-arounds. This list applies to DT800/DT80 firmware version 7.04 Last updated 01-May-2008 ------------------------------------------------------------------------------- 1640 "Logger's units" field in web UI mimic configuration dialog is not updated following the selection of a different source channel WORK-AROUND: Use "Custom units" field, or delete and recreate mimic. ------------------------------------------------------------------------------- 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 ------------------------------------------------------------------------------- 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. ------------------------------------------------------------------------------- 1105 Logger may reset if you try to re-establish a PPP connection after a PPP connection was unexpectedly broken eg by unplugging cable. WORK-AROUND: Ensure that serial cable is not unplugged during a PPP session. ------------------------------------------------------------------------------- 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. ------------------------------------------------------------------------------- 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. ------------------------------------------------------------------------------- 975 DT80 with smsx modem. Can't send a SMS message and receive real time data. It seems that real time returned data is sent via the host port to which the SMSx modem is connected. Possibly, this happens because the command processor receives characters from the SMSX modem when it shouldn't. Returns are then sent on the port on which the "command" was received. WORK-AROUND: There is no work-around. ------------------------------------------------------------------------------- 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. ------------------------------------------------------------------------------- 898 PPP doesn't work with modems The logger does not switch to PPP mode until it sees CLIENT (to which it responds CLIENTSERVER). However Windows only sends this for direct serial connections. For modems the connection event serves the same purpose so it doesn't send anything (just starts sending PPP packets). WORK-AROUND: Workaround is to setup a login script (.scp file) on Windows (Network properties Security tab) eg: proc main delay 5 transmit "^M^J" delay 5 transmit "CLIENT" waitfor "CLIENTSERVER" endproc ------------------------------------------------------------------------------- 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. ------------------------------------------------------------------------------- 866 FTP connections may be refused. This can happen if FTP connections to the logger are not properly closed down. The logger is unable to free its half of connections that are not properly closed down. It eventually runs out of free connections to use to establish new FTP sessions. WORK-AROUND: Users connecting to a DT80 via FTP should use close the connection properly, as opposed to simply shutting down there PC. ------------------------------------------------------------------------------- 787 Errors in returned statistical values if an overrange sample occurs; in particular (NUM) returns overrange, and in the report interval following the one with the overrange sample (INT) is calculated using an incorrect number of samples. WORK-AROUND: Ensure that input is never overrange. ------------------------------------------------------------------------------- 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 (DT80 only) PE channel factor (wrap value) is not accepted WORK-AROUND: There is no work-around ------------------------------------------------------------------------------- 484 If P45=1 or 2 (add DDE/OLE tags), whitespace in chan name is supposed to be replaced by underscores, but isn't WORK-AROUND: Don't include whitespace in a channel name ------------------------------------------------------------------------------- 481 NAMEDCVS output is incorrect in formatted (/H) mode WORK-AROUND: There is no work-around ------------------------------------------------------------------------------- 333 (DT800 only) When measuring resistance, the DT800 sometimes does not set the excitation power correctly, especially if the excitation power is set to a low level. WORK-AROUND: Use a higher excitation level if possible. ------------------------------------------------------------------------------- 316 (DT800 only) The "data manipulation" channels options (DF, DT, RS, IB and RC) and the "digital manipulation" channel options (TOF, TOR, TRR, TFF, TRF, & TFR) sometimes don't work when analog measurements require autoranging. These channel options DO work when applied to counters and CVs, and for analog channels where a gain lock option has also been applied. Also note that RA1S 1V 1V(TOR,200,GL20V) will still not work. The 1V that isn't gain locked will cause the problem to occur. Both versions of 1V need to be gain locked. WORK-AROUND: Use a gain locking channel option in conjunction with data or digital manipulation options. ------------------------------------------------------------------------------- 295 (DT800 only) When measuring the same resistance twice in a row at the start of a schedule there can be a small difference in the first measurement and subsequent readings. eg. for BEGIN RA1S 1PT385 1PT385 1PT385 END the first measurement typically reads about 0.05 degC higher than the others. WORK-AROUND: Insert a dummy channel between the first two measurements so they are non-consecutive eg. BEGIN RA1S 1PT385 1CV(W) 1PT385 1PT385 END ------------------------------------------------------------------------------- 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. ------------------------------------------------------------------------------- 255 (DT800 only) Increased noise in first burst measurement compared with subsequent bursts. This is due to auto-ranging - the first burst is acquired at a higher than optimum voltage range. WORK-AROUND: Always use an appropriate gain-lock option withg burst measurements. ------------------------------------------------------------------------------- 254, 334 (DT800 only) Logger resets if too many consecutive analog channels defined in a schedule. Only occurs in highly contrived situation eg BEGIN RA1S 1..10TK 1..10TK 1..10TK 1..10TK 1..10TK END WORK-AROUND: Insert a dummy non-analog channel eg 1CV(W) in the middle of the list ------------------------------------------------------------------------------- 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--