![]() (So hardware.addon with some weak-pulldowns might be possible to implement) Maybe "94,10" (Rocktech) vs. Using the old Rocktech release, Logic analyser is working, readout is done on CH2. There were a bitpattern shown when switched back to scope-mode, but somehow the software got f*cked up then. Some signal generator codes: 62,00 square wave output 60,00 sine wave output 61,00 triangle output Some misc codes: 34,01 enable logic analyzer mode 34,00 enable scope mode I somehow captured data in logic analyzer mode (with the SainSmart software provided). No more codes avail, so no CH1/CH2 on/off, no trigger settings. with 10ms timebase polling rate is now 100ms with response times 70/200ms and 32k datapacketsize (compared to 64k at the Rocktech software), so this is running totally async. The SainSmart software version has changed polling-rate/packet-size. Which for my needs leaves two tasks:- 1)gating the go-code before it leaves the PC or through hardware/firmware in the scope 2)finding out what all the twiddly hardware setup codes are (optional, if I am prepared to live with the supplied # software)Ĭode: Timebase Samplerate dpps Size 50ns-1us 504us 2.420us 2.4200ns 2.4MHz 5 65536 500ns 2.4MHz 5 65536 1ms-5ms 240kHz 5 65536 10ms 240kHz 3,7* 131072 20ms 240kHz 1,85* 262144 100ms 240kHz 0,91* 524288 200ms 240kHz 0,459* 1048576 *Data-request-polling is set to 200ms (5rps), response (dpps - data packets per second) from scope lags behind. However the good news is that if the go-code can be timed properly by the PC, or gated in hardware, single shot triggering is possible, but only in the sense that the scope acquires data post-trigger. At 100Mhz 2 channels running, data acquisition takes around 650uS and transfer 15mS, so blind 95+% of time. All this means that there are periods of black out, which get more dominant with timebase speed. The whole process is then repeated, issue go code, check status, stop fifo when full and transfer data under USB "interrupt". On my machine this takes around 15mS (not sure why so slow). ![]() When the EZUSB does detect fifo full, it returns a code of 21h, halts the fifo (and hence data acquisition) and then blasts 2^17 bytes to the PC under a USB "interrupt". The host(pc) issues a "go code" of 33h, periodically checks the status of the FIFO with command 50h, which returns 2Ch for fifo not full. In fact, once the scope is setup (permit USB interrupt data transfer gain,ACDC etc) the sequence of events is incredibly simple. And low, I see the command set I've already seen in the firmware, the only code I was missing is E7. Which of course it is not All: After days of negative feelings as to progress, I finally got round to Wiresharking the USB stream. Ganzuul: The point? perhaps just to be able to say it is an "open" interface. Are there elements that you are searching for? I guess you are not planning on rewriting the DLL! But thanks for the BS204 heads up anyway. I am still making progress on the code, but ask myself whether there is anybody wanting it. the BS204 is exactly what I need in terms of functionality. Doctormord: Argh! seems like I brought my DDS140 two weeks too early.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |