Skip to content
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.

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

EUROTHERM: MODBUS Control #4240

Closed
KathrynBaker opened this issue Apr 9, 2019 · 13 comments
Closed

EUROTHERM: MODBUS Control #4240

KathrynBaker opened this issue Apr 9, 2019 · 13 comments
Assignees
Labels

Comments

@KathrynBaker
Copy link
Member

KathrynBaker commented Apr 9, 2019

As someone supporting Eurotherms at ISIS I want to be able to use MODBUS to communicate with them as well as the existing EI-BISYNC methods.

Acceptance Criteria

  1. The Eurotherm can be controlled via either comms protocol mentioned (EI-BISYNC, already existing, or MODBUS)
  2. The Eurotherm 32h8i has been confirmed as either working with this IOC, or has had a ticket created to generate an IOC to talk with it

Notes

  1. All existing Eurotherms can talk MODBUS as well as EI_BISYNC so this can be developed and tested against any Eurotherm
  2. It may be needed if greater knowledge of the Quick Cooling Cryostat - Needle Valve Controller is required
  3. It would allow the facility to stop ordering the Eurotherms with the extra comms protocol, which whilst not a large cost of itself is a significant proportional cost of each Eurotherm
  4. We have a standard Eurotherm available to test with (I believe)
  5. A request has been received to interact with a https://www.eurotherm.com/en/products/temperature-controllers-en/indicator-and-alarm-units-en/3200i-indicator-and-alarm-unit/ which uses ModBus RTU (https://www.eurotherm.com/?wpdmdl=27877) after the long shutdown
  6. User Support have been asked as to whether or not they have a unit we could test with
@FreddieAkeroyd
Copy link
Member

@Tom-Willemsen
Copy link
Contributor

Proposed as the long-term solution to #5756

@DominicOram
Copy link
Contributor

Proposed so that we don't continually hotfix #5756

@FreddieAkeroyd
Copy link
Member

Or we test replyTimout = 2000 elsewhere and then roll it out?

@FreddieAkeroyd
Copy link
Member

Interestingly the DLS modbus driver calls modbusInterposeConfig to insert a 2000ms timeout...

@KathrynBaker KathrynBaker added the bucket proposals that didn't make into the sprint label May 6, 2021
@KathrynBaker KathrynBaker removed the bucket proposals that didn't make into the sprint label May 26, 2021
@DominicOram DominicOram added the bucket proposals that didn't make into the sprint label Jun 16, 2021
@DominicOram DominicOram added this to the SPRINT_2021_05_27 milestone Jun 16, 2021
@DominicOram DominicOram removed this from the SPRINT_2021_05_27 milestone Jun 17, 2021
@Tom-Willemsen
Copy link
Contributor

Tom-Willemsen commented Sep 9, 2022

PRs:

Docs:

Follow-up issues:

Note: until #7345 has been done, we should prefer to use ei-bisynch comms to eurotherms wherever possible, as the current approach to scaling factors is very error-prone in subtle ways (e.g. wrong PID settings would make a eurotherm appear to talk correctly and may even change temperature ok for small changes, but would fail to change temperature during larger changes)

Note for reviewer: there are two eurotherms in the office you can test with - a 2000 series and a 3000 series. We had a third eurotherm but electronics have asked for this back before cycle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants