Acetone

Members
  • Posts

    3
  • Joined

  • Last visited

Acetone's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. I have set up a sequence, activated by a button, that records transistor characteristic curves - multiple traces are created dynamically, complete with legend, specifying conditions for each trace. The button is the only control I use, so the sequence has a DeleteAllTraces() at its beginning, to clear the graph area at the beginning of the next experiment. The traces are removed, however, the legends remain until the first new trace appears (it is not drawn in real-time; I collect the data in an array for each trace, so that I can delete the channel history before each new trace, so there's about a minute or so with the empty graph and the "old" trace labels above it). Is there a way to clear the legend as well, so that each experiment run begins with a completely empty graph? It should be noted that since the traces are created dynamically, the variable that I use for their names stores only the most recent one at the end of a run.
  2. I see. Not declaring it as a string from the very beginning might be what happened, yeah. Thank you!
  3. Hello, I had a strange issue with my sequence. I used two global string variables named "CurrX" and "CurrY". These were intended to dynamically specify X and Y expressions for graph traces. However, the sequence just wouldn't work, the traces would be added (as seen in the graph properties; no actual trace appeared on the graph), but both expressions would be shown as "NaN". When I tried seeing the current value of these variables (typing "?CurrX" in the command line), it would return the "NaN" value as well. As best as I could figure, everything else in the sequence was working as intended. Rather frustrated, I just replaced every instance of the "CurrX" by a different word, which should probably not be repeated here - and it fixed the issue. Same with "CurrY". As far as I've searched the user's guide, there's no mention of variable names beginning with "Curr" causing any problems - indeed, some of the examples therein use "current" as a variable name. Is there any reason why "CurrX" and "CurrY" cannot be used, and if so, is there a comprehensive list of any other reserved/unavailable variable names?