Products > Test Equipment
Siglent scope: trial and error to find proper syntax for SCPI commands
rfclown:
--- Quote from: tautech on October 18, 2023, 08:50:27 am ---
--- Quote from: Performa01 on October 18, 2023, 08:35:38 am ---
--- Quote from: 2N3055 on October 18, 2023, 06:52:36 am ---Again, manual you are referring to is from 2014, as URL you posted clearly states. Manuals can have typos and new features are added all the time, so manuals are corrected and updated. Please download current one as per Tautech link.
--- End quote ---
This happens only with Siglent. All other manufacturers are perfect in this regard.
--- End quote ---
Additional bold added.
The clue to this is the latest programming manual version: E02D
Some Siglent websites list the manual release date in the URL, some don't so the version # is always the most reliable indication of the latest.
--- End quote ---
Indeed, the problem for me was the manual. I Googled, and picked the first URL I saw that was on the Siglent website.
As far as the PACU command, it is very different between the two manuals, not just a difference of a space. No wonder I couldn't guess at the correct syntax.
Old manual command example (pg 84): PACU 2, PKPK, C1
New manual command example (pg 120): PACU
PKPK,C 1
This was cut-and-pasted from the manual into this message window. Notice the linefeed after the PACU command... whoops! It should be, "PACU PKPK,C 1" which is how it appears on the manual in a pdf viewer. Sometimes spaces are important, which is why my normal habit is to cut-and-paste from a manual or programming example so that I don't make a mistake.
KungFuJosh:
--- Quote from: nctnico on October 18, 2023, 07:15:31 pm ---Trying to work on one problem at a time is a much better approach compared to randomly trying to fix things. When your car doesn't start, you are not going to inflate your tires or clean the steering wheel.
--- End quote ---
A modern car might need a firmware/software upgrade when troubleshooting. Everything set to a common standard before wasting time randomly fixing things.
2N3055:
--- Quote from: rfclown on October 18, 2023, 08:22:03 pm ---
--- Quote from: tautech on October 18, 2023, 08:50:27 am ---
--- Quote from: Performa01 on October 18, 2023, 08:35:38 am ---
--- Quote from: 2N3055 on October 18, 2023, 06:52:36 am ---Again, manual you are referring to is from 2014, as URL you posted clearly states. Manuals can have typos and new features are added all the time, so manuals are corrected and updated. Please download current one as per Tautech link.
--- End quote ---
This happens only with Siglent. All other manufacturers are perfect in this regard.
--- End quote ---
Additional bold added.
The clue to this is the latest programming manual version: E02D
Some Siglent websites list the manual release date in the URL, some don't so the version # is always the most reliable indication of the latest.
--- End quote ---
Indeed, the problem for me was the manual. I Googled, and picked the first URL I saw that was on the Siglent website.
As far as the PACU command, it is very different between the two manuals, not just a difference of a space. No wonder I couldn't guess at the correct syntax.
Old manual command example (pg 84): PACU 2, PKPK, C1
New manual command example (pg 120): PACU
PKPK,C 1
This was cut-and-pasted from the manual into this message window. Notice the linefeed after the PACU command... whoops! It should be, "PACU PKPK,C 1" which is how it appears on the manual in a pdf viewer. Sometimes spaces are important, which is why my normal habit is to cut-and-paste from a manual or programming example so that I don't make a mistake.
--- End quote ---
I do must warn you that PDF format is actually very bad. It was made for page typesetting.
Perfectly visually rendered page, when copied and pasted can paste as a spageti because of how PDF internally works...
And writer that creates page has no control of how internally PDF renderer works...
I have been bitten by random spaces, mixed codepages and scrambled sentences when copy/pasting from PDF.
I still do it, many times it goes without problems, but I always proofread what was pasted..
All in all, what is important is that you sorted out problem at hand and can move on with your work..
And if you do find any problems, report .. Or if you need help, ask... Maybe someone can help..
Best,
Navigation
[0] Message Index
[*] Previous page
Go to full version