Manual – Starflow Ultrasonic Doppler Instrument
Model 6526
Unidata Manual - 6526 Starflow User Manual Issue 17 01 2020.docx
Page 34
If all goes well, a
Logger successfully re-programmed
message will appear (with
Disconnected
as the final message). Click
OK
to close the progress window.
If any errors are detected and reported on the computer screen, you may then correct them and
Program Starflow again. Error messages are:
Error
Correction
Timeout on Prompt
Check that the cable is connected to the right communication port.
Check that this port you are using is selected in the Communications
window for this Scheme.
Consult the computer’s documentation to verify the port’s designation.
Timeout on Output
Communications errors. Starflow not responding to request. Could be
caused by a program running on your computer in the background. Check
connections, halt other programs running on your computer, then try again.
Timeout on Input
Logger will have
powered down
Extended error x
Error configuring Starflow. Write down the number, check connections,
then try again. If unsuccessful, contact your nearest support center.
Hex byte expected
Transmission errors. Non-fatal informative errors indicating a
communication error has been detected. Check cabling or Modem’s
telecommunications line. The transmission is automatically retried and the
system will proceed normally.
Bad Checksum
<CR> expected
Verify error
File not found
Save the Scheme again (this generates files needed), or re-install Starflow
Software.
Firmware insufficient The Hardware chosen for the Scheme doesn’t match Starflow. Re-create
the Scheme using the correct Starflow model.
Modem Reports – No
Carrier
The remote Modem not answering. Check phone number. Check that
remote Modem is functioning.
Modem Reports –
Busy
The remote Modem is off the hook. Wait, then try again.
Modem Reports – No
Dial Tone
The Modem is not connected to the phone socket.
Connect, then try again.