Author Topic: Open Source Oscilloscope, can it be done?  (Read 70099 times)

0 Members and 1 Guest are viewing this topic.

Offline BradC

  • Super Contributor
  • ***
  • Posts: 2104
  • Country: au
Re: Open Source Oscilloscope, can it be done?
« Reply #100 on: October 31, 2017, 08:25:32 am »
More and more laptops are supporting eGPU nowadays. It's even possible to cobble together your own eGPU from under $20 in parts plus the GPU itself.

Those who can afford such laptop and external PCIe cabinet most likely can afford and will be willing to get just proper standalone scope.

Thunderbolt is just PCIe and I've had machines with those ports for 6ish years now. Laptop and Deskop, Mac & PC.
 
The following users thanked this post: tooki

Offline erikg

  • Contributor
  • Posts: 25
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #101 on: October 31, 2017, 04:21:36 pm »
Quote
BTW you did "skip" most of my arguments except one, which is not that important actually.

Okay.  I'll go back and reply a bit more completely.

 
Quote
I am not ready to literally waste all the PC resources and performance just because you cannot comprehend that - if you have FPGA then best way is to use it, place RAM and processing where it supposed to be - at/in the FPGA :)

I actually comprehend this pretty well, and I think this is just a point where we have differing opinions.  Certainly FPGAs are excellent solutions and suitable for this task, but I think you're imagining the "right" way to design an Oscilloscope and I'm imagining an "unconventional" design that has other benefits.

Really, the differences in opinion in this thread and between us are based on different assumptions about what an open source Oscilloscope should be.  I can see four different points of view represented:

  • People who believe that an open source 'scope is only worth doing if it surpasses in price or performance what's available commercially, specifically the various Chinese import scopes.  Certainly it's hard to come up with a design that beats what already exists in both areas.
  • People who believe that an open source 'scope should be designed to cover the niche roles of a cheap/simple/portable/accessory scope, so it can be (for example) left in a field location to trigger on some very rare event, or used for tasks requiring dedication of a scope where someone would not want to tie up their main or preferred scope for a long time period.
  • People who believe that an open source scope is worth doing simply because of the benefits of having an open hardware design available to everyone.  Open Hardware is a concept that is in its infancy compared to open source software, but it's easy to see what benefits it could have if an open source scope project "takes off".  The most well known open source software project in the world has gone from being an academic curiosity to being the most used operating system in the world, period.  This is an extreme example, but if anything remotely similar to this were to happen for open hardware, the benefits would be obvious.
  • People who value the idea of designing an open hardware 'scope as a challenge for its own sake.

I tend to identify with the third point of view.  I believe that moving the main functionality of the scope into software would open the potential pool of developers for the project from the few that understand hardware and FPGAs enough to contribute to anyone with some device level programming experience in Linux.  The more people who are able to contribute, the better the project will become.  Certainly there are altruistic people all over the world, but most people with the skills to design or program something like an Oscilloscope choose their projects the same way most of the people posting in this thread do - based on how useful it would be for them personally.

So what I'm imagining isn't a traditional design for this reason.  Instead of a dedicated FPGA based scope which requires specialized hardware design knowledge I think it is possible to design what amounts to a digitizer card and add software to achieve the functions of an oscilloscope. 

If such a thing can be done within the constraints for a DIY project (cost, manufacturability) for a reasonable price and without design compromises turning the project into a toy rather than a tool, that is a much better route to go for an open hardware project because the success of open software and hardware projects depend heavily on popularity.  Just like a book, it will have little impact on people who can't read the language in which it is written, so it makes sense to design an open hardware project to appeal to the widest audience possible.  Putting the main functions of such a tool in software means that not only can it attract more developers for oscilloscope functionality, but since it can be reprogrammed for many more uses it gains an even wider audience.  It could be a high speed digitizer for software defined radio, or a processor for sonar data, or many other things.

If it is not technically and economically possible now, I think it will be in the next few years as technology advances.  It's even possible to see the day when an external peripheral with a wireless connection will perform all the functions of an oscilloscope, voltmeter, logic analyzer, vector network analyzer, spectrum analyzer, etc.  Essentially all these systems in their modern versions read data and provide it to a processor, and software does the rest.  Eventually, the hardware will merge into a single device class below a certain performance level simply because it's cheaper to make it that way.  All the various functions will be in software.  So I think an open hardware project could anticipate this.




 
The following users thanked this post: cdev

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Open Source Oscilloscope, can it be done?
« Reply #102 on: October 31, 2017, 07:17:29 pm »
Thank you for providing deep insight into your reasoning :) I appreciate that.

I agree that PCIe sampler architecture you propose is indeed possible. On the other hand you have only one single strong argument: community that knows PC-programming languages better than VHDL/Verilog. - True. But is it really showstopper?

Hi-performance 1Gsps sampler scope is not a kid's toy. Someone shall implement PCIe bus PHY with all the bells and whistles... and not only that. In my opinion/experience PCIe is not that easy task at all. Not to mention PCIe-capable FPGA price. Sample processing and storage is much more simpler task than PCIe PHY. Obviously couple of FPGA guru's needed as core of the project, but I believe - either it is done elegant way or there will be not enough enthusiasts ready to invest their time.

>I believe that moving the main functionality of the scope into software would open the potential pool of developers for the project from the few that understand hardware and FPGAs enough to contribute to anyone with some device level programming experience in Linux.

Well... huge pool of linux programmers is not enough. They shall be interested in the final product too.

> The more people who are able to contribute, the better the project will become.

The less people who could actually use product (laptop/minipc owners and those who do not like PC on the desk facing backwards) - the less support it will get.

> Certainly there are altruistic people all over the world, but most people with the skills to design or program something like an Oscilloscope choose their projects the same way most of the people posting in this thread do - based on how useful it would be for them personally.

Exactly. Personally I vote against PCIe sampler and do not participate. Why? - I have two computers, miniPC and desktop tower PC. None is suitable for PCIe sampler. MiniPC does not have PCIe slots nor Thunderbolt, but dekstop tower PC is standing on the floor too far away for scope leads to reach my table. I am not going to put that huge box on the table facing its back to me just because there is/could_be open source scope PCIe adapter which costs 2x my standalone 1Gsps scope, Sorry.
« Last Edit: October 31, 2017, 07:25:46 pm by ogden »
 

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Open Source Oscilloscope, can it be done?
« Reply #103 on: October 31, 2017, 10:31:37 pm »
Reality check: does anyone besides erikg want open source PC-based scope which costs more than "made in china" standalone? Please share your opinion.
« Last Edit: October 31, 2017, 10:35:13 pm by ogden »
 

Offline rhb

  • Super Contributor
  • ***
  • Posts: 3476
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #104 on: October 31, 2017, 11:06:54 pm »
QEX came today with an article about a stand alone 100 MHz BW direct sampling SDR.  It uses a Zynq based Zedboard running Linux on a dual core ARM A9 and an AD 9467 eval board.  It takes a monitor, keyboard and mouse.

The web site is panoradio-sdr.de

This is everything for a single channel open source scope except the scope code. And it's all COTS.

AD9467 eval board $406 (Digikey)
Zedboard $495  (Digikey)

So approximately 1/2 a Rigol DS1102E for ~$1000.  However, it *is* 16 bit rather than 8.  So it's more Keysight and friends territory.

Using a desktop PC only makes things harder and more expensive.  There is no affordable way to get the BW required.

The real virtue of an open source scope is being able to fix bugs and add features.
 
The following users thanked this post: cdev

Offline rhb

  • Super Contributor
  • ***
  • Posts: 3476
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #105 on: October 31, 2017, 11:04:29 pm »
QEX came today with an article about a stand alone 100 MHz BW direct sampling SDR.  It uses a Zynq based Zedboard running Linux on a dual core ARM A9 and an AD 9467 eval board.  It takes a monitor, keyboard and mouse.

The web site is panoradio-sdr.de

This is everything for a single channel open source scope except the scope code. And it's all COTS.

AD9467 eval board $406 (Digikey)
Zedboard $495  (Digikey)

So approximately 1/2 a Rigol DS1102E for ~$1000.  However, it *is* 16 bit rather than 8.  So it's more Keysight and friends territory.

Using a desktop PC only makes things harder and more expensive.  There is no affordable way to get the BW required.

The real virtue of an open source scope is being able to fix bugs and add features.
 

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Open Source Oscilloscope, can it be done?
« Reply #106 on: November 01, 2017, 12:02:05 am »
This is everything for a single channel open source scope except the scope code. And it's all COTS.

AD9467 eval board $406 (Digikey)
Zedboard $495  (Digikey)

I rather have 8-bit 4 channel 1mV/div to 10V/div 50MHz 1GSPS scope for 400$ than 1-channel 500MSPS 16bit sampler without PGA and who knows when there will be scope software - for 1000$. Or am I missing something here?
 

Offline rhb

  • Super Contributor
  • ***
  • Posts: 3476
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #107 on: November 01, 2017, 12:48:36 am »
I'd like to suggest looking at this thread:

https://www.eevblog.com/forum/testgear/agilent-54835a-scope-%284-channel-1ghz-4gss%29-repair-uphack/msg1251605/#msg1251605

which describes an early HP implementation of a PC based scope in considerable detail.

There's less to a scope than an SDR, but I don't particularly care either way.  I've got an Instek MSO in shipment to augment my DS1102E.  If someone makes an open source scope that is credible I'll probably get one and write things like VNA routines for it.  But I'm not going to design the hardware.  At least not any time soon.

BTW The Zedboard includes a Xilinx FPGA.  The ARM is just to run the user interface and other minor tasks.
 

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Open Source Oscilloscope, can it be done?
« Reply #108 on: November 01, 2017, 11:40:04 am »
If someone makes an open source scope that is credible I'll probably get one and write things like VNA routines for it.

VNA is closer to SDR than scope. Either it is low cost (more or less toy-) VNA add-on board with PC software for 4-channel <= 100MHz SCPI-capable scopes or it shall be built using SDR approach. How about 25 .. 1500 MHz VNA built out of four RTL2832U+R820T USB tuner dongles (8$ each, delivered)? Board with USB hub, programmable synth, couplers and clock fanout buffers for tuners needed and obviously PC software. Could be blockbuster in result. Tuners shall be freq/phase synced using following approach: https://www.rtl-sdr.com/a-multi-channel-coherent-rtl-sdr-product-for-passive-radardirection-finding-and-more/
 

Offline rhb

  • Super Contributor
  • ***
  • Posts: 3476
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #109 on: November 01, 2017, 02:21:58 pm »
[
VNA is closer to SDR than scope. Either it is low cost (more or less toy-) VNA add-on board with PC software for 4-channel <= 100MHz SCPI-capable scopes or it shall be built using SDR approach. How about 25 .. 1500 MHz VNA built out of four RTL2832U+R820T USB tuner dongles (8$ each, delivered)?


If you're doing HF design, a 100-200 MHz scope will work just fine.  Though, like the RTL-SDR it suffers from the 8 bit limitation.  As for using an SDR, that's the main reason I bought an SDRplay RSP2 and a LimeSDR.  The RTL-SDR is OK for VHF, but adding 4 downconverters makes it expensive for HF.  Buying a VNWA 3E is probably a cheaper option once you take into account directional couplers and the other bits an RTL-SDR setup would need.  But the RTL-SDR approach would be fine for someone using the sub GHz ISM bands.

There are a slew of VNA projects spawned by the cheap RF chipsets.
 

Offline erikg

  • Contributor
  • Posts: 25
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #110 on: November 01, 2017, 03:35:34 pm »
Quote
On the other hand you have only one single strong argument: community that knows PC-programming languages better than VHDL/Verilog. - True. But is it really showstopper?

I don't view it as a "showstopper" exactly.  Simply put, the more people an open source project appeals to the more likely it is to be successful.  You can argue that a software defined scope would be less attractive to EE types like yourself, and that could certainly be true, but the numbers are what matters.  The head count of people who know how to program in C or Python is a much bigger number than the head count people who know how to program an FPGA, so if only 1 in 1000 (0.01%) of C/Python people are interested, that's still far more individuals than if 1 in 20 FPGA programmers (5%) are interested.

Quote
Hi-performance 1Gsps sampler scope is not a kid's toy. Someone shall implement PCIe bus PHY with all the bells and whistles... and not only that. In my opinion/experience PCIe is not that easy task at all. Not to mention PCIe-capable FPGA price. Sample processing and storage is much more simpler task than PCIe PHY.

Probably not as expensive or hard as you think.  When I think of hardware to implement a PCIe capable scope, I'm thinking of something like an Artix-7, so between about $100-$200 US.  Xilinx has a PCIe "integrated block" supported on this series, so it's possible to just use that with supporting components for PCIe... basically a shrink wrapped solution.  An even quicker alternative would be to use an FPGA module like a Mars: https://www.enclustra.com/en/products/fpga-modules/mars-mx2/

... in which case only a carrier board needs to be designed with the supporting chips like the ADC and an SODIMM socket for the module.  Single unit price on these is more like $250-$300 US, so it's more expensive than a complete DIY, but it's also easier.

Probably the best way to go for a digitizing card is to specify hardware capabilities and interface methods for the software and permit multiple hardware implementations anyway :)  Kind of the path that Sigrok takes, being hardware agnostic.  That way is even better for a software defined project, because you can completely toss the previous generation of hardware if some great new technology comes out and keep most of your feature set.

Quote
Well... huge pool of linux programmers is not enough. They shall be interested in the final product too.

Yes, but if the project is defined mostly in software then the card will attract developers for applications other than oscilloscopes.

Quote
The less people who could actually use product (laptop/minipc owners and those who do not like PC on the desk facing backwards) - the less support it will get.

That's true if you assume that the card wouldn't be usable in a laptop or mini PC... if the card is low profile it probably would work in mini PCs, and even if it's not, then a solution like what gets used for GPU crypto coin mining could be used - essentially a flex based extension for the PCIe slot that runs to an add-on enclosure for the card, like this:

http://www.overclock.net/t/1427731/pci-express-extender-cables-benchmarked

As far as the PC facing backwards, it's not all that hard to get extra long probe cables (this is the solution HP used for their mainframe based Oscilloscopes) or a front facing breakout box could be designed to provide front BNC connectors.  It's extra cost, of course. 

Thinking about it, though, it probably makes sense instead of the above to use an external PCIe interface like Thunderbolt-3... it already exists on many systems, has plenty of speed, and if you use USB-C over TB3 you even get power delivery over the cable.  The scope digitizer "Card" would be a module in a box connected via thunderbolt to the PC.  One small box with BNC connectors and one cable to the PC up to 2 meters long.


Quote
None is suitable for PCIe sampler. MiniPC does not have PCIe slots nor Thunderbolt, but dekstop tower PC is standing on the floor too far away for scope leads to reach my table. I am not going to put that huge box on the table facing its back to me just because there is/could_be open source scope PCIe adapter which costs 2x my standalone 1Gsps scope, Sorry.


So you'd be unwilling to buy a $50 US PCIe card to put in your desktop tower PC to allow use of an external digitizer in a box on your table to which you attach leads, costing something like $400-$500?   Maybe you'd need to wait until the price comes down? :)



Quote
Reality check: does anyone besides erikg want open source PC-based scope which costs more than "made in china" standalone? Please share your opinion.

Opinion gathering is ok, but note that we're not really voting on something here.  I'm just writing this to learn about peoples' opinions and thoughts on this subject.  If I kick off a development project for a digitizer like this, you can be sure you'll see an announcement from me.  Right now I'm really only capable of writing the software for it, though.  Still learning hardware.

Thanks!

 

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Open Source Oscilloscope, can it be done?
« Reply #111 on: November 01, 2017, 04:37:50 pm »
So you'd be unwilling to buy a $50 US PCIe card to put in your desktop tower PC to allow use of an external digitizer in a box on your table to which you attach leads, costing something like $400-$500?   Maybe you'd need to wait until the price comes down? :)

I do not need such. After all I have standalone scope already. What I could consider to get: 400-500$ 200MHz 1Gsps USB/Ethernet mixed signal scope with deep & segmented memory. Ideally with optional 50ohm RF input channel - spectrum analyzer / RF-sampler. - Customizabe open source version of Tek MDO3000 :)

[edit] I'm afraid that you overestimate how much job is done in the FPGA of USB scope versus PCIe sampler scope. FPGA just do sampling, trigger, buffer management and interpolation (only samples going to be shown on display). All the measurements of resulting waveform is done by CPU in both cases anyway. Very good example is Infiniium early revision which has very dumb sampler with analog(?) trigger circuit, comparably slow CPU and slow bus between sampler and CPU, yet still it does lot of various signal measurements - obviously using CPU.

I'd like to suggest looking at this thread:

https://www.eevblog.com/forum/testgear/agilent-54835a-scope-%284-channel-1ghz-4gss%29-repair-uphack/msg1251605/#msg1251605

which describes an early HP implementation of a PC based scope in considerable detail.
« Last Edit: November 01, 2017, 05:40:50 pm by ogden »
 

Offline erikg

  • Contributor
  • Posts: 25
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #112 on: November 01, 2017, 06:51:36 pm »
Quote
Very good example is Infiniium early revision which has very dumb sampler with analog(?) trigger circuit, comparably slow CPU and slow bus between sampler and CPU, yet still it does lot of various signal measurements - obviously using CPU.

That thread is an interesting read, but it's not really comparable to what we're talking about.  That's partly because that hardware is so incredibly old, but the important difference is the location of the sample buffer.  Essentially those Infinium scopes are PCs in the same box as a scope board, not a PC with a scope card.  If you took the internals of a stand alone DSO and found a way to interface them to a PC so it could be the UI, those scopes are what you would have.

By way of contrast, I've been talking about using modern components and a fast bus to add high speed data acquisition to a PC in such a way that it can be programmed to function as an Oscilloscope, with the sample buffer in main memory.  Ideally, the only components on the card would be those needed to acquire the data and get it into main memory.


 

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Open Source Oscilloscope, can it be done?
« Reply #113 on: November 01, 2017, 07:37:11 pm »
> That thread is an interesting read, but it's not really comparable to what we're talking about.

It is. - As an example that hi-end 5GSPS scope do not need direct to RAM sampling to do it's job very well. But whatever. You don't listen anyway so I am wrapping up this conversation.

> I've been talking about using modern components and a fast bus to add high speed data acquisition to a PC in such a way that it can be programmed to function as an Oscilloscope

I noticed. You have strong opinion about how to build hi-speed electronics but seems, do not have any experience in the field. So be it. Good luck building you sampler!
 

Offline erikg

  • Contributor
  • Posts: 25
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #114 on: November 01, 2017, 09:46:59 pm »
Well, there's a big difference between not listening and not agreeing, and we just don't agree.

I don't have any intention at this point of building this thing, as I've said repeatedly the whole thing is just a design exercise for me.

Who knows though, maybe sometime I will.

 

Offline haastyle

  • Contributor
  • Posts: 23
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #115 on: November 14, 2017, 06:36:21 pm »
FYI, the Haasoscope project is now live!
https://www.crowdsupply.com/andy-haas/haasoscope
I've really put some effort into it, and the specs have improved significantly.
Pick up a few!
 

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Open Source Oscilloscope, can it be done?
« Reply #116 on: November 14, 2017, 10:36:13 pm »
FYI, the Haasoscope project is now live!
https://www.crowdsupply.com/andy-haas/haasoscope

Congrats and good luck!  :clap:
Hopefully you will meet your goal.

Quote
I've really put some effort into it, and the specs have improved significantly.

You also released new revision pretty fast. Respect! Noticed that you introduced AC/DC switching and 50 ohm input. -Very good. Thou I still believe that this is kind of "tinkerscope", due to external interface which I also consider as slow (for scope). In my humble opinion your product can become much more desirable if you put Cypress FX2LP or some USB-enabled ARM uC on-board - to achieve higher update speeds (20Hz is so slooooow). Then your product would be single-piece instrument which could have enclosure some day too. Just my 2 cents :)

I would like to see how test signals look not only on your scope but compared to at least one worthy competitor from Comparison Table, on both 5V and 500mV ranges. Especially want to see claimed bandwidth. Would be nice to see noise floor measurements - existing waveforms looks kinda noisy.
 

Offline haastyle

  • Contributor
  • Posts: 23
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #117 on: November 14, 2017, 11:32:22 pm »
Hi,
Thanks for the support!
20 Hz looks pretty fast on the screen - that's 20 _frames_ per second. It's hard to see more than that! However, for higher-speed data collection, I do offer a plug on FT232H board, which is supported by the firmware/software, and offers ~30x more bandwidth for the serial connection, and up to full USB2 speed (480MB/s) if someone writes a C++ interface using the FTDI drivers (wouldn't be too hard to do something simple).
I invested time in reducing noise last month - it's much better now - just about 1-2 mV in either range! I've moved to a 4-layer board with a full ground plane, and better dc offset control mechanism (DAC vs. PWM).
The bandwidth is as claimed. I've tested with an Agilent 80 MHz signal generator and see almost no degradation until 60 MHz. The 80 MHz sin wave is still very viewable in the 250 MS/s (2 channel) mode. (I've also implemented sinx/x filtering (in python), which cleans it up nicely!)
Best, Andy.
 

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Open Source Oscilloscope, can it be done?
« Reply #118 on: November 15, 2017, 01:07:16 am »
Thanks for the support!

You are welcome :)

Quote
20 Hz looks pretty fast on the screen - that's 20 _frames_ per second. It's hard to see more than that!

Well.. Even for movies 20Hz is not enough :) When you are trying to catch various irregularities of the signal - then you need to get on the screen as many waveforms per second as possible, preferably intensity-graded way. The more - the better. You want to minimize blind time of the scope to maximize your chances of seeing something that does not happen too often.

Further reading: https://cdn.rohde-schwarz.com/pws/dl_downloads/dl_application/application_notes/1er02/1ER02_1e.pdf
EEVblog discussion: https://www.eevblog.com/forum/testgear/some-important-points-to-remember-when-evaluating-waveform-update-rates/msg205797/#msg205797
There also was some oscilloscope review by Dave where he was measuring, comparing and commenting update rate of some scopes. Unfortunately I struggle to find it at the moment.

Quote
However, for higher-speed data collection, I do offer a plug on FT232H board, which is supported by the firmware/software, and offers ~30x more bandwidth for the serial connection, and up to full USB2 speed (480MB/s)

Good news then! Why don't you put it on the board? After all it is "just" ~3.1$/piece @100qty.

Quote
I invested time in reducing noise last month - it's much better now - just about 1-2 mV in either range!

Seems like 1..2 counts of ADC which is completely OK for any digital scope. I just wondered why this particular screen seems so "noisy":
https://www.crowdsupply.com/img/efc5/8chan_png_project-body.jpg
One more reason to show "side by side" comparison of the same test signal to some competitor scope, like Rigol DS1104Z.

Quote
The bandwidth is as claimed. I've tested with an Agilent 80 MHz signal generator and see almost no degradation until 60 MHz. The 80 MHz sin wave is still very viewable in the 250 MS/s (2 channel) mode.

Good. Then you shall demonstrate it too - so potential buyers see true performance of this thing.
 

Offline ez24

  • Super Contributor
  • ***
  • Posts: 3082
  • Country: us
  • L.D.A.
YouTube and Website Electronic Resources ------>  https://www.eevblog.com/forum/other-blog-specific/a/msg1341166/#msg1341166
 

Offline haastyle

  • Contributor
  • Posts: 23
  • Country: us
Re: Open Source Oscilloscope, can it be done?
« Reply #120 on: November 15, 2017, 01:31:22 am »
Ah, I agree that "blurry super fast update" mode is cool. I'll have to work on that. I think it's fair to say that's rarely available for $99 though.
With the USB2 output it should be doable.

Yes, some of those screenshots are with an older, noisy, prototype. Here is a more recent pic from yesterday:
https://www.dropbox.com/s/a3ox94f5zdex4d9/low%20noise%20sin.png?dl=0

As for bandwidth, I do have that shot in the video of scrolling up to 40 MHz in the FFT plot. You can see the amplitude is unchanged up to 40 MHz at least. It's also here:
https://www.dropbox.com/s/nmfw128er7p4hfu/scope%20fft.mp4?dl=0

Get one and test it out for me! OR maybe Dave can review?!  :o :-[

 

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Open Source Oscilloscope, can it be done?
« Reply #121 on: November 15, 2017, 02:09:15 am »
Ah, I agree that "blurry super fast update" mode is cool. I'll have to work on that. I think it's fair to say that's rarely available for $99 though.

Indeed. On the other hand, hopefully you are not building "just yet another low cost scope", right? Having some unique feature will add to the value of your product.

Quote
As for bandwidth, I do have that shot in the video of scrolling up to 40 MHz in the FFT plot. You can see the amplitude is unchanged up to 40 MHz at least.

Well... at least amplitude does not steadily go down :) However to be honest - does not look smooth to me at all. Amplitude jumps around and what's worse - bounds of vertical scale too. Can't you make it fixed? Maybe you can make separate video just with smooth and slow sweep 0..60MHz during 1minute as (IMHO) elegant demonstration of bandwidth and FFT function?

Quote
Get one and test it out for me! OR maybe Dave can review?!  :o :-[

Sorry, I have scope already, not a blogger/vlogger too. Maximum I can offer - share some thoughts about your hardware/software. You make some promotional doc/pic/video for new features of you product, put preliminary versions somewhere, PM me. I will look and tell what I think. Disclaimer: I just represent my view, better you doublecheck everything with couple of other people too, before implementing something I suggested to you :)
 

Offline ogden

  • Super Contributor
  • ***
  • Posts: 3731
  • Country: lv
Re: Open Source Oscilloscope, can it be done?
« Reply #122 on: November 15, 2017, 02:21:03 am »
 

Offline seaCAT

  • Newbie
  • Posts: 1
  • Country: au
Re: Open Source Oscilloscope, can it be done?
« Reply #123 on: November 22, 2017, 06:59:11 am »
As a person learning hardware engineering from a software engineering background i can confirm that the prospect of an open source, PC based scope is exactly what i want.
I would be willing to pay much more for it than a proprietary device of a similar specification as it would both allow me to operate natively in an environment that i am accustomed to and to deploy any modifications to the functionality of the scope with a few commands.

I feel like we must not be alone either as this exists(for a hefty 10k price tag):
http://www.wuntronic.de/files/wuntronic-theme-2016/Downloads/Thunderbolt-3-PCIe-Gen3-Digitizers-Overview.pdf

 

Offline hv222

  • Regular Contributor
  • *
  • Posts: 66
  • Country: pl
Re: Open Source Oscilloscope, can it be done?
« Reply #124 on: December 01, 2017, 10:58:40 pm »
I have an idea to design new main board for Keysight 1000 x-series scope, to make it 800MHz bandwidth.  It have ADC, FPGA and processor on separated board, so I will be much easier then design all oscilloscope hardware and software for processor and FGPA. Do you have some schematics, application notes, literature and other resources, which can be helpful? I want to base on http://www.ti.com/lit/ug/tiduba4/tiduba4.pdf and on photos from Dave teardown - https://www.flickr.com/photos/eevblog/albums/72157657671196148 . I have complete schematic of Keysight main board from reverse engineering.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf