Michael Aivaliotis

2 minutes ago, Aristos Queue said:

Is that true in the recent versions? The typedefs got revision protection in LV 2015, I think. If the mutation is going to throw away data, it does the same sort of "relink" behavior as when changing conpanes of subVI so you preserve the data. 

I'm confident you have data to support your argument. However, I've been burned so many times that I cannot keep track of if it was fixed or what version it was fixed or even if it was fixed but is buggy and it works only under certain conditions. I have lost money because of this and don't risk it anymore. Sorry. But the fact that it was an issue for so many years and only addressed in 2015, gives me pause. Again, not doubting your statement, but I don't trust it.

I strongly suggest you don't even touch NXG.

LabVIEW 2018 has Python support if that's what you need.

On 12/18/2018 at 5:10 AM, Petr said:

But this produces huge init VI BD (see example for only5 nested objects and imagine the same for 100 objects)

It's worse than what you show. I see a lot of typedefs there. One issue with your approach is that there is no guarantee your values will remain when you update your typedefs. I have been using LabVIEW long enough to know that you should never trust typedefs on the block digram to keep the values when they get updated. I would change your code right now because it will fail in the future.

Please check again. I think something got changed in the upgrade, but i think i fixed it now.
You can use this forum for testing:

https://lavag.org/forum/2-for-testing/

4 hours ago, bbean said:

I know about the RAD.  But I think my needs are similar viSci, because I actually need to "wipe" a cRIO before removing it from a "secure" area and then re-image it from the clean media.

From NIMax you can format a cRIO.

Reboot the controller and try again. Does it work?

13 hours ago, bbean said:

I need to image a few cRIOs in the near future.

Creating a crio image is a little different than changing the entire OS stack from Windows to Linux.
You can image a crio using the Replication and Deployment utility. I use this all the time.

Quote

 I would like to convert the cDAQ 9133 with WES7 to LinuxRT. 

I think you would need to get the installation image NI uses to setup that specific Linux cRIO and some instructions. NI has the image and they can choose to give it to you or not. If they can't provide it due to warranty or licensing issues. Then they should offer a service where you send it in so they can do it for free or even a fee. It's not unreasonable to ask for a service fee since this is not a common request. However, considering the astronomical cost of the hardware, they should do this without question. In the past, when I've requested things from support that are out of the ordinary, they tend to shrug it off. However, once I get a sales rep involved and explain the customer need and criticality of the situation, then they have the power to get support to do anything. NI should be doing this, not you.

Not sure what's going on but their download speed is a snails pace across the board.

I mentioned that I would make an announcement when new account creation will be available. Well, today's the day! I added a google captcha system on the Wiki so it will prevent bot registrations. I think this is working. I haven't seen any spammers for a couple days that it's been running. So if you have the urge to contribute or use the Wiki for your LabVIEW related content, then go right ahead.

There's no restriction at the moment to what content is allowed. As long as it relates to LabVIEW in some way and adds some useful information. There will be ongoing editing of course as content comes in.

Hey LAVA worshipers! Just wanted to update y'all on recent changes to the site. LAVA and the WIKI are now running on a dedicated server. You will notice that the site runs faster because of this. Also because of the transfer, we got more disk space which will help if we want to host a repo in the future. Anyway, just wanted to keep you in the loop so  you know that there's work happening behind the scenes to keep the LAVA site running smoothly and with the latest features. Some of the funds for this comes from the site ads and some comes from the yearly LAVA BBQ. So thank you all for your contributions and support.

7 hours ago, MikaelH said:

I hope it will be easier in NXG.

😀

Check out the awesome home page updates that @The Q has made. Huge improvement. I love it!

https://labviewwiki.org

Just ditch 8.5 man.

*sigh*

Seems like a LabVIEW bug.

@Antoine Chalons doesn't have to write the session reference back to the class. But he also can still keep the class object out.

Have you investigated a source distribution? It should pull in the DLL since they are referenced by the VIs.

3 hours ago, Phillip Brooks said:

EasyXML Toolkit

Ya, but at least I can checkout the EasyXML repo locally and even fork it, which I have.

50 minutes ago, TomOrr0W said:

LabVIEW 2015 SP1 is also supported on WIndows 10

Yes, I ran into this issue as well. I couldn't upgrade a customer PC to Windows 10 because I was using LV2014. So then I decided to upgrade to LV2018, but the customer had 1 PC running WindowsXP. yes. XP. So that aborted the whole upgrade, just for 1 PC. So the highest I could go was LV2015.

On 9/28/2018 at 12:01 AM, ThomasGutzler said:

Interesting choice on ignoring the incoming error when you get the attributes

Yes, but ignoring the IPE error out on read as well? I would think that you would want to know if the IPE structure fails completely. This would be a sign of a bad DVR ref.

10 hours ago, Rolf Kalbermatter said:

But I'm not familiar with the exact release procedure

That's great @Rolf Kalbermatter . If we can figure out this last piece, then it would go a long way to allowing improvements to the library. I think it would also be useful to document this procedure somewhere, perhaps in the Wiki. However, I think the answer might be: email JKI to get it released.

See this post. This thread is now closed.