How do I send commands to my oscilloscope in NIMAX?

[Norbert_B]

If the provided EXE runs properly, the drivers should be working as well....

maybe there are some options left on the tab "USB Settings". Take a look and check things out.

The main question is: can ATTEN provide information on how they communicate with the scope in the EXE?

They'd probably not going to share much information on this.

Honestly, you should start asking yourself if the "saved money" by purchasing a less expensive instrument is not spent by now by trying to fiddle out how to use this instrument outside the predefined EXE the vendor provides.

My experience is that especially the cheap vendors lack of interconnectivity to common programming languages and lack of documentation/support. This is were they usually save the money to sell their products for less money.....

In VISA test panel, you can also look into the configuration options for the session. Make sure that the options fit to the instrument (termination character, ...). If this works out, transfer those settings to a LV VI; there are some VISA examples available which should be adopted quite quickly.

Norbert

[jonabel1971]

Whether or not I got a cheap scope is regardless.   I need to get it working.   The drivers come in a .zip file, not an executable - so I am doing things manually.   Yes, it sucks, but my experiments are paid for out of my own pocket, so to answer your next question - no, I am not buying a more expensive scope.  I will have to search for the driver location if  nobody knows where the 64-bit driver directory is located for LV/NIMax.

[Norbert_B]

I wasn't going to tell you to buy another hardware. i was just pointing out that the decision for a cheaper instrument led to the fact that you now have more work to get it up and running (if this is possible at all); THIS is creating more costs than a more expensive instrument. So just take it as recommendation for future projects.

As already said, if the instrument works with "its EXE", the hardware interface works correctly.

I expect the source of the problem to be some special setting for the communication; most often, instruments require specific termination characters in order to work properly. An example for such a termination character is '/n' or '/crlf'.

If you get no information on this, all you can do is to "brute force test" and see if anything is going to work.

Also, check different commands and see which are already working and which are not. Try to bug ATTENs support about the uniqueness of those commands. "What makes these different to others like '*IDN?'?".

Besides: do not mark some reply as "answer" if you still have questions on the topic.

thanks,

Norbert