Skip to content

Nanodac #207

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Tom-Willemsen wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Nanodac #207

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions doc/specific_iocs/temp_controllers/Nanodac.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Nanodac

The "Eurotherm Nanodac" controller (not to be confused with a {doc}`Eurotherm` controller) is a temperature controller.

It talks via standard Modbus/TCP; our IOC is based on support imported from ORNL.

## Control loops

The Nanodac can be configured using two "loops", and an "advanced loop". The "advanced loop" allows multi-channel {abbr}`master/slave configurations (This is the terminology used by the device itself)`.

The "advanced loop" only has very basic support implemented: changing the setpoint. The simple loops additionally allow control of e.g. PID settings.

## Modbus data types

Modbus allows reading from two areas: a 'scaled integer' area, and a floating-point area.

The formula to translate a "scaled integer" address to a "floating-point" address is {math}`32768 + (A_{integer} {\times} 2)`. The list of scaled integer addresses is given in the manual.

Note that the scaled integer area will fail to correctly read temperatures or other readbacks above {math}`327.68` for a channel with 2 d.p. of precision.
Loading