2636A: Basic TSP Commands Cause Runtime Errors

Hi,

I have some difficulties communicating with a model 2636A SMU.
I also use 2 2602B with the same code and experience no issues.

For some TSP commands like "smua.abort()" or any "smua.trigger....", a TSP Runtime error is triggered.
- TSP Runtime error at line 1: attempt to call field `abort' (a nil value)    
- TSP Runtime error at line 1: attempt to index field `trigger' (a nil value) 

it looks as if these commands are unknown to the SMU, which seems weird. Are there any settings which could cause such a behavior or am I overlooking something basic?

Many Thanks!
 

Are you sure it is an A version?  There was an earlier version without any letter suffix (2636 vs 2636A vs. 2636B).
The original 2636 level would not recognize the smua.trigger..... like what you experience.

When you query the *IDN? command, what is the returned model number in the response?

Ah, there is the basic fact I overlooked! Yes, indeed, it's a 2636 non A. Thanks :) !

With these models, the triggering seems to be handled in a more "minimalistic" way.

I would like to build a custom list and trigger each list value individually via the GPIB GET command.
Upon reading the manual, this doesn't seem possible with ICL commands alone, but it requires a dedicated TSP script.