Gribo

You learn something new each day

Neil, While LV is not used in any financial role that I know of, it is used in many industrial applications. You don't want to be the one that enabled the next Flame/Doku, the same as Siemens didn't want to be the first, when their engineers said it is not their problem.

Why would you expose a cRIO or PXI to the world? Air gaps, Updating the PC host OS/firewall, and strict security enforcement are the way to go in most of the use cases of LabView (said the one who built a Google map interface )

RSI and Carpal tunnel syndrom are serious issues, call your doctor/physiotherapist for a better advice. My solution was to switch hands (Got a left handed mouse) and take a 10 minutes break every two hours.

View File LibreOffice Simple LV interface A set of simple VIs that uses the LibreOffice / OpenOffice UNO API. The result is very similar to MS Office ActiveX API. Currently, only Calc is supported. This was tested on Windows 8 with LV2013 64 bit and LibreOffice 64 bit. Submitter Gribo Submitted 10/13/2015 Category *Uncertified* LabVIEW Version License Type

Ok, I managed to get the code above to work properly. There was a missing x86 VC2010 runtime dll on the target computer. the x64 was installed as a default, so I had to explicitly install the x86 too.

I compiled both 32 and 64 bits, the 64 bit works without a problem. I think I will rename the DLL themselves, as Shaun suggested. This solution smells like a hack, what happens after a software update? The programmer needs to remember to rename these files? I tried to be smart.

There is also an .INI file which directs to the API install path. It has just one line. C:\program files (x86)\signal hound\spike\api. I verified that the generated path is ok. Rolfk, this might explain why the same code works with the invoke nodes having the DLL path predefined. It should have behaved the same in both cases, or, at least report a file not found error (#7). I even tried placing the DLL in the same directory as the executable, which is one of the location windows searches for them, and got the same error.

Hello, I wrote an application which can use either a 32 bit or a 64 bit dll, it loads the dll from a path specified in an INI file. This code works properly on the development machine (LV2013, both 32 and 64 bit, both with a debugger and as an EXE) but doesn't work on the tester machine as an executable. It throws error code 13 (in LV2013 - file is not a resource, in LV2014 - Failed to load DLL due to invalid format or missing dependencies). However, when I change all the Invoke nodes to use a static predefined path, everything is OK. What am I doing wrong here? I rather maintain one code base and build for each target than maintain a code for each target. The API dll is from signalhound.com http://signalhound.com/spike

Autodesk Trueview or DesignReview has a COM (ActiveX) component that allows LV to display a DWG file.

Check the Excel .NET API reference from Microsoft. The application object has an option to start hidden.

The best Amazon review poetry by far: http://www.amazon.com/review/R3I8VKTCITJCX6

Do you use the MP3 files or the original .MOD files?

Those buggers cannot be all facing the same direction, that ship was way too slippery to control.

I hope you know about this: http://sc2.sourceforge.net/

Civilian GPS have velocity limits encoded into the firmware (~500m/s). If your rocket surpass that, you can't use GPS.

It depends on what sort of peripherals and how many events/hour you require. A unit which reports once a day can last years on a single LiSOCl AA battery, on the other side, a smartphone which has its transceiver and CPU always on lasts a day or so.

They are expansive, however, I can ask regarding some of our older, unsupported products, since your requirements are relatively simple.

RTLS systems can be quite expansive, especially with these requirements. I work for a company which makes such systems, indoor/outdoor location, sensors and relay outputs, LCD on the agents, GUI and even a LV API. We have used the system in the past to track workers in a construction site. You can check us out at http://www.precysetech.com Another company is Aeroscout, which can use the wifi infrastructure for their active tags access points. Their main market is health care (tracking equipment in a hospital).

Wireless takes too much energy compared to wired. Personally, I prefer optics.

That is very interesting, I wonder if these properties can be exposed somehow.

You use the system exec.vi under the connectivity palette to run the AVRDUDE.

Version 1 was uploaded. It has all the features I wanted, that is, a bi-directional interface between a standard browser and a LabView application. There are still scale-ability issues, which will require a more capable messaging library (0MQ is my prime candidate).

You need few packages, OpenG and JSON Labview, both available from the code repository here, or better yet, via the VIPM.