3/11/2023 0 Comments Github xscope gabotronics![]() ![]() That probably fits the bill for your ADC readings, but for the other examples you gave (Serial, IR PWM etc), a Logic Analyser might be more suitable. ![]() Of course that was also mainly true for traditional analogue 'scopes, but it's rather easier to "confuse" yourself with the subsampling artefacts of a digital scope.Ĭlick to expand.For working with Analogue signals, that vary with time, you need a 'scope - any scope, being better than no scope. Secondly, it is a rather slow "Sampling" 'scope which means that for "higher" frequencies (potentially not far into the kHz region) it needs a "periodic" (continuous) waveform and a reliable sync / trigger signal. Unlikely, particularly for typical PICaxe projects, but it could be a very expensive mistake. Since it connects directly to your computer (USB connection for data and power) there is a slight risk that you might "destroy" the PC if you do something really bad. There are probably other advantages but I had better mention a few disadvantages: Also, as it uses your computer's screen, it's easy to take a screenshot (Print Screen), the "User Interface" is quite good and it has a storage / persistence capability for slower signals. It has several strengths and weaknesses: Firstly, it has two channels (plus an External Sync capability) it's amazing how often a second (displayed) channel is useful and sometimes it's absolutely essential. For example, I used it for a forum thread HERE (end of post #1). Personally, I have the original "DPScope SE" which uses identical software and is basically the same, but built inside a "box" with connectors for 'scope probes, etc. I reduced the delay until I could see the desired effect above. The scope showed that on my first pass, the delay was too long, running over into the next half-cycle. ![]() The program delays for a decreasing time before firing the triac to provide a "soft start" to a (simulated) A.C. Running at SETFREQ M16, "PAUSE 1" takes 317 microseconds incrementing to PAUSE 2 adds 250 microseconds. This screen shot from DPScopeSE shows that the triac on-time (red signal) was ramping as desired after being triggered by the zero-crossing trigger (blue): I like that it's so tiny, especially compared to the 70-pound used monster I had 40 years ago.Ī few days ago I wanted to look at the timing of an AC "cycle slicing" program which was attempting to capture a zero-crossing trigger of a 60Hz (North American) AC signal (tested using a 12V AC wall plug transformer) to fire a triac for an increasing period within the 8.33ms half-cycle time (120 half cycles per second). Update configure.ac bug URL for gitlab migrationįix up documentation of NAS command line flagsĪutogen.I don't need to use my DPScopeSE very often, but it's illuminating when I do. To make it really 'standalone', there's more fiddling required to get the libraries into the app itself.Īdd support for process ID and names on Solarish systems Note that it links to brew's qt and libusb, so it will only work on your computer. If anyone wants to compile it themselves, here's what I did:ġ) get homebrew and Apple's developer tools (homebrew should give you instructions if you don't have them)Ģ) install qt and libusb: brew install qt libusbĤ) change into the cloned dir: cd xscopes-qtĥ) fix linking info: edit 'XprotolabInterface.pro', find the line which looks like 'unix:!macx:!symbian: LIBS += -lusb-1.0' (near the end) and delete ':!macx', so that it looks like 'unix:!symbian: LIBS += -lusb-1.0'ħ) now you should have a newly created 'xscope.app' in your directory. It's working for me on Mavericks and Mountain Lion I did by best to include all the necessary libraries into the app, but I may have missed something, so let me know if the app doesn't work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |