| Products > Test Equipment |
| New bench scope - Fnirsi 1014D, 7", 1GSa/s |
| << < (53/67) > >> |
| pcprogrammer:
A pointer on something that is different between the 1013D and 1014D is the screen brightness setting in the FPGA. It uses the same command 0x38, but it takes only one byte as setting. 0x78 is full on. Have not looked at the settable range, so needs some experimentation. Is simple to modify in the "fpga_control.c" file. Look at functions "fpga_set_translated_brightness" and "fpga_set_backlight_brightness". |
| donwulff:
--- Quote from: pcprogrammer on January 08, 2023, 07:02:41 am ---The touch handling in the firmware is based on detection of touch in one of the defined buttons or dedicated areas, and if it is a menu it will open that menu and use dedicated functions to handle the touch in that. It might not be easy to connect this to the input from the user interface controller. But everything for this is found in the "statemachine" and "scope_functions" files. --- End quote --- Yeah, touch is by necessity "modal" whereas the buttons are more global in nature. It bugs me because I wouldn't want to re-write the whole UI and then people would have to keep both implementations in synch. Maybe some event-driven model. Did the same copy-paste (of my own code/defines) error for the serial port, making both Divisor Latch LSB/MSB register same, then writing 0 to MSB... |O Something else that was different for 1014D, at least to your custom firmware, is the 1014D stock firmware sets the MCU clock to 576 MHz. This means the Divisor Latch is 4% too large for the 600 MHz clock. With those fixed I got the key values easy, so now I can start raking my head for the way to combine touch & buttons in meaningful way. It sends 0xff to the knob-processor before each read, which I guess works as rudimentary flow-control if it responds only when it receives 0xff. I haven't looked if there's a buffer beyond the FIFO on that side though. But at least all the pieces for programming it are there now. The "PECOS SCOPE" load-screen is flashing in a weird way, I wonder if that is related to the brightness setting. The main scope screen is fine though, so that's not a problem. Because the speed of booting is one of the strengths of the scope, it might be skipped anyway. --- Code: ---1 RUN/STOP 2 AUTO 3 MENU 4 S PIC 5 S WAV 6 H CUR 7 V CUR 8 > 9 ^ 10 OK 11 v 12 < 13 SLOW 14 CH1 15 CONF (CH1) 16 CH2 17 CONF (CH2) 18 ORIG 19 MODE 20 EDGE 21 CHX 22 50% 23 F1 24 F2 25 F3 26 F4 27 F5 28 F6 29 GEN 30 NEXT 31 LAST 32 DEL 33 SEE ALL 34 SEL 35 + SEL 36 - SEL 37 + POS (CH1) 38 - POS (CH1) 39 + POS (CH2) 40 - POS (CH2) 41 - POS (ORIG) 42 + POS (ORIG) 43 + LEVEL 44 - LEVEL 49 ON 200 OFF --- End code --- |
| pcprogrammer:
--- Quote from: donwulff on January 09, 2023, 12:28:16 pm ---The "PECOS SCOPE" load-screen is flashing in a weird way, I wonder if that is related to the brightness setting. The main scope screen is fine though, so that's not a problem. Because the speed of booting is one of the strengths of the scope, it might be skipped anyway. --- End quote --- Yes, that has to do with the brightness setting. By modifying the load screen code to just write 0x38 and then 0x78 to the FPGA instead of 0x38, 0xEA, 0x60 (if not mistaken out the top of my head) it will stop the flickering. Had the same issue with the firmware backup program. Good work on getting the commands send from the user interface controller. I wonder why they set the F1C100s to a lower clock then the 1013D. Will be fun to see the 1013D firmware working on the 1014D, but modifying the screen setup might be needed to deal with the function buttons on the right of the screen. Edit: And there is the AWG of course. There in lies a lot of fun stuff to do, like sweeping to measure filter response. |
| pcprogrammer:
I checked the command list with the front panel of my scope, and noticed the three bigger knobs are missing from it. The channel sensitivities and the time base time per division selector. The gap between - level and on is not large enough to fit them all, so do they have another set between on and off? |
| donwulff:
Oh dang, they don't have label so I missed them. 45 - X CH1 46 + X CH1 47 - Y CH2 48 + Y CH2 49 - GEN (TIME) 50 + GEN (TIME) The 49 is actually an error, it seems to report random/last encoder position on boot, which will be annoying. Could be sort of weird to have separate code for that, as the scope doesn't technically "see" it, and is physically same button. 200 does show up for the POWER button when it's running (and shuts down about a second after). I have the plastic knobs off because I'm intending to check under the tin-cans, although AliExpress is having delays even mailing the KAQY214(S) chips, so will be a while until I'll be able to try anything with that... should probably put it back together before I break something. And yes the AWG is still kind of open book, the scope will work without it though. But I hope I'll be able to find time to play with the AWG/mods and even FPGA. First step is getting it usable with the custom firmware though. |
| Navigation |
| Message Index |
| Next page |
| Previous page |