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

Aborting trigger when different modes are selected #103

Closed
prasimix opened this Issue Apr 13, 2017 · 3 comments

Comments

Projects
2 participants
@prasimix
Contributor

prasimix commented Apr 13, 2017

If for example ch2 trigger is set to FIXed, and ch1 to LIST, switching off ch2 (OUTP OFF) will stop LIST execution on the ch1. There is not need for such behavior despite the fact that single triggering system is used for controlling both channels. Therefore only if channel is in STEP or LIST mode should affect output of other channel when switched off.

@prasimix prasimix added this to the M5 milestone Apr 13, 2017

@prasimix prasimix added this to Ready to implement in M5 Apr 13, 2017

mvladic added a commit that referenced this issue Apr 18, 2017

@mvladic mvladic moved this from Ready to implement to Ready to test in M5 Apr 18, 2017

@prasimix

This comment has been minimized.

Show comment
Hide comment
@prasimix

prasimix Apr 18, 2017

Contributor

Partially resolved. There is no need that channel's voltage and current output set values stays disabled when channel output is turned off.

Contributor

prasimix commented Apr 18, 2017

Partially resolved. There is no need that channel's voltage and current output set values stays disabled when channel output is turned off.

mvladic added a commit that referenced this issue Apr 18, 2017

@prasimix

This comment has been minimized.

Show comment
Hide comment
@prasimix

prasimix Apr 18, 2017

Contributor

It's now enabled, but keypad page cannot be entered. Also if encoder confirmation mode is selected it's possible now to "intrude" other channel's (ch1 in our example) output value settings.

Contributor

prasimix commented Apr 18, 2017

It's now enabled, but keypad page cannot be entered. Also if encoder confirmation mode is selected it's possible now to "intrude" other channel's (ch1 in our example) output value settings.

mvladic added a commit that referenced this issue Apr 19, 2017

@prasimix

This comment has been minimized.

Show comment
Hide comment
@prasimix

prasimix Apr 19, 2017

Contributor

Fixed

Contributor

prasimix commented Apr 19, 2017

Fixed

@prasimix prasimix closed this Apr 19, 2017

@prasimix prasimix moved this from Ready to test to Finished in M5 Apr 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment