Cannot locate the En/Dequeue Message VI's

[David99999]

I'm going through LV Core 2 and its showing me messaging. Trying to follow along but I cannot for the life of me locate the VI's they are using. I used the search bar and everything. See attached screenshot. I did go into the Data Communication>Actor Framework>Advanced>Message Queue> and then there's a couple Enqueue's and Dequeue's but they do not look the same, and just give me an wiring error.

[wiebe@CARYA]

It looks like an old actor framework version VI to me.

It looks like the Enqueue.vi in AF's Advanced>Message Queue palette.

[dkfire]

Or AMC or from Core 2 material?

[BertMcMahan]

That's not from Actor Framework. Those are custom as part of the queued message handler project template. From the LabVIEW splash screen, click "Create project" then find that template.

You won't find them in the palletes.

[Kyle97330]

---

@BertMcMahan wrote:

That's not from Actor Framework. Those are custom as part of the queued message handler project template. From the LabVIEW splash screen, click "Create project" then find that template.

You won't find them in the palletes.

---

That is where I recognize that icon from.  However, the wire that is coming out of the icon in the screenshot appears to be a channel wire, not a queue reference wire.  I'm using LabVIEW 2018, so it's possible the template was updated since then to use a channel wire instead.

So, if you do create the project as mentioned, but don't get a VI with the same output wire, that's probably why.

[BertMcMahan]

---

@Kyle97330 wrote:

---

@BertMcMahan wrote:

That's not from Actor Framework. Those are custom as part of the queued message handler project template. From the LabVIEW splash screen, click "Create project" then find that template.

You won't find them in the palletes.

---

That is where I recognize that icon from.  However, the wire that is coming out of the icon in the screenshot appears to be a channel wire, not a queue reference wire.  I'm using LabVIEW 2018, so it's possible the template was updated since then to use a channel wire instead.

So, if you do create the project as mentioned, but don't get a VI with the same output wire, that's probably why.

---

Ah, you're right, good catch. It's the Channeled Message Handler template.

[David99999]

Ok so it's still a custom template that's not located in the palette. Good to know! Wish it would have been more clear about that. I'll probably steer away from using that method in my programs and stick to what's available in the palette's for now.

[Darren]

I would say this isn't really a palette vs. non-palette issue, so much as a design issue. The designer of the Channel Message Handler project template included those VIs in the template code in case the end user of the template decided they needed to customize the VIs in some way. For example, if you decided that you wanted the message to be an enum instead of a string, you wouldn't be able to customize the VIs in that way if they were core LabVIEW VIs that shipped in vi.lib and were on a palette somewhere.