From d3d9ad056499aed034096e37aeefdf3830bef436 Mon Sep 17 00:00:00 2001
From: Ron Sluiter <rsluiter@users.noreply.github.com>
Date: Mon, 21 Aug 2006 18:30:01 +0000
Subject: [PATCH] Pre-release update.

---
 README | 47 +++++++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 45 insertions(+), 2 deletions(-)

diff --git a/README b/README
index 444b679a..7b5255bd 100644
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-Motor Record R5-9 Release Notice
+Motor Record R6-0 Release Notice
 ===============================================================================
 
 The motor record software in this release is compatible with EPICS base
@@ -7,7 +7,7 @@ R3.14.8.2.
 
 Contents
 ========
-
+	
 This <supporttop> contains the following motor record related items:
         - motor record and device driver database definitions.
         - the record level support library.
@@ -113,6 +113,49 @@ Known Problems
         entered in the VAL or DVAL field.
 
 
+Modification Log from R5-9 to R6-0
+==================================
+
+1) The OMS MAXv polling rate, which set is from the MAXvSetup() st.cmd command,
+        is allowed to be as high as the OS clock rate; i.e.,
+	(1/epicsThreadSleepQuantum()).
+	
+        File modified: drvMAXv.cc - changed polling rate error check to,
+	               1 <= polling rate <=  (1/epicsThreadSleepQuantum())
+
+2) Since R4-5 (item #9), RDBD must be >= MRES.  The test for this condition
+        was done using floating point values.  This caused an occasional
+        error that resulted in the record not always issuing a motor move
+        command when RDBD = MRES and the user issued incremental move request
+        equal to MRES.
+
+        File modified: do_work() in motorRecord.cc - changed test from float
+                       to integer math.
+
+3) A warning message was added with R5-6 when a user attempted to move an OMS
+        motor with an invalid velocity (slew <= base).  Applications that
+        manipulate the velocity values are unaware of this restriction and
+        create a torrent of these messages.  With this release the OMS device
+        will only output this warning message once.
+        
+        File modified: Added message latch to oms_build_trans() in devOmsCom.cc
+
+4) Added a work around for OMS PC68/78 firmware error.  PC68/78 controllers
+        make an erroneous response after they are queried with the "?KP"
+	command at boot-up.  This resulted in 1st axis having same position (RP
+	command) as last the axis.
+
+	File modified: Added a dummy comm. transaction to motor_init() in
+	               drvOmsPC68.cc.
+
+5) GPIB under ASYN allows only one input EOS character; no output EOS is
+        allowed. Adjustments were made to the Newport ESP300 driver to
+        accomodate this restriction.
+
+        File modified: Changed EOS from "\r\n" to "\n" in motor_init(). Process
+                       the \r in recv_mess().
+
+
 Modification Log from R5-8 to R5-9
 ==================================