bmoyer

I just created a new snippet to test hooovahh's explanation. Does this one work for you? Edit: Trying my example didn't work for me either. I used to be able to do it in Internet Explorer but newer web browsers don't seem to support this anymore.

That's pretty much what I do too. When I have a re-entrant VI that creates IMAQ refs, I use the VI clone name as part of the Image Name. If you're concerned about the memory used when the VI isn't active, you can close the IMAQ refs and then later reopen them, but I don't usually bother doing this much anymore, as most (if not all) of my Imaging apps are developed in 64-bit now.

Thanks for everyone's feedback. I wasn't aware of the Flush Event Queue, so I if needed, hopefully I'll remember to use it in the future. As for that comment in the Timeout case, I guess I never fully understood or saw an example of the concept being implemented so I wasn't exactly sure what it meant. So, I'm guessing that I put the data in the Actor Internal Data cluster along with a needs display update boolean (for each type of data that I want with delayed display). When the code returns to the Timeout case, read the various update booleans and act on them there, or (probably a cleaner method) call the cases (in the "Follow-on Actions and Error Handling") that update those indicators/controls. Is that about right?

I was wondering how you make the front panel display update lossy. Currently, when I want to do this, I check the Time of the event, and if the event is, let's say >1s old, I don't bother updating the display/indicator. If that how you go about it, or is there another way? Is there a way to only get the latest event and ignore the rest? I'm asking this mainly from the perspective of using your Messenger Library toolkit. Thanks, Bruce

Thanks! Wish you would've told me that a few months ago! 😉

I've been dealing with silent crashes for some months now, and it's been a frustrating exercise (I created some NI support tickets to try to help, but that's been difficult as well). I'm using LV2017.0.1f4 (64-bit) and I suspect it's related to possibly a misbehaving NI frame grabber (NI PCIe-1433) since it seems to crash most often when starting up/initializing communication with the cameras. The system has 6 frame grabbers and also has various hardware (power supplies, temperature chamber, etc.). Recently (yesterday) I disabled the parallel startup of the communications and one of the frame grabbers was acting up (noise on the camera com channel) so I only used 5 of the 6 frame grabbers and last night the entire run was successful! My coworker was amazed! We are running another test tonight to make sure it wasn't a fluke. So right now I'm pointing the finger at either faulty hardware or some bug not allowing many simultaneous IMAQ connections to all start up at the same time. Bruce

Thanks for your replies. It's probably a problem on our internal network, since I can log in from home on my personal computer just fine using Chrome and FIrefox. I was just wondering if anyone has experienced this since it's so difficult getting corporate IT to start working on something like this, and the process of explaining and trying to convince over and over has been a pain (based on past experience). My local IT person is aware of the issue, but it's not clear when or if this will get fixed. Thanks for you help! Bruce

Clearing the cache and history and logging out of Chrome didn't help.

It's working at this moment actually now it's not (on Chrome), but the issue comes and goes (it doesn't work more times than not). Incognito mode is disabled by IT here. When it happens I will try clearing the cache. It happens on both my laptop and my workstation. I installed and tried Firefox yesterday and that was having the same issue. Thanks, Bruce

I've been having this issue for some time now (probably since the end of last year), if I use Chrome (or Firefox) to access LAVA G, it hardly ever works (doesn't show the website). It works reliably using IE but I prefer not to use IE anymore if possible because websites are beginning to warn me that it won't be supported for much longer. Are others also seeing this behavior? Thanks, Bruce

This might be worth looking at but no solution was given: https://forums.ni.com/t5/LabVIEW/Failure-to-initialize-lvanlys-DLL/td-p/3759330?profile.language=en They were having the same trouble but with LV2017.

Just to clarify, is this device similar in functionality to the NI-845x? I'm trying to understand the application of such a device. https://www.ni.com/en-us/support/model.usb-8451.html Thanks!

Thanks, I'm currently doing a project using I2C so I'd like to look into this option. I noticed that Product Datasheet 56 is called out in this link but not listed in the datasheets page. Does this enable I2C communications over a COM port? What speeds/settings are available? Thanks!

Sorry, I don't have an answer, but I encountered this problem very recently (it was brought to my attention yesterday!). I don't remember making any changes, it was the NI 3-button dialog getting stuck behind another dialog. I just re-built the exe and it worked so problem solved! (until it comes back on the next build) I'm using LV2017SP1f3. You would think that the most recent modal window would be of higher modality than the previous.

Thanks for the reply. I was looking at: https://www.sonnetstore.com/products/echo-express-3d-thunderbolt3 There are other ones as well from Magma and other suppliers. I have both Camera Link and CoaXPress (Bitflow) framegrabbers, hoping to use both with a laptop with Thunderbolt. Why do you recommend CXP? What CXP frame grabber do you use? I still haven't found much support for it. Thanks, Bruce