| Products > Test Equipment |
| SPD3303X-E SCPI Interface issues |
| << < (3/8) > >> |
| finos:
Can the siglent handle 2 simultaneous connections querying data? |
| rf-loop:
--- Quote from: SpiderKenny on June 06, 2019, 02:21:27 pm ---Hi I have an SPD3303X-E and I'm trying to write some code for it. I have written code for SCPI devices before (such as my Rigol DS2202E) without any trouble. I'm connecting over TCP/IP to port 5025, so I'm using SCPIP RAW not VXI-11 The problem I am finding is that many of the commands listed in the QuickStart manual don't work. I think I may have missed something. For example, if I send "*IDN?" then I get the correct response: "Siglent Technologies,SPD3303X-E,SPD3XHBC3R0662,1.01.01.02.05,V3.0" And if I send "*READLL?" I get the correct response too: "4,13.90,0.00,0.00,20.06,0.00,0.00,18.00,1.70,32.00,3.20" But if I send things like "OUTPut CH1,ON" then the power supply just beeps, and reading the error code with "SYSTem:ERRor?" results in: "ERROR: 3 Command keywords were not recognized" Is there some other step I need before sending some of these commands? --- End quote --- I do not know if this is your problem but least it need check carefully: When you send string there need care syntax. Siglent SPD programming tips tell this: --- Quote from: Siglent SPD programming tips ---"There are two areas that differ from some other instrumentation:" --- End quote --- And here is one: --- Quote from: Siglent SPD programming tips ---The SPD requires ā\nā termination only. Additional characters will cause a failure. --- End quote --- \n is LF (LineFeed) (0x0A) \r is CR (Carriage Return) (0x0D) So do not terminate command string how ever. Just LF alone. Cisco/Appendix: ASCII Character Set and Hexadecimal Values https://www.cisco.com/c/en/us/td/docs/ios/12_4/cfg_fund/command/reference/cfnapph.html (I have not any SPD for test this) |
| HendriXML:
I didn't want to create a new thread, but one issue I'm having with this PSU is that, when channel 1 and 2 are disabled in fast succession. The last command does not change the actual status of the channel. Which means it stays ON, no error beeps. If I wait between calls then it's ok. --- Code: ---OUTPut CH1,OFF OUTPut CH2,OFF --- End code --- The strange thing is that the status --- Code: ---SYSTem:STATus? Result: 0x5 --- End code --- Shows that channel 2 is "off", but in reality the button is lighted and I get a voltage readout A wait time of 100 ms has occasional misfunctioning A wait time of 300 ms seems to be OK, but that's not what I call solid interfacing |
| tautech:
--- Quote from: HendriXML on October 27, 2019, 11:09:36 pm ---I didn't want to create a new thread, but one issue I'm having with this PSU is that, when channel 1 and 2 are disabled in fast succession. The last command does not change the actual status of the channel. Which means it stays ON, no error beeps. If I wait between calls then it's ok. --- End quote --- Trying to remember where I've seen mention of a wait between commands....maybe it was from you in some other thread ? The grey matter is letting me down ATM so I might come back with another post or edit. :-\ |
| tautech:
--- Quote from: HendriXML on October 27, 2019, 11:09:36 pm ---I didn't want to create a new thread, but one issue I'm having with this PSU is that, when channel 1 and 2 are disabled in fast succession. The last command does not change the actual status of the channel. Which means it stays ON, no error beeps. If I wait between calls then it's ok. --- Code: ---OUTPut CH1,OFF OUTPut CH2,OFF --- End code --- The strange thing is that the status --- Code: ---SYSTem:STATus? Result: 0x5 --- End code --- Shows that channel 2 is "off", but in reality the button is lighted and I get a voltage readout A wait time of 100 ms has occasional misfunctioning A wait time of 300 ms seems to be OK, but that's not what I call solid interfacing --- End quote --- OK had a quick look at the Quick start guide and there might be a way around this. http://siglentna.com/wp-content/uploads/dlm_uploads/2017/10/SPD3303X_QuickStart_QS0503X-E01B.pdf P35 3.1 Syntax Conventions A vertical bar ( | ) separates parameter choices. For example, {CH1|CH2} in the above command indicates that you can specify a channel. The bar is not sent with the command string. So using an example from the start of that chapter we come up with this: [{CH1|CH2}:]OUTPut, OFF I'm no programmer so this could be wrong but maybe it's worth a try ? Further down on P40 in 8. OUTPut OUTPut {CH1|CH2|CH3},{ON|OFF} One should work as expected. |
| Navigation |
| Message Index |
| Next page |
| Previous page |