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

Adding support for the minghe mhs5200 #150

Merged
merged 14 commits into from Feb 14, 2019
Merged

Adding support for the minghe mhs5200 #150

merged 14 commits into from Feb 14, 2019

Conversation

CatherineH
Copy link
Contributor

No description provided.

@coveralls
Copy link

coveralls commented Sep 10, 2016

Coverage Status

Coverage increased (+0.2%) to 84.736% when pulling 945b1dc on ch-mhs-mhs5200 into 19919d8 on develop.

instruments/minghe/mhs5200a.py Outdated Show resolved Hide resolved
instruments/minghe/mhs5200a.py Outdated Show resolved Hide resolved
instruments/minghe/mhs5200a.py Outdated Show resolved Hide resolved
instruments/minghe/mhs5200a.py Outdated Show resolved Hide resolved
instruments/minghe/mhs5200a.py Outdated Show resolved Hide resolved
instruments/minghe/mhs5200a.py Show resolved Hide resolved
instruments/minghe/mhs5200a.py Outdated Show resolved Hide resolved
@coveralls
Copy link

coveralls commented Sep 17, 2016

Coverage Status

Coverage increased (+0.3%) to 84.77% when pulling 84da64c on ch-mhs-mhs5200 into 19919d8 on develop.

@coveralls
Copy link

coveralls commented Sep 17, 2016

Coverage Status

Coverage increased (+0.3%) to 84.77% when pulling 07cf48a on ch-mhs-mhs5200 into 19919d8 on develop.

@CatherineH
Copy link
Contributor Author

This has been tested with the function generator and it works.

@coveralls
Copy link

coveralls commented Sep 17, 2016

Coverage Status

Coverage increased (+0.3%) to 84.778% when pulling ac6aa9d on ch-mhs-mhs5200 into 19919d8 on develop.

@coveralls
Copy link

coveralls commented Sep 27, 2016

Coverage Status

Coverage increased (+0.3%) to 84.778% when pulling fa654cc on ch-mhs-mhs5200 into 19919d8 on develop.

@scasagrande
Copy link
Contributor

Uh, what's going on with that last commit?

I'm currently working (working from commit fa654cc) on trying to come up with a nice solution to the function generator base class. I didn't write it expecting multiple channel FGs, so I'm just tweaking things.

@CatherineH
Copy link
Contributor Author

I implemented the duty cycle wrong, and in trying to bring that change in, reverted some other changes. I'm going to roll it back to fa654cc and try to add it to that.

@coveralls
Copy link

coveralls commented Sep 29, 2016

Coverage Status

Coverage increased (+0.2%) to 86.729% when pulling 0066802 on ch-mhs-mhs5200 into 7ccdc13 on develop.

@scasagrande scasagrande added this to the 0.4 milestone Oct 5, 2016
@scasagrande scasagrande modified the milestones: 0.4, 0.5 Feb 7, 2019
@scasagrande scasagrande merged commit e05dad5 into develop Feb 14, 2019
@scasagrande scasagrande deleted the ch-mhs-mhs5200 branch February 14, 2019 23:58
scasagrande added a commit that referenced this pull request Feb 19, 2019
* Drop support for Python 3.4 (#200)

* Fix issue #197 (#201)

Where checking if value is in enum will raise value error in Py38

* Improvements to APT (#167)

* Added driver/motor tables for T/KDC001 APT devs.

* Moved TODO comment to avoid pylint error.

* Misc Py3k changes for ThorLabs APT

* motion_timeout for APT motor cmds, fix scale factor

* ThorLabsAPT: Example of new config support.

* More pylint fixes

* Fix for line continuation convention.

* Rearranged imports into standard order.

* Added an APT test. Not working yet.

* Fix linting issues

* New handling in loopback for empty terminator.

* struct.Struct for contents of hw_info packets

* Support for specifying expected apt pkt sizes

* Fixes to APT and APT tests

* Missed a conflict marker.

* Fixed bug due to `if size` falling through on size == 0.

* Removed trailing whitespace.

* Locked requirements.txt; see #174.

* Remove numpy version pinning in requirements.txt

* Add tests to cover additional loopback comm behaviour

* Make pylint happy

* Revert changes to size=0 behaviour in loopback comm

* Fix bug with SCPIFunctionGenerator.function, add tests (#202)

* Fix bug with SCPIFunctionGenerator.function, add tests

* Fix linting

* Fix Agilent 33220a, add tests (#203)

* Function Generator single/multi-channel consistency (#206)

* Function Generator single/multi-channel consistency

* Fix Py27 linting issue

* Fix linting issue

* Add tests for FunctionGenerator abstract instrument

* Adding support for the minghe mhs5200 (#150)

* added mhs5200

* added minghe function generator

* added absolute_import

* fixed scaling on frequency

* switched to abstract instrument class

* fixed a few docstrings

* after testing with device

* Minghe MHS5200 - Add instrument to docs

* isolating changes from cc1 test station:

* Revert "isolating changes from cc1 test station:"

This reverts commit 87b8dec.

* reverting changes and fixing duty cycle

* Update for new FunctionGenerator multichannel consistency update

* Docstring modifications (#207)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants