CT2DAC

VIPM 2018 (by company policy). Could that be the issue?

Cannot install versions more recent than 1.13 with VIPM - error: unable to download from repository.

First in the queue the event of the cluster element, second the event of the cluster.

(easy to find out, I was just lazing off...  😎)

Confirmation is welcome!

I have a cluster with several elements.

For a few, I have a "special treatment" so I need a specific event case, in addition the cluster event case.

What is the event priority?

First the cluster than the single element o vice versa?

I see it's quite sometime this has been posted, but only now I ever come accross it (although I have long been interested in programmatically creating data structures from "end result files" instead of painstakingly jotting down every cluster, field, subcluster, array, etc.).

EXCELLENT piece of work!!!!!!! A lot of stuff to learn from!

Thanks.

On 2/6/2023 at 3:00 PM, hooovahh said:

You can embed the ico file in the VI as a string constant, and do the same thing, saving it to a temporary location as well.

This is quick and easy, it is certainly worth a try.

Thanks.

Oooold thread, but maybe someone will answer.

I'd like to change the icon but NOT from an .ico file, i'd prefer to have a LabView image constant.

I tried to find some .net to create an image from an array instead of "from file" but I got lost and cannot find anything when selecting on LV .net constructor....

It has been a long lasting problem, obviously not easy to solve.
I keep hoping somewhere, someplace, someone will have a genious idea and help solve it.

Meantime, I think Shaun's idea of stubs is still the 'least painful' way to it.

Sometimes, I still go "specific simulators" - but it's far too time consuming - most often I just 'dry code' and test only when instruments arrive. Experience helps, in this case, to avoid falling on the same old traps.

I'll dig into this, with new projects and as time goes by...

I fear you may be right, but I still hope for some input.

After all, there are now plenty of powerful language parsing/processing techniques and algorithms, so what can be so complicated in a trivial handful of commands and parameters?

Why not bring some of that knowledge to help poor old engineers having to do with low-tech serial devices (while awaiting delivery)?

Hello All.

I have the need for instrument simulators, that I can use while developing and the instruments are not physically available.

Think of any RS232, or ETH instrument: dmm, motion controller, hardware interface, sensor, whatever.

I would like to have a piece of software that I would "connect" to and send commands. This sw would basically do syntax checking and reply with error codes in case of invalid syntax or with some 'valid' reply - a 'simulated' dmm would reply with a random value (maybe within a range). [I know of IVI instrument simulator, but this offers a limited number and, most often, my instruments are not IVI/SCPI compatible].

Now, the main issue is that I would like to avoid writing a specific simulator for every instrument I come across with; it would be time consuming and error prone, defeating the whole purpose of working with simulators (which is mainly getting ahead and saving time, while waiting for instruments to become available).

I would like to have the syntax specified in a text file (I know the commands syntax from the instrument manual, much like: CMD param1 -OPT1=param2... etc.). It resembles what command line interpreters, language compiler preprocessors do, based on a syntax/grammar description (abstract syntax tree?).

Searching on the net gives out a lot of stuff; however everything is specifically targeted for for windows, linux and other programming languages.

I could not find anything "programmable" or general purpose.

I came across a couple of posts - Exterface by Daklu and Gold Parser Engine by Taylorh140 - which seem to point in the 'right' direction but I can't seem to find any code to work on.

Is there anyone out there that can point me towards any kind of resource - not necessarily LabView - that can perform as I "dream of" and from I can learn/use?

👍
Thank you so much!!!

On 4/1/2022 at 5:05 PM, hooovahh said:

Attached is my terrible and hacky solution that works pretty quickly.  On Windows it uses the Ping View Info program calling it from the command line, then parsing the results.  It uses a couple of functions from the OpenG File I/O.

Find Ping IP Devices.vi 77.1 kB · 18 downloads

In LV2018, please, please....

Bean's VI's still rockin........ 🤩

Thanks Bean, saved my day!