non-scpi compliant command strings

[crossrulz]

---

@rolfk wrote:

---

@novaktamas wrote:

What's made me really upset a couple hours ago, that I downloaded the API reference of NI-DCPower, which is a whopping 787 pages PDF. If I'm lucky it takes only a couple days to implement the new API, but it can easily be prolonged for some weeks.

---

You should feel happy. 😁 Some manufacturers make the task of getting any form of manual beyond the Users Manual an exercise in persistence and begging, until you get some kind soul that is willing to make that extra step to search for the document internally and send it to you. Or they make you go through 40 pages of legalize and then sign the document in which you pledge your first born for the case that you accidentally let the document slinger around and get into the wrong hands (which is generally anyone that they haven't been able to force to go through the same procedure). 🙄

---

Rolfk, you got off easy.  I have had several instruments that had no documentation even remotely available, not even to tech support.  I have had a few that were even worse: the documentation was wrong.  Out came the oscilloscope to figure out what was going over the RS-232 bus and/or reserve engineering the commands from supplied software.

[novaktamas]

I'm aware this is how it works, still...I'd be more understanding if it was purchased from the ebay, 25 bucks from the Red Dragon Corp, PRC.  It is strange when large "honorable" firms do this kinda support for a 10k+ €/$ product. I nail it: this is not the case here. The NI manual is available and detailed....1000+ pages...I'd be much happier with a SCPI command reference of 20 pages 😄