jkisoftware/hal-webinar

Webinar – Creating a Hardware Abstraction Layer in LabVIEW

HAL-Webinar

Webinar – Creating a Hardware Abstraction Layer in LabVIEW

How To:

1. Apply the VI Package Configuration using VI Package Manager (vipm.jki.net) for LabVIEW 2015
2. Open HAL Webinar.lvproj in LabVIEW 2013+ IDE
3. From the project environment, Run "Microscope.TestLauncher.vi"
4. Click on wells to see the XYStage move to that location and capture a simulated image.

*To use Camera.IMAQdx class, you will require a valid Vision RunTime License or Vision Development License from National Instruments (ni.com)

Settings files

• You can edit "simulated.ini" file provided to change the relative path to images folder and use your own images
• You can edit "hal.ini" file provided to use a more specific camera (IMAQdx code provided).

To add your own camera or XYStage classes derived from these base classes, open "Microscope.lvclass:enumerateStaticDependencies.vi" and modify the configuration-driven dependency injection and add your specific class in the appropriate case structure.

If you have any questions, please contact JKI at jki.net or create an issue on this thread. We hope you enjoy trying the code and creating awesome Hardware Abstraction Layers for your projects!

Credits

HAL Webinar content is an open source project maintained by JKI.

License

HAL Webinar is distributed under the open source three clause BSD license providing everyone right to use and distribute both souce code and compiled versions. See LICENSE file for details.

JKI State Machine Objects

This code is based on JKI State Machine Objects, an other open-source project from JKI

Get JKI SMO and SMO Editor.

If you prefer you can get the templates directly using VIPM

Get JKI SMO Templates.

hal-webinar's Issues

Save for oldest version possible

There is one particular reason for saving in LabVIEW 2015? I understand that sometimes some features are unavaliable on older versions.
I'm currently downloading an avaliation version of LV2015 to test this code, maybe I pull request this project in older version.

Precise timing & SMO

LabVIEW provides a "Timed Loop" structure for precise timing. I see that SMO uses a "While Loop" with event struture, and setting a Timeout provides a similar feature to a timed loop.
I don't fully understands the concept of Timed Loop, but it might be needed if my future developments, and for sure I could not use SMO for precise timing routines, but I would like to converge most of my subsystems in SMO framework.

This would be an option?