Michael Aivaliotis

I put a temporary ban on inserting external links in posts (except from a safe list). We'll see what affect it has.

Thanks for raising your concerns. I'm aware of the problem. The root cause I believe is the forums framework itself. It has many safeguards, but it seems that the spammers are always one step ahead. There are still more avenues I can explore, so I haven't given up.

I have worked extensively with several of my customers with Ethercat devices using the NI solution. I'm glad you figured it out. It seems like you're on your way. Finding the ESI file is the trick and making sure it's "installed" on the cRIO and the PC side. To echo what Rolf mentioned. You will get very little support from NI if things go wrong, or if you want to do something that is outside of the typical use-cases.

Note: you have zero control over the topology of the Ethercat network. NI hides this network discovery algorithm, and you cannot influence it. This comes up when you have more than one device on the network and/or you have Ethercat switches in the mix. For example, if you daisy chain another device it will be named device 1 (in your image, your first one is named "device"). If you swap the devices in the chain, they will also swap position and hence, names and you cannot control this behavior. In other words, the physical network cabling dictates the device list order and naming you see in your project. This might not affect you, in your case, but something to be aware of. Especially since your shared variables will be invalidated.

Personally, I don't use statically defined shared variables because I typically work with highly dynamic systems. But using your approach will work just fine and is the easiest way to get started. There is a way, to dynamically discover devices on the Ethercat bus. Here is an NI article describing this: Programmatically Discover and Access EtherCAT I/O Items - NI This might be useful and good to know in case you need this approach.

I fixed the issue. It was actually kind of funny. So there's a security rule on the server to protect against SQL injection. It found a match with "User_group". I guess it thought someone was trying to get the user data from the database? 😁 I added an exception. All good now.

4 hours ago, LogMAN said:

here is another issue I stumbled upon

I'll take a look and get back to you. But that's a strange error to get on editing a page. I recall editing this page just recently without issue. 😕

9 hours ago, Rolf Kalbermatter said:

I just checked the logs and am surprised how many user creation log entries are there.

Unfortunately, many of those are bots. I've disable user:pages long time ago, because of the spam. If there's anyone that deserves a lot of credit lately it's @LogMAN. He's doing amazing work cleaning up the pages and adding/editing content.

There's a push recently from NI to support the Wiki and promote its use to the broader community and within NI internally as well. So, we should see more traffic and more activity than usual, which is great. This is one of the reasons for the recent stability updates.

I encourage everyone here on LAVA to find whatever LabVIEW topic they are passionate about and start adding some pages or even fleshing out some existing content that needs improvement. One way to start would be to find some information that you always wish NI had easily available on their website but could never get easy access to. Then create that on the Wiki.

It looks like the reorg of the LabVIEW Wiki domain caused the channel to go away. I'm investigating this to see if it can be fixed.

41 minutes ago, LogMAN said:

I did a quick test in a private MediaWiki instance and got it to work using the fix available on GitHub

Thanks! That worked.

4 hours ago, LogMAN said:

The most recent change listed is from December 27th, 2024.

I fixed it. I had to disable an extension that was breaking that page for some reason.

4 hours ago, LogMAN said:

The extension has not been updated since 2021. It is, however, listed as "stable".

Several others have reported it broken on the support page.

3 hours ago, LogMAN said:

The TreeAndMenu extension is missing, however, which breaks certain pages

Unfortunately, this extension had to be dropped. It's broken in MediaWiki 1.43. I'm investigating a fix.

The LabVIEW Wiki has received an update. Hopefully, it responds with fewer errors.

Do you have a contract in place with this customer? It sounds like no.

If you DO have a contract, then does the contract allow for time-bombs in delivered software?

Just saw this update. Will take a look.

I've been getting reports recently from people, that the LabVIEW Wiki is offline sometimes. I've never experienced this myself so I'm curious if people on here have noticed anything. Typically, the issue manifests with a 503 Service Unavailable message. I will investigate further this weekend when I have time, but just wanted to get some general idea.

Has anyone tried using these?

https://revolutionpi.com/revolution-pi-series/

Looking for a new profession?

Thanks for the link. I'll check it out.

I'm using my own installer builder for my LabVIEW app. I now want to include some NI drivers. What is the best approach? I don't want to use the NI installer builder.

I've seen this here, but not sure if the output of this can be called from my 3rd party installer builder. What have others done?

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000fyxySAA&l=en-US

2 hours ago, X___ said:

Other cheaper and more powerful alternatives may be available

Having a bad day? 😀

On 2/15/2022 at 12:48 PM, Gribo said:

Anecdotal evidence, I know, but here  (Toronto, Canada) The number of open LabVIEW developer positions is practically 0.

I worked in Toronto for many years in the past and can tell you that this is nothing new. The "market" for LabVIEW in that area is not very strong. I don't know why, but it's always been like that. There are definitely LabVIEW "Hubs", where there are more opportunities. It also highly depends on if there is a concentration of companies that use LabVIEW in one area. For example, the SF Bay Area where I am now has many job opportunities. LabVIEW users\developers knowledgeable with the language jump from company to company spreading the word. What makes LabVIEW grow is the same as it was from inception. Someone falls in love with the language and becomes an evangelist that then carries the torch and spreads the word. NIWeek was definitely the "church", where we brought others to hear the "good word". Whether we like it or not, my friends, this is a religion...