You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by DeeJay September 9, 2024
I can see that CLCapture has been available for over 2 years, so I may be misunderstanding how to use it.
Whatever I try, I get a .csv where all rows and all columns (other than the first row of channel names) contain Zero.
Testing with current V5.1 released code.
Tried with basic Pico and the appropriate UF2. Also with a PicoW and both variants of UF2 firmware.
Tried with CLCapture on both RasPiOS (Debian arm64) and Windows10 workstations.
The Pico running the LA firmware is being fed a serial UART message on its Physical pin #15 - LA Channel #14. Running the graphical LA app correctly acquires the input signal. The arguments supplied to CLCcapture are intended to be those that are used to configure the acquisition in ./LogicAnalyzer.
If I disable the serial signal generator so there is no test signal the LA does not start the capture until I enable to generator source, so I am confident that the Trigger data is being applied to the correct pin (Pin 15, Channel 14) on the Pico.
Where supported by the PicoW firmware I have tried both usb-serial and tcp/ip network connections from the workstation to the Pico.
A typical invocation of CLCapture looks like this -
(This isn't urgent for me. I don't HAVE to be able to generate a .csv of the data. This is largely curiosity to compare LogicAnalyzer with the two other Sigrok-based Pico LA solutions I am aware of.)
{edit: added later... }
It seems to be a regression failure. The capture works as expected with the Pico .UF2 and Win10 CLCapture.exe at Release v2.1.1.0 Jan 2023.)
The text was updated successfully, but these errors were encountered:
Discussed in #137
Originally posted by DeeJay September 9, 2024
I can see that CLCapture has been available for over 2 years, so I may be misunderstanding how to use it.
Whatever I try, I get a .csv where all rows and all columns (other than the first row of channel names) contain Zero.
Testing with current V5.1 released code.
Tried with basic Pico and the appropriate UF2. Also with a PicoW and both variants of UF2 firmware.
Tried with CLCapture on both RasPiOS (Debian arm64) and Windows10 workstations.
The Pico running the LA firmware is being fed a serial UART message on its Physical pin #15 - LA Channel #14. Running the graphical LA app correctly acquires the input signal. The arguments supplied to CLCcapture are intended to be those that are used to configure the acquisition in ./LogicAnalyzer.
If I disable the serial signal generator so there is no test signal the LA does not start the capture until I enable to generator source, so I am confident that the Trigger data is being applied to the correct pin (Pin 15, Channel 14) on the Pico.
Where supported by the PicoW firmware I have tried both usb-serial and tcp/ip network connections from the workstation to the Pico.
A typical invocation of CLCapture looks like this -
(This isn't urgent for me. I don't HAVE to be able to generate a .csv of the data. This is largely curiosity to compare LogicAnalyzer with the two other Sigrok-based Pico LA solutions I am aware of.)
{edit: added later... }
It seems to be a regression failure. The capture works as expected with the Pico .UF2 and Win10 CLCapture.exe at Release v2.1.1.0 Jan 2023.)
The text was updated successfully, but these errors were encountered: