UART, I2C and SPI for sure! Much more useful than CAN in my opinion. Glad to see the Beta has I2C in it now. One more suggestion on the UART, is if you could make it RS485 compatible, you would have a real winner.
I am holding back on the deep memory 4 channel version until UART is supported. Once it is, you have another sale on your hands.
Thanks for an already great product. My Tek scopes are collecting more and more dust around here.
i agree with all of you!
For individual use it would be perfect if picotech offers a plugin system, like someone else already suggested. Then everybody can desing individual needed decoders. In my case for example DMX. I guess because of less users interested in DMX, picotech won't implement DMX decoding next time...
Because of this it would be nice if picotech would think about such a solution that customers can help themselves...
Thank you for your suggestion, I have forwarded your idea to the relevant department. Obviously no promises can be made, however every enquiry will be looked into.
I think. *Most* customers will probably just need UART or SPI coding. A few months ago, you made a questionnaire about this with all your customers, so you should know by the numbers, what the customers want.
Picotech, make it easy for yourself, and for the customers, just add UART/SPI like you added CAN. Several of the previous comments on this thread also suggest this.
Here comes one more vote for additional serial protocols: PLEASE picoscope add UART and SPI !!!!
I am about to purchase picoscopes for my company, I am still hesitating due to lack of functionality regarding missing protocols, but I hope and I am confident that you guys manage to add this in the near future!
Thanks for the UART and SPI decoding! They both works and they are a great asset during product development. I really think they should pay back to you in terms of new scopes sold.
There are a few points for improvement.
1. The UART gets confused if the chars are comming without time spacing. This is a problem.
2. The excel export (only tried SPI) a data sheet. This data sheet has too much "looking pretty" formatting. The time should not be exported with "1.2us" or "3.5ns". The time unit should be in a separate cell.
I already have a new project that will need both UART and SPI. Great gear.
The same problem of UART getting confused with chars without spacing has also been reported by maxsca and elman on another thread. maxsca has included psdata file.
I am working on another aspect of my project at the moment, so I can not make a psdata file with UART problems.
Hi,
If you haven't already got a sample, I've got a screen shot & psdata for the UART back to back timing issue. ('1', '2', '3' sent)
It looks like when you specify 8n1 the UART decoder is actaully waiting for all 10 bits (start, 8 data, stop) and so missing the falling edge of the next start bit. All it needs to do is wait for 9.5 bits like a real UART would.