Any idea why I'm opening the attached .csv on PulseView and is giving me duty of 50%? if you look on the content of the file the duty is 25%, I'm importing on HZ 62500, to match the captured time ... not sure why because if captured it on Saleae with 500kS/s (maybe because it divide the sample for 8 channels.
Why am I want use it on PulseView if I have Saleae? A: it's because I need decode other .csv that are not captured on Saleae, because Saleae don't import .csv
Just in case i rename it to .txt to comply with the rule of the forum
If you export that, then you see that the first channel is always zero and the second channel is 0,1,0,1,0,1. That is also what PulseView shows.
I think PulseView wants data that is captured with a certain fixed sample rate. Perhaps PulseView has also troubles with the floating point number. The file "digital.txt" is just one signal with timing and data.
I don't know PulseView well enough. There is a 't' for timestamp format when importing comma-separated data, but I was not able to make PulseView see the first column as a timestamp.
I read a little more and seems that Pulseview like you said consider constant rate, the first column using t, don't do calculations (I don't know why it exists), because if it assume each line has the same time interval it don't need time ... Seems to be more to keep standards,
I open a bug for the developers they confirmed that, and invited me to fix the code ... but I don't have enough knowledge for that.
