 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Micromite and Micromite Plus Beta 36
Page 1 of 3   |
|||||
| Author | Message | ||||
Geoffg Guru  Joined: 06/06/2011 Location: AustraliaPosts: 3292 |
There is a new beta version (B32) for the Micromite and Micromite Plus and it can be downloaded from the usual place: http://geoffg.net/Downloads/Micromite/Micromite_4.7_Beta.zip (clear your browser cache first). This one has a lot of fixes and changes. All known bugs (except the Win10 USB issue) have been fixed and a lot of the new features have been implemented. Barring undiscovered bugs I believe that the MX170 version is almost at the final version while the MX470 version (Micromite Plus) still needs some more work adding new controls, etc (check the file MMPlusIssues.txt for details). I have some other things to attend to (like writing a magazine article on the MX170 version) so I am not planning another beta for a month or more. All the changes are listed in the file Changes.txt but the highlights are: - OPTION LCDPANEL has been changed to allow the default colours, font and brightness to be set up for when the LCD is used as the console (WW & MMAndy should be happy). - Added the ability to embed fonts in the BASIC program. They look a little like CFunctions and allow a wide range of specialty fonts to be loaded with the program. The MMBasic firmware zip file now includes 14 ready to go embedded fonts. - Because of the above change font #1 has been removed from the MX170 version (it can now been embedded) and all the fonts in both the MX170 and MX470 versions have been renumbered. This will break many programs (sorry) but hopefully this will be the last change to the font numbering scheme. - Included Peter Mather's loadable drivers for the ILI9163 and ST7735 LCDs and removed the built-in drivers for these from the MX170 version (this clawed back about 1KB of flash for use in bug fixes). - The GUI LED command now takes a caption. - Implemented "ghost text" for the GUI TEXTBOX and GUI NUMBERBOX controls. - MMBasic has two new commands: CONTINUE FOR and CONTINUE DO. Plus many more changes. Two that I have not been able to implement are STATIC and constant arrays but I will re-investigate them later. The manuals have been updated to reflect these changes so if something does not work as you expect check the manual. Geoff (now waiting for the bugs to appear) Geoff Graham - http://geoffg.net |
||||
twofingers Guru Joined: 02/06/2014 Location: GermanyPosts: 1593 |
Hi Geoff, thanks for providing this new version! Looks like a huge amount of work. Thanks again Michael causality ≠correlation ≠coincidence |
||||
| viscomjim Guru Joined: 08/01/2014 Location: United StatesPosts: 925 |
Awesome as usual!!!!! Thanks! |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
Geoff means Beta B36  |
||||
kiiid Guru Joined: 11/05/2013 Location: United KingdomPosts: 671 |
Ah, I love great news...  http://rittle.org -------------- |
||||
| viscomjim Guru Joined: 08/01/2014 Location: United StatesPosts: 925 |
Quick thing to check in advanced features manual page 16... The 28 and 44-pin Micromites include two built in fonts while the Micromite Plus has six built in fonts plus it can load up to ten additional fonts from the SD card. Page 17 says... Micromite only. One font is built into the 28-pin and 44-pin Micromites plus additional fonts can be installed using embedded fonts (see below) |
||||
Zonker Guru Joined: 18/08/2012 Location: United StatesPosts: 767 |
GUI DEFAULT HIDDEN working nicely..! Just got the update shot onto the GCmicroboard2 and everything settled back in... The GUI object creating process goes much faster now..! (sweet) Currently using 49 objects and need another setup screen to allow the end user to change the threshold settings, (the color areas) of the gauge faces. Thank you very much Geoff for the update.. Perfect timing..!
Will keep working with it... |
||||
| MMAndy Regular Member  Joined: 16/07/2015 Location: United StatesPosts: 91 |
Windows 8.1 with B36 MM+ with SSD1963 7" TFT lcd display Under option lcdpanel console ... the font parameter "allowable" range is 2-6 but font 1 is needed for proper console editing? BTW ... workaround - by using "option lcdpanel console" without any parameters will default to font 1 but I still need to set the backlight brightness?  |
||||
| Zonker Guru Joined: 18/08/2012 Location: United StatesPosts: 767 |
While testing v4.7b36 on the CGmicroboard2, I think I maybe ran into bug..? I am using the GUI FCOLOUR command that was working in b32, but now trips the "Invalid Command" error... Not sure why... I am using it to control the colors of a display box... If ch3flt_old<>ch3flt Then Print "CHT 1 fault "+Str$(ch3flt) If ch3flt>1 And screen_state=1 Then GUI fcolour RGB(red), cht1_data_box CtrlVal(cht1_data_box)="FLT" Else GUI fcolour RGB(green), cht1_data_box EndIf ch3flt_old=ch3flt EndIf will check back tomorrow after work... Thanks Gent's |
||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
Cannot SETPIN interrups above 30. Something like SETPIN 55,INTL,XXX is rejected as invalid configuration, although pin55 is a valid interrupt pin according to the manual. This is on the 470 MM+ 64. This is a known bug from previous betas, but I am just giving it a small prod in case it has been forgotten about. Smoke makes things work. When the smoke gets out, it stops! |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
With a IL9341 TFT connected (64pinner with B36), typing BACKLIGHT x will cause the display to clear, and the backlight be on bright. I know the BACKLIGHT command is for the SSD displays, I am just trying to 'break' things!!
WW |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
I am getting strange results with an ILI9341 TFT after issuing the LOAD IMAGE command. The TFT is 320x240 pixels, and has been tried on R & RL orientations. I am using a test bitmap of a red heart (filled) on a white background (and saved as 320x240 pixels). First time, the BMP loaded rows of white pixels up to the bottom of the heart, then done a couple of pixel rows (continuing the red pixels) ok, then all other pixel rows (or red pixels making up the heart) were offset resulting in a 'scrambled' image. After re-issunig the LCDPANEL command to try different orientations, I now only get the 'LOAD IMAGE' command to respond about 10% of the time (still drawing image incorrectly). The 90% of the time it doesn't draw anything, it just hangs after pressing the Enter key. Ctrl-C has no response; I have to reset. I have tried multiple BMPs; all created in Windows Paint. I have no issues with BMPs generated for the SSD TFTs so assume this is an ILI9341 'issue'. Has anyone else tried a ILI9341 on B36 - if so, did you see any strange behaviour?? Thanks, WW |
||||
atmega8 Guru Joined: 19/11/2013 Location: GermanyPosts: 724 |
Geoff, No Support on the 100 PIN Versions, or forgotten to update the Manual ?? Manual says: "OPTION CLOCKTRIM ±n Trim the frequency of the internal oscillator on the 28 and 44-pin Micromites." EDIT: TEST on Snadpic terminal shows: option CLOCKTRIM +1 Error: Unrecognised option So not implemented, why ? THX |
||||
TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
CLOCKTRIM was needed on the micromites that used the internal RC oscillator. On boards that used a crystal, adjustment of frequency is not needed and the size of the tuning steps with CLOCKTRIM are not fine enough to trim a crystal. Jim VK7JH MMedit |
||||
| Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3292 |
Thanks for the feedback everyone, most appreciated. Thanks, I will fix it in the next beta. I am amazed that anyone would want to use font #1 for editing (so small) but for the moment the workaround would be to specify font 2 in the CONSOLE option then set font #1 in the subroutine MM.STARTUP which can be "hidden" in the library. BTW I have just discovered that the CONSOLE option does not allow for an optional hash character (#) before the font number - I will fix that also. That is strange, I don't know where it has gone. Anyway, thanks and I will fix it in the next beta. No, you can only set interrupts up to pin 32. I put this limitation in to prevent the interpreter form having to scan all the pins which would slow it down considerably (especially on a 100 pin chip). The current manual is correct (it does not list pin 55 as an interrupt). Is pin 55 important to you? I am looking at implementing a scheme which would allow almost any pin to be used as an interrupt without a performance penalty. Thanks, I will insert an error check. Hmm, works fine for me. This is the test image that I use: 2015-10-12_235413_tiger2.zip Geoff Geoff Graham - http://geoffg.net |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
Hey guys. 
Current manual for B36, shows pins 54 and 55 as interrupt capable. I guess then the manual needs another update then.....  Smoke makes things work. When the smoke gets out, it stops! |
||||
| Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3292 |
Damn, you are right... sorry 
As it happens, since my last post I have been fiddling with the interrupt handling code and it is easy to modify - so the next beta will allow you to set an interrupt on any digital input pin. Geoff Geoff Graham - http://geoffg.net |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
Oh, you are a champ, Geoff!!!!
I don't need to hack the PCB now. Smoke makes things work. When the smoke gets out, it stops! |
||||
| MMAndy Regular Member Joined: 16/07/2015 Location: United StatesPosts: 91 |
Even though the maximum length of the command line is 255 characters, we found that on large lines of code, the on-board editor cuts off the characters (font 2 > 67 chars) and the extra characters cannot be seen. By reducing the font size to 1 will reveal all the characters for editing. Also, importing code from older programs, which has long character lines and placing them on the SD drive will wrap the characters on to the next line when using the on-board editor. Saving this file will cause many errors. So, by using the smallest font possible (font 1) both conditions are eliminated. If we had a choice to use an easy to read larger font we would but the built-in editor would need to accept longer character lines with wrap. MM+, SSD1963 7" TFT |
||||
| Zonker Guru Joined: 18/08/2012 Location: United StatesPosts: 767 |
While trying to update or change the values of hidden controls, they are still trying to set the background of the control to the color defined during the controls creation... (me thinks)... 
I used a white background to catch it... Normally, I would be using black as the background, so it would be easy to miss... the same happens when setting the "ghost text"... 
Will keep playing... |
||||
| Page 1 of 3 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
