Michael Aivaliotis

All of this spam was created a long time ago when the site was more vulnerable. The wiki has been locked down since then, and this should not happen again (but some get through). I deleted the first list of pages you mentioned. The uploaded images are tedious to delete because there no simple tool I've found to do it on a mass scale. Since they're not linked anywhere then they don't do much harm except use up server space. It seems you have time. So I will connect with you directly offline to give you some rights.

The OP didn't clarify his requirements so we could all be wrong. But ya, all you guys say is true. - Thanks. My intent was to start the conversation, not to provide the best solution. I just wanted to show how the delete from array works and to provide some visuals.

I dunno. Your question is not clear, but let me take a shot. This example deletes the last 3 elements of an array of strings. Don't forget that array indexes start at 0, not 1.

@Tim_S, the OP makes a valid point. All you say is true, however, the link remains broken and the person packaging the OpenG tools should either fix the link and provide the documentation, or remove the link from the package build.

We're starting to add the back catalog to YouTube. NIWeek 2018 videos are also up.

Mark of course has the originals and always will. So that's not an issue. However, nobody cares about some LabVIEW videos. Yes, that's a great idea. It's a wiki so anyone can add them if needed. Feel free to contact them or edit the page. That's because the videos are unlisted. We are doing this so that in order to view the videos you have to go to the wiki page as the entry point. This way they are kept within the community. This was the compromise to balance accessibility. We can deal with that issue if we hit it, which I doubt we will. Considering the videos are unlisted and we have approval by the presenters.

Hey folks. this year we're trying something new. All Videos for NIWeek 2019 can be found here: https://labviewwiki.org/wiki/NIWeek_2019 Feedback welcome. Thanks to @Mark Balla and other volunteers for recording the videos. Edit: We're starting to add the back catalog to YouTube. NIWeek 2018 videos are also up.

I don't have the time or desire to figure out how to automate this. But it's cool that trick works.

Is this error message coming from a VI that you are running on the RT target? Have you tried using the NI Distributed System Manager? I use that to debug Ethercat issues. When you switch to Active mode using NI DSM, it works pretty consistently. Unfortunately the NI Ethercat driver is a load of poop. Soft reboot of the controller usually fixes things up.

No.

I have no idea. That seems to be a URL in the old format which died a log time ago. The post probably still exists but was converted to a new URL format and there is no redirect.

What happens when you create a page? Do you get an error or something?

I think it's solved now.

Thanks for the interesting conversation. I've resolved the issue however, in a roundabout way and by cleaning up my code. The UDP communication code in question is a model written in LabVIEW running on VeriStand, which is essentially a bunch of LabVIEW RT timed loops running on a Phar Lap target. So the model essentially opens a UDP connection, sends the message, then closes the connection. This is done at a rate of 50Hz. I changed the code so that it opens the connection at the start of the test and the model just continuously sends the message at the 50Hz rate, then at the end of the test I close the UDP connection. This resolved the issue because now the ARP is not sent anymore, like at all. Well, maybe at the start? But I haven't checked that, so I should do that later. The explanation I can come up with is, I was closing the connection every 20ms, so the OS considered the port closed, so it took that time to do the normal housekeeping of sending the ARP? But since the port was always open to a known IP address (and thus mac ID), it didn't need to do the ARP. I don't know, just my guess. Ok, so bring on the comments about, why I would keep opening and closing the port. Bring it on, I can handle it... 😀

Looking at this post by an NI employee. It seems that the ARP table cannot be statically defined on Phar Lap.