Bulk Electrolysis w/ Coulometry (BE)
First of all, I greatly appreciate your work on making the LibEC SDK available. I am using C# to load functions from the LibEC.dll and it works well to run experiments. When I called the CHI_hasTechnique function it returns a number which changed everytime. How to tell whether the technique (given by an ID passing to the CHI_hasTechnique function) is supported? Thanks!
libec 0.1.12
libec: SWV for 1040c
fixed with a tiny tweak to BaseRecorder? no, didn't work out side of simulator
libec: SWV for 1040c
fixed with a tiny tweak to BaseRecorder
Okay, looks like ACV is unaffected because there is a natural delay in the code. Both techniques should be affected - and the bug is probably in Recorder.
The ordering is indeed jumbled in plotoptions.exe, but the series labels are CORRECT.
libec: SWV for 1040c
Unexpected output ordering for Sequential SWV with > 3 channels. Does NOT happen with ACV. WHAT??
CHI_getExperimentData_24series() done
libec: SWV for 1040c
libec: ACV for 10xxC
24-channel C API function done.
everything done except C API monstrosity CHI_getExperimentData_24series() TO-DO: also need to change RECORDER_H__MAX_LABVIEW_CHANNELS
libec: ACV for 10xxC
everything done except C API monstrosity CHI_getExperimentData_24series()
Priority list from end-user: AC voltammetry (1 channel) w/ in-phase response > AC voltammetry (1 channel) w/ in- and out-of-phase responses > squarewave (1 channel) with forward and reverse > everything with 8 channels. also TO-DO: test 24 channels using simulator + plotoptions
libec: ISTEP for 7E
libec: CA and CC for 1040C
libec: ACV for 10xxC
libec: SWV for 1040c
time to expose forward and reverse currents now also
libec: ACV for 10xxC
Don't forget to copy chyqw -at- chinstr -dot- com when done.
libec: 12xxC support
libec 0.1.10.1
libec: SWV for 1040c
libec: CA and CC for 1040C
libec: ISTEP for 7E
libec: Common counter/reference for Multiplexer
libec: CHI_set_mch() should be zero-based?
Oh right, due to range checking in RunnerBase, this requires a bona fide patch to make working electrode #1 accessible.
libec: CHI_set_mch() should be zero-based?
libec: Common counter/reference for Multiplexer
libec: Model not detected on COM4
Should be fixed in 0.1.10.
libec 0.1.10
libec 0.1.10
libec 0.1.9 wide release
libec 0.1.9 wide release
libec: ISTEP for 7E
Added to libec 0.1.9.4
libec: ISTEP for 7E
Corroborating evidence: both 0.1.8.16 and the previous commit (8707d61) do not experience this issue. Since nothing after 0.1.9 touches the COM port code, that narrows it down to like 10 lines of changes.
Basically done, but waiting on results of Ticket #54, which may affect all techniques and all models.
Input side is actually nearly identical to STEP, so this should actually be very fast.
Output side appears to be trivial - incredibly simple logic, considering how annoying the input parameters are. But I suppose all it does is tell the galvanostat a series of steps. Nothing too fancy at all.
Maybe the problem is that setBaudRateInHardware() logic is actually different from raw call to setBaudRate(). In that case, then 0.1.8.16 should actually succeed, but b400146f should fail. If this analysis is correct, the proposed fix is to change setBaudRateInHardware() to omit the abort condition of isOpen() (i.e., don't worry about the edge case of hot-changing for now).
Error message is definitely from exports.cpp: openComFromUser()
libec: Model not detected on COM4
Hmm, maybe g_comm needs to be instantiated after g_iModelExt?
libec: Model not detected on COM4
libec: ISTEP for 7E
Available as of libec 0.1.9.1
libec: SWV for 1040c
libec: CA and CC for 1040C
libec: CA and CC for 1040C
libec: CA and CC for 1040C
Output side: same as CV, and uses combined CaCcRun() subroutines; should be (relatively)...
Input side: CA and CC are almost identical, except for a few voltage options, and...
libec: CA and CC for 1040C
libec: IMPE for 6xxE
This question was answered in my previous post. Locking this thread as further discussion...
Has the code for IMPE been added to chi.vi
libec: IMPE for 6xxE
Available in "chi.vi" and "chi_controls.llb" as of svn rev 49. Closing.
copyright year bump
9D: IMPE
libec 0.1.9 wide release
libec: COM port speed
Patched for all models in 0.1.9; closing.
IMPE6C for 9D
Patched in 0.1.8.16; waiting on user confirmation
So g_iBaud was actually exposed way back in 0.1.3.2, but this was implemented incorrectly,...
libec: SWV singleChannelStorage() is an underestimate
Patched integrationTest instead - the 3x estimate is preferred because it is more...
The correct (but still ugly) way to fix this is in the dll side is to have a M_SWV...
The correct (but still ugly) way to fix this is in the dll side is to have a M_SWV...
libec: SWV singleChannelStorage() is an underestimate
CC (6E/7E/9D) is broken
I am presently occupied with ticket #49, which includes a potential bug that may...
Dear Jonathan, When will you be able to send me the updated chi.vi? Regards, Dr....
verified as working by user
Any single Runner changing the baud rate would affect all other Runners. Create CHI_setFastBaudRate()...
Looking closer, supported series have the software setting initialized to fast com...
Looks like CHI_setParameter("g_iBaud", 1) is already wired up in current version,...
As stated in my original email, click "labview" then "download now". This is the...
Can u please send me step by step instructions to download and the link as a mail.....
[edited to remove personal information] The link in the old mail takes me to the...
I am unable to reproduce your issue; the link downloads version 0.1.8.14 of libec6008e.dll...
The link in the old mail takes me to the same page which is last updated on August...
ail takes me to the same page which is last updated on August 2016.. I downloaded...
Dear Jonathan, The link in the old mail takes me to the same page which is last updated...
The link is in the previous email I sent you and is the same as the original download...
Kindly send me the link to download teh file or send me to file itself
libec: IMPE for 6xxE
libec: suppress "real-time data may be unavailable" warning