Problem with SCPI commands for Fluke 8846A

[verfelixt]

Hey guys,
I am trying to access an Fluke 8846A (https://download.flukecal.com/pub/literature/8845A___pmeng0300.pdf) via GPIB/VISA. However, many SCPI commands are not recognized, and I can not figure out why. For example, "*IDN?" will give me the response as described in the manual, "*RST" also works fine. When I try other commands, like "MEAS:volt:ac? 10", which is listed as an example in the manual, the device is showing errors -102 (Syntax Error) and -420 (unterminated command).
Do you have an idea on how I can solve this problem?

Kind regards

[JÞB]

---

@verfelixt wrote:

Hey guys,
I am trying to access an Fluke 8846A (https://download.flukecal.com/pub/literature/8845A___pmeng0300.pdf) via GPIB/VISA. However, many SCPI commands are not recognized, and I can not figure out why. For example, "*IDN?" will give me the response as described in the manual, "*RST" also works fine. When I try other commands, like "MEAS:volt:ac? 10", which is listed as an example in the manual, the device is showing errors -102 (Syntax Error) and -420 (unterminated command).
Do you have an idea on how I can solve this problem?

Kind regards

---

Well yes.

To set a 10A range for AC Voltage Measurement use

"MEAS:volt:ac 10" no question mark.

To Query the configured AC Voltage Measurement range use

"MEAS:volt:ac?" The device will respond with 10 or whatever range is actually set.

You have simply misunderstood what you read in the manual.   THANK YOU for actually reading it 😊

[verfelixt]

That does not work, too. As described, "*IDN?" or "*RST" are working, commands like "CONF?", "MEAS:volt:ac?"/"MEAS:volt:dc?" will not work and cause the described errors on the device. Same goes for other commands that do not prompt a response from the device like "MEAS:volt:ac 10" (no question mark 😉 )

[JÞB · Accepted solution]

The prototype is

MEAS:VOLT:AC <range>, <resolution>

Range can be "min", "max" or some value less than the devices maximum.

To set just the range use 

MEAS:VOLT:AC:RANG <VAL>

NOW, that's assuming the language is set to l1

In l2 you would send

VAC

RANGE <ENUM from table 23a or 23b>

In l3 you would need a urinalysis screening prior to reporting to work. But get and out functions were very time saving back when communicating with smoke signal speeds.

[verfelixt]

Thank you very much, the wrong language was the problem, it was set to L2, not L1. I should have read the manual more properly 🙂

[JÞB]

---

@verfelixt wrote:

Thank you very much, the wrong language was the problem, it was set to L2, not L1. I should have read the manual more properly 🙂

---

No, thank you for linking it!  I've used similar devices in the past and that darn manual was probably one of the least clear I have read.  No shame for a novice to come away with a headache after reading that!  Glad I could help.

[billko]

---

@verfelixt wrote:

Thank you very much, the wrong language was the problem, it was set to L2, not L1. I should have read the manual more properly 🙂

---

You did your homework by reading the manual and tried your best to implement it.  No shame in that!!!  🙂