Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Last week
  3. The mutex ensures that no one else can perform a read or write while it is locked. Otherwise you could mismatch requests and replies. [W1,R1], [W2,R2] instead of potential W1, W2, R1, R2 You could have it in a non-reentrant VI, but then you would also restrict parallel operations for completely different ports. In this case, in could be wired direclty to out since there are no modifications to it. The mutex will be locked either way.
  4. Hello everyone, Is someone can explain me. How works this modbus VI? Two questions : I never used the "in place element structure" what's the point of using this type of structure? Is it better FGV? Is it important connect "Modbus master out" at the end of this structure VI or, if it plug to the input "Modbus master in" it will do the same? This VI use a memory control, how it work ? (three question sorry 😊) Kind regards. François A.
  5. I've no experience with Redis. For monitoring/supervision/alerting, you don't need local storage at all. MQTT might be worth looking at for that. Sorry I couldn't be more helpful but looks like a cool project.
  6. This tool is now available on my company website : https://exxalis.fr/solutions Version 2.0.0, compiled with LabVIEW 2023 Q1 64-bits
  7. well, NSV are out of cause here first because it's a linux distributed system, second because of their own proven merits 😆... The background is this, BTW. We have 17 PCs up and running as of now, expected to grow to 40ish. The main business logic, involving the production of control process variables, is done by tens of Matlab processes, for a variety of reasons. The whole system is a huge data producer (we're talking of TBs per night), but data is well handled by other pipelines. What I'm concerned with here is monitoring/supervision/alerting/remediation. Realtiming is not strict, latencies of the order of seconds could even be tolerated. Logging is a feature of any SCADA, but it's not the main or only goal here; this is why I'd be happy with a side Tango or whatever module dumping to a historical database, but I would not look in the first place into a model "first dump all to local SQLs, then reread them and merge and ponder about the data". I'd think that local, in-memory PV stores, local first level remediation clients, and centralized system health monitoring is the way to go. As for the jenga tower, the mixup of data producers is life, but it is not that EPICS or Tango come without a proven reliability pedigree! And of course I'd chose only one ecosystem, I'm at the stage of choosing which. ETA: as for redis I ran into this. Any experience?
  8. My tuppence is that anything is better than Network Shared Variables. My first advice is choose one or two, not a jenga tower of many. What's the use-case here? Is the data real-time (you know what I mean) over the network? Are the devices dependent on data from another device or is the data accumulated for exploitation later? If it's the latter, I would go with SQLite locally (for integrity and reliability) and periodic merges to MySQL [Maria] remotely (for exploitation). Both of those technologies have well established API's in almost all languages.
  9. One important thing to note is that if the application was built with the "Pass all command line arguments to application" key checked the OS Open Document event is never triggered 🙁 (come to think of it this might be why it has not worked as expected in the past 🤔). This might be a show stopper in cases where you *sometimes* want to be able to launch the app with additional/other arguments, e.g. to trigger some special behaviour. We do that to allow system administrators to disable some features in the application depending on the user's access, or point the application to an alternative configuration e.g..
  10. Could it be that the filter event only works for LabVIEW file types? There is no reason to let an application filter file types that LabVIEW doesn't know about how to handle anyway. They will be simply dropped into the "round archive folder" /dev/null anyhow if the normal event doesn't capture them.
  11. Yes, it does work 🙌 When that tip first got out way back it did not seem to do the job properly, but it does now, in LabVIEW 2022 at least. I could not get the filter-version of the event to give me anything for some reason, but the regular does and it picks up opening multiple files together. (Looking at the issue again earlier I noticed VIPM e.g. still uses the helper app (VIPM File Handler.exe), but perhaps that is just a legacy / if it ain't broke, don't fix it thing. This is "supersecretstuff" too though, so trusting that it will continue to work is another issue.)
  12. Reviving this thread. I'm looking for a distributed PV solution for a setup of some tens of linux PCs, each one writing some ten of tags at a rate of a few per sec, where the writing will mostly be done by Matlab bindings, and the supervisory/logging/alerting whatnot by clients written in a variety of languages not excluding LV. OSS is not strictly mandatory but essentially part of the culture. I'd would be looking at REDIS, EPICS and Tango-controls (with its annexes Sardana, Taurus) in the first place, but I haven't yet dwelled into them order to compare own merits. In fact I had a project where I interfaced with Tango some years ago, and I contributed cleaning up the official set of LV bindings then. As for EPICS, linux excludes the usual Network Shared Variables stuff (or the EPICS i/o module), but I found for example CALab which looks on spot. Matlab bindings seem available for the three. The ability of handling structured data vs. just double or logical PV may be a discriminant, if one solution is particularly limited in that respect. Has anyone recommendations? Is anyone aware of toolkits I could leverage onto?
  13. Earlier
  14. The task of intercepting WM_DDE_EXECUTE message has been around for a while here and there. Except that private OS Open Document event there are two more ways to get this done. 1. Using Windows Message Queue Library 2. Using DDEML of WinAPI and self-written callback library More details can be found in this thread. I now think that it could even be simplified a bit, if one could try to hack that internal LinkDdeCallback function and reuse it like LabVIEW does. But I feel too lazy to check it now.
  15. I was fairly sure that there was actually an application event for file open events passed from the OS to the running application, but seem to have dreamed that up. It shouldn't be to difficult to add although might have some implications. Would have to be a filter event that can check the file name and then indicates if LabVIEW should further handle it (for LabVIEW known file types), or if it should be ignored (potentially handling it yourself). Ahh, it's super secret private special stuff: And seems to have trouble in some newer versions than 8.2! Although Ton says he got it to work in 2009 again.
  16. https://www.physicsforums.com/threads/looking-for-information-on-verity-sd100-monochromator-unit.1058950/
  17. 0 I have attached a RS232 to USB converter and connected SD-100 Verity Monochromator Legacy Equipment(circa 1999 Device). No software available(unable to find and manufacturer does not have) to drive commands to the unit. I know the unit is a self contained with logic and microprocessed controlled and with external(via Rs232)commands will do its own arrangements to scan and send back plottable data from the RS232 port etc. I have randomly sent commands through the Debugging software to send commands and observe the received data. The unit does not respond and not sure if its because its looking for the right commands or a series of commands I am not aware of etc. I am at a lost and would like to be able to use this equipment. Anyone who might have an inkling on the approach or a better idea please let me know... Thanks in advance!!!
  18. Command line arguments is fine for the initial launch, but the helper app is used to also pick up double-clicks on associated files when the applictaion is already running.
  19. Under Linux, it is in the Configure tab of the compile worker, see https://lavag.org/topic/22267-installing-ni-lvfpga-un-ubuntu-20/?do=findComment&comment=144693 . Under Windows? At first sight I haven't found anything relevant in C:\Program Files (x86)\National Instruments\FPGA\CompileWorker .
  20. Recently I resinstalled LabVIEW 2019 and FPGA19.0 ,FlexRIO 19.0 and I couldnt find where to change the number to compile at the same time. Im pretty sure there is an option in LabVIEW 2019 when trying to comile FPGA VIs ,if you input 3 then three VIs can compile at the same time.(By default you can only compile one ,which is relatively slow when I have multiple VIs which requires many hours each to compile.) Now I just cannot find where to change the number, does anyone there know where and how to change the number? Thanks.
  21. This toolkit does not rely on TestStand license, completely developed using LabVIEW.
  22. Hello,Hoover I'm glad you're interested in the kit. There are no restrictions on the use of this toolkit at this time, only an activation code is required to use it, I can provide the activation code if you want to test it out. There is no source code in this toolkit, it mainly contains an application (SequenceEditor) and a PPL (TestEngine) and some examples. There is no detailed documentation in English yet, but I can start by providing a simple usage document that shows you how to get started with the toolkit. Most of the features in this toolkit are designed to work with TestStand, so if you are familiar with TestStand, using this toolkit will be easy.
  23. I sense a candidate for https://thedailywtf.com/
  24. This looks interesting. What are the licensing used? What are the restrictions? Is there a manual that is in English? Is the source code available?
  25. So I use Inno Setup for making most of my LabVIEW installers. It is pretty easy to setup file association with the registry like the LabVIEW Wiki mentioned. Here is a post explaining some of the settings. Once I'm on the LabVIEW side I've always used the property node Application >> Command Line Arguments. Maybe I've just used that because the event didn't always exist? I'd like to think the property node gives you more control since I can send other command line arguments not just a file. But the majority of the time I do just want the file path.
  26. I can't even find threads I posted in last week. It's a skill, to be sure.
  27. Oh, I knew. I just like to poke dormant threads (keeps the context instead of duplicating it into a new one) until their issue is resolved. Only then can they die, and live on forever in the cloud😉
  1. Load more activity
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.