With the standard installer I cant save sr-files, so I switched to the nightly build as it should work there. But in the nightly build there is no support for pipistrello ols 64M.
Why can't you save .sr files with the standard installer?
I used the pulseview-0.2.0-installer.exe, thats the only one (as I know) which supports pipistrello OLS 64M. With this version it is not possible to save files (bug 451). I dont understand how to use the Bugfix for saving files to v2.0.2 or how to add the driver for OLS 64M to the nightly build :(
To be honest, using an ancient version from 2014 won't really solve matters one way or another. Please download a nightly debug build and install it. Running "pulseview -l 5" then lets you see what's going on. The Pipistrello support was never removed, so if the device isn't working then there are other issues - I'm hoping that the debug output can give us a clue.
Does the actual nightly build contain the support for the 64M version of pipistrello? I can only see "pipistrello ols" instead of "pipistrello ols 64M"
The pipistrello is recognized by pulseview 0.2.0, the latest pulseview and ols. But: just with pulseview 0.2.0 and ols I can capture data. With the latest pulseview I can not receive any data. Other people do also have suc issues. I talked to magnus, he said it is an sigrok issue.
Please provide a log created using "pulseview -l 5" and trying to perform an acquisition. Who is Magnus? What is the "sigrok issue" you're speaking of?
I tried to generate the logfile as you said, but there is no one. I have a windows machine, where is the logfile? not in the folder where pulseview is. magnus is the developer of pipistrello. he ported the logic analyser to his board. i told him that the board will be accepted by pulseview last nightly, but i cant capture data. with pulseview version 0.2.0 i can capture data. this is the sigrok issue. it has nothing to do with pipistrello or his code.
> I tried to generate the logfile as you said, but there is no one. I have a > windows machine, where is the logfile? not in the folder where pulseview is. PV doensn't generate log files, it writes its log output to the console. The standard nightly Windows build doesn't enable the creation of that console, so you'll have to download the nightly Windows debug build as I wrote before. Did you do that? Once you do, you'll see debug output on the text console when running "pulseview -l 5". You can then copy this output to a text file.
Do you have an updated log file (with -l 5 ideally) showing the problem? As far as I'm aware no support for any OLS based devices was ever removed, so it should work fine. If not, we need more information to analyze the problem. The current PulseView nightly installer (Debug version) will give you a log, recent version also have a log window in the Settings -> Logging dialog. And/or you could also use sigrok-cli with "-l 5" to get a log (and check if the problem happens there too).
Closing this bug for now, we don't have sufficient information to be able to figure out if there is a problem at all and/or what it might be. As mentioned above, we're not aware of multiple pipistrello drivers or versions in libsigrok, there's only one. As per build log, the Windows installers for PulseView and sigrok-cli *do* build that driver: - pipistrello-ols................. yes Saving .sr files should work fine with the current installers as well, we're not aware of any issues there. Please feel free to re-open if there's more information such as an "-l 5" log from a debug build, exact steps performed so we can potentially try to reproduce etc.