Stimulator agents

[dixilo]

Description

This pull request contains several agents and driver codes to handle devices for LAT stimulator. New agents are:

• devantech_dS378: Ethernet relay to switch on/off devices via ethernet.
• kikusui_pcr500ma: AC power supply used for stimulator heater.
• om_blh, om_ble2: Controller for motors producted by Oriental Motor Co., Ltd.. BLH series is used for the latest version of the stimulator. Codes for BLE2 series was also developed for the previous version now in Chicago. This agent run in Kria KR260 inside the stimulator electronics box.
• stm_encoder: Reader for stimulator encoder. This agent run in Kria KR260 inside the stimulator electronics box.
  • This reader accesses a custom-made IP inside the PL of ZynqMP device. The firmware code can be found in https://github.com/dixilo/kr260_stm.
• stm_thermo: Reader for thermometers in the stimulator. This agent run in Kria KR260 inside the stimulator electronics box.
  • Thermometer readers are either MAX31856 (thermocouple) or MAX31865 (RTD). Communication to these devices are via SPI cores implemented in the PL.
  • Linux kernel supports these devices via Industrial I/O subsystem. Codes here are thus simple.

Motivation and Context

These codes will be used to operate the LAT stimulator.

How Has This Been Tested?

We tested the functionality by actual devices which will be deployed to the site.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.

[BrianJKoopman]

Thanks for submitting this PR @dixilo! And apologies for the slow reply following the holidays. With five agents and nearly 3,000 lines this is going to take a while to get through. It would be helpful on the reviewer side, based on past experience with groups of agents like the HWP agents, if you could break this up into separate PRs per agent. That way it's a bit less daunting of a review, issues in one agent won't hold up merging of other agents, and we could have different team members review different agents more easily. Would you mind doing that?

[dixilo]

Yes, I can split this PR to separate PRs per agent. What do you think is the best way to split PR? Making branches per agent from main and then copy files by git checkout -p [commit id] [file name] to these branches is the best way to do this? Please let me know if you have any idea @BrianJKoopman .

[BrianJKoopman]

Yes, I can split this PR to separate PRs per agent. What do you think is the best way to split PR? Making branches per agent from main and then copy files by git checkout -p [commit id] [file name] to these branches is the best way to do this? Please let me know if you have any idea @BrianJKoopman .

Thanks @dixilo! There isn't a ton of history here, sort of up to you on how much you want to preserve it. If not at all, I'd make different branches per agent and just re-commit the relevant agent code per branch.

If you'd like to preserve the history here, I'd probably create a new branch for each agent at the head of this stimulator branch, then do an interactive rebase (git rebase -i main) on each and 'edit' the commits to drop the agents unrelated to the named agent branch. For particular agents this'll mean just dropping certain commits. Not sure if there's an easier way to split this out.