You Are Here:
You are here: SCPI Guide > Protocol > Protocol Errors

Protocol Errors

Below is a list of possible errors and their explanations. They can be retrieved using tSYSTem:ERRor[:NEXT]?

  • -100,"Command error". This is the generic syntax error for devices that cannot detect more specific errors. This code indicates only that a Command Error defined in IEEE-488.2, 11.5.1.1.4 has occurred.
  • -102,"Syntax error". An unrecognized command or data type was encountered.
  • -105,"GET not allowed". A Group Execute Trigger was received within a program message (see IEEE-488.2, 7.7).
  • -108,"Parameter not allowed". Parameter given for command which does not have any parameters.
  • -109,"Missing parameter". Command requiring parameter(s) is issued without them.
  • -112,"Program mnemonic too long". Protocol keyword too long. All keywords are less than 12 characters long.
  • -113,"Undefined header". The header is syntactically correct, but it is undefined for this specific device; for example, BXYZ is not defined for any device.
  • -120,"Numeric data error". Number format is not recognized.
  • -129,"Numeric data out of range". Numeric parameter value is invalid.
  • -140,"Character data error". This error, as well as errors 141 through –149, is generated  when parsing a character data element. This particular error message is used when the device cannot detect a more specific error.
  • -141,"Invalid character data". Either the character data element contains an invalid character or the particular element received is not valid for the header.
  • -148,"Character data not allowed". Character data detected when number is expected.
  • -150,"String data error". String. This error as well as errors –151 through –159 is generated when parsing a string data element. This particular error message is used when the device cannot detect a more specific error.
  • -151,"Invalid string data". A string data element was expected, but was invalid for some reason (see IEEE-488.2, 7.7.5.2); for example, an END message was received before the terminal quote character. 
  • -158,"String data not allowed". String data detected when number is expected.
  • -160,"Block data error”. This error, as well as errors –161 through –169, is generated when parsing a block data element. This particular error message is used when the instrument cannot detect a more specific error.
  • -161,"Invalid block data". A block data element was expected, but was invalid for some reason (see IEEE-488.2, 7.7.6.2); for example, an END message was received before the length was satisfied.
  • -190,"Execution in progress". Command not allowed in current state.
  • -191,"Execution not in progress". Command requiring scenario/signal generator executing issued when device is idle.
  • -192,"Unused channel". Query or command for a channel that is currently not allocated to any signal.
  • -193,"RSG command overflow occurred". Too many RSG commands were received to process within a GSG 10 Hz epoch.
  • -194,"RSG command underflow occurred". Underflow detection was enabled, and no GSG RSG commands were received within a GSG 100 ms epoch.
  • -200,"Execution error". Scenario execution failed to start.
  • -220,"Parameter error". Scenario/signal generator started without a scenario.
  • -221,"Settings conflict". Indicates that a legal program data element was parsed but could not be executed due to the current counter state (see IEEE-488.2, 6.4.5.3 and 11.5.1.1.5.)
  • -221,"Settings conflict; invalid combination of channel and function". See above.
  • -222,"Data out of range". Indicates data values are out of range or input data such as Navigation data files have incompatible ranges of validity.
  • -224,"Illegal parameter value". Scenario configuration has illegal coordinates or date.
  • -225,"Out of memory". Command processing was interrupted because of the lack of memory.
  • -241,"Hardware missing". This error is given only when the reference clock signal is missing when scenario/signal generator is started or when the Ethernet MAC address cannot be found. Check that the external reference clock is connected. Verify Network Ethernet Port detection and activity lights.
  • -250,"Mass storage error". Copying/moving files is not allowed between directories.
  • -256,"File name not found". File operation attempted on a non-existing file or directory.
  • -257,"File name error". File name is empty.
  • -410,"Query INTERRUPTED”. Indicates that a condition causing an INTERRUPTED Query error occurred (see IEEE-488.2, 6.3.2.3).
  • 1401,"Wrong program data checksum found". Checksum of file transferred is invalid.
  • 1403,"File length error". In file transfer length is invalid. This can be happen if there is not enough memory or storage space on device to retrieve file.
  • 1404,"File type error". Invalid file type given.