Use Global Variable instead of InfoBlock about asylum-api HOT 12 CLOSED

@Monkeymerlot I'm working on this. Just wanted you to be aware

from asylum-api.

Yes sorry typo in GitHub. We made this work on Cypher with code hotfix

from asylum-api.

Confusingly, GV() means "Get Value" and reads the value from the Global Variable Table.

from asylum-api.

from asylum-api.

OK it should be really easy to make the change. You should be able to only change "Asylum_Driver_GetLVDTParameters.vi" as this is the only place that is calling the X(Y)LVDT parameters that was causing the issue. It would be best build a unit testable "build" function that ensures the proper format of the string before it gets sent to the Igor API if you wanted to be consistent with the rest of the driver. The tests are in the Asylum API Project.

from asylum-api.

Hi @Monkeymerlot correct that is where the LVDT parameters are retrieved. However it's a little more complicated because I can't just change Build Read Value because it appears that td_ReadValue is still needed in some other places, OR the names in the tables are similar but slightly different.
For example:

• td_ReadValue("XLVDT Sense") ✔️
• GV("XLVDT Sens") ☹️
• GV("XLVDTSens") ✔️ [no space!]

from asylum-api.

It's not a big deal, I just need to make a new subVI for "read value" that is distinct from "td_read value". I should be able to get to it this morning

from asylum-api.

I was thinking that you would make a new functionality called "GetValue" and then use the GV(...) like I do with the td_readvalue, and then replace that in the VI I mentioned above.

from asylum-api.

@Monkeymerlot yes exactly

from asylum-api.

Check out https://github.com/levylabpitt/Asylum-API/tree/GetValue

from asylum-api.

This look great thanks

from asylum-api.

GV("XLVDT Sens") ☹️

Did you try GV("XLVDTSens") ie no e at the end as well? That is what is listed in the master variables table :

from asylum-api.