RayR

I kept looking for the link until I realized that the large text was screaming at me to click it.. LOL!! I'll be seeing you guys at the venue.... and during NI Week..

Salt Lick was good

The camera is connected via GigE Ethernet network.

Hi everyone, Is it possible to read the memory contents directly from the camera's memory? In other words, If the Invoke Node can provide the pointer to the active memory, can we access the memory location directly from the camera instead of using the CopyToArray function? The reason for asking is because a client needs to read the image faster than 4ms/MB that it takes the function to read the image data and write it to an array. Below is an image of what is implemented and what is desired. The first image is what is desired. The 2nd image is what is currently implemented. (I did not have the Vision toolkit installed on this PC).

So far, everything looks good. I should have time today to test the ComboBox. I think it will work, but I want to test it before before posting it to the original thread.

We're doing something very similar to what you did in your demo code (thank you). Your demo worked on my machine.. I will try it on the other development machine where the "bug" was found. Dr. Powell: While debugging, we are opening the Front Panels. How? Well... they opened automatically as set in the VI properties (to open when called). We also used an invoke node to open the front panel. It did not change anything. I will pay attention to your last recommendation. Thanks

I basically duplicated the String class with a few changes to support the ComboBox. Part of the code was the "Get JSON Data.vi method. At the moment it looks very much like the one from "string". My question is: In what you wrote above, should the support for this function be part of the Select class or should I base the modifications of the newly created Get JSON Data.vi which is specifically for the ComboBox? I suspect it is the latter if I modify the Get JSON Data.vi located in the ComboBox class it will be what is necessary to support it. I agree that it should somewhat be like the ring or enumerator. While waiting for your response, I will start to modify the one in ComboBox.

No dynamic event... Just Dynamic VIs. I tried variations on what you wrote and none of it worked. As a matter of fact, I discovered more... let's say "troubling" features.. concerning Dynamically calling a re-entrant VI. I would be extremely surprised if I was the first to attempt such an approach. For now, we implemented a workaround. As I have time, I will create a snippet of similar code to investigate.

To answer the first question: the default value for duration is zero 0. When calling the VI, it passes a value of 30. When setup as a re-entrant VI,, none of the clones show any value other than 0. When setting the VI as non-re-entrant, the value of 30 appears in the control of the VI. We also have breakpoints in the dynamic VI and monitor the values. The second question: We have probed both the calling VI and the dynamic VI. Simply changing it to non-re-entrant results in getting the value 30 as expected. Opening the VI reference inside the loop was a recent modification during the investigation. You may be giving me an idea. Something that I have never tried... Are you saying that setting the x40-80 will create a clone pool even if the VI is not set as re-entrant? Because your last sentence appears to be correct. We have another parallel VI which has the earlier implementation where the Open VI Reference is outside the loop. They both share the same / similar issue. While waiting for your response, we will investigate.

I've worked with dynamic events for many years; however, this is the first time I implement code that calls a dynamic re-entrant VI. The VI call works and the dynamic VIs run. That's not the issue. The issue is that we wire values to the dynamic VI call. When setting the VI as normal (non-re-entrant), the values make it to the dynamic VI without any problem. However, as soon as we turn on the re-entrant features, the values are no longer making it to the dynamic clones. I am curious if anyone has seen this in prior projects? Is it a bug? Is it a limitation? The reason for this approach is that we need to make a call to a function that measures sound pressure levels using a microphone attached to a DAQmx card. The number of microphones can vary from 1 to 2 to 4 to 8 to 16 (and possibly some combinations in between). Using a re-entrant VI was the natural was to implement this. However, the function (VI) needs to run dynamically and wait for a rendez-vous signal while other processes are running in parallel. All of the measurement and noise sources need to run in parallel; hence, the use of dynamic VIs. In the code shown above, you would expect the value 30 to appear in the dynamic VIs. That is the case when re-entrant is turned off. We tried both combinations of re-entrant configurations, various configurations for the opening of the dynamic VI (as can be witnessed by the hex constants on the block diagram). Some of the code such as looking at the number of iterations is for debugging purposes. Any comments? Or ideas? Is it a bug? Or a limitation? I do have a workaround in mind, but would like to know why this issue surfaced in the first place. Thanks, RayR

Thanks Hooovahh, I was on the right path and was about to post a question, but you already provided the details. Thanks!

I break my replies in small sections due to posts not making it. I would like to contribute the Combo Box support for the VI (project). I just started looking deeper into the code this morning, but may not have much time to do so today. However, any indications of where the support code lies would be grateful. Looking at the existing code that supports the Ring control would be great. Where is that VI within the project? Thanks! RayR

Interesting... I thought I had posted a reply... it must not have made it. Let's see... what did I write... Here goes.. (again) The two obvious indicators are "Calibration Date" and "Measured Sensitivity". When remotely clicking on "Calibrate" button, the local VI runs and displays values for those 2 indicators, but the values are not displayed in the remote page.

Since I am in the debugging phase of my application, I did not want to hijack this thread for my issues. The conversation is continued here: https://lavag.org/topic/19969-debugging-interactive-html-vi/

As expected, some of the controls are seen as images. This is similar to what I reported yesterday in the original thread. Below is the configuration that I used for the controls; hence the one shown above (Selected Room). The check-marks are not selected for "Show as image" or "Value Only". No check marks.. Would the issue be related to using "System" controls? Or is it related to some other non-supported feature? Or is it something completely different?