Forum Replies Created
- AuthorPosts
twoodParticipanttwood January 28, 2021 at 11:18 am in reply to: Spike 3.5.13 screenshots and annotations //php bbp_reply_id(); ?>
Hi Andrew
I needed to persist more – thought I’d tried all of the permutations but not that one. For me, this one works:
SYST:IMAG:SAV “C:\GDDS\SpikeImages\SpikeImg.PNG”but these do not:
SYST:IMAG:SAV “C:\GDDS\SpikeImages\SpikeImg”
SYST:IMAG:SAV “C:\GDDS\Mission PC\SpikeImages\SpikeImg.PNG”Seems it needs the explicit file extension and no spaces in folder names. I’d also replaced the “\” with “/” as per the Spike manual though I’m not sure if it matters…
Thanks for offering the status data via SCPI. My device is outdoors and built into an enclosure so quite difficult to check if it’s still OK.
twoodParticipanttwood January 28, 2021 at 10:02 am in reply to: Spike 3.5.13 screenshots and annotations //php bbp_reply_id(); ?>
Hi Andrew
Thanks for the prompt reply and the tip about older versions.
I’m using SCPI to remote control. I couldn’t get “SYST:IMAG:SAV xxx” to work so I’m using “SYST:IMAG:SAV:QUIC” instead. I’m not wild about QUIC because I can’t specify the folder to use but it seems to consistently use the last manual save folder, which is good enough.
I’m fine with the metadata and I think having it somewhere in the file would be great, I just want some control over its appearance.
If I could, I’d also like device temperature and voltage via SCPI. I gave up on trying to get this via calls to sa_api.dll intermingled with Spike invocations (Spike occasionally fails to find the device even though I’ve called saCloseDevice() a few seconds beforehand).
Terry
- AuthorPosts