| Menu | JAQForum Ver 19.10.27 |
| Menu | JAQForum Ver 19.10.27 |
Forum Index : Microcontroller and PC projects : PicoMite V6.01.00 betas
  Page 2 of 3   |
||||||
Hi Peter, OK thanks I'll look out for the firmware. If I draw the circles to a framebuffer it draws at about 3500 cps, so I was thinking I would get results closer to your GUI TEST LCDPANEL, using the BUFF driver, but presumably not? Any sugestions on how I use the OPTION AUTOREFRESH command which you mentioned? Regards, Kevin. |
||||||
Here is a full set of the 6.01.00b3 files PicoMiteV6.00.03b2.zip Implements OPTION AUTOREFRESH ON/OFF and REFRESH commands Fixes bug in BLIT x1,y1,x2,y2,w,h for buffered drivers The RP2040 files should work as before with no changes. The RP2350 VGA files have the new KEYPAD command variant. In addition HDMI files have the new resolutions and standard RP2350 PicoMite files have the buffered drivers. Wasn't implemented before this release. OPTION AUTOREFRESH is a temporary option which is set to ON whenever a program is run or a program ends. When set to off drawing commands take place to the buffer but the display is not updated. Updates will restart and catch up with OPTION AUTOREFRESH ON, alternatively you can leave it to OFF and force a screen write using the REFRESH command. GUI TEST LCDPANEL now shows the number of circles/second when you exit the test normally (NOT Ctrl-C) |
||||||
tried on board with audio hdmi usb the manual suggestions and ok  |
||||||
Ok, thanks Peter, I'll give it a go when I'm home from Bisley. Regards Kevin. |
||||||
Bisley? Are you a rifle target shooter? Used to go there with my father when he was firing a .22 at tiny targets |
||||||
I prefer the longer stuff 600 to 1200yds, though today only 100yds with yes .22 & .357 under lever (John Wayne) :-) |
||||||
Welcome to Ukraine, gentlemen! Here, as part of the Armed Forces of Ukraine, you can shoot from any type of caliber at any distance! |
||||||
Just walk in to any hunting store in USA. I went in for new boots and came out with a 7mm Ultra Mag  |
||||||
The Betting and Gaming Act of 1960 officially ended the requirement for mandatory archery practice in England. Aren't we lucky? :) |
||||||
New in V6.01.00b2 is the function: MM.SUPPLY This allows you to monitor the battery voltage. SetPin GP29, AIN ' A3=GP29 VSYS/3=GP29 VSYS--R5=200K--+--R6=100K--GND Print "VSYS/3=GP29 = "; Pin(GP29) ' +--C3= 1nF--GND Print "VSYS = "; Pin(GP29) * 3.01 ' +-AIN=GP29--GND Print "MM.SUPPLY = "; MM.SUPPLY VSYS/3=GP29 = 1.62031746 VSYS = 4.874729915 MM.SUPPLY = 4.871428571 Regards, Jan. |
||||||
But has this stopped working on the Pico? ;) OPTION VCC n (where n is the measured 3V3 voltage) - you really need this step anyway SETPIN GP29 AIN PRINT PIN(GP29) * 1.51515 (or tweak to suit your particular Pico's divider) |
||||||
Mick, You'll have to ask Peter. I tried the example above on a standard RP2040 Raspberry Pi Pico, so > ? MM.SUPPLY Regards, Jan. |
||||||
Mick, I think Peter took that into account? Only OPTION LCD BACKLIGHT 0 is a bit unclear? > option list PicoMite MMBasic RP2040 Edition V6.01.00b2 OPTION COLOURCODE ON OPTION HEARTBEAT OFF OPTION PICO OFF OPTION CPUSPEED (KHz) 200000 OPTION DISPLAY 44, 80 OPTION LCD BACKLIGHT 0 > list pins GP0 1 OFF GP1 2 OFF GP2 4 OFF GP3 5 OFF GP4 6 OFF GP5 7 OFF GP6 9 OFF GP7 10 OFF GP8 11 OFF GP9 12 OFF GP10 14 OFF GP11 15 OFF GP12 16 OFF GP13 17 OFF GP14 19 OFF GP15 20 OFF GP16 21 OFF GP17 22 OFF GP18 24 OFF GP19 25 OFF GP20 26 OFF GP21 27 OFF GP22 29 OFF GP23 41 OFF GP24 42 OFF GP25 43 OFF GP26 31 OFF GP27 32 OFF GP28 34 OFF GP29 44 AIN Regards, Jan. |
||||||
Hi Peter, I've been playing with the new BUFFER driver and puerly for my own interest, could you give a bit more info on what is happening in the background. I tuned the circle drawing (below) to give me about 100 circles per second on the standard driver. Then using the BUFF driver, set to auto refresh, I get 200 cps, which is fine, but if I turn off auto refresh, and do a refresh every circle, I now get 600 cps? If I then use the timer to give me a 10Hz refresh I get about 3000 cps?, however there is screen tearing? What is the difference in the background, to what's going on? Is there a function like the Framebuffer sync, to reduce screen tearing? Thanks for any info. Regards, Kevin. PS. I've now found, if I put a Pause 33 after the Refresh command, while doing 10Hz Refresh, I can get about 2000cps without the tearing. :-) Option AUTOREFRESH Off 'On Dim Integer a,t Dim Integer b(15)=(RGB(white),RGB(yellow),RGB(lilac),RGB(brown),RGB(fuchsia),RGB (rust),RGB(magenta),RGB(red),RGB(cyan),RGB(green),RGB(cerulean),RGB(midgreen),RG B(cobalt),RGB(myrtle),RGB(blue),RGB(black)) Timer =0 For a=0 To 6000 Circle Rnd*480,Rnd*320,Rnd*68+12,1,,,b(a Mod 16) If Timer > 99 Then Timer =0:Inc t:Refresh 'Refresh Next Print 6000/(0.1*t),t Edited 2025-07-30 20:52 by Bleep |
||||||
Version 6.01.00b5 files PicoMiteV6.00.03b5.zip This should fix the map command for all HDMI resolutions - please report In addition, the map command and function are now implemented for the new buffered LCD drivers MAP(n)=RGB888value 'n=0 to 255 MAP SET MAP RESET ? MAP(n) 'n=0 to 255 NB: It can't be implemented for non-buffered drivers |
||||||
Hi Peter, that was quick! Can't find any problems with the mapping so far!  Greetings Daniel |
||||||
|
||||||
G'day Peter, Some observations and questions from testing with PicoMiteV6.00.03b5(1) Tested on HDMIUSB and RP2350HDMI MAP command appears to be working in all resolutions (mode 3) MAP Grayscale / Greyscale only works in 640x480 and 720x400 (mode 3), should it work in all resolutions? Is the MAP function intended to return the current value assigned to a MAP(index) or the default value for the mode? currently only returns default value as far as I can tell. Unfortunately 1024x600 resolution has dropped back to 30HZ so I can only test on main monitor  Had planned to post some photos of the monitor at 1024x600 but not much point, they do not do the actual screen justice, it is now a pleasure to use Regards, Lyle. |
||||||
It hasn't. Your monitor is lying. One of mine does too. The pixel clock is 252MHz which gives exactly 60Hz This is correct. It returns a value that will allow you to access that map value. map(0)=RGB(255,0,0) cls map(0) ' map(0) returns 0 which is the RGB level for BLACK which is normally in location 0 of the map. I'll look at this |
||||||
G'day Peter, Thanks for the clarification, some more experimenting required before it finally sinks in 100% Can I ask you to please verify any changes made when "2025-07-25_025614" and V6.00.03b2 where released are still applied? These worked perfectly with both 1024x600 monitors and showed 60Hz on the main monitor, although this isn't diagnostic as you mention. With V6.00.03b5 neither 1024x600 units will sync (one does momentarily) and this indicates something has changed. Regards, Lyle. |
||||||
| Page 2 of 3 |
||||||
 |
The Back Shed's forum code is written, and hosted, in Australia. |
