Comments on: Active VI Toolkit public alpha – Erlang style message passing concurrency toolkit for LabVIEW

By: Tomi Maila

Tomi Maila — Fri, 16 Jan 2009 15:12:55 +0000

Hi sachsm, right now I’ve not got time to develop this particular project. However, by adding to your LabVIEW INI file a line XNodeWizardMode=True, you can view the generated code by right clicking the nodes on the block diagram and selecting “what ever its name was” item from the context menu.

By: sachsm

sachsm — Fri, 16 Jan 2009 14:50:09 +0000

Hi Tomi,

I was wondering if you are planning a next release for the Active VI toolkit.
I am interested in its application for fast and flexible messaging within a distributed computing environment consisting of a variety of cRIO’s and PC’s. I am interested to understand the underlying mechanism used to handle the message response. When the sender is waiting for reply is it pending in an event structure, or for a notifier or ?

By: Tushar

Tushar — Tue, 18 Mar 2008 05:32:17 +0000

see this post
http://forums.lavag.org/Tushar-s-Event-Architecture-t10360.html

I was also working on something which can pass events between different VIs along with event data.
but my approach was bit different than you.

i do expect a comment from you

By: Tomi Maila

Tomi Maila — Sat, 01 Mar 2008 16:16:15 +0000

Todd, I’ll send you an email to troubleshoot the issue together with you. I tested registering myself a new user name and there were no problems. Maybe your internet operator or email program has regarded the email as spam. The subject of the email should be [ExpressionFlow] Your username and password. Anyway I can manually set the password for you.

By: Todd Vangilder

Todd Vangilder — Sat, 01 Mar 2008 14:40:37 +0000

I am intrested in trying out the active vi toolkit, but I cant download unless I am registered, and the regestration process is not sending out the E-mail with my password. I also tried the change pasword, even though I don’t have one, and it did not send me an E-mail either.

By: CBL

CBL — Fri, 29 Feb 2008 22:08:48 +0000

Thanks so much for distributing this as ogp files.

I have to admit when I read your Erlang blog article, I never once thought you might be considering adding Erlang type concurrency to LabVIEW. I thought you may just use Erlang for its strengths. It is great that you are trying to migrate a strength of Erlang to LabVIEW.

I’m going through the examples now – it all looks very professional – thanks for making my Friday afternoon more enjoyable!

By: Philippe Guerit (PJM_LabVIEW)

Philippe Guerit (PJM_LabVIEW) — Fri, 29 Feb 2008 19:00:43 +0000

Ah, make sens (the srtict for type only). I did not realized that this was a “for type only” input.
By the way, good job on the blog as well. Just by reading it, it is quite easy to figure out what are the intent of your examples (even for people like me that know nothing whatsoever about Erlang).

PJM

By: Tomi Maila

Tomi Maila — Fri, 29 Feb 2008 18:49:23 +0000

Philippe, thanks for your comments. The glyphs are different because they have different meaning. The star is supposed to mean a strict VI type (for type only). The box is meaning a static VI reference which can either be strict (as in the example) or non-strict.

By: Philippe Guerit (PJM_LabVIEW)

Philippe Guerit (PJM_LabVIEW) — Fri, 29 Feb 2008 18:21:16 +0000

Tomi,

This look very interesting!
I will definitively have to try this.
At first glance, one thing that seem a little “odd” is that you appear to be using different glyphs for representing (what I assume to be) VI references. For instance, in your first screenshot, a strict static VI ref is connected to a “rectangle with bold top edge” glyph then later with a “star” glyph. It seem like this should be the same glyph.
Now that I am thinking more about it, maybe in the first glyph the node does not know that it is a strict static VI ref but the last node does, thus the “star” for the strictness.

PJM

By: Jim Kring

Jim Kring — Fri, 29 Feb 2008 17:59:16 +0000

Tomi: Great work on the new toolkit. This looks very exciting!