TheBackShed.com

Forum Index : Microcontroller and PC projects : Micromite MMBasic Ver 5.04.10 Beta

Page 4 of 4

Author

Message

Geoffg

Guru

Joined: 06/06/2011
Location: Australia
Posts: 3292

Posted: 03:05am 01 Nov 2018

Copy link to clipboard

Print this post

OK, another version (beta 13) where I think that I have nailed the problem. I will be grateful if anyone who experienced this latest issue could try it out.

You can download the beta from the usual place: http://geoffg.net/micromite.html

This is a strange affair and is something to do with the performance of the PC or Windows. On one of my machines (a high end 6 core 4.3GHz CPU) the MM+ with beta 12 worked perfectly but on the Surface Pro (2 core 2.5GHz) with the same version of Windows 10 it failed as it did for Zonker and Mailbu. I was fortunate to have one machine that failed otherwise it would have been impossible to find the cause. This is why I hope that as many people as possible could try beta 13, someone might have a PC that is more susceptible.

The final solution was for the MM+ to service the USB more often. Beta 12 did it every 500uS, beta 13 now does it much faster (every 50uS approx).

Geoff Graham - http://geoffg.net

Malibu
Senior Member

Joined: 07/07/2018
Location: Australia
Posts: 260

Posted: 03:36am 01 Nov 2018

Copy link to clipboard

Print this post

All good Geoff!

Firmware went in 1st time and I individually put in all the options to test them one-by-one. The only headache was the usual problems with windows trying to find the port after each reset. Not a big deal though...
Here's a screen grab of my system if it helps you -

Thanks again

John

Zonker

Guru

Joined: 18/08/2012
Location: United States
Posts: 767

Posted: 10:04am 01 Nov 2018

Copy link to clipboard

Print this post

Confirmed... Just got done with the programming sequence... All good...!!

Wow Geoff..!! Must have been a real hair pull trying to figure this out...
In the EIS hardware design, I am using one of the serial console port pins to connect the SDcard interface so I couldn't use a serial port USB adapter...

Will continue testing Beta-13 after work today... GUI Gauge time..!!

A big thank you Geoff for all the time and hard work done on our behalf..!!

Greg Fordyce
Senior Member

Joined: 16/09/2011
Location: United Kingdom
Posts: 153

Posted: 10:10pm 10 Nov 2018

Copy link to clipboard

Print this post

Geoff, a couple of things on beta 13;

I've noticed weird behaviour using the circular gauges if "unit$" isn't specified. The gauge will sometimes adopt the unit$ from another gauge. Of course the solution is to always specify unit$. Just thought I would mention it.

Also page 16 of the MM+ manual mentions '...SSD1966 LED_A...' twice, it should probably read '...SSD1963 LED_A...'

Otherwise I can't fault Beta 13, thanks Geoff for your work!

Greg

p.s. It's been a while for me, the last version I used was 4.7!

Geoffg

Guru

Joined: 06/06/2011
Location: Australia
Posts: 3292

Posted: 05:33am 11 Nov 2018

Copy link to clipboard

Print this post

Thanks Greg. That behaviour is intended, for all controls the parameters in italics are optional and if not specified will default to that used in the previous declaration of a control. The beta documentation did not make this obvious.

The idea is that you could define a number of controls without having to repeat the same details. For example this would create three identical gauges in a row:

GUI GAUGE 1, 150, 350, 100, RGB(white),RGB(black),0,100,1,"`C",RGB(green),75,RGB(red)
GUI GAUGE 2, 300, 350, 100
GUI GAUGE 3, 450, 350, 100

I am not sure if this "feature" was a good idea but it seemed like a good idea at the time (famous last words).

Thanks for the typos, I will fix that for future versions.

Geoff

Geoff Graham - http://geoffg.net

CircuitGizmos

Guru

Joined: 08/09/2011
Location: United States
Posts: 1427

Posted: 06:16pm 11 Nov 2018

Copy link to clipboard

Print this post

How about something like a '*'

GUI GAUGE 1, 150, 350, 100, RGB(white),RGB(black),0,100,1,"`C",RGB(green),75,RGB(red)
GUI GAUGE 2, 300, 350, 100 *
GUI GAUGE 3, 450, 350, 100 *

Or some other way to say DITTO. That way it is deliberate, rather than a surprise.

Micromites and Maximites! - Beginning Maximite

Volhout
Guru

Joined: 05/03/2018
Location: Netherlands
Posts: 5091

Posted: 10:42am 12 Nov 2018

Copy link to clipboard

Print this post

I don't feel I am really entitled to comment (being a non frequent user), but my emotions forced me to reply.

Please don't do it.

It makes code unreadable and unpredictable.
It is far simpler and more structured to define the
"RGB(white,RGB(black........"
and use the define at locations needed.

Volhout

b.t.w it does not even save typing, since you typically copy the whole line anyway.
It only may save code pace.

PicomiteVGA PETSCII ROBOTS

astro1
Regular Member

Joined: 26/06/2016
Location: Australia
Posts: 53

Posted: 08:27am 26 Nov 2018

Copy link to clipboard

Print this post

How do you de-active a GAUGE to be able to call up a new one with a different max?

Edit: GUI DELETE from v5.05.01 docs. :')
Edited by astro1 2018-11-27

Page 4 of 4

Print this page

To reply to this topic, you need to log in.