| Products > Test Equipment |
| Building my own scope |
| << < (5/32) > >> |
| Bud:
TI application note on a high speed front end https://www.ti.com/tool/TIDA-00826 |
| tggzzz:
There is a fine line between tackling a project that stretches you and one which can't be completed within reasonable time and effort. Engineers ought to be able to distinguish[1]. N.B. it is not for me to define "stretches you", "completed", "reasonable time", "reasonable effort". That's your decision :) However, there is also nothing wrong with trying something, finding where the pain points are, finding workarounds - and knowing what you would do better next time. Indeed, in some circumstances that can be positively beneficial, e.g. during job interviews being able to demonstrate that you are interested in the subject and in continuously improving your knowledge and judgement. Back in the 70s I built a 6800 computer (similar to an Altair 8080) from scratch. In many ways it was appalling, but I learned a hell of a lot and could discuss things with other people. I would suggest that learning when and how to use (or to avoid using) FPGAs is a useful skill, just as learning how to programme microcontrollers is useful. I would also suggest that if you are starting from scratch, then the magnitude of learning FPGAs is similar to that of learning MCUs. Have fun! :) [1] Eric Laithwaite at Imperial College used to set exams where one question was easy and sufficient get you a pass mark, one was more challenging and couuld get you a good degree, and one could not be answered adequately in the time available. He expected his undergraduate engineers to be able to determine which questions to avoid. If they couldn't, they wouldn't make good engineers anyway. |
| balnazzar:
--- Quote from: tggzzz on October 20, 2022, 06:50:15 pm ---There is a fine line between tackling a project that stretches you and one which can't be completed within reasonable time and effort. Engineers ought to be able to distinguish[1]. N.B. it is not for me to define "stretches you", "completed", "reasonable time", "reasonable effort". That's your decision :) However, there is also nothing wrong with trying something, finding where the pain points are, finding workarounds - and knowing what you would do better next time. Indeed, in some circumstances that can be positively beneficial, e.g. during job interviews being able to demonstrate that you are interested in the subject and in continuously improving your knowledge and judgement. Back in the 70s I built a 6800 computer (similar to an Altair 8080) from scratch. In many ways it was appalling, but I learned a hell of a lot and could discuss things with other people. I would suggest that learning when and how to use (or to avoid using) FPGAs is a useful skill, just as learning how to programme microcontrollers is useful. I would also suggest that if you are starting from scratch, then the magnitude of learning FPGAs is similar to that of learning MCUs. Have fun! :) [1] Eric Laithwaite at Imperial College used to set exams where one question was easy and sufficient get you a pass mark, one was more challenging and couuld get you a good degree, and one could not be answered adequately in the time available. He expected his undergraduate engineers to be able to determine which questions to avoid. If they couldn't, they wouldn't make good engineers anyway. --- End quote --- I have to say I'm studying physics, not engineering. We are somewhat supposed to venture even in stuff that cannot be explored in any reasonable stretch of time ::) But yours are good advices nonetheless! One step forward would be establishing if it's absolutely necessary to use a FPGA. I'm sure it'd be interesting to learn FPGAs per se, but nevertheless I need to know if one can make a functional scope with just a computer, a front end, and an ADC. |
| tautech:
Where did balnazzar go ? I think he fell in here: |
| pcprogrammer:
A scope without a FPGA is certainly possible, but would not have a high sampling rate. Take a look at these little scopes made with a STM32103 MCU. Just 1MSa/s, but good as a basis to learn about how a scope works. Schematics of the Wave2 of jyetech can be found here. https://jyetech.com/wp-content/uploads/105-15800-00M.pdf For higher sample rates without a FPGA you would need a more powerful processor and an external ADC. Don't have examples on this. With a FPGA there are many options like for example a zynq board you mentioned but high speed ADC modules need fancy FPGA boards with FMC connectors. It would then be easier to buy for example a Hantek DSO2C10 and make your own FPGA design and software for that. The schematics are reverse engineered by me and can be found here: https://github.com/pecostm32/Hantek_DSO2000/tree/main/Schematics For a system with less bandwidth and easier to build with modules I already pointed you to my Lichee Nano repository. I refer to a 2 channel 65MSa/s 12 bit ADC module there. For a scope it would need more work on a front end, which is not in my skill set, but for a starting point it is good enough. As a learning tool the FNIRSI-1013D is also fun. It has all the hardware needed to make a scope, and there is plenty of info about it in my repositories and the thread here on the forum. I'm currently trying to reverse engineer the FPGA design of it. Also as a learning project :) https://www.eevblog.com/forum/testgear/fnirsi-1013d-100mhz-tablet-oscilloscope/ https://github.com/pecostm32/FNIRSI-1013D-1014D-Hack A PCIe card that is not even very fast but 16bits can be found here: https://buy.advantech.eu/Boards-Cards/Data-Acquisition-I-O-Data-Acquisition-I-O-Cards-PCI-Express-Cards/model-PCIE-1840-AE.htm?country=France&token=638018915275564395&f=AUS It is very expensive. Hope this helps you make up your mind. Have fun with what ever you choose. |
| Navigation |
| Message Index |
| Next page |
| Previous page |