Test and Measurement Forum

Hi

The serial decoding is great. It was first introduced in a beta release over a year ago, and has improved in many steps since then.

The decoding (both UART and SPI) is now fast and reliable, except for the last char in each sweep. For SPI, the last char is often decoded to 'unknown'. I first got a shock, because I thought, there was somthing wrong with my hardware, but then I noticed, that it was always the last char of the sweep, and therefore, I could concluded that it was not my hardware, that had a problem.

A part from the bug above, there are a two things that could be improved:

(1) The 'signal idle state' setting on UART decoding is default set to low. This should be changed to high, this is much more common.

(2) The 'bit order' setting on SPI decoding is default set to LSB first. This should be MSB first, this is much more common.

Alternatively, save the decoding settings with the startup settings.


Having the SPI/UART settings in a extra window behind, helps to keep the interface clean looking, but these settings are very important and when they are out of sight, they are out of mind.

I will check this out for you but need to know which version of of PicoScope beta you are using.

It is the latest version, 6.5.80.5.

The fustration that made me write the first post, is that I work on one project for 3-4 months. And therefore, it is irritating to have to go into *hidden-menus* to re-change settings every time PS is starting.

Please can you try the beta version from http://labs.picotech.com/ which can be installed alongside a release version without interaction.

The startup settings are stored correctly although I haven't been able to verify the decoding issue.

I have testet with beta 6.6.10.1.

The SPI/UART settings are saved correctly with the startup settings.

But the default settings for SPI and UART are still reset to
(1) LSB first (SPI)
and
(2) idle low (UART)

and 99% of users will need
(1) MSB first (SPI)
(2) idle high (UART)

This is easy to verify that PS has these "unusual" default settings, just open the decoding, you don't need to have hardware that produces the actual signals.
It is a very quick fix to solve in programming pico scope.


by the way, now that I was testing the new beta version... why is the ruler not fixed 100% it is improved but not fixed: When you zoom using the mouse, the scale is not rounded to nice values. Please see the attachment, the scale should have been 20, 21,...,30 this is easier to read and can be used in documentation.

Look at Matlab to see an example of how to make the scale zoom.

I will pass your comments to the development team.

Thanks

At the moment I work alot with both UART and SPI signals.

Using the current BETA version.

There are two more things that should be corrected:

1) When there is a lot of data, then it is impossible to stop PS6. I have to take the probe off the test circuit. Otherwise PS6 is too buzy to check that the STOP button has been pressed. (FIX THIS SIMPLE BUG!! )

2) Sometimes (sorrry I don't know how to reproduce this), the decoded serial SPI data is only shown partially on the screen with the waveform. The window shows the decoded data correctly. though..

Can you confirm the exact beta version you are using and I can test the issue here and pass the information on to the development team.

Help->About and cut and paste all the info from the bottom box will all the information we need. Additionally selecting File->SaveCurrentWaveform and selecting pssettings file type will enable us to run Picoscope with your specific setup

Hi,

It is so long time since I reported the errors, that I have updated SP6 since... and to my delight seen that these errors have been corrected in

PicoScope® 6 - PC Oscilloscope software version: 6.6.12.4
Copyright © 1995-2011, Pico Technology Ltd

Model: PicoScope 5203
Serial Number: VJY86/42
USB Version: 2,0
Calibration Date: 27. marts 2009
Hardware Version: 1
Driver Version: 1.4.2.147


... but PS6 still has odd default settings for UART and SPI....

I have reported your final point to the development team

OK - so I failed to read the fine print!

I purchased the 3206B specifically to use the serial decode function.

My serial data rate is 250kB - this is shown under autobaud when I sample data, but is not available in the pull down list, and I cannot see sensible decode data.

250kB is extremely common in the Entertainment industry as the DMX512 protocol used for theatrical lighting runs at that rate.

Please consider adding decode at this baud rate

It would also help to be able to set when (after the trigger condition has been satisifed), when the serial data analyser is activated.

Can you submit a psdata file to support@picotech.com showing a sample data trace and we can take a look at this for you.

Martyn

I have sent you some files - but they may be too big for your email system. Let me know how you get on. I am flying back to the UK today, so will be in the office Thursday.

Thanks for those. I will follow up through our helpdesk system and update here at a later date.