The original GUI-freeze symptom appears fixed: during ARB download the UI stayed responsive.
However, the download still failed functionally with: [ERR] ARB download: No SCPI block after WAVEDATA,
Conclusion: threading fix looks good, but the real-device ARB download response parser is still wrong or too strict.
Steps to reproduce
Connect to Instrument
Open ARB and Refresh
Try to download a stored user waveform (e.g. Test_pulse)
Instrument model / firmware
No response
Host environment
No response
Error text / SCPI response / traceback
Integrated terminal shows in V0.2:
ARB download started: USER,Test_pulse ...
[ERR] ARB download: No SCPI block after WAVEDATA,
Checks
I tested this more than once
I checked whether this is already reported
### Affected version
v0.2
### Area
arb
### Severity
high
### What happened?
HW test update on real SDG2042X:
The original GUI-freeze symptom appears fixed: during ARB download the UI stayed responsive.
However, the download still failed functionally with:
`[ERR] ARB download: No SCPI block after WAVEDATA,`
Conclusion: threading fix looks good, but the real-device ARB download response parser is still wrong or too strict.
### Steps to reproduce
1. Connect to Instrument
2. Open ARB and Refresh
3. Try to download a stored user waveform (e.g. Test_pulse)
### Instrument model / firmware
_No response_
### Host environment
_No response_
### Error text / SCPI response / traceback
**Integrated terminal shows in V0.2:**
```
ARB download started: USER,Test_pulse ...
[ERR] ARB download: No SCPI block after WAVEDATA,
```
### Checks
- [x] I tested this more than once
- [x] I checked whether this is already reported
Tested on real SDG2042X after the ARB rework in v0.2.1.
Original problem
In v0.2 the GUI freeze during ARB download was already fixed, but the actual download still failed on the real instrument with:
[ERR] ARB download: No SCPI block after WAVEDATA,
So the remaining problem was not UI responsiveness anymore, but the ARB download response parser being too strict for the real SDG response format.
What was changed in v0.2.1
Reworked the ARB handling in the affected area
ARB download parser now accepts both:
SCPI block format after WAVEDATA,
raw payload directly after WAVEDATA,
Improved parsing of STL? BUILDIN and STL? USER
Built-in ARB selection now uses index-based handling
User ARB selection continues to use name-based handling
Hardware test result
Retested on the real SDG2042X.
Result:
ARB download works
ARB upload works
No freeze observed during the tested transfer path
Original functional failure from Issue #15 could not be reproduced anymore
Conclusion
Issue #15 is considered fixed and hardware-verified in v0.2.1.
Suggested closure note
Closing this issue as fixed in v0.2.1 after successful real-hardware test of both ARB download and ARB upload.
## Issue #15 update
Tested on real SDG2042X after the ARB rework in **v0.2.1**.
### Original problem
In v0.2 the GUI freeze during ARB download was already fixed, but the actual download still failed on the real instrument with:
`[ERR] ARB download: No SCPI block after WAVEDATA,`
So the remaining problem was not UI responsiveness anymore, but the ARB download response parser being too strict for the real SDG response format.
### What was changed in v0.2.1
- Reworked the ARB handling in the affected area
- ARB download parser now accepts both:
- SCPI block format after `WAVEDATA,`
- raw payload directly after `WAVEDATA,`
- Improved parsing of `STL? BUILDIN` and `STL? USER`
- Built-in ARB selection now uses index-based handling
- User ARB selection continues to use name-based handling
### Hardware test result
Retested on the real SDG2042X.
**Result:**
- ARB download works
- ARB upload works
- No freeze observed during the tested transfer path
- Original functional failure from Issue #15 could not be reproduced anymore
### Conclusion
Issue #15 is considered **fixed and hardware-verified** in **v0.2.1**.
### Suggested closure note
Closing this issue as fixed in v0.2.1 after successful real-hardware test of both ARB download and ARB upload.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Affected version
v0.2
Area
arb
Severity
high
What happened?
HW test update on real SDG2042X:
The original GUI-freeze symptom appears fixed: during ARB download the UI stayed responsive.
However, the download still failed functionally with:
[ERR] ARB download: No SCPI block after WAVEDATA,Conclusion: threading fix looks good, but the real-device ARB download response parser is still wrong or too strict.
Steps to reproduce
Instrument model / firmware
No response
Host environment
No response
Error text / SCPI response / traceback
Integrated terminal shows in V0.2:
Checks
Issue #15 update
Tested on real SDG2042X after the ARB rework in v0.2.1.
Original problem
In v0.2 the GUI freeze during ARB download was already fixed, but the actual download still failed on the real instrument with:
[ERR] ARB download: No SCPI block after WAVEDATA,So the remaining problem was not UI responsiveness anymore, but the ARB download response parser being too strict for the real SDG response format.
What was changed in v0.2.1
WAVEDATA,WAVEDATA,STL? BUILDINandSTL? USERHardware test result
Retested on the real SDG2042X.
Result:
Conclusion
Issue #15 is considered fixed and hardware-verified in v0.2.1.
Suggested closure note
Closing this issue as fixed in v0.2.1 after successful real-hardware test of both ARB download and ARB upload.