It is hard to criticise PicoScope on the whole, as their products & the company ethos are exceptional & quite unique in this day & age, however if I was to raise a niggle, then it would be this.
The implementation of seemingly obvious features that are kind of basic & necessary within the automotive sector, appear have been missing for a long time & even though the omissions have been raised on numerous occasions, still the gaps remain.
I noticed the other day that duty cycle measurement still does not cover the more common "duty cycle low = on" that we see almost without exception in our testing environment. For sure, it is easy to do the maths & figure that a displayed 75% duty cycle, translates to the 25% that we are seeing via serial data on the scan tool, but really? should this most basic measurement not be made available for us within the software, without the fuss of having to create a maths channel, or mental arithmetic.
It occured to me also that there used to be a nice feature within the long forgotten Pico 5 software, that enabled us to view a measured value in numerical form (like we see on a regular DVOM). This was actually a useful feature in my opinion, as it can be quite difficult sometimes to view & judge the voltage as seen in the regular waveform layout, when viewed through the windscreen from the drivers seat. Currently (no pun honest ) there is the facility to display a measurement in a large font, but this only displays an average which only updates as the screen capture is completed (or between rulers or cycling at rulers, but all options equally miss the point). What we really need is a numerical display which displays a "live" value in real time.
These are two features from my immediate wish list, but I wonder what other users might think? Is there something that niggles you, but you put up with & work around it without a thought?
I remember years ago, having a regular moan about the fact that Pico lagged behind Snap-on scopes, in terms of its ability to graph frequency & plot it live on screen. Snap-on had this covered years in advance & it worked well, yet it took Pico an age to wake up & realise the need. Inverted secondary is another one, but I have said enough.
A lot of these features would be a walk in the park to implement (I think) & I suspect that the only reason we don't have them, is because Pico development, don't think that we really need them. We see this a lot with diag tool developers too. They decide what is good for us, instead of listening to what the guys at the sharp end want.
Like I said from the outset, Pico is a phenomenal company & I have great respect for what they do for us, but hey, I am greedy & I want more!
Politely of course.
That would be a good addition. Indeed most actuators, nowadays are "Ground Side Switched" As a side note, in my experience quite a lot of scan tools get that the wrong way round.that duty cycle measurement still does not cover the more common "duty cycle low = on" that we see almost without exception in our testing environment. For sure, it is easy to do the maths & figure that a displayed 75% duty cycle, translates to the 25% that we are seeing via serial data on the scan tool
Thanks for this - we do spend a lot of time listening to customers and collecting feedback. We make 100s of improvements every year to the software but we also get 1000s of suggestions so can not get them all done.
We do read, discuss and consider all requests. We also try to get the improvements that will help improve the product for the biggest number of people done first, but at times have also worked on features essential to small groups of user - for example making sure older products work on the latest operating systems.
At the moment we are working on two areas, improvements to the user interface (controls) and measurements. It will be a while before you see these improvements but on the other hand now is a great time to make suggestions on these areas. Certainly the negative duty cycle measurement will be addressed in this work but one of the reasons this has not been done already is that there is a work around (invert the channel first) or as you say do some mental arithmetic (sorry, no one likes maths). I may be mistaken but I think some time ago we had to choose between 2 different improvements here - giving the ability to graph changing duty cycle or adding in the inverted measurement. At the time the ability to graph was deemed to be more useful to more customers but I accept not everyone will agree with that choice.
To comment on a few of the other points, we do address inverted secondary: there is a guided test to set that up but if you have other ideas on how to make that easier please let me know.
A meter mode is a common request and I agree using large fonts in measurements is not a 100% solution. I would add however that in the old PicoScope 5 the meter mode did do the same thing you described - grab a waveform then display the average of it. That's the way a meter works to avoid the values jumping around so much you can not read it.
Please keep the feedback coming but also please bear with us if your request does not get to the top of the list. One way you can help is spread the word that we are recruiting more software engineers so if you have any friends / relatives who might want to work for a (to use your nice words) a phenomenal company then send them our way (or point them at https://jobs.picotech.com/).
Just reading this one through regarding negative duty cycle.
The link below will assist with the creation of such a math channel with regards to negative duty measurements.
This will help whilst the suggestions made are discussed and implemented according
I have to ask myself though, can it really be so hard, to introduce a proper measurement for ground switch duty cycle?
Surely we shouldn't have to create a maths channel though, to allow us to use a function that needs to be there by default. It feels a little bit like we are having to fix Pico software, so that it is fit for purpose. (maybe a bit strong perhaps, but a valid point nonetheless)
I wouldn't be happy if I bought a BMW & I was told that I couldn't use it on a motorway, unless I created a simple code, that allowed the feature to work.
Come on Pico (please )
Rest assured Dave, all new feature requests are considered and often implemented.
I too would like to see a simpler approach to graphing duty and I am sure it will happen.
In the meantime I have created 4 x Duty Math channels below which can be imported into PicoScope so removing the need for creation.
Please download and save the above files to a location on your PC.
Open PicoScope and click on Tools > Math Channels > Import
Select the location on your PC where you have downloaded the above files
Click on the file required and click on Open
The Duty Math Channel will now be loaded into the Math Channel Library where it will remain for selection when required.
This will now remove the need for math channel creation and provide the negative duty graphing feature when required (Four Clicks away)
Select Tools > Math Channels > tick the box adjacent to the Duty Math Channel you require (in the Library section) followed by OK
A brief video of the process can be viewed below
Once again, thank you for the feedback from all, take care…….Steve
I've tripped over this a couple of times, but can't see anyone else mention it, so never shy , I have another feature request ... well tweak ...
On the Rotational Ruler, you currently only support 10 cylinders ... and guess what ... yep, we have lots of 12's (and the odd 16 for good measure). Please can you add a bigger value (maybe go so far as 36 or 48 to allow for other uses beyond where it can be applied today?
On labels, any chance of allowing custom text , so instead of 0,90,270,360 or whatever, allow a comma or semi colon separated list of labels so the user can add firing order, or events specific to 1 cylinder or coils or whatever ... ?
The numeric custom selection, right now, it uses the last used units (720 or 200) with no explanation , why not allow 2 boxes - 1 for the numeral to be divided ie the Total (and data entry check the numeric value) and the other for units (again 4-5chrs), that way you can break down partial events like 270deg ...
just a further request , as been playing with toothed wheels, and also after your (Steve's) play with ABS sensors ...
Is it possible, based on my previous request, to increase the number of graduations for the rotational ruler, so that for larger number graduations a "tradition ruler" style scale is used. This would help quickly identify the number of teeth visually when using it to help count teeth offsets, total teeth and comparing 2 sensors outputs, and if you also added the ability to:
1. move the ruler (not the start or finish - the entire ruler) without disrupting the scale (where the time base remains constant this has lots of applications) - so 2 sensors can be compared within the same buffer/range of buffers.
2. Move on the Y axis the position of the legend/graduation points (to align with the peaks or baselines of waveforms)