You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the version 1.1.0 of this CD, if you try to load a Capability from a file (which we can call it "offline"), then the existent JSON JKI parser is not able to define the "default" values in the capability. This happen because that information is in the "registers" and not in the properties, so the parser has to do that. In this meanwhile, if you want to obtain the "default" values, the best way is to read the Capabilities from a online card and, then, Export the parameters. Then, you can just read this file afterwards (better than trying to just a raw or capability file.
To make the transition easier, SLSC R&D was able to create an API that allows you to do such work. It would be advisable to use this API instead of the JKI tool: https://github.com/ni/slsc-capability-explorer. Also, this new tool uses RapidJSON. which is faster. However, this API only support 2017 and up. @jashnani , @csjall , @buckd
The text was updated successfully, but these errors were encountered:
Hey @Austrim and @Karl-G1 , I am tagging you so you can "manage" this request. This request is not very "hard" to be done and the benefit is considerable. If we change from JKI JSON parser to the RapidJSON, then this API above could be leveraged easily. That also only requires you to change one place in the custom device, so I think we should consider scheduling this before the next release of the EDS.
And one more comment: since in VS 2020 we make the earliest support version of VS 2017, this could be a good opportunity to remove the extra code necessary to support VS 2015/VS2016. That way, this can make a lot of the code branches not necessary anymore (or the extra XML file for previous version).
In the version 1.1.0 of this CD, if you try to load a Capability from a file (which we can call it "offline"), then the existent JSON JKI parser is not able to define the "default" values in the capability. This happen because that information is in the "registers" and not in the properties, so the parser has to do that. In this meanwhile, if you want to obtain the "default" values, the best way is to read the Capabilities from a online card and, then, Export the parameters. Then, you can just read this file afterwards (better than trying to just a raw or capability file.
To make the transition easier, SLSC R&D was able to create an API that allows you to do such work. It would be advisable to use this API instead of the JKI tool: https://github.com/ni/slsc-capability-explorer. Also, this new tool uses RapidJSON. which is faster. However, this API only support 2017 and up. @jashnani , @csjall , @buckd
The text was updated successfully, but these errors were encountered: