From nigel.kendrick at gmail.com  Wed Jun  1 10:30:01 2016
From: nigel.kendrick at gmail.com (Nigel Kendrick)
Date: Wed, 1 Jun 2016 15:30:01 +0100
Subject: [Microbit-Python] Microbit in STEM
In-Reply-To: <VI1PR0801MB158320AE47D0BEFDD0927A6AA6460@VI1PR0801MB1583.eurprd08.prod.outlook.com>
References: <VI1PR0801MB158320AE47D0BEFDD0927A6AA6460@VI1PR0801MB1583.eurprd08.prod.outlook.com>
Message-ID: <CA+ziQAScqiRVndmwzASDqPGTZxdUOQsVPGOLuvPDO5jjiQp3Jg@mail.gmail.com>

Thanks Dave,

I've bookmarked the page, will register and see how I can contribute. Looks
like a suitable place for back-end teams, with the Stack Exchange site
servicing the users and hobbyists - no doubt many will contribute to both.

For what it's worth, I added a comment to a thread on The Register about
the preorder announcement, encouraging people to head over to Area 51 at
Stack Exchange and help push things along.

On 31 May 2016 at 14:19, Dave Gibbs <D.Gibbs at stem.org.uk> wrote:

> I'd be happy to host something in the National STEM Learning Centre online
> groups. We have micro:bit threads running in a couple:
>
> https://www.stem.org.uk/community/groups/37459/physical-computing-and-robotics
> would be the ideal place.
>
> Regards,
> Dave
>
> Dave Gibbs
> STEM Computing & Technology Specialist
> National STEM Learning Centre & Network / UK Space Education Office
> (ESERO-UK)
> STEM Learning Ltd
>
> Tel:      0044 (0)1904 328 362
> Mob:   0044 (0) 7772 306 228
> Email:  d.gibbs at stem.org.uk
>
> Twitter: @adgibbs @STEMLearningLtd
> Web: www.stem.org.uk and www.esero.org.uk
>
>
> -----Original Message-----
> From: Microbit [mailto:microbit-bounces+d.gibbs=
> nationalstemcentre.org.uk at python.org] On Behalf Of
> microbit-request at python.org
> Sent: 31 May 2016 14:13
> To: microbit at python.org
> Subject: Microbit Digest, Vol 12, Issue 35
>
> Send Microbit mailing list submissions to
> microbit at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.python.org/mailman/listinfo/microbit
> or, via email, send a message with subject or body 'help' to
> microbit-request at python.org
>
> You can reach the person managing the list at
> microbit-owner at python.org
>
> When replying, please edit your Subject line so it is more specific than
> "Re: Contents of Microbit digest..."
>
>
> Today's Topics:
>
>    1.  Microbit in STEM (Rob Wilson)
>    2. Re: Microbit in STEM (Nigel Kendrick)
>    3. Re: Microbit in STEM (David Whale)
>    4. Re: Microbit in STEM (Nicholas H.Tollervey)
>    5. Re: Microbit in STEM (Loop Space)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 31 May 2016 12:08:20 +0100
> From: "Rob Wilson" <rob at rwilson.org.uk>
> To: microbit at python.org
> Subject: [Microbit-Python]  Microbit in STEM
> Message-ID: <1021B079-C7AB-4EC4-B205-39734872CDC9 at rwilson.org.uk>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi Nigel
> I like the idea of ?sharing knowledge etc?. Maybe a STEM microbit wiki or
> something?
>
> I like the spectrum analyser! I?ve had a vague idea to write a singing
> coach (analyse voice pitch and display difference to played tone) which
> would need a Fourier Transform like that. Not done anything about it yet ?.
>
> > Hi Rob,
> >
> > I am a STEM ambassador with micro:bit too. I'm hoping that the
> > ambassador community can team up to share knowledge etc. but at the
> > moment things are a bit fragmented. I have a few things in the
> > pipeline - there's a few pics below and a video...
> >
> > https://imgur.com/a/Rn6Cr
> >
> > https://www.youtube.com/watch?app=desktop&persist_app=1&v=SE4Bb1NHyU4
> >
> > Nigel Kendrick
> > aka Linker3000
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 31 May 2016 13:09:56 +0100
> From: Nigel Kendrick <nigel.kendrick at gmail.com>
> To: For Pythonic MicroBit related discussions <microbit at python.org>
> Subject: Re: [Microbit-Python] Microbit in STEM
> Message-ID:
> <CA+ziQARhOZKxnz3T2ATfSyKMHO42kMjU=pXq6nUvr06omJGMQw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Rob,
>
> We'd just need a home for the wiki - do you have any good connections at
> STEM HQ that could help make it official, as opposed to just setting up a
> site somewhere? My contacts are all in the regional office and they seem to
> struggle to get traction back up the chain for anything. I have also
> considered 'partnering' with the BBC for a knowledge sharing section within
> their micro:bit site, but I am making no headway there.
>
> Also, I am a new Ambassador so I haven't made many regional or national
> contacts yet - I'd love to find out 'where the action is' with regards to
> other STEM ambassadors working in IT/electronics.
>
> Basic FFT on the micro:bit would be doable (a la Arduino etc.), but my
> configuration samples the audio in 5 fixed frequency bands on a external
> chip and sends a representative analogue voltage for each band to the
> micro:bit. The end-game is to have a board with the spectrum analyser chip,
> an electret mic with amplifier, a sound triggered logic signal and a class
> D bridge amp (it's quite loud, considering it's runnign from 3V!) all
> powered from the micro:bit.
>
> All the best
>
> --Nigel Kendrick
>
> On 31 May 2016 at 12:08, Rob Wilson <rob at rwilson.org.uk> wrote:
>
> > Hi Nigel
> > I like the idea of ?sharing knowledge etc?. Maybe a STEM microbit wiki
> > or something?
> >
> > I like the spectrum analyser! I?ve had a vague idea to write a singing
> > coach (analyse voice pitch and display difference to played tone)
> > which would need a Fourier Transform like that. Not done anything about
> it yet ?.
> >
> > Hi Rob,
> >>
> >> I am a STEM ambassador with micro:bit too. I'm hoping that the
> >> ambassador community can team up to share knowledge etc. but at the
> >> moment things are a bit fragmented. I have a few things in the
> >> pipeline - there's a few pics below and a video...
> >>
> >> https://imgur.com/a/Rn6Cr
> >>
> >> https://www.youtube.com/watch?app=desktop&persist_app=1&v=SE4Bb1NHyU4
> >>
> >> Nigel Kendrick
> >> aka Linker3000
> >>
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.python.org/pipermail/microbit/attachments/20160531/f3d8c4cb/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Tue, 31 May 2016 13:25:32 +0100
> From: David Whale <david at thinkingbinaries.com>
> To: For Pythonic MicroBit related discussions <microbit at python.org>
> Subject: Re: [Microbit-Python] Microbit in STEM
> Message-ID:
> <CABeH_SuuEK=a_jrDg8r1czu1P2ZXhFfXZb9k9QPVvnBH78uLPg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Rob/Nigel,
>
> There is a wiki already set up by a STEM ambassador, but it needs some
> energy behind it:
>
> microbit.wiki
>
> Also, we're all trying to get enough energy behind this Stack Overflow
> site, to build a self sustaining community, please join in! Only 10 more
> questions above a score of 10 and we can move to the next stage. There must
> be more than 10 people on this mailing list that haven't registered yet,
> that could do, and upvote a few questions (and also raise some Python
> questions for consideration too)
>
> http://area51.stackexchange.com/proposals/96237/microbit
>
> David.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.python.org/pipermail/microbit/attachments/20160531/a908b046/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 4
> Date: Tue, 31 May 2016 14:09:06 +0100
> From: "Nicholas H.Tollervey" <ntoll at ntoll.org>
> To: microbit at python.org
> Subject: Re: [Microbit-Python] Microbit in STEM
> Message-ID: <d4a3de49-554c-0758-b002-da7b844635b5 at ntoll.org>
> Content-Type: text/plain; charset="windows-1252"
>
> Hello from Portland (I'm at PyCon in the US at the moment).
>
> I hope to be able to have some good news in the coming weeks about Python
> Software Foundation support for web based resources and community
> development around not just the micro:bit, but Pythonic education in
> general.
>
> Yours hopefully,
>
> N.
>
> On 31/05/16 13:25, David Whale wrote:
> > Rob/Nigel,
> >
> > There is a wiki already set up by a STEM ambassador, but it needs some
> > energy behind it:
> >
> > microbit.wiki
> >
> > Also, we're all trying to get enough energy behind this Stack Overflow
> > site, to build a self sustaining community, please join in! Only 10
> > more questions above a score of 10 and we can move to the next stage.
> > There must be more than 10 people on this mailing list that haven't
> > registered yet, that could do, and upvote a few questions (and also
> > raise some Python questions for consideration too)
> >
> > http://area51.stackexchange.com/proposals/96237/microbit
> >
> > David.
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 473 bytes
> Desc: OpenPGP digital signature
> URL: <
> http://mail.python.org/pipermail/microbit/attachments/20160531/4314b4d5/attachment-0001.sig
> >
>
> ------------------------------
>
> Message: 5
> Date: Tue, 31 May 2016 14:12:45 +0100
> From: Loop Space <loopspace at mathforge.org>
> To: microbit at python.org
> Subject: Re: [Microbit-Python] Microbit in STEM
> Message-ID: <f84fe10d-0eb4-ba84-3ccd-1d403b028829 at mathforge.org>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> RE the SE site, note that it's better to vote strategically in this
> stage.  The proposal needs questions with 10 or more votes, so if a
> question already has 10 or more votes then it is a somewhat wasted vote to
> vote on it given that people have limited number of votes at this point.
>
> Andrew
>
> On 31/05/2016 13:25, David Whale wrote:
> > Rob/Nigel,
> >
> > There is a wiki already set up by a STEM ambassador, but it needs some
> > energy behind it:
> >
> > microbit.wiki
> >
> > Also, we're all trying to get enough energy behind this Stack Overflow
> > site, to build a self sustaining community, please join in! Only 10
> > more questions above a score of 10 and we can move to the next stage.
> > There must be more than 10 people on this mailing list that haven't
> > registered yet, that could do, and upvote a few questions (and also
> > raise some Python questions for consideration too)
> >
> > http://area51.stackexchange.com/proposals/96237/microbit
> >
> > David.
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
> ------------------------------
>
> End of Microbit Digest, Vol 12, Issue 35
> ****************************************
> ________________________________
>
>
> STEM Learning Limited registered in England and Wales, Company Number
> 05081097.
> Registered Office: National Science Learning Centre, University of York,
> Heslington, York, North Yorkshire, YO10 5DD
>
> This e-mail is intended only for the named recipient, may be confidential
> and may also be privileged. Please notify us immediately if you are not the
> intended recipient. You should not copy it, forward it or use it for any
> purpose or disclose the contents to any person. If you have received this
> e-mail in error, please notify us as soon as possible on +44 (0)1904328300
> and destroy your copy.
>
> Unless otherwise expressly stated, this e-mail is not intended to
> constitute a business letter, order form or other offer or invitation to
> you, nor does this e-mail form the basis of any contract. Contracts may not
> be concluded by e-mail and any contract or agreement attached is subject to
> contract and shall not and is not intended to create a legally binding
> relationship.
>
> STEM Learning Limited has taken reasonable precautions to ensure no
> viruses are present in this email and does not accept responsibility for
> any loss or damage arising from the use of this email or attachments. This
> email has been scanned by the Websense Email Security System. For more
> information please visit:
> http://www.websense.com/content/websense-email-security-products.aspx
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160601/33eb772a/attachment-0001.html>

From rob at rwilson.org.uk  Wed Jun  1 16:33:27 2016
From: rob at rwilson.org.uk (Rob Wilson)
Date: Wed, 1 Jun 2016 21:33:27 +0100
Subject: [Microbit-Python] Microbit in STEM
In-Reply-To: <CA+ziQAScqiRVndmwzASDqPGTZxdUOQsVPGOLuvPDO5jjiQp3Jg@mail.gmail.com>
References: <VI1PR0801MB158320AE47D0BEFDD0927A6AA6460@VI1PR0801MB1583.eurprd08.prod.outlook.com>
 <CA+ziQAScqiRVndmwzASDqPGTZxdUOQsVPGOLuvPDO5jjiQp3Jg@mail.gmail.com>
Message-ID: <1719B339-CB17-44A5-A263-591B6369EAEA@rwilson.org.uk>

And thanks from me too.
I have registered and posted.
Rob

> On 1 Jun 2016, at 15:30, Nigel Kendrick <nigel.kendrick at gmail.com> wrote:
> 
> Thanks Dave,
> 
> I've bookmarked the page, will register and see how I can contribute. Looks like a suitable place for back-end teams, with the Stack Exchange site servicing the users and hobbyists - no doubt many will contribute to both.
> 
> For what it's worth, I added a comment to a thread on The Register about the preorder announcement, encouraging people to head over to Area 51 at Stack Exchange and help push things along.
> 
>> On 31 May 2016 at 14:19, Dave Gibbs <D.Gibbs at stem.org.uk> wrote:
>> I'd be happy to host something in the National STEM Learning Centre online groups. We have micro:bit threads running in a couple:
>> https://www.stem.org.uk/community/groups/37459/physical-computing-and-robotics would be the ideal place.
>> 
>> Regards,
>> Dave
>> 
>> Dave Gibbs
>> STEM Computing & Technology Specialist
>> National STEM Learning Centre & Network / UK Space Education Office (ESERO-UK)
>> STEM Learning Ltd
>> 
>> Tel:      0044 (0)1904 328 362
>> Mob:   0044 (0) 7772 306 228
>> Email:  d.gibbs at stem.org.uk
>> 
>> Twitter: @adgibbs @STEMLearningLtd
>> Web: www.stem.org.uk and www.esero.org.uk
>> 
>> 
>> -----Original Message-----
>> From: Microbit [mailto:microbit-bounces+d.gibbs=nationalstemcentre.org.uk at python.org] On Behalf Of microbit-request at python.org
>> Sent: 31 May 2016 14:13
>> To: microbit at python.org
>> Subject: Microbit Digest, Vol 12, Issue 35
>> 
>> Send Microbit mailing list submissions to
>> microbit at python.org
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://mail.python.org/mailman/listinfo/microbit
>> or, via email, send a message with subject or body 'help' to
>> microbit-request at python.org
>> 
>> You can reach the person managing the list at
>> microbit-owner at python.org
>> 
>> When replying, please edit your Subject line so it is more specific than "Re: Contents of Microbit digest..."
>> 
>> 
>> Today's Topics:
>> 
>>    1.  Microbit in STEM (Rob Wilson)
>>    2. Re: Microbit in STEM (Nigel Kendrick)
>>    3. Re: Microbit in STEM (David Whale)
>>    4. Re: Microbit in STEM (Nicholas H.Tollervey)
>>    5. Re: Microbit in STEM (Loop Space)
>> 
>> 
>> ----------------------------------------------------------------------
>> 
>> Message: 1
>> Date: Tue, 31 May 2016 12:08:20 +0100
>> From: "Rob Wilson" <rob at rwilson.org.uk>
>> To: microbit at python.org
>> Subject: [Microbit-Python]  Microbit in STEM
>> Message-ID: <1021B079-C7AB-4EC4-B205-39734872CDC9 at rwilson.org.uk>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>> 
>> Hi Nigel
>> I like the idea of ?sharing knowledge etc?. Maybe a STEM microbit wiki or something?
>> 
>> I like the spectrum analyser! I?ve had a vague idea to write a singing coach (analyse voice pitch and display difference to played tone) which would need a Fourier Transform like that. Not done anything about it yet ?.
>> 
>> > Hi Rob,
>> >
>> > I am a STEM ambassador with micro:bit too. I'm hoping that the
>> > ambassador community can team up to share knowledge etc. but at the
>> > moment things are a bit fragmented. I have a few things in the
>> > pipeline - there's a few pics below and a video...
>> >
>> > https://imgur.com/a/Rn6Cr
>> >
>> > https://www.youtube.com/watch?app=desktop&persist_app=1&v=SE4Bb1NHyU4
>> >
>> > Nigel Kendrick
>> > aka Linker3000
>> 
>> 
>> ------------------------------
>> 
>> Message: 2
>> Date: Tue, 31 May 2016 13:09:56 +0100
>> From: Nigel Kendrick <nigel.kendrick at gmail.com>
>> To: For Pythonic MicroBit related discussions <microbit at python.org>
>> Subject: Re: [Microbit-Python] Microbit in STEM
>> Message-ID:
>> <CA+ziQARhOZKxnz3T2ATfSyKMHO42kMjU=pXq6nUvr06omJGMQw at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>> 
>> Hi Rob,
>> 
>> We'd just need a home for the wiki - do you have any good connections at STEM HQ that could help make it official, as opposed to just setting up a site somewhere? My contacts are all in the regional office and they seem to struggle to get traction back up the chain for anything. I have also considered 'partnering' with the BBC for a knowledge sharing section within their micro:bit site, but I am making no headway there.
>> 
>> Also, I am a new Ambassador so I haven't made many regional or national contacts yet - I'd love to find out 'where the action is' with regards to other STEM ambassadors working in IT/electronics.
>> 
>> Basic FFT on the micro:bit would be doable (a la Arduino etc.), but my configuration samples the audio in 5 fixed frequency bands on a external chip and sends a representative analogue voltage for each band to the micro:bit. The end-game is to have a board with the spectrum analyser chip, an electret mic with amplifier, a sound triggered logic signal and a class D bridge amp (it's quite loud, considering it's runnign from 3V!) all powered from the micro:bit.
>> 
>> All the best
>> 
>> --Nigel Kendrick
>> 
>> On 31 May 2016 at 12:08, Rob Wilson <rob at rwilson.org.uk> wrote:
>> 
>> > Hi Nigel
>> > I like the idea of ?sharing knowledge etc?. Maybe a STEM microbit wiki
>> > or something?
>> >
>> > I like the spectrum analyser! I?ve had a vague idea to write a singing
>> > coach (analyse voice pitch and display difference to played tone)
>> > which would need a Fourier Transform like that. Not done anything about it yet ?.
>> >
>> > Hi Rob,
>> >>
>> >> I am a STEM ambassador with micro:bit too. I'm hoping that the
>> >> ambassador community can team up to share knowledge etc. but at the
>> >> moment things are a bit fragmented. I have a few things in the
>> >> pipeline - there's a few pics below and a video...
>> >>
>> >> https://imgur.com/a/Rn6Cr
>> >>
>> >> https://www.youtube.com/watch?app=desktop&persist_app=1&v=SE4Bb1NHyU4
>> >>
>> >> Nigel Kendrick
>> >> aka Linker3000
>> >>
>> > _______________________________________________
>> > Microbit mailing list
>> > Microbit at python.org
>> > https://mail.python.org/mailman/listinfo/microbit
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://mail.python.org/pipermail/microbit/attachments/20160531/f3d8c4cb/attachment-0001.html>
>> 
>> ------------------------------
>> 
>> Message: 3
>> Date: Tue, 31 May 2016 13:25:32 +0100
>> From: David Whale <david at thinkingbinaries.com>
>> To: For Pythonic MicroBit related discussions <microbit at python.org>
>> Subject: Re: [Microbit-Python] Microbit in STEM
>> Message-ID:
>> <CABeH_SuuEK=a_jrDg8r1czu1P2ZXhFfXZb9k9QPVvnBH78uLPg at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>> 
>> Rob/Nigel,
>> 
>> There is a wiki already set up by a STEM ambassador, but it needs some energy behind it:
>> 
>> microbit.wiki
>> 
>> Also, we're all trying to get enough energy behind this Stack Overflow site, to build a self sustaining community, please join in! Only 10 more questions above a score of 10 and we can move to the next stage. There must be more than 10 people on this mailing list that haven't registered yet, that could do, and upvote a few questions (and also raise some Python questions for consideration too)
>> 
>> http://area51.stackexchange.com/proposals/96237/microbit
>> 
>> David.
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://mail.python.org/pipermail/microbit/attachments/20160531/a908b046/attachment-0001.html>
>> 
>> ------------------------------
>> 
>> Message: 4
>> Date: Tue, 31 May 2016 14:09:06 +0100
>> From: "Nicholas H.Tollervey" <ntoll at ntoll.org>
>> To: microbit at python.org
>> Subject: Re: [Microbit-Python] Microbit in STEM
>> Message-ID: <d4a3de49-554c-0758-b002-da7b844635b5 at ntoll.org>
>> Content-Type: text/plain; charset="windows-1252"
>> 
>> Hello from Portland (I'm at PyCon in the US at the moment).
>> 
>> I hope to be able to have some good news in the coming weeks about Python Software Foundation support for web based resources and community development around not just the micro:bit, but Pythonic education in general.
>> 
>> Yours hopefully,
>> 
>> N.
>> 
>> On 31/05/16 13:25, David Whale wrote:
>> > Rob/Nigel,
>> >
>> > There is a wiki already set up by a STEM ambassador, but it needs some
>> > energy behind it:
>> >
>> > microbit.wiki
>> >
>> > Also, we're all trying to get enough energy behind this Stack Overflow
>> > site, to build a self sustaining community, please join in! Only 10
>> > more questions above a score of 10 and we can move to the next stage.
>> > There must be more than 10 people on this mailing list that haven't
>> > registered yet, that could do, and upvote a few questions (and also
>> > raise some Python questions for consideration too)
>> >
>> > http://area51.stackexchange.com/proposals/96237/microbit
>> >
>> > David.
>> >
>> >
>> > _______________________________________________
>> > Microbit mailing list
>> > Microbit at python.org
>> > https://mail.python.org/mailman/listinfo/microbit
>> >
>> 
>> 
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: signature.asc
>> Type: application/pgp-signature
>> Size: 473 bytes
>> Desc: OpenPGP digital signature
>> URL: <http://mail.python.org/pipermail/microbit/attachments/20160531/4314b4d5/attachment-0001.sig>
>> 
>> ------------------------------
>> 
>> Message: 5
>> Date: Tue, 31 May 2016 14:12:45 +0100
>> From: Loop Space <loopspace at mathforge.org>
>> To: microbit at python.org
>> Subject: Re: [Microbit-Python] Microbit in STEM
>> Message-ID: <f84fe10d-0eb4-ba84-3ccd-1d403b028829 at mathforge.org>
>> Content-Type: text/plain; charset=windows-1252; format=flowed
>> 
>> RE the SE site, note that it's better to vote strategically in this stage.  The proposal needs questions with 10 or more votes, so if a question already has 10 or more votes then it is a somewhat wasted vote to vote on it given that people have limited number of votes at this point.
>> 
>> Andrew
>> 
>> On 31/05/2016 13:25, David Whale wrote:
>> > Rob/Nigel,
>> >
>> > There is a wiki already set up by a STEM ambassador, but it needs some
>> > energy behind it:
>> >
>> > microbit.wiki
>> >
>> > Also, we're all trying to get enough energy behind this Stack Overflow
>> > site, to build a self sustaining community, please join in! Only 10
>> > more questions above a score of 10 and we can move to the next stage.
>> > There must be more than 10 people on this mailing list that haven't
>> > registered yet, that could do, and upvote a few questions (and also
>> > raise some Python questions for consideration too)
>> >
>> > http://area51.stackexchange.com/proposals/96237/microbit
>> >
>> > David.
>> >
>> >
>> > _______________________________________________
>> > Microbit mailing list
>> > Microbit at python.org
>> > https://mail.python.org/mailman/listinfo/microbit
>> >
>> 
>> 
>> 
>> ------------------------------
>> 
>> Subject: Digest Footer
>> 
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>> 
>> 
>> ------------------------------
>> 
>> End of Microbit Digest, Vol 12, Issue 35
>> ****************************************
>> ________________________________
>> 
>> 
>> STEM Learning Limited registered in England and Wales, Company Number 05081097.
>> Registered Office: National Science Learning Centre, University of York, Heslington, York, North Yorkshire, YO10 5DD
>> 
>> This e-mail is intended only for the named recipient, may be confidential and may also be privileged. Please notify us immediately if you are not the intended recipient. You should not copy it, forward it or use it for any purpose or disclose the contents to any person. If you have received this e-mail in error, please notify us as soon as possible on +44 (0)1904328300 and destroy your copy.
>> 
>> Unless otherwise expressly stated, this e-mail is not intended to constitute a business letter, order form or other offer or invitation to you, nor does this e-mail form the basis of any contract. Contracts may not be concluded by e-mail and any contract or agreement attached is subject to contract and shall not and is not intended to create a legally binding relationship.
>> 
>> STEM Learning Limited has taken reasonable precautions to ensure no viruses are present in this email and does not accept responsibility for any loss or damage arising from the use of this email or attachments. This email has been scanned by the Websense Email Security System. For more information please visit: http://www.websense.com/content/websense-email-security-products.aspx
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160601/b08e7e75/attachment-0001.html>

From stewart at penguintutor.com  Thu Jun  2 03:17:44 2016
From: stewart at penguintutor.com (Stewart Watkiss)
Date: Thu, 2 Jun 2016 08:17:44 +0100
Subject: [Microbit-Python] Microbit in STEM
In-Reply-To: <mailman.1014.1464691112.1834.microbit@python.org>
References: <mailman.1014.1464691112.1834.microbit@python.org>
Message-ID: <574FDD98.1000400@penguintutor.com>

> I've just joined up, having been to a STEM event in Glos, introducing the microbit. Having retired last year I am now a STEM ambassador, helping out at a number of schools in this county.


Welcome to STEMNet. I'm also a STEM ambassador in Worcestershire, I've 
just renewed my membership (ie DBS check) so I've been a member 3 years now.

I've run and helped at a variety of different activities at schools 
around the county. Mostly these have been Scratch (CodeClub) or 
Raspberry Pi based so far, but I'm currently in touch with a school that 
is waiting for their micro:bits to arrive.

Other than my individual work with the schools I've found it quite hard 
to get traction towards more co-operation within STEMNet. One of the 
challenges is that I don't think there are so many in the Technology 
field in the county compared with the Science subjects. There are a few 
core members that I meet at events; they are mainly CodeClub volunteers.

The most successful events I've been involved with are a Raspberry Pi 
club (I've recently started attending "Slice of Pi" which is a Raspberry 
Pi club at Redditch HOW College) and the joint Code Club & Raspberry Jam 
events that Tim Wilson has been co-ordinating (Midlands co-ordinator for 
Code Club). We've had micro:bits at some of these events, but they have 
been quite rare so far. I've borrowed a micro:bit from the STEMNet 
county stock, but I've got two on pre-order for myself, so hope to show 
these off more at future events.

Stewart
--
@stewartwatkiss / @penguintutor



From rob at rwilson.org.uk  Sat Jun  4 05:47:59 2016
From: rob at rwilson.org.uk (Rob Wilson)
Date: Sat, 04 Jun 2016 10:47:59 +0100
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
Message-ID: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>

Hi,
I assume - maybe wrongly - that using the BBC micro:bit website for 
saving scripts, compiling etc is the way to go (if other routes are 
easier/better then please let me know).
I emailed the Beeb for the ?facilitator? code a week ago but 
haven?t heard anything back.
Is this normal?
Thanks,
Rob

From rob at rwilson.org.uk  Sat Jun  4 05:50:29 2016
From: rob at rwilson.org.uk (Rob Wilson)
Date: Sat, 04 Jun 2016 10:50:29 +0100
Subject: [Microbit-Python] Web page for this email list
Message-ID: <029C6694-A045-493C-84B2-B7DE47CAC046@rwilson.org.uk>

Hi again
I once found a web page for this email list, but can?t find it now 
(wrong search terms I guess).
It?s useful to trawl through previous threads.
Can anyone help?
Rob

From andrewferguson500 at gmail.com  Sat Jun  4 06:08:44 2016
From: andrewferguson500 at gmail.com (Andrew Ferguson)
Date: Sat, 4 Jun 2016 11:08:44 +0100
Subject: [Microbit-Python] Web page for this email list
In-Reply-To: <029C6694-A045-493C-84B2-B7DE47CAC046@rwilson.org.uk>
References: <029C6694-A045-493C-84B2-B7DE47CAC046@rwilson.org.uk>
Message-ID: <5752A8AC.7080904@gmail.com>

https://mail.python.org/mailman/listinfo/microbit

(Funnily enough it's actually in the email you sent - Mailman appends 
the link to every message that is sent.)

On 04/06/16 10:50, Rob Wilson wrote:
> Hi again
> I once found a web page for this email list, but can?t find it now 
> (wrong search terms I guess).
> It?s useful to trawl through previous threads.
> Can anyone help?
> Rob
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit


From nigel.kendrick at gmail.com  Sat Jun  4 07:46:02 2016
From: nigel.kendrick at gmail.com (Nigel Kendrick)
Date: Sat, 4 Jun 2016 12:46:02 +0100
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
In-Reply-To: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
References: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
Message-ID: <007b01d1be56$acbe90d0$063bb270$@gmail.com>

I asked the same question via the Web site as a STEM ambassador about two months ago. *Eventually* I received a reply that codes should be available 'shortly' via my local STEM team, but they haven't heard anything and the whole micro:bit project seems to have big holes in the joined-up thinking. It's like pulling teeth trying to make headway in some areas.

-- Nigel

-----Original Message-----
From: Microbit [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org] On Behalf Of Rob Wilson
Sent: 04 June 2016 10:48
To: microbit at python.org
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?

Hi,
I assume - maybe wrongly - that using the BBC micro:bit website for saving scripts, compiling etc is the way to go (if other routes are easier/better then please let me know).
I emailed the Beeb for the ?facilitator? code a week ago but haven?t heard anything back.
Is this normal?
Thanks,
Rob
_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


From rob at rwilson.org.uk  Sat Jun  4 10:13:15 2016
From: rob at rwilson.org.uk (Rob Wilson)
Date: Sat, 4 Jun 2016 15:13:15 +0100
Subject: [Microbit-Python] Web page for this email list
In-Reply-To: <5752A8AC.7080904@gmail.com>
References: <029C6694-A045-493C-84B2-B7DE47CAC046@rwilson.org.uk>
 <5752A8AC.7080904@gmail.com>
Message-ID: <D107D63E-3123-4CC6-9516-63EE1BBF6E36@rwilson.org.uk>

Ah, that link takes me to a page with, for example, change password.
But *not* the list of messages!
Am I missing something?

> On 4 Jun 2016, at 11:08, Andrew Ferguson <andrewferguson500 at gmail.com> wrote:
> 
> https://mail.python.org/mailman/listinfo/microbit
> 
> (Funnily enough it's actually in the email you sent - Mailman appends the link to every message that is sent.)
> 
>> On 04/06/16 10:50, Rob Wilson wrote:
>> Hi again
>> I once found a web page for this email list, but can?t find it now (wrong search terms I guess).
>> It?s useful to trawl through previous threads.
>> Can anyone help?
>> Rob
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit


From rob at rwilson.org.uk  Sat Jun  4 10:15:32 2016
From: rob at rwilson.org.uk (Rob Wilson)
Date: Sat, 4 Jun 2016 15:15:32 +0100
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
In-Reply-To: <007b01d1be56$acbe90d0$063bb270$@gmail.com>
References: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
 <007b01d1be56$acbe90d0$063bb270$@gmail.com>
Message-ID: <37FB7BA5-3AC4-4CBA-BF6D-1B21BE597371@rwilson.org.uk>

Thanks!
Is there a better way to develop Python on microbit?
I guess I could just copy/paste my scripts to a local editor rather than wait for the Beeb to send me a code!

> On 4 Jun 2016, at 12:46, Nigel Kendrick <nigel.kendrick at gmail.com> wrote:
> 
> I asked the same question via the Web site as a STEM ambassador about two months ago. *Eventually* I received a reply that codes should be available 'shortly' via my local STEM team, but they haven't heard anything and the whole micro:bit project seems to have big holes in the joined-up thinking. It's like pulling teeth trying to make headway in some areas.
> 
> -- Nigel
> 
> -----Original Message-----
> From: Microbit [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org] On Behalf Of Rob Wilson
> Sent: 04 June 2016 10:48
> To: microbit at python.org
> Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
> 
> Hi,
> I assume - maybe wrongly - that using the BBC micro:bit website for saving scripts, compiling etc is the way to go (if other routes are easier/better then please let me know).
> I emailed the Beeb for the ?facilitator? code a week ago but haven?t heard anything back.
> Is this normal?
> Thanks,
> Rob
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit


From ntoll at ntoll.org  Sat Jun  4 10:17:56 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Sat, 4 Jun 2016 15:17:56 +0100
Subject: [Microbit-Python] Web page for this email list
In-Reply-To: <D107D63E-3123-4CC6-9516-63EE1BBF6E36@rwilson.org.uk>
References: <029C6694-A045-493C-84B2-B7DE47CAC046@rwilson.org.uk>
 <5752A8AC.7080904@gmail.com>
 <D107D63E-3123-4CC6-9516-63EE1BBF6E36@rwilson.org.uk>
Message-ID: <5703d481-4f0f-9e99-5cff-2210a83ff808@ntoll.org>

Click the link (on the page you just referred to) where it says
"Archives" - it'll take you here:

https://mail.python.org/pipermail/microbit/

:-)

N.

On 04/06/16 15:13, Rob Wilson wrote:
> Ah, that link takes me to a page with, for example, change password.
> But *not* the list of messages!
> Am I missing something?
> 
>> On 4 Jun 2016, at 11:08, Andrew Ferguson <andrewferguson500 at gmail.com> wrote:
>>
>> https://mail.python.org/mailman/listinfo/microbit
>>
>> (Funnily enough it's actually in the email you sent - Mailman appends the link to every message that is sent.)
>>
>>> On 04/06/16 10:50, Rob Wilson wrote:
>>> Hi again
>>> I once found a web page for this email list, but can?t find it now (wrong search terms I guess).
>>> It?s useful to trawl through previous threads.
>>> Can anyone help?
>>> Rob
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160604/a02ee0b4/attachment-0001.sig>

From carlos.p.a.87 at gmail.com  Sat Jun  4 10:19:09 2016
From: carlos.p.a.87 at gmail.com (Carlos P.A.)
Date: Sat, 04 Jun 2016 14:19:09 +0000
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
In-Reply-To: <37FB7BA5-3AC4-4CBA-BF6D-1B21BE597371@rwilson.org.uk>
References: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
 <007b01d1be56$acbe90d0$063bb270$@gmail.com>
 <37FB7BA5-3AC4-4CBA-BF6D-1B21BE597371@rwilson.org.uk>
Message-ID: <CAC_p0yB1w7wfnQAw8VoXyFFiCXzhuJ+SN3yO_kpPe+PwDw7pVw@mail.gmail.com>

Check out the Mu editor if you haven't done so already: http://codewith.mu

On Sat, 4 Jun 2016 15:15 Rob Wilson, <rob at rwilson.org.uk> wrote:

> Thanks!
> Is there a better way to develop Python on microbit?
> I guess I could just copy/paste my scripts to a local editor rather than
> wait for the Beeb to send me a code!
>
> > On 4 Jun 2016, at 12:46, Nigel Kendrick <nigel.kendrick at gmail.com>
> wrote:
> >
> > I asked the same question via the Web site as a STEM ambassador about
> two months ago. *Eventually* I received a reply that codes should be
> available 'shortly' via my local STEM team, but they haven't heard anything
> and the whole micro:bit project seems to have big holes in the joined-up
> thinking. It's like pulling teeth trying to make headway in some areas.
> >
> > -- Nigel
> >
> > -----Original Message-----
> > From: Microbit [mailto:microbit-bounces+nigel.kendrick=
> gmail.com at python.org] On Behalf Of Rob Wilson
> > Sent: 04 June 2016 10:48
> > To: microbit at python.org
> > Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
> >
> > Hi,
> > I assume - maybe wrongly - that using the BBC micro:bit website for
> saving scripts, compiling etc is the way to go (if other routes are
> easier/better then please let me know).
> > I emailed the Beeb for the ?facilitator? code a week ago but haven?t
> heard anything back.
> > Is this normal?
> > Thanks,
> > Rob
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
> >
> > ---
> > This email has been checked for viruses by Avast antivirus software.
> > https://www.avast.com/antivirus
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160604/6fca1509/attachment.html>

From rob at rwilson.org.uk  Sat Jun  4 10:33:41 2016
From: rob at rwilson.org.uk (Rob Wilson)
Date: Sat, 4 Jun 2016 15:33:41 +0100
Subject: [Microbit-Python] Web page for this email list
In-Reply-To: <5703d481-4f0f-9e99-5cff-2210a83ff808@ntoll.org>
References: <029C6694-A045-493C-84B2-B7DE47CAC046@rwilson.org.uk>
 <5752A8AC.7080904@gmail.com>
 <D107D63E-3123-4CC6-9516-63EE1BBF6E36@rwilson.org.uk>
 <5703d481-4f0f-9e99-5cff-2210a83ff808@ntoll.org>
Message-ID: <6C824535-321F-41A2-A09E-996341558BEF@rwilson.org.uk>

Thanks, how did I miss that!

> On 4 Jun 2016, at 15:17, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:
> 
> Click the link (on the page you just referred to) where it says
> "Archives" - it'll take you here:
> 
> https://mail.python.org/pipermail/microbit/
> 
> :-)
> 
> N.
> 
>> On 04/06/16 15:13, Rob Wilson wrote:
>> Ah, that link takes me to a page with, for example, change password.
>> But *not* the list of messages!
>> Am I missing something?
>> 
>>> On 4 Jun 2016, at 11:08, Andrew Ferguson <andrewferguson500 at gmail.com> wrote:
>>> 
>>> https://mail.python.org/mailman/listinfo/microbit
>>> 
>>> (Funnily enough it's actually in the email you sent - Mailman appends the link to every message that is sent.)
>>> 
>>>> On 04/06/16 10:50, Rob Wilson wrote:
>>>> Hi again
>>>> I once found a web page for this email list, but can?t find it now (wrong search terms I guess).
>>>> It?s useful to trawl through previous threads.
>>>> Can anyone help?
>>>> Rob
>>>> _______________________________________________
>>>> Microbit mailing list
>>>> Microbit at python.org
>>>> https://mail.python.org/mailman/listinfo/microbit
>>> 
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>> 
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit


From ntoll at ntoll.org  Sat Jun  4 13:18:33 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Sat, 4 Jun 2016 18:18:33 +0100
Subject: [Microbit-Python] Web page for this email list
In-Reply-To: <6C824535-321F-41A2-A09E-996341558BEF@rwilson.org.uk>
References: <029C6694-A045-493C-84B2-B7DE47CAC046@rwilson.org.uk>
 <5752A8AC.7080904@gmail.com>
 <D107D63E-3123-4CC6-9516-63EE1BBF6E36@rwilson.org.uk>
 <5703d481-4f0f-9e99-5cff-2210a83ff808@ntoll.org>
 <6C824535-321F-41A2-A09E-996341558BEF@rwilson.org.uk>
Message-ID: <bd4348fc-78d3-9bbe-709c-c0a24c14e799@ntoll.org>

It's not really that obvious.

N.

On 04/06/16 15:33, Rob Wilson wrote:
> Thanks, how did I miss that!
> 
>> On 4 Jun 2016, at 15:17, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:
>>
>> Click the link (on the page you just referred to) where it says
>> "Archives" - it'll take you here:
>>
>> https://mail.python.org/pipermail/microbit/
>>
>> :-)
>>
>> N.
>>
>>> On 04/06/16 15:13, Rob Wilson wrote:
>>> Ah, that link takes me to a page with, for example, change password.
>>> But *not* the list of messages!
>>> Am I missing something?
>>>
>>>> On 4 Jun 2016, at 11:08, Andrew Ferguson <andrewferguson500 at gmail.com> wrote:
>>>>
>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>
>>>> (Funnily enough it's actually in the email you sent - Mailman appends the link to every message that is sent.)
>>>>
>>>>> On 04/06/16 10:50, Rob Wilson wrote:
>>>>> Hi again
>>>>> I once found a web page for this email list, but can?t find it now (wrong search terms I guess).
>>>>> It?s useful to trawl through previous threads.
>>>>> Can anyone help?
>>>>> Rob
>>>>> _______________________________________________
>>>>> Microbit mailing list
>>>>> Microbit at python.org
>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>
>>>> _______________________________________________
>>>> Microbit mailing list
>>>> Microbit at python.org
>>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160604/e697b167/attachment.sig>

From ntoll at ntoll.org  Sat Jun  4 13:21:29 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Sat, 4 Jun 2016 18:21:29 +0100
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
In-Reply-To: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
References: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
Message-ID: <ee4e4f01-82a6-da43-5f86-00e0c6d88fb6@ntoll.org>

On 04/06/16 10:47, Rob Wilson wrote:
> Hi,
> I assume - maybe wrongly - that using the BBC micro:bit website for
> saving scripts, compiling etc is the way to go (if other routes are
> easier/better then please let me know).
> I emailed the Beeb for the ?facilitator? code a week ago but haven?t
> heard anything back.
> Is this normal?
> Thanks,
> Rob
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

I wish the BBC had done a better job with the website. It was a painful
experience to create the Python editor for it.

Happily, I hope we'll have a Python only micro:bit website soon, with
the latest and greatest editor, tutorials and links to resources, not
just for the BBC micro:bit.

I'm pushing hard for this to happen, but it depends on the PSF board
releasing funds to pay for it.

N.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160604/3fd0322b/attachment.sig>

From rob at rwilson.org.uk  Sat Jun  4 13:41:40 2016
From: rob at rwilson.org.uk (Rob Wilson)
Date: Sat, 04 Jun 2016 18:41:40 +0100
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
In-Reply-To: <ee4e4f01-82a6-da43-5f86-00e0c6d88fb6@ntoll.org>
References: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
 <ee4e4f01-82a6-da43-5f86-00e0c6d88fb6@ntoll.org>
Message-ID: <0C06312F-9FF8-4F63-89C8-3E68AB17E723@rwilson.org.uk>

You?ve done a great job!

On 4 Jun 2016, at 18:21, Nicholas H.Tollervey wrote:

> On 04/06/16 10:47, Rob Wilson wrote:
>> Hi,
>> I assume - maybe wrongly - that using the BBC micro:bit website for
>> saving scripts, compiling etc is the way to go (if other routes are
>> easier/better then please let me know).
>> I emailed the Beeb for the ?facilitator? code a week ago but haven?t
>> heard anything back.
>> Is this normal?
>> Thanks,
>> Rob
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>
> I wish the BBC had done a better job with the website. It was a painful
> experience to create the Python editor for it.
>
> Happily, I hope we'll have a Python only micro:bit website soon, with
> the latest and greatest editor, tutorials and links to resources, not
> just for the BBC micro:bit.
>
> I'm pushing hard for this to happen, but it depends on the PSF board
> releasing funds to pay for it.
>
> N.
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

From ben at benmr.com  Sat Jun  4 16:29:48 2016
From: ben at benmr.com (Ben Mustill-Rose)
Date: Sat, 4 Jun 2016 21:29:48 +0100
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
In-Reply-To: <0C06312F-9FF8-4F63-89C8-3E68AB17E723@rwilson.org.uk>
References: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
 <ee4e4f01-82a6-da43-5f86-00e0c6d88fb6@ntoll.org>
 <0C06312F-9FF8-4F63-89C8-3E68AB17E723@rwilson.org.uk>
Message-ID: <CAC7gt1J4yaS=5+ujMuRj2vDmq3cBxv=OonfevsrH6S+EB_2Log@mail.gmail.com>

Would you still like a code now that you've been introduced to Mu?
I'll prod the relevant person on Monday for you if so. FYI the team's
a bit stretched at the moment which might be the cause of the delay.

On 6/4/16, Rob Wilson <rob at rwilson.org.uk> wrote:
> You?ve done a great job!
>
> On 4 Jun 2016, at 18:21, Nicholas H.Tollervey wrote:
>
>> On 04/06/16 10:47, Rob Wilson wrote:
>>> Hi,
>>> I assume - maybe wrongly - that using the BBC micro:bit website for
>>> saving scripts, compiling etc is the way to go (if other routes are
>>> easier/better then please let me know).
>>> I emailed the Beeb for the ?facilitator? code a week ago but haven?t
>>> heard anything back.
>>> Is this normal?
>>> Thanks,
>>> Rob
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>
>> I wish the BBC had done a better job with the website. It was a painful
>> experience to create the Python editor for it.
>>
>> Happily, I hope we'll have a Python only micro:bit website soon, with
>> the latest and greatest editor, tutorials and links to resources, not
>> just for the BBC micro:bit.
>>
>> I'm pushing hard for this to happen, but it depends on the PSF board
>> releasing funds to pay for it.
>>
>> N.
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>

From rob at rwilson.org.uk  Sat Jun  4 17:27:49 2016
From: rob at rwilson.org.uk (Rob Wilson)
Date: Sat, 4 Jun 2016 22:27:49 +0100
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
In-Reply-To: <CAC7gt1J4yaS=5+ujMuRj2vDmq3cBxv=OonfevsrH6S+EB_2Log@mail.gmail.com>
References: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
 <ee4e4f01-82a6-da43-5f86-00e0c6d88fb6@ntoll.org>
 <0C06312F-9FF8-4F63-89C8-3E68AB17E723@rwilson.org.uk>
 <CAC7gt1J4yaS=5+ujMuRj2vDmq3cBxv=OonfevsrH6S+EB_2Log@mail.gmail.com>
Message-ID: <240388B1-7AE2-4BC1-B994-26E940BBE227@rwilson.org.uk>

Yes please, I need to at least get familiar with it.
Thanks.

> On 4 Jun 2016, at 21:29, Ben Mustill-Rose <ben at benmr.com> wrote:
> 
> Would you still like a code now that you've been introduced to Mu?
> I'll prod the relevant person on Monday for you if so. FYI the team's
> a bit stretched at the moment which might be the cause of the delay.
> 
> On 6/4/16, Rob Wilson <rob at rwilson.org.uk> wrote:
>> You?ve done a great job!
>> 
>>> On 4 Jun 2016, at 18:21, Nicholas H.Tollervey wrote:
>>> 
>>>> On 04/06/16 10:47, Rob Wilson wrote:
>>>> Hi,
>>>> I assume - maybe wrongly - that using the BBC micro:bit website for
>>>> saving scripts, compiling etc is the way to go (if other routes are
>>>> easier/better then please let me know).
>>>> I emailed the Beeb for the ?facilitator? code a week ago but haven?t
>>>> heard anything back.
>>>> Is this normal?
>>>> Thanks,
>>>> Rob
>>>> _______________________________________________
>>>> Microbit mailing list
>>>> Microbit at python.org
>>>> https://mail.python.org/mailman/listinfo/microbit
>>> 
>>> I wish the BBC had done a better job with the website. It was a painful
>>> experience to create the Python editor for it.
>>> 
>>> Happily, I hope we'll have a Python only micro:bit website soon, with
>>> the latest and greatest editor, tutorials and links to resources, not
>>> just for the BBC micro:bit.
>>> 
>>> I'm pushing hard for this to happen, but it depends on the PSF board
>>> releasing funds to pay for it.
>>> 
>>> N.
>>> 
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit


From nigel.kendrick at gmail.com  Sat Jun  4 17:34:03 2016
From: nigel.kendrick at gmail.com (Nigel Kendrick)
Date: Sat, 4 Jun 2016 22:34:03 +0100
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
In-Reply-To: <CAC7gt1J4yaS=5+ujMuRj2vDmq3cBxv=OonfevsrH6S+EB_2Log@mail.gmail.com>
References: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
 <ee4e4f01-82a6-da43-5f86-00e0c6d88fb6@ntoll.org>
 <0C06312F-9FF8-4F63-89C8-3E68AB17E723@rwilson.org.uk>
 <CAC7gt1J4yaS=5+ujMuRj2vDmq3cBxv=OonfevsrH6S+EB_2Log@mail.gmail.com>
Message-ID: <CA+ziQASYdPctDJSOtpT0sCT2HExHW3-sPg1mrEMe4pSLa2GAww@mail.gmail.com>

I certainly would like a code as I have some project code I'd like to share.

If the team needs any help with workload and wants to enlist a STEM
ambassador on a voluntary basis feel free to pass on my name and contact
details; I'm keen to help where it would be of benefit.

-- Nigel Kendrick
On 4 Jun 2016 21:29, "Ben Mustill-Rose" <ben at benmr.com> wrote:

> Would you still like a code now that you've been introduced to Mu?
> I'll prod the relevant person on Monday for you if so. FYI the team's
> a bit stretched at the moment which might be the cause of the delay.
>
> On 6/4/16, Rob Wilson <rob at rwilson.org.uk> wrote:
> > You?ve done a great job!
> >
> > On 4 Jun 2016, at 18:21, Nicholas H.Tollervey wrote:
> >
> >> On 04/06/16 10:47, Rob Wilson wrote:
> >>> Hi,
> >>> I assume - maybe wrongly - that using the BBC micro:bit website for
> >>> saving scripts, compiling etc is the way to go (if other routes are
> >>> easier/better then please let me know).
> >>> I emailed the Beeb for the ?facilitator? code a week ago but haven?t
> >>> heard anything back.
> >>> Is this normal?
> >>> Thanks,
> >>> Rob
> >>> _______________________________________________
> >>> Microbit mailing list
> >>> Microbit at python.org
> >>> https://mail.python.org/mailman/listinfo/microbit
> >>
> >> I wish the BBC had done a better job with the website. It was a painful
> >> experience to create the Python editor for it.
> >>
> >> Happily, I hope we'll have a Python only micro:bit website soon, with
> >> the latest and greatest editor, tutorials and links to resources, not
> >> just for the BBC micro:bit.
> >>
> >> I'm pushing hard for this to happen, but it depends on the PSF board
> >> releasing funds to pay for it.
> >>
> >> N.
> >>
> >> _______________________________________________
> >> Microbit mailing list
> >> Microbit at python.org
> >> https://mail.python.org/mailman/listinfo/microbit
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160604/e63e8149/attachment-0001.html>

From nigel.kendrick at gmail.com  Sat Jun  4 17:36:30 2016
From: nigel.kendrick at gmail.com (Nigel Kendrick)
Date: Sat, 4 Jun 2016 22:36:30 +0100
Subject: [Microbit-Python] Getting a facilitator code for the BBC site?
In-Reply-To: <ee4e4f01-82a6-da43-5f86-00e0c6d88fb6@ntoll.org>
References: <BA133EF0-8E79-49AC-AA1F-4E779281CDDB@rwilson.org.uk>
 <ee4e4f01-82a6-da43-5f86-00e0c6d88fb6@ntoll.org>
Message-ID: <CA+ziQATAFx_ovOOUxAwQ=Hrmqey4fZQUOFEb7uL7Kkzu+wMdMw@mail.gmail.com>

That sounds like good news for the future. Keep up the good work. Happy to
help if you need testers.

-- Nigel
On 4 Jun 2016 18:21, "Nicholas H.Tollervey" <ntoll at ntoll.org> wrote:

> On 04/06/16 10:47, Rob Wilson wrote:
> > Hi,
> > I assume - maybe wrongly - that using the BBC micro:bit website for
> > saving scripts, compiling etc is the way to go (if other routes are
> > easier/better then please let me know).
> > I emailed the Beeb for the ?facilitator? code a week ago but haven?t
> > heard anything back.
> > Is this normal?
> > Thanks,
> > Rob
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
>
> I wish the BBC had done a better job with the website. It was a painful
> experience to create the Python editor for it.
>
> Happily, I hope we'll have a Python only micro:bit website soon, with
> the latest and greatest editor, tutorials and links to resources, not
> just for the BBC micro:bit.
>
> I'm pushing hard for this to happen, but it depends on the PSF board
> releasing funds to pay for it.
>
> N.
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160604/ce739a77/attachment.html>

From nigel.kendrick at gmail.com  Sun Jun  5 11:10:59 2016
From: nigel.kendrick at gmail.com (Nigel Kendrick)
Date: Sun, 5 Jun 2016 16:10:59 +0100
Subject: [Microbit-Python] working with micro:bit libraries
Message-ID: <00e301d1bf3c$7877dfc0$69679f40$@gmail.com>

Hi Everyone,

 

Here's the start of some code I am writing. Unless I include the "import
microbit" line, the code generates an error on the sleep line. What am I not
appreciating or is this correct?

 

from microbit import *

import microbit

 

while True:

 

    # Reset the external circuit and wait 1mS for things to settle

    pin2.write_digital(1)

    pin2.write_digital(0)

    microbit.sleep(1)

    

[snip]

 

Thanks

 

-- Nigel

 

 



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160605/308b8377/attachment.html>

From chris at c-mart.in  Sun Jun  5 12:22:44 2016
From: chris at c-mart.in (Chris Martin)
Date: Sun, 5 Jun 2016 09:22:44 -0700
Subject: [Microbit-Python] working with micro:bit libraries
In-Reply-To: <00e301d1bf3c$7877dfc0$69679f40$@gmail.com>
References: <00e301d1bf3c$7877dfc0$69679f40$@gmail.com>
Message-ID: <575451D4.8090107@c-mart.in>

Try `sleep(1)` instead of `microbit.sleep(1)`, then you can remove the
`import microbit` line. (Your star import in the first line makes the
sleep() function available in the local namespace so it doesn't need to
be prefixed with a module name.)

If you have three hours and want to deeply learn how all of this works,
I recommend David Beazley's talk on Modules and Packages from PyCon 2015:

https://www.youtube.com/watch?v=0oTh1CXRaQ0

Chris

On 06/05/2016 08:10 AM, Nigel Kendrick wrote:
> Hi Everyone,
> 
>  
> 
> Here?s the start of some code I am writing. Unless I include the ?import
> microbit? line, the code generates an error on the sleep line. What am I
> not appreciating or is this correct?
> 
>  
> 
> from microbit import *
> 
> import microbit
> 
>  
> 
> while True:
> 
>  
> 
>     # Reset the external circuit and wait 1mS for things to settle
> 
>     pin2.write_digital(1)
> 
>     pin2.write_digital(0)
> 
>     microbit.sleep(1)
> 
>    
> 
> [snip]
> 
>  
> 
> Thanks
> 
>  
> 
> -- Nigel
> 
>  
> 
>  
> 
> 
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> 	Virus-free. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> 
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 

From nigel.kendrick at gmail.com  Sun Jun  5 12:49:42 2016
From: nigel.kendrick at gmail.com (Nigel Kendrick)
Date: Sun, 5 Jun 2016 17:49:42 +0100
Subject: [Microbit-Python] working with micro:bit libraries
In-Reply-To: <575451D4.8090107@c-mart.in>
References: <00e301d1bf3c$7877dfc0$69679f40$@gmail.com>
 <575451D4.8090107@c-mart.in>
Message-ID: <00fb01d1bf4a$42959740$c7c0c5c0$@gmail.com>

Thanks Chris,

I wondered about that and did in fact try it, but I ended up with errors
elsewhere in my code. I am now an hour or so older and wiser and realise
that I have to remove the "microbit." references from all other lines too.

I'll check out the video and also the docs.

-- Nigel
-----Original Message-----
From: Microbit [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org]
On Behalf Of Chris Martin
Sent: 05 June 2016 17:23
To: For Pythonic MicroBit related discussions <microbit at python.org>
Subject: Re: [Microbit-Python] working with micro:bit libraries

Try `sleep(1)` instead of `microbit.sleep(1)`, then you can remove the
`import microbit` line. (Your star import in the first line makes the
sleep() function available in the local namespace so it doesn't need to be
prefixed with a module name.)

If you have three hours and want to deeply learn how all of this works, I
recommend David Beazley's talk on Modules and Packages from PyCon 2015:

https://www.youtube.com/watch?v=0oTh1CXRaQ0

Chris

On 06/05/2016 08:10 AM, Nigel Kendrick wrote:
> Hi Everyone,
> 
>  
> 
> Here's the start of some code I am writing. Unless I include the 
> "import microbit" line, the code generates an error on the sleep line. 
> What am I not appreciating or is this correct?
> 
>  
> 
> from microbit import *
> 
> import microbit
> 
>  
> 
> while True:
> 
>  
> 
>     # Reset the external circuit and wait 1mS for things to settle
> 
>     pin2.write_digital(1)
> 
>     pin2.write_digital(0)
> 
>     microbit.sleep(1)
> 
>    
> 
> [snip]
> 
>  
> 
> Thanks
> 
>  
> 
> -- Nigel
> 
>  
> 
>  
> 
> 
>
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai
gn=sig-email&utm_content=emailclient>
> 	Virus-free. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_
> campaign=sig-email&utm_content=emailclient>
> 
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 
_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


From coryanws at gmail.com  Mon Jun  6 10:32:38 2016
From: coryanws at gmail.com (Coryan)
Date: Mon, 6 Jun 2016 15:32:38 +0100
Subject: [Microbit-Python] Manipulating memory with Micropython
Message-ID: <f7990304-a5b1-1fb3-22dd-3a039814954a@gmail.com>

Hello folks,

Micropython seems to have a pretty cool module called "uctypes" which, 
amongst other things, allows you to access data from memory and work 
with it in your Python script as a bytes object.

I'd quite like to do something similar on the Micro:Bit, but it doesn't 
seem like uctypes or any of its contained functions are included in the 
Microbit module. Does anyone know if there are any other fuctions 
available that might do something similar?

Thanks so much for your help,

Best,
Coryan


From damien.p.george at gmail.com  Mon Jun  6 10:41:57 2016
From: damien.p.george at gmail.com (Damien George)
Date: Mon, 6 Jun 2016 15:41:57 +0100
Subject: [Microbit-Python] Manipulating memory with Micropython
In-Reply-To: <f7990304-a5b1-1fb3-22dd-3a039814954a@gmail.com>
References: <f7990304-a5b1-1fb3-22dd-3a039814954a@gmail.com>
Message-ID: <CANw+Mzm6C-tun5YHfLkCowcX+MOzzZFF2=F2CJjyzu3-bWVXPQ@mail.gmail.com>

You can try the (u)struct module:

>>> import struct
>>> buf = struct.pack('BHI', 1, 2, 3)
>>> buf
b'\x01\x00\x02\x00\x03\x00\x00\x00'
>>> struct.unpack('BHI', buf)
(1, 2, 3)

Only thing is that it can't access arbitrary memory at a specified
location, only bytes/bytearray objects.


On Mon, Jun 6, 2016 at 3:32 PM, Coryan <coryanws at gmail.com> wrote:
> Hello folks,
>
> Micropython seems to have a pretty cool module called "uctypes" which,
> amongst other things, allows you to access data from memory and work with it
> in your Python script as a bytes object.
>
> I'd quite like to do something similar on the Micro:Bit, but it doesn't seem
> like uctypes or any of its contained functions are included in the Microbit
> module. Does anyone know if there are any other fuctions available that
> might do something similar?
>
> Thanks so much for your help,
>
> Best,
> Coryan
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

From coryanws at gmail.com  Mon Jun  6 10:52:59 2016
From: coryanws at gmail.com (Coryan)
Date: Mon, 6 Jun 2016 15:52:59 +0100
Subject: [Microbit-Python] Microbit Digest, Vol 13, Issue 8
In-Reply-To: <mailman.474.1465224120.2305.microbit@python.org>
References: <mailman.474.1465224120.2305.microbit@python.org>
Message-ID: <062f0eac-0be1-20bf-d9ba-fda69aeb1473@gmail.com>

Hi Damien,

Thanks for that, I didn't know that struct was available to import - 
though unfortunately it's more the ability to access arbitrary memory 
that I need (I don't mind if it's returned as a bytes object, or a list 
of ints, or whatever else.)

Is there a list of all the modules I can import from Micropython?

Thanks for your help,

Best,
Coryan


> ------------------------------
>
> Message: 5
> Date: Mon, 6 Jun 2016 15:41:57 +0100
> From: Damien George <damien.p.george at gmail.com>
> To: For Pythonic MicroBit related discussions <microbit at python.org>
> Subject: Re: [Microbit-Python] Manipulating memory with Micropython
> Message-ID:
> 	<CANw+Mzm6C-tun5YHfLkCowcX+MOzzZFF2=F2CJjyzu3-bWVXPQ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> You can try the (u)struct module:
>
>>>> import struct
>>>> buf = struct.pack('BHI', 1, 2, 3)
>>>> buf
> b'\x01\x00\x02\x00\x03\x00\x00\x00'
>>>> struct.unpack('BHI', buf)
> (1, 2, 3)
>
> Only thing is that it can't access arbitrary memory at a specified
> location, only bytes/bytearray objects.
>
>
> On Mon, Jun 6, 2016 at 3:32 PM, Coryan <coryanws at gmail.com> wrote:
>> Hello folks,
>>
>> Micropython seems to have a pretty cool module called "uctypes" which,
>> amongst other things, allows you to access data from memory and work with it
>> in your Python script as a bytes object.
>>
>> I'd quite like to do something similar on the Micro:Bit, but it doesn't seem
>> like uctypes or any of its contained functions are included in the Microbit
>> module. Does anyone know if there are any other fuctions available that
>> might do something similar?
>>
>> Thanks so much for your help,
>>
>> Best,
>> Coryan
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>


From damien.p.george at gmail.com  Mon Jun  6 11:08:02 2016
From: damien.p.george at gmail.com (Damien George)
Date: Mon, 6 Jun 2016 16:08:02 +0100
Subject: [Microbit-Python] Microbit Digest, Vol 13, Issue 8
In-Reply-To: <062f0eac-0be1-20bf-d9ba-fda69aeb1473@gmail.com>
References: <mailman.474.1465224120.2305.microbit@python.org>
 <062f0eac-0be1-20bf-d9ba-fda69aeb1473@gmail.com>
Message-ID: <CANw+Mz=vDrV0FKqRMzPvTqVkWGnCFfY5HM4FNEQ=j6KSy4MWYw@mail.gmail.com>

No, there isn't any list of available module.  We really should make one!

If you want to be able to access arbitrary memory then uctypes is the
way to go (there is also machine.mem8/16/32 accessors for peek/poke
but they are also not enabled on the microbit).

We can enabled these features, but they take flash space and there's
not much left...

There is a way at the moment to access arbitrary memory, using inline assembler:

@micropython.asm_thumb
def peek(r0):
    ldr(r0, [r0, 0])

@micropython.asm_thumb
def poke(r0, r1):
    str(r1, [r0, 0])

The first argument is the memory address.  The second argument to poke
is the value to put.  They are both 32-bit accessor functions and the
address must be 4-byte aligned.




On Mon, Jun 6, 2016 at 3:52 PM, Coryan <coryanws at gmail.com> wrote:
> Hi Damien,
>
> Thanks for that, I didn't know that struct was available to import - though
> unfortunately it's more the ability to access arbitrary memory that I need
> (I don't mind if it's returned as a bytes object, or a list of ints, or
> whatever else.)
>
> Is there a list of all the modules I can import from Micropython?
>
> Thanks for your help,
>
> Best,
> Coryan
>
>
>> ------------------------------
>>
>> Message: 5
>> Date: Mon, 6 Jun 2016 15:41:57 +0100
>> From: Damien George <damien.p.george at gmail.com>
>> To: For Pythonic MicroBit related discussions <microbit at python.org>
>> Subject: Re: [Microbit-Python] Manipulating memory with Micropython
>> Message-ID:
>>
>> <CANw+Mzm6C-tun5YHfLkCowcX+MOzzZFF2=F2CJjyzu3-bWVXPQ at mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> You can try the (u)struct module:
>>
>>>>> import struct
>>>>> buf = struct.pack('BHI', 1, 2, 3)
>>>>> buf
>>
>> b'\x01\x00\x02\x00\x03\x00\x00\x00'
>>>>>
>>>>> struct.unpack('BHI', buf)
>>
>> (1, 2, 3)
>>
>> Only thing is that it can't access arbitrary memory at a specified
>> location, only bytes/bytearray objects.
>>
>>
>> On Mon, Jun 6, 2016 at 3:32 PM, Coryan <coryanws at gmail.com> wrote:
>>>
>>> Hello folks,
>>>
>>> Micropython seems to have a pretty cool module called "uctypes" which,
>>> amongst other things, allows you to access data from memory and work with
>>> it
>>> in your Python script as a bytes object.
>>>
>>> I'd quite like to do something similar on the Micro:Bit, but it doesn't
>>> seem
>>> like uctypes or any of its contained functions are included in the
>>> Microbit
>>> module. Does anyone know if there are any other fuctions available that
>>> might do something similar?
>>>
>>> Thanks so much for your help,
>>>
>>> Best,
>>> Coryan
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

From nevil.hunt at hotmail.co.uk  Tue Jun  7 14:02:29 2016
From: nevil.hunt at hotmail.co.uk (Nevil Hunt)
Date: Tue, 7 Jun 2016 19:02:29 +0100
Subject: [Microbit-Python] 
 =?cp1256?q?Maximum_Size_of_Microbit_Python_Pro?=
 =?cp1256?b?Z3JhbT/+?=
In-Reply-To: <DUB131-W445B000C6E17C3ECB4C3C5C36E0@phx.gbl>
References: <mailman.35.1461081602.28608.microbit@python.org>, ,
 <CAMkcNyyPujV69bzZRSHAyExxU6g2YvPsV_VX9qzjV1q6KFc7uQ@mail.gmail.com>,
 <DUB131-W445B000C6E17C3ECB4C3C5C36E0@phx.gbl>
Message-ID: <DUB131-W409484913DCF7B1D09992FC35D0@phx.gbl>

Hi All,
 
I'm still having problems hitting the maximum size of Python program that will run on the micro:bit with programs of very modest length (~150 lines)
Does any one know if anything can be done about it?
 
FYI I am compiling the Hex file using the Web interface.
I've also noticed that I can get a failing program to run if I delete a few lines of comments. Surely the compiled hex file doesn't include the comments, or does it?
 
 
Regards,
 
Nevil

 
 
From: nevil.hunt at hotmail.co.uk
To: microbit at python.org
Date: Thu, 21 Apr 2016 13:03:10 +0100
Subject: Re: [Microbit-Python]  Maximum Size of Microbit Python Program??




Hi Coryan,
 
Thanks for the info.
 
I'm programming using the Web interface rather than the stand alone Mu - whether that makes any difference to the size of the Hex file I don't know.
The Hex files from my Block programs seem to be 500 -573k
The Hex files from my Python programs seem to be 573 -595k where all programs up to 590k run OK. It's just the 595k one that doesn't
I don't know how the Hex file maps to the 256k, 65k & 8k you mention.
 
My concerns are two fold
1) Exceeding the size is silent - there is no error/warning when compiling or downloading
2) My program isn't that big! Only ~150 lines of code
 
I suspect it just need some s/w switch changing but that level of detail is beyond me!
 
Regards,
 
Nevil

 
Date: Wed, 20 Apr 2016 10:25:49 +0100
From: coryanws at gmail.com
To: microbit at python.org
Subject: Re: [Microbit-Python] Microbit Digest, Vol 11, Issue 10

Hello Nevil,

I may be wrong about some of these, but I believe the following are true:

 - The maximum size of the flash memory on an nRF51822 is 256 kilobytes
 - The width of the "Size" field in a MicroPython program header is 16 bits, which limits its size to 65 kilobytes.
 - The Mu IDE will refuse to flash scripts that are larger than 8192 bytes

The smallest of these is Mu's limit of 8kb, so that'd be the limit you'd hit first. Note that the actual size of the hex files you are generating will be larger than this, as they're in Intel Hex, not pure binary.

Hope that helps!
 - Coryan




On Tue, Apr 19, 2016 at 5:00 PM,  <microbit-request at python.org> wrote:
Send Microbit mailing list submissions to

        microbit at python.org



To subscribe or unsubscribe via the World Wide Web, visit

        https://mail.python.org/mailman/listinfo/microbit

or, via email, send a message with subject or body 'help' to

        microbit-request at python.org



You can reach the person managing the list at

        microbit-owner at python.org



When replying, please edit your Subject line so it is more specific

than "Re: Contents of Microbit digest..."





Today's Topics:



   1. Maximum Size of Microbit Python Program? (Nevil Hunt)





----------------------------------------------------------------------



Message: 1

Date: Mon, 18 Apr 2016 18:17:05 +0100

From: Nevil Hunt <nevil.hunt at hotmail.co.uk>

To: "microbit at python.org" <microbit at python.org>

Subject: [Microbit-Python] Maximum Size of Microbit Python Program?

Message-ID: <DUB131-W66074EA0FFD3E703617583C36B0 at phx.gbl>

Content-Type: text/plain; charset="iso-8859-1"



Hi,



I think I may have exceeded the maximum size a microbit Python Program can be!

My program compiles OK. Appears to download OK. But then doesn't run. There is no error message during the download and no error message on the microbit.

I'm fairly sure it's the program's size that's the problem as I've experimented gradually reducing the size of the program until it started to work again.



Does anyone know what is the maximum size a microbit Python Program can be?

And what is it limited by? Is it the size available in the micro:bit's Flash?

And how do I know how big my program is? Is it simply down to the size of the Hex file?

(I have a working program which is 590k and one that doesn't run which is 595k)



Thanks,



Nevil





-------------- next part --------------

An HTML attachment was scrubbed...

URL: <http://mail.python.org/pipermail/microbit/attachments/20160418/5b64fb20/attachment-0001.html>



------------------------------



Subject: Digest Footer



_______________________________________________

Microbit mailing list

Microbit at python.org

https://mail.python.org/mailman/listinfo/microbit





------------------------------



End of Microbit Digest, Vol 11, Issue 10

****************************************




_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit 		 	   		  

_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160607/41c23142/attachment.html>

From david at thinkingbinaries.com  Tue Jun  7 14:19:39 2016
From: david at thinkingbinaries.com (David Whale)
Date: Tue, 7 Jun 2016 19:19:39 +0100
Subject: [Microbit-Python] 
	=?utf-8?q?Maximum_Size_of_Microbit_Python_Prog?=
	=?utf-8?b?cmFtP+KAjw==?=
In-Reply-To: <DUB131-W409484913DCF7B1D09992FC35D0@phx.gbl>
References: <mailman.35.1461081602.28608.microbit@python.org>
 <CAMkcNyyPujV69bzZRSHAyExxU6g2YvPsV_VX9qzjV1q6KFc7uQ@mail.gmail.com>
 <DUB131-W445B000C6E17C3ECB4C3C5C36E0@phx.gbl>
 <DUB131-W409484913DCF7B1D09992FC35D0@phx.gbl>
Message-ID: <CABeH_Su5ZyQ4_E-teuMNKZqfYucdHZ2jEMcsNTb1br27Lvi24Q@mail.gmail.com>

Hi Neville,

I'm pretty sure the comments are included - the way it has always worked is
that the web interface just appends a small binary header and then your
python script to the embedded hex file it has cached in the browser. That
way, no processing of the script is required. i.e. hex = [MICROPYTHONHEX +
hex(BINARYHEADER) + hex(SCRIPT_INCLUDING_COMMENTS)]

Here is a Python version of the code that does that process:
https://github.com/bbcmicrobit/micropython/blob/master/tools/makecombinedhex.py


I believe that all that Nicholas does in the web interface is the same, but
in javascript, as it is easy.

That way, of course, just like all of the other editors, it is possible to
completely recreate the source from a .hex file (as kids have a habit of
not saving the source programs, or not keeping good records as to which
source program generated which hex program).

So yes, comments take up space.

There is a pending question on the area51 proposed stackexchange site at
the moment, where I ask how users can know in advance of flashing their
micro:bit, whether the program will fit or not. There seems to be no
obvious way in any of the editors of getting a read-out of how much of the
available memory is used *before* you flash it and find it doesn't fit.


The other thing to find out is whether you are running out of flash memory,
or running out of runtime memory. I would imagine that Damien's micropython
parser ignores comments as it iterates through the flash version of the
script file to parse it into bytecode in RAM - but you should check with
Damien for clarification of how to work out if this is 'running out of
flash' or 'running out of memory while parsing', as I can't find the code
for that at the moment

Damien?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160607/c327f3fd/attachment-0001.html>

From nevil.hunt at hotmail.co.uk  Tue Jun  7 15:32:42 2016
From: nevil.hunt at hotmail.co.uk (Nevil Hunt)
Date: Tue, 7 Jun 2016 20:32:42 +0100
Subject: [Microbit-Python] 
 =?cp1256?q?Maximum_Size_of_Microbit_Python_Pro?=
 =?cp1256?b?Z3JhbT/+?=
In-Reply-To: <CABeH_Su5ZyQ4_E-teuMNKZqfYucdHZ2jEMcsNTb1br27Lvi24Q@mail.gmail.com>
References: <mailman.35.1461081602.28608.microbit@python.org>,
 <CAMkcNyyPujV69bzZRSHAyExxU6g2YvPsV_VX9qzjV1q6KFc7uQ@mail.gmail.com>,
 <DUB131-W445B000C6E17C3ECB4C3C5C36E0@phx.gbl>,
 <DUB131-W409484913DCF7B1D09992FC35D0@phx.gbl>,
 <CABeH_Su5ZyQ4_E-teuMNKZqfYucdHZ2jEMcsNTb1br27Lvi24Q@mail.gmail.com>
Message-ID: <DUB131-W95D886D651FACC9BAD6FCC35D0@phx.gbl>

Thanks David,
 
I now see how it is done, so, yes, the comments will use up precious memory space.
 
FYI I've just tried downloading the latest stand-alone mu editor to see if that allows me to write bigger programs but it doesn't. When a program gets over the same size and I hit "download" nothing happens (i.e. the yellow led doesn't start to flash) but if I delete a few lines of comments, the download  then works.
 
It sounds like you have already lodged the issue that exceeding the program size limit whether from the web interface or from the mu editor is silent - thanks.
It then leaves the other issue as to whether anything can be done to increase the size of program that can be run. My program is really of very modest size.
 
Anyone else got any thoughts on the matter?
 
 
Nevil
 
From: david at thinkingbinaries.com
Date: Tue, 7 Jun 2016 19:19:39 +0100
To: microbit at python.org
Subject: Re: [Microbit-Python] 	Maximum Size of Microbit Python Program??

Hi Neville,
I'm pretty sure the comments are included - the way it has always worked is that the web interface just appends a small binary header and then your python script to the embedded hex file it has cached in the browser. That way, no processing of the script is required. i.e. hex = [MICROPYTHONHEX + hex(BINARYHEADER) + hex(SCRIPT_INCLUDING_COMMENTS)]
Here is a Python version of the code that does that process:https://github.com/bbcmicrobit/micropython/blob/master/tools/makecombinedhex.py


I believe that all that Nicholas does in the web interface is the same, but in javascript, as it is easy.
That way, of course, just like all of the other editors, it is possible to completely recreate the source from a .hex file (as kids have a habit of not saving the source programs, or not keeping good records as to which source program generated which hex program).
So yes, comments take up space.
There is a pending question on the area51 proposed stackexchange site at the moment, where I ask how users can know in advance of flashing their micro:bit, whether the program will fit or not. There seems to be no obvious way in any of the editors of getting a read-out of how much of the available memory is used *before* you flash it and find it doesn't fit.

The other thing to find out is whether you are running out of flash memory, or running out of runtime memory. I would imagine that Damien's micropython parser ignores comments as it iterates through the flash version of the script file to parse it into bytecode in RAM - but you should check with Damien for clarification of how to work out if this is 'running out of flash' or 'running out of memory while parsing', as I can't find the code for that at the moment
Damien?



_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160607/b94e4700/attachment.html>

From mschafer at wireframe.biz  Tue Jun  7 21:05:39 2016
From: mschafer at wireframe.biz (Mark Schafer)
Date: Wed, 8 Jun 2016 13:05:39 +1200
Subject: [Microbit-Python] 
 =?utf-8?q?Maximum_Size_of_Microbit_Python_Prog?=
 =?utf-8?b?cmFtP+KAjw==?=
In-Reply-To: <DUB131-W95D886D651FACC9BAD6FCC35D0@phx.gbl>
References: <mailman.35.1461081602.28608.microbit@python.org>
 <CAMkcNyyPujV69bzZRSHAyExxU6g2YvPsV_VX9qzjV1q6KFc7uQ@mail.gmail.com>
 <DUB131-W445B000C6E17C3ECB4C3C5C36E0@phx.gbl>
 <DUB131-W409484913DCF7B1D09992FC35D0@phx.gbl>
 <CABeH_Su5ZyQ4_E-teuMNKZqfYucdHZ2jEMcsNTb1br27Lvi24Q@mail.gmail.com>
 <DUB131-W95D886D651FACC9BAD6FCC35D0@phx.gbl>
Message-ID: <60bda24e-9fbf-4a92-c3f6-8692b94c967b@wireframe.biz>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160608/82c497be/attachment.html>

From ntoll at ntoll.org  Wed Jun  8 04:59:36 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Wed, 8 Jun 2016 09:59:36 +0100
Subject: [Microbit-Python] 
 =?utf-8?q?Maximum_Size_of_Microbit_Python_Prog?=
 =?utf-8?b?cmFtP+KAjw==?=
In-Reply-To: <60bda24e-9fbf-4a92-c3f6-8692b94c967b@wireframe.biz>
References: <mailman.35.1461081602.28608.microbit@python.org>
 <CAMkcNyyPujV69bzZRSHAyExxU6g2YvPsV_VX9qzjV1q6KFc7uQ@mail.gmail.com>
 <DUB131-W445B000C6E17C3ECB4C3C5C36E0@phx.gbl>
 <DUB131-W409484913DCF7B1D09992FC35D0@phx.gbl>
 <CABeH_Su5ZyQ4_E-teuMNKZqfYucdHZ2jEMcsNTb1br27Lvi24Q@mail.gmail.com>
 <DUB131-W95D886D651FACC9BAD6FCC35D0@phx.gbl>
 <60bda24e-9fbf-4a92-c3f6-8692b94c967b@wireframe.biz>
Message-ID: <5757DE78.6090102@ntoll.org>

Hi Folks,

Essentially, what David W. said about how it works. It won't make a
difference which environment you use to generate the hex, they work in
the same way.

Let me be very clear: there are two issues relating to "size".

1) The size of the script.
2) The amount of memory used when running the script.

I hope we're all agreed that we're talking about 1 in this instance. Put
simply, it's the size of the Python file that's important here. Think of
it as a measure of the number of characters. Less characters is good.

There is actually a way to get more space for Python files but that
depends upon the file system work we're currently close to landing /
documenting / tooling.

I'll provide more details when things become available.

Best wishes,

N.


On 08/06/16 02:05, Mark Schafer wrote:
> I ran into this problem early on where lots of comments making my code
> too large.
> I could not come up with a solution except some sort of mode in mu (or
> similar IDE) that stripped comments before sending. If you read the
> results back though - you have lost info.  So needs to be tightly
> coupled with IDE :(
> 
> Its an interesting problem because teaching people implies more comments
> but this limits the runnable size to smaller programs. I had to remove
> all of my embedded explanations.
> 
> 
> On 6/8/2016 7:32 AM, Nevil Hunt wrote:
>> Thanks David,
>>  
>> I now see how it is done, so, yes, the comments will use up precious
>> memory space.
>>  
>> FYI I've just tried downloading the latest stand-alone mu editor to
>> see if that allows me to write bigger programs but it doesn't. When a
>> program gets over the same size and I hit "download" nothing happens
>> (i.e. the yellow led doesn't start to flash) but if I delete a few
>> lines of comments, the download  then works.
>>  
>> It sounds like you have already lodged the issue that exceeding the
>> program size limit whether from the web interface or from the mu
>> editor is silent - thanks.
>> It then leaves the other issue as to whether anything can be done to
>> increase the size of program that can be run. My program is really of
>> very modest size.
>>  
>> Anyone else got any thoughts on the matter?
>>  
>>  
>> Nevil
>>  
>> ------------------------------------------------------------------------
>> From: david at thinkingbinaries.com
>> Date: Tue, 7 Jun 2016 19:19:39 +0100
>> To: microbit at python.org
>> Subject: Re: [Microbit-Python] Maximum Size of Microbit Python Program????
>>
>> Hi Neville,
>>
>> I'm pretty sure the comments are included - the way it has always
>> worked is that the web interface just appends a small binary header
>> and then your python script to the embedded hex file it has cached in
>> the browser. That way, no processing of the script is required. i.e.
>> hex = [MICROPYTHONHEX + hex(BINARYHEADER) +
>> hex(SCRIPT_INCLUDING_COMMENTS)]
>>
>> Here is a Python version of the code that does that process:
>> https://github.com/bbcmicrobit/micropython/blob/master/tools/makecombinedhex.py
>>
>>
>> I believe that all that Nicholas does in the web interface is the
>> same, but in javascript, as it is easy.
>>
>> That way, of course, just like all of the other editors, it is
>> possible to completely recreate the source from a .hex file (as kids
>> have a habit of not saving the source programs, or not keeping good
>> records as to which source program generated which hex program).
>>
>> So yes, comments take up space.
>>
>> There is a pending question on the area51 proposed stackexchange site
>> at the moment, where I ask how users can know in advance of flashing
>> their micro:bit, whether the program will fit or not. There seems to
>> be no obvious way in any of the editors of getting a read-out of how
>> much of the available memory is used *before* you flash it and find it
>> doesn't fit.
>>
>>
>> The other thing to find out is whether you are running out of flash
>> memory, or running out of runtime memory. I would imagine that
>> Damien's micropython parser ignores comments as it iterates through
>> the flash version of the script file to parse it into bytecode in RAM
>> - but you should check with Damien for clarification of how to work
>> out if this is 'running out of flash' or 'running out of memory while
>> parsing', as I can't find the code for that at the moment
>>
>> Damien?
>>
>>
>>
>> _______________________________________________ Microbit mailing list
>> Microbit at python.org https://mail.python.org/mailman/listinfo/microbit
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>> No virus found in this message.
>> Checked by AVG - www.avg.com <http://www.avg.com>
>> Version: 2016.0.7639 / Virus Database: 4598/12379 - Release Date: 06/07/16
>>
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160608/c1b877fd/attachment-0001.sig>

From nevil.hunt at hotmail.co.uk  Wed Jun  8 06:13:41 2016
From: nevil.hunt at hotmail.co.uk (Nevil Hunt)
Date: Wed, 8 Jun 2016 11:13:41 +0100
Subject: [Microbit-Python] 
 =?utf-8?q?Maximum_Size_of_Microbit_Python_Prog?=
 =?utf-8?b?cmFtP+KAjw==?=
In-Reply-To: <5757DE78.6090102@ntoll.org>
References: <mailman.35.1461081602.28608.microbit@python.org>,
 <CAMkcNyyPujV69bzZRSHAyExxU6g2YvPsV_VX9qzjV1q6KFc7uQ@mail.gmail.com>,
 <DUB131-W445B000C6E17C3ECB4C3C5C36E0@phx.gbl>,
 <DUB131-W409484913DCF7B1D09992FC35D0@phx.gbl>,
 <CABeH_Su5ZyQ4_E-teuMNKZqfYucdHZ2jEMcsNTb1br27Lvi24Q@mail.gmail.com>,
 <DUB131-W95D886D651FACC9BAD6FCC35D0@phx.gbl>,
 <60bda24e-9fbf-4a92-c3f6-8692b94c967b@wireframe.biz>,
 <5757DE78.6090102@ntoll.org>
Message-ID: <DUB131-W14C17A288BE2530FD6017BC35E0@phx.gbl>

Hi Nick,
 
Thanks for your reply - it sounds like it's an issue you are actively looking into - thanks!
 
Yes, I'm fairly sure in my case it is the size of the script that is the problem, not the run time memory since reducing the number of comments makes it work.
 
Do you have even a rough idea at this stage of how much more space could be freed up and/or a target for the maximum size script that you feel would be adequate?
 
Keep us posted with progress and keep up the good work!
 
 
Regards,
 
Nevil
 
From: ntoll at ntoll.org
To: microbit at python.org
Date: Wed, 8 Jun 2016 09:59:36 +0100
Subject: Re: [Microbit-Python]  Maximum Size of Microbit Python Program??

Hi Folks,
 
Essentially, what David W. said about how it works. It won't make a
difference which environment you use to generate the hex, they work in
the same way.
 
Let me be very clear: there are two issues relating to "size".
 
1) The size of the script.
2) The amount of memory used when running the script.
 
I hope we're all agreed that we're talking about 1 in this instance. Put
simply, it's the size of the Python file that's important here. Think of
it as a measure of the number of characters. Less characters is good.
 
There is actually a way to get more space for Python files but that
depends upon the file system work we're currently close to landing /
documenting / tooling.
 
I'll provide more details when things become available.
 
Best wishes,
 
N.
 
 
On 08/06/16 02:05, Mark Schafer wrote:
> I ran into this problem early on where lots of comments making my code
> too large.
> I could not come up with a solution except some sort of mode in mu (or
> similar IDE) that stripped comments before sending. If you read the
> results back though - you have lost info.  So needs to be tightly
> coupled with IDE :(
> 
> Its an interesting problem because teaching people implies more comments
> but this limits the runnable size to smaller programs. I had to remove
> all of my embedded explanations.
> 
> 
> On 6/8/2016 7:32 AM, Nevil Hunt wrote:
>> Thanks David,
>>  
>> I now see how it is done, so, yes, the comments will use up precious
>> memory space.
>>  
>> FYI I've just tried downloading the latest stand-alone mu editor to
>> see if that allows me to write bigger programs but it doesn't. When a
>> program gets over the same size and I hit "download" nothing happens
>> (i.e. the yellow led doesn't start to flash) but if I delete a few
>> lines of comments, the download  then works.
>>  
>> It sounds like you have already lodged the issue that exceeding the
>> program size limit whether from the web interface or from the mu
>> editor is silent - thanks.
>> It then leaves the other issue as to whether anything can be done to
>> increase the size of program that can be run. My program is really of
>> very modest size.
>>  
>> Anyone else got any thoughts on the matter?
>>  
>>  
>> Nevil
>>  
>> ------------------------------------------------------------------------
>> From: david at thinkingbinaries.com
>> Date: Tue, 7 Jun 2016 19:19:39 +0100
>> To: microbit at python.org
>> Subject: Re: [Microbit-Python] Maximum Size of Microbit Python Program????
>>
>> Hi Neville,
>>
>> I'm pretty sure the comments are included - the way it has always
>> worked is that the web interface just appends a small binary header
>> and then your python script to the embedded hex file it has cached in
>> the browser. That way, no processing of the script is required. i.e.
>> hex = [MICROPYTHONHEX + hex(BINARYHEADER) +
>> hex(SCRIPT_INCLUDING_COMMENTS)]
>>
>> Here is a Python version of the code that does that process:
>> https://github.com/bbcmicrobit/micropython/blob/master/tools/makecombinedhex.py
>>
>>
>> I believe that all that Nicholas does in the web interface is the
>> same, but in javascript, as it is easy.
>>
>> That way, of course, just like all of the other editors, it is
>> possible to completely recreate the source from a .hex file (as kids
>> have a habit of not saving the source programs, or not keeping good
>> records as to which source program generated which hex program).
>>
>> So yes, comments take up space.
>>
>> There is a pending question on the area51 proposed stackexchange site
>> at the moment, where I ask how users can know in advance of flashing
>> their micro:bit, whether the program will fit or not. There seems to
>> be no obvious way in any of the editors of getting a read-out of how
>> much of the available memory is used *before* you flash it and find it
>> doesn't fit.
>>
>>
>> The other thing to find out is whether you are running out of flash
>> memory, or running out of runtime memory. I would imagine that
>> Damien's micropython parser ignores comments as it iterates through
>> the flash version of the script file to parse it into bytecode in RAM
>> - but you should check with Damien for clarification of how to work
>> out if this is 'running out of flash' or 'running out of memory while
>> parsing', as I can't find the code for that at the moment
>>
>> Damien?
>>
>>
>>
>> _______________________________________________ Microbit mailing list
>> Microbit at python.org https://mail.python.org/mailman/listinfo/microbit
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>> No virus found in this message.
>> Checked by AVG - www.avg.com <http://www.avg.com>
>> Version: 2016.0.7639 / Virus Database: 4598/12379 - Release Date: 06/07/16
>>
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 
 
 
 

_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160608/2cbaf202/attachment.html>

From mail at timgolden.me.uk  Fri Jun 10 06:37:27 2016
From: mail at timgolden.me.uk (Tim Golden)
Date: Fri, 10 Jun 2016 11:37:27 +0100
Subject: [Microbit-Python] [slightly OT] Using micro:bit to teach Assembler
Message-ID: <575A9867.3040708@timgolden.me.uk>

A teacher friend of mine asked whether micro:bits could be used to teach
Assembler? (I pointed out that something like a RPi setup might be
easier, given the volume of material available for RPi & Linux in
general. He responded that he has about 6 Raspberry Pis but 120 Microbits!)

Until a comment by Damien on this list the other day I hadn't realised
that MicroPython could generate inline assembler:

  https://micropython.org/doc/tut-asm

and that does look like a very a nice compromise. I haven't tried it out
yet but the examples obviously apply to the pyboard. As far as I can
tell, they share an instruction set, but I'm not sure where to look to
find the equivalent details (memory addresses etc.) to, eg, light an LED
on the micro:bit.

Is this feasible? Have I misunderstood anything?

TJG

From nigel.kendrick at gmail.com  Fri Jun 10 07:37:36 2016
From: nigel.kendrick at gmail.com (Nigel Kendrick)
Date: Fri, 10 Jun 2016 12:37:36 +0100
Subject: [Microbit-Python] Pulsing I/O pins
Message-ID: <CA+ziQAQe-5zfibe8oGJM6wW8CUCEcFQtLUZrkFb=cyiVcgmOGw@mail.gmail.com>

Hi folks,

I had to take some timing measurements so I thought I'd share just in case
it's of use:

For those without access to a 'scope (or who can't be bothered to drag it
out!), if you toggle an I/O pin by writing something like this in the Block
Editor:

digital write 0 to pin P2
digital write 1 to pin P2
digital write 0 to pin P2

You get a pulse with a 5uS duration.

Adding extra 'high' stages adds 5uS per stage - example:

digital write 0 to pin P2
digital write 1 to pin P2
digital write 1 to pin P2
digital write 0 to pin P2

Gives a 10uS pulse and so on.

Repeating the same experiment in micropython, things are slower because the
language is interpreted:

from microbit import *

pin2.write_digital(0)

while True:
    pin2.write_digital(1)
    pin2.write_digital(0)
    sleep(1)
# End of while loop

1 x pin2.write_digital(1) = 68uS

2 x pin2.write_digital(1) = 136uS

etc.

You could stretch the timing using loops - and above 1mS you could
pause/sleep - but just repeating the pin writes seems more controlled and
easier to work out.

I tried padding the highs with comments - eg:

while True:
    pin2.write_digital(1)
    #
    #
    pin2.write_digital(0)
    sleep(1)
# End of while loop

but the difference, if anything, was negligible.

-- Nigel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160610/8a075e20/attachment.html>

From microbit at sheep.art.pl  Fri Jun 10 07:47:11 2016
From: microbit at sheep.art.pl (Radomir Dopieralski)
Date: Fri, 10 Jun 2016 13:47:11 +0200
Subject: [Microbit-Python] Pulsing I/O pins
In-Reply-To: <CA+ziQAQe-5zfibe8oGJM6wW8CUCEcFQtLUZrkFb=cyiVcgmOGw@mail.gmail.com>
References: <CA+ziQAQe-5zfibe8oGJM6wW8CUCEcFQtLUZrkFb=cyiVcgmOGw@mail.gmail.com>
Message-ID: <20160610134711.78241523@ghostwheel>

I'm not sure this is a good way to time things. It may change
arbitrarily with updates or even depending on the version of compiler
you use to compile the micropython code...

Comments will not have any effect, because Micropython is not, in fact,
an "interpreted" language in the sense that BASIC was. It is compiled
into bytecode, that is then executed on a virtual machine. Comments get
removed in the compilation step.

On Fri, 10 Jun 2016 12:37:36 +0100
Nigel Kendrick <nigel.kendrick at gmail.com> wrote:

> Hi folks,
> 
> I had to take some timing measurements so I thought I'd share just in
> case it's of use:
> 
> For those without access to a 'scope (or who can't be bothered to
> drag it out!), if you toggle an I/O pin by writing something like
> this in the Block Editor:
> 
> digital write 0 to pin P2
> digital write 1 to pin P2
> digital write 0 to pin P2
> 
> You get a pulse with a 5uS duration.
> 
> Adding extra 'high' stages adds 5uS per stage - example:
> 
> digital write 0 to pin P2
> digital write 1 to pin P2
> digital write 1 to pin P2
> digital write 0 to pin P2
> 
> Gives a 10uS pulse and so on.
> 
> Repeating the same experiment in micropython, things are slower
> because the language is interpreted:
> 
> from microbit import *
> 
> pin2.write_digital(0)
> 
> while True:
>     pin2.write_digital(1)
>     pin2.write_digital(0)
>     sleep(1)
> # End of while loop
https://bitbucket.org/thesheep/micropython-ili9341/src/4fe3cd28006e171eec16aff9e7cbae8ed394f88d/ili9341.py?fileviewer=file-view-default#ili9341.py-142:157> 
> 1 x pin2.write_digital(1) = 68uS
> 
> 2 x pin2.write_digital(1) = 136uS
> 
> etc.
> 
> You could stretch the timing using loops - and above 1mS you could
> pause/sleep - but just repeating the pin writes seems more controlled
> and easier to work out.
> 
> I tried padding the highs with comments - eg:
> 
> while True:
>     pin2.write_digital(1)
>     #
>     #
>     pin2.write_digital(0)
>     sleep(1)
> # End of while loop
> 
> but the difference, if anything, was negligible.
> 
> -- Nigel



-- 
Radomir Dopieralski

-- 
Radomir Dopieralski

From nigel.kendrick at gmail.com  Fri Jun 10 08:06:44 2016
From: nigel.kendrick at gmail.com (Nigel Kendrick)
Date: Fri, 10 Jun 2016 13:06:44 +0100
Subject: [Microbit-Python] Pulsing I/O pins
In-Reply-To: <20160610134711.78241523@ghostwheel>
References: <CA+ziQAQe-5zfibe8oGJM6wW8CUCEcFQtLUZrkFb=cyiVcgmOGw@mail.gmail.com>
 <20160610134711.78241523@ghostwheel>
Message-ID: <CA+ziQASE5bBTOnPf3+-i_4S4w-H0AC+wKa-k_22JKWu7VM1UVw@mail.gmail.com>

Agreed on both counts (timing and bytecode) - just keeping things simple!

On 10 June 2016 at 12:47, Radomir Dopieralski <microbit at sheep.art.pl> wrote:

> I'm not sure this is a good way to time things. It may change
> arbitrarily with updates or even depending on the version of compiler
> you use to compile the micropython code...
>
> Comments will not have any effect, because Micropython is not, in fact,
> an "interpreted" language in the sense that BASIC was. It is compiled
> into bytecode, that is then executed on a virtual machine. Comments get
> removed in the compilation step.
>
> On Fri, 10 Jun 2016 12:37:36 +0100
> Nigel Kendrick <nigel.kendrick at gmail.com> wrote:
>
> > Hi folks,
> >
> > I had to take some timing measurements so I thought I'd share just in
> > case it's of use:
> >
> > For those without access to a 'scope (or who can't be bothered to
> > drag it out!), if you toggle an I/O pin by writing something like
> > this in the Block Editor:
> >
> > digital write 0 to pin P2
> > digital write 1 to pin P2
> > digital write 0 to pin P2
> >
> > You get a pulse with a 5uS duration.
> >
> > Adding extra 'high' stages adds 5uS per stage - example:
> >
> > digital write 0 to pin P2
> > digital write 1 to pin P2
> > digital write 1 to pin P2
> > digital write 0 to pin P2
> >
> > Gives a 10uS pulse and so on.
> >
> > Repeating the same experiment in micropython, things are slower
> > because the language is interpreted:
> >
> > from microbit import *
> >
> > pin2.write_digital(0)
> >
> > while True:
> >     pin2.write_digital(1)
> >     pin2.write_digital(0)
> >     sleep(1)
> > # End of while loop
>
> https://bitbucket.org/thesheep/micropython-ili9341/src/4fe3cd28006e171eec16aff9e7cbae8ed394f88d/ili9341.py?fileviewer=file-view-default#ili9341.py-142:157
> >
> > 1 x pin2.write_digital(1) = 68uS
> >
> > 2 x pin2.write_digital(1) = 136uS
> >
> > etc.
> >
> > You could stretch the timing using loops - and above 1mS you could
> > pause/sleep - but just repeating the pin writes seems more controlled
> > and easier to work out.
> >
> > I tried padding the highs with comments - eg:
> >
> > while True:
> >     pin2.write_digital(1)
> >     #
> >     #
> >     pin2.write_digital(0)
> >     sleep(1)
> > # End of while loop
> >
> > but the difference, if anything, was negligible.
> >
> > -- Nigel
>
>
>
> --
> Radomir Dopieralski
>
> --
> Radomir Dopieralski
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160610/fbba022a/attachment.html>

From nevil.hunt at hotmail.co.uk  Sat Jun 11 09:05:55 2016
From: nevil.hunt at hotmail.co.uk (Nevil Hunt)
Date: Sat, 11 Jun 2016 14:05:55 +0100
Subject: [Microbit-Python] Pulsing I/O pins
In-Reply-To: <CA+ziQASE5bBTOnPf3+-i_4S4w-H0AC+wKa-k_22JKWu7VM1UVw@mail.gmail.com>
References: <CA+ziQAQe-5zfibe8oGJM6wW8CUCEcFQtLUZrkFb=cyiVcgmOGw@mail.gmail.com>,
 <20160610134711.78241523@ghostwheel>,
 <CA+ziQASE5bBTOnPf3+-i_4S4w-H0AC+wKa-k_22JKWu7VM1UVw@mail.gmail.com>
Message-ID: <DUB131-W49EDDE3C811D9E34448597C3510@phx.gbl>

Hi Nigel,
 
FYI this article gives the pulse timing if programmed in 'C'
http://www.i-programmer.info/programming/hardware/9651-getting-started-with-cc-on-the-microbit.html?start=1

Nevil 
 
From: nigel.kendrick at gmail.com
Date: Fri, 10 Jun 2016 13:06:44 +0100
To: microbit at python.org
Subject: Re: [Microbit-Python] Pulsing I/O pins

Agreed on both counts (timing and bytecode) - just keeping things simple!

On 10 June 2016 at 12:47, Radomir Dopieralski <microbit at sheep.art.pl> wrote:
I'm not sure this is a good way to time things. It may change

arbitrarily with updates or even depending on the version of compiler

you use to compile the micropython code...



Comments will not have any effect, because Micropython is not, in fact,

an "interpreted" language in the sense that BASIC was. It is compiled

into bytecode, that is then executed on a virtual machine. Comments get

removed in the compilation step.



On Fri, 10 Jun 2016 12:37:36 +0100

Nigel Kendrick <nigel.kendrick at gmail.com> wrote:



> Hi folks,

>

> I had to take some timing measurements so I thought I'd share just in

> case it's of use:

>

> For those without access to a 'scope (or who can't be bothered to

> drag it out!), if you toggle an I/O pin by writing something like

> this in the Block Editor:

>

> digital write 0 to pin P2

> digital write 1 to pin P2

> digital write 0 to pin P2

>

> You get a pulse with a 5uS duration.

>

> Adding extra 'high' stages adds 5uS per stage - example:

>

> digital write 0 to pin P2

> digital write 1 to pin P2

> digital write 1 to pin P2

> digital write 0 to pin P2

>

> Gives a 10uS pulse and so on.

>

> Repeating the same experiment in micropython, things are slower

> because the language is interpreted:

>

> from microbit import *

>

> pin2.write_digital(0)

>

> while True:

>     pin2.write_digital(1)

>     pin2.write_digital(0)

>     sleep(1)

> # End of while loop

https://bitbucket.org/thesheep/micropython-ili9341/src/4fe3cd28006e171eec16aff9e7cbae8ed394f88d/ili9341.py?fileviewer=file-view-default#ili9341.py-142:157>

> 1 x pin2.write_digital(1) = 68uS

>

> 2 x pin2.write_digital(1) = 136uS

>

> etc.

>

> You could stretch the timing using loops - and above 1mS you could

> pause/sleep - but just repeating the pin writes seems more controlled

> and easier to work out.

>

> I tried padding the highs with comments - eg:

>

> while True:

>     pin2.write_digital(1)

>     #

>     #

>     pin2.write_digital(0)

>     sleep(1)

> # End of while loop

>

> but the difference, if anything, was negligible.

>

> -- Nigel







--

Radomir Dopieralski



--

Radomir Dopieralski

_______________________________________________

Microbit mailing list

Microbit at python.org

https://mail.python.org/mailman/listinfo/microbit




_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160611/0c6bd662/attachment.html>

From damien.p.george at gmail.com  Sat Jun 11 09:07:32 2016
From: damien.p.george at gmail.com (Damien George)
Date: Sat, 11 Jun 2016 14:07:32 +0100
Subject: [Microbit-Python] Pulsing I/O pins
In-Reply-To: <CA+ziQASE5bBTOnPf3+-i_4S4w-H0AC+wKa-k_22JKWu7VM1UVw@mail.gmail.com>
References: <CA+ziQAQe-5zfibe8oGJM6wW8CUCEcFQtLUZrkFb=cyiVcgmOGw@mail.gmail.com>
 <20160610134711.78241523@ghostwheel>
 <CA+ziQASE5bBTOnPf3+-i_4S4w-H0AC+wKa-k_22JKWu7VM1UVw@mail.gmail.com>
Message-ID: <CANw+Mz=Hi82WayoiwJgaC8NkR-K5mZ_kgv+67_yK7zHpnn2a6w@mail.gmail.com>

If your aim is to make short pulses on a pin, try using the SPI
peripheral and writing a bit pattern that has a pulse.

On Fri, Jun 10, 2016 at 1:06 PM, Nigel Kendrick
<nigel.kendrick at gmail.com> wrote:
> Agreed on both counts (timing and bytecode) - just keeping things simple!
>
> On 10 June 2016 at 12:47, Radomir Dopieralski <microbit at sheep.art.pl> wrote:
>>
>> I'm not sure this is a good way to time things. It may change
>> arbitrarily with updates or even depending on the version of compiler
>> you use to compile the micropython code...
>>
>> Comments will not have any effect, because Micropython is not, in fact,
>> an "interpreted" language in the sense that BASIC was. It is compiled
>> into bytecode, that is then executed on a virtual machine. Comments get
>> removed in the compilation step.
>>
>> On Fri, 10 Jun 2016 12:37:36 +0100
>> Nigel Kendrick <nigel.kendrick at gmail.com> wrote:
>>
>> > Hi folks,
>> >
>> > I had to take some timing measurements so I thought I'd share just in
>> > case it's of use:
>> >
>> > For those without access to a 'scope (or who can't be bothered to
>> > drag it out!), if you toggle an I/O pin by writing something like
>> > this in the Block Editor:
>> >
>> > digital write 0 to pin P2
>> > digital write 1 to pin P2
>> > digital write 0 to pin P2
>> >
>> > You get a pulse with a 5uS duration.
>> >
>> > Adding extra 'high' stages adds 5uS per stage - example:
>> >
>> > digital write 0 to pin P2
>> > digital write 1 to pin P2
>> > digital write 1 to pin P2
>> > digital write 0 to pin P2
>> >
>> > Gives a 10uS pulse and so on.
>> >
>> > Repeating the same experiment in micropython, things are slower
>> > because the language is interpreted:
>> >
>> > from microbit import *
>> >
>> > pin2.write_digital(0)
>> >
>> > while True:
>> >     pin2.write_digital(1)
>> >     pin2.write_digital(0)
>> >     sleep(1)
>> > # End of while loop
>>
>> https://bitbucket.org/thesheep/micropython-ili9341/src/4fe3cd28006e171eec16aff9e7cbae8ed394f88d/ili9341.py?fileviewer=file-view-default#ili9341.py-142:157>
>> > 1 x pin2.write_digital(1) = 68uS
>> >
>> > 2 x pin2.write_digital(1) = 136uS
>> >
>> > etc.
>> >
>> > You could stretch the timing using loops - and above 1mS you could
>> > pause/sleep - but just repeating the pin writes seems more controlled
>> > and easier to work out.
>> >
>> > I tried padding the highs with comments - eg:
>> >
>> > while True:
>> >     pin2.write_digital(1)
>> >     #
>> >     #
>> >     pin2.write_digital(0)
>> >     sleep(1)
>> > # End of while loop
>> >
>> > but the difference, if anything, was negligible.
>> >
>> > -- Nigel
>>
>>
>>
>> --
>> Radomir Dopieralski
>>
>> --
>> Radomir Dopieralski
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>

From damien.p.george at gmail.com  Sat Jun 11 09:18:20 2016
From: damien.p.george at gmail.com (Damien George)
Date: Sat, 11 Jun 2016 14:18:20 +0100
Subject: [Microbit-Python] [slightly OT] Using micro:bit to teach
 Assembler
In-Reply-To: <575A9867.3040708@timgolden.me.uk>
References: <575A9867.3040708@timgolden.me.uk>
Message-ID: <CANw+Mzkqe+qGKsVvXSEc6GtjGmrCou8XPNMff-q0RPmYM3ceaA@mail.gmail.com>

Yes, the @micropython.asm_thumb decorator works on the microbit.

See an example here:
https://github.com/bbcmicrobit/micropython/blob/master/examples/asmleds.py

The instruction set for the microbit is more restricted than pyboard
(Cortex M0 vs Cortex M4) but there's enough there to do everything.


On Fri, Jun 10, 2016 at 11:37 AM, Tim Golden <mail at timgolden.me.uk> wrote:
> A teacher friend of mine asked whether micro:bits could be used to teach
> Assembler? (I pointed out that something like a RPi setup might be
> easier, given the volume of material available for RPi & Linux in
> general. He responded that he has about 6 Raspberry Pis but 120 Microbits!)
>
> Until a comment by Damien on this list the other day I hadn't realised
> that MicroPython could generate inline assembler:
>
>   https://micropython.org/doc/tut-asm
>
> and that does look like a very a nice compromise. I haven't tried it out
> yet but the examples obviously apply to the pyboard. As far as I can
> tell, they share an instruction set, but I'm not sure where to look to
> find the equivalent details (memory addresses etc.) to, eg, light an LED
> on the micro:bit.
>
> Is this feasible? Have I misunderstood anything?
>
> TJG
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

From nigel.kendrick at gmail.com  Sat Jun 11 11:31:17 2016
From: nigel.kendrick at gmail.com (Nigel Kendrick)
Date: Sat, 11 Jun 2016 16:31:17 +0100
Subject: [Microbit-Python] Pulsing I/O pins
In-Reply-To: <CANw+Mz=Hi82WayoiwJgaC8NkR-K5mZ_kgv+67_yK7zHpnn2a6w@mail.gmail.com>
References: <CA+ziQAQe-5zfibe8oGJM6wW8CUCEcFQtLUZrkFb=cyiVcgmOGw@mail.gmail.com>
 <20160610134711.78241523@ghostwheel>
 <CA+ziQASE5bBTOnPf3+-i_4S4w-H0AC+wKa-k_22JKWu7VM1UVw@mail.gmail.com>
 <CANw+Mz=Hi82WayoiwJgaC8NkR-K5mZ_kgv+67_yK7zHpnn2a6w@mail.gmail.com>
Message-ID: <009401d1c3f6$4cb77e40$e6267ac0$@gmail.com>

Just to clarify; my initial posting was designed to be a general  guideline
and start point for teachers and pupils who need to strobe/clock external
peripherals and are aiming for pulse widths and inter-signal timing that
meets general specs. 

-- Nigel

-----Original Message-----
From: Microbit [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org]
On Behalf Of Damien George
Sent: 11 June 2016 14:08
To: For Pythonic MicroBit related discussions <microbit at python.org>
Subject: Re: [Microbit-Python] Pulsing I/O pins

If your aim is to make short pulses on a pin, try using the SPI peripheral
and writing a bit pattern that has a pulse.

On Fri, Jun 10, 2016 at 1:06 PM, Nigel Kendrick <nigel.kendrick at gmail.com>
wrote:
> Agreed on both counts (timing and bytecode) - just keeping things simple!
>
> On 10 June 2016 at 12:47, Radomir Dopieralski <microbit at sheep.art.pl>
wrote:
>>
>> I'm not sure this is a good way to time things. It may change 
>> arbitrarily with updates or even depending on the version of compiler 
>> you use to compile the micropython code...
>>
>> Comments will not have any effect, because Micropython is not, in 
>> fact, an "interpreted" language in the sense that BASIC was. It is 
>> compiled into bytecode, that is then executed on a virtual machine. 
>> Comments get removed in the compilation step.
>>
>> On Fri, 10 Jun 2016 12:37:36 +0100
>> Nigel Kendrick <nigel.kendrick at gmail.com> wrote:
>>
>> > Hi folks,
>> >
>> > I had to take some timing measurements so I thought I'd share just 
>> > in case it's of use:
>> >
>> > For those without access to a 'scope (or who can't be bothered to 
>> > drag it out!), if you toggle an I/O pin by writing something like 
>> > this in the Block Editor:
>> >
>> > digital write 0 to pin P2
>> > digital write 1 to pin P2
>> > digital write 0 to pin P2
>> >
>> > You get a pulse with a 5uS duration.
>> >
>> > Adding extra 'high' stages adds 5uS per stage - example:
>> >
>> > digital write 0 to pin P2
>> > digital write 1 to pin P2
>> > digital write 1 to pin P2
>> > digital write 0 to pin P2
>> >
>> > Gives a 10uS pulse and so on.
>> >
>> > Repeating the same experiment in micropython, things are slower 
>> > because the language is interpreted:
>> >
>> > from microbit import *
>> >
>> > pin2.write_digital(0)
>> >
>> > while True:
>> >     pin2.write_digital(1)
>> >     pin2.write_digital(0)
>> >     sleep(1)
>> > # End of while loop
>>
>> https://bitbucket.org/thesheep/micropython-ili9341/src/4fe3cd28006e17
>> 1eec16aff9e7cbae8ed394f88d/ili9341.py?fileviewer=file-view-default#il
>> i9341.py-142:157>
>> > 1 x pin2.write_digital(1) = 68uS
>> >
>> > 2 x pin2.write_digital(1) = 136uS
>> >
>> > etc.
>> >
>> > You could stretch the timing using loops - and above 1mS you could 
>> > pause/sleep - but just repeating the pin writes seems more 
>> > controlled and easier to work out.
>> >
>> > I tried padding the highs with comments - eg:
>> >
>> > while True:
>> >     pin2.write_digital(1)
>> >     #
>> >     #
>> >     pin2.write_digital(0)
>> >     sleep(1)
>> > # End of while loop
>> >
>> > but the difference, if anything, was negligible.
>> >
>> > -- Nigel
>>
>>
>>
>> --
>> Radomir Dopieralski
>>
>> --
>> Radomir Dopieralski
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


From mail at timgolden.me.uk  Sat Jun 11 16:37:33 2016
From: mail at timgolden.me.uk (Tim Golden)
Date: Sat, 11 Jun 2016 21:37:33 +0100
Subject: [Microbit-Python] [slightly OT] Using micro:bit to teach
 Assembler
In-Reply-To: <CANw+Mzkqe+qGKsVvXSEc6GtjGmrCou8XPNMff-q0RPmYM3ceaA@mail.gmail.com>
References: <575A9867.3040708@timgolden.me.uk>
 <CANw+Mzkqe+qGKsVvXSEc6GtjGmrCou8XPNMff-q0RPmYM3ceaA@mail.gmail.com>
Message-ID: <22a2712c-278f-b9a0-872e-b9bb4f4e267f@timgolden.me.uk>

On 11/06/2016 14:18, Damien George wrote:
> Yes, the @micropython.asm_thumb decorator works on the microbit.
>
> See an example here:
> https://github.com/bbcmicrobit/micropython/blob/master/examples/asmleds.py
>
> The instruction set for the microbit is more restricted than pyboard
> (Cortex M0 vs Cortex M4) but there's enough there to do everything.


Thanks very much: next time I'll think to check the examples first!

TJG

From f.vdd at telenet.be  Sat Jun 11 03:58:16 2016
From: f.vdd at telenet.be (on6fv)
Date: Sat, 11 Jun 2016 09:58:16 +0200
Subject: [Microbit-Python] microbit
Message-ID: <575BC498.50003@telenet.be>

Hello,

where can I buy a Microbit in Belgium?
With best regards.

Freddy


From chris at c-mart.in  Mon Jun 13 01:01:36 2016
From: chris at c-mart.in (Chris Martin)
Date: Sun, 12 Jun 2016 22:01:36 -0700
Subject: [Microbit-Python] Hacking an LCD Monitor with MicroPython on
 micro:bit
Message-ID: <575E3E30.5050309@c-mart.in>

This weekend I built my first hardware integration project with the
micro:bit:

https://blog.c-mart.in/posts/hacking-lcd-monitor-micropython

I'm happy to contribute the code to the overall project but it's
somewhat specific to my particular computer monitor. I intend this more
as a demonstration of how easy it is to build this kind of stuff.
MicroPython really reduced the incidental complexity and let me focus on
solving the problem.

Chris Martin

From rob at rwilson.org.uk  Mon Jun 13 03:25:27 2016
From: rob at rwilson.org.uk (Rob Wilson)
Date: Mon, 13 Jun 2016 08:25:27 +0100
Subject: [Microbit-Python] Hacking an LCD Monitor with MicroPython on
 micro:bit
In-Reply-To: <575E3E30.5050309@c-mart.in>
References: <575E3E30.5050309@c-mart.in>
Message-ID: <00909A71-8B5D-4CD6-8451-6DE1BD33E0E0@rwilson.org.uk>

Chris, a great write-up. I will post a comment on the blog.
Rob

> On 13 Jun 2016, at 06:01, Chris Martin <chris at c-mart.in> wrote:
> 
> This weekend I built my first hardware integration project with the
> micro:bit:
> 
> https://blog.c-mart.in/posts/hacking-lcd-monitor-micropython
> 
> I'm happy to contribute the code to the overall project but it's
> somewhat specific to my particular computer monitor. I intend this more
> as a demonstration of how easy it is to build this kind of stuff.
> MicroPython really reduced the incidental complexity and let me focus on
> solving the problem.
> 
> Chris Martin
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

From mail at stevesimmons.com  Mon Jun 13 19:56:24 2016
From: mail at stevesimmons.com (Stephen Simmons)
Date: Tue, 14 Jun 2016 00:56:24 +0100
Subject: [Microbit-Python] Microbit motion sensors at PyCon UK Teachers' Day
Message-ID: <575F4828.8040505@stevesimmons.com>

Hi everyone,


Would anyone like to help me put together a microbit session for the PyCon UK teachers' day using motion sensors? My plan is to use python on the microbit to illustrate some motion-related maths/physics principles from accelerometer/gyroscope data.

Ideally we would prepare some exercises with direct relevance to classwork that teachers could take back to their students and use right away.

So if you know microbits and are keen to help, get in touch!

If you are a teacher with ideas you'd to implement, or you know teachers with ideas, then get in touch too.

The deadline for proposals is in 2 weeks...

Cheers
Stephen

P.S. I have also submitted a proposal on sensor fusion algorithms for the main PyCon UK conference, using MetaWear PRO wearables. They can transmit 9-axis accelerometer/gyroscope/magnetometer data over Bluetooth in real time. The microbit, as I understand it (mine will arrive in 2 weeks...) doesn't have enough memory to load Python and Bluetooth together. So we will have to be more creative about logging/retrieving results. Plenty of time to work through this in July/August. First step is the proposal....

From ntoll at ntoll.org  Tue Jun 14 06:03:51 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Tue, 14 Jun 2016 11:03:51 +0100
Subject: [Microbit-Python] Hacking an LCD Monitor with MicroPython on
 micro:bit
In-Reply-To: <575E3E30.5050309@c-mart.in>
References: <575E3E30.5050309@c-mart.in>
Message-ID: <575FD687.8010604@ntoll.org>

On 13/06/16 06:01, Chris Martin wrote:
> This weekend I built my first hardware integration project with the
> micro:bit:
> 
> https://blog.c-mart.in/posts/hacking-lcd-monitor-micropython
> 
> I'm happy to contribute the code to the overall project but it's
> somewhat specific to my particular computer monitor. I intend this more
> as a demonstration of how easy it is to build this kind of stuff.
> MicroPython really reduced the incidental complexity and let me focus on
> solving the problem.
> 
> Chris Martin
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 

That's a great write up... ;-)

N.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160614/60034675/attachment.sig>

From nick.cook at newcastle.ac.uk  Tue Jun 14 13:22:28 2016
From: nick.cook at newcastle.ac.uk (Nick Cook)
Date: Tue, 14 Jun 2016 17:22:28 +0000
Subject: [Microbit-Python] microbit_stub - a Python module to test micro:bit
 Python programs
Message-ID: <D385FBE2.1C71E%nick.cook@newcastle.ac.uk>

I have released my microbit_stub module on github. It is  a Python module to test microbit micropython programs without needing a physical micro:bit, completely offline. You can do what you will with it from the github home:

<https://github.com/casnortheast/microbit_stub>https://github.com/casnortheast/microbit_stub

It as a textual "emulator" of the micro:bit (as defined by the microbit micropython API) that allows you to take a microbit micropython program and test it using the microbit_stub module. It is intended to be useful if you do not have a micro:bit, or if you are not using the offline mu editor with a REPL window and need something more than the error feedback on the micro:bit screen. Or it can just be used by pupils (and others!) to test program syntax and logic before running on the micro:bit (or after if they get an error and cannot easily work out what the problem is). Programs using this module should run in any Python IDE (including IDLE) and at the command line.

Some documentation, tests and example programs are on the github page (including simple support for simulation of microbit state).

It should work with any microbit program by changing the import statement to import "microbit_stub" instead of "microbit". There is also a sub directory in the release that uses "microbit" as the module name and, therefore, does not require any change to an existing program (you will see from the README that I am not undecided about which approach to take :).

I may at some point extend the module to provide a graphical emulation (or the option of it). Peter Dring has produced a Web-based micro:bit Python simulator that could also be of interest (it is intended for a different usage to this module) - see: http://community.computingatschool.org.uk/resources/4479. And there is David Whale's minecraft micro:bit, see: https://github.com/whaleygeek/mc_microbit. There may be others.

Nick

Nick Cook
Lecturer in Computing Science at Newcastle University
and lead of CAS North East: http://casne.ncl.ac.uk/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160614/c87cf903/attachment.html>

From ntoll at ntoll.org  Tue Jun 14 13:43:39 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Tue, 14 Jun 2016 18:43:39 +0100
Subject: [Microbit-Python] microbit_stub - a Python module to test
 micro:bit Python programs
In-Reply-To: <D385FBE2.1C71E%nick.cook@newcastle.ac.uk>
References: <D385FBE2.1C71E%nick.cook@newcastle.ac.uk>
Message-ID: <5760424B.2010300@ntoll.org>

Hi Nick,

Briefly, because I have a busy evening ahead of me... wow - I can't wait
to play with this. Congratulations..!

I'll play with it tomorrow ;-)

N.

On 14/06/16 18:22, Nick Cook wrote:
> I have released my microbit_stub module on github. It is  a Python
> module to test microbit micropython programs without needing a physical
> micro:bit, completely offline. You can do what you will with it from the
> github home:
> 
> <https://github.com/casnortheast/microbit_stub>https://github.com/casnortheast/microbit_stub
> 
> It as a textual "emulator" of the micro:bit (as defined by the microbit
> micropython API) that allows you to take a microbit micropython program
> and test it using the microbit_stub module. It is intended to be useful
> if you do not have a micro:bit, or if you are not using the offline mu
> editor with a REPL window and need something more than the error
> feedback on the micro:bit screen. Or it can just be used by pupils (and
> others!) to test program syntax and logic before running on the
> micro:bit (or after if they get an error and cannot easily work out what
> the problem is). Programs using this module should run in any Python IDE
> (including IDLE) and at the command line.
> 
> Some documentation, tests and example programs are on the github page
> (including simple support for simulation of microbit state).
> 
> It should work with any microbit program by changing the import
> statement to import "microbit_stub" instead of "microbit". There is also
> a sub directory in the release that uses "microbit" as the module name
> and, therefore, does not require any change to an existing program (you
> will see from the README that I am not undecided about which approach to
> take :).
> 
> I may at some point extend the module to provide a graphical emulation
> (or the option of it). Peter Dring has produced a Web-based micro:bit
> Python simulator that could also be of interest (it is intended for a
> different usage to this module) -
> see: http://community.computingatschool.org.uk/resources/4479. And there
> is David Whale's minecraft micro:bit,
> see: https://github.com/whaleygeek/mc_microbit. There may be others.
> 
> Nick
> 
> Nick Cook
> Lecturer in Computing Science at Newcastle University
> and lead of CAS North East: http://casne.ncl.ac.uk/
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160614/31a427cf/attachment.sig>

From nick.cook at newcastle.ac.uk  Wed Jun 15 05:10:27 2016
From: nick.cook at newcastle.ac.uk (Nick Cook)
Date: Wed, 15 Jun 2016 09:10:27 +0000
Subject: [Microbit-Python] microbit_stub - a Python module to test micro:bit
 Python programs
Message-ID: <D386DA0F.1C75F%nick.cook@newcastle.ac.uk>

Thanks

I hope it lives up to your expectations :)

My priority was to deal with the display, buttons, and I/0 pins.

Gestures are randomly generated as are compass positions. I think it would be easy to include gestures as part of the "microbit state". I didn't because I ran out of time and wanted to release it.

An overall aim is to keep things as simple as possible and hopefully easy to understand. I will leave it to others to decide whether I have achieved that :)

I have not tried to do anything about serial interface or bluetooth. I am not sure it is sensible to.

Nick


On 14/06/16, Nicholas H.Tollervey wrote:
> Hi Nick,
>
> Briefly, because I have a busy evening ahead of me... wow - I can't wait
> to play with this. Congratulations..!
>
> I'll play with it tomorrow ;-)
>
> N.

On 14/06/16 18:22, Nick Cook wrote:
>
 I have released my microbit_stub module on github. It is  a Python
> module to test microbit micropython programs without needing a physical
> micro:bit, completely offline. You can do what you will with it from the
> github home:
>
> <https://github.com/casnortheast/microbit_stub>https://github.com/casnortheast/microbit_stub
>
> It as a textual "emulator" of the micro:bit (as defined by the microbit
> micropython API) that allows you to take a microbit micropython program
> and test it using the microbit_stub module. It is intended to be useful
> if you do not have a micro:bit, or if you are not using the offline mu
> editor with a REPL window and need something more than the error
> feedback on the micro:bit screen. Or it can just be used by pupils (and
> others!) to test program syntax and logic before running on the
> micro:bit (or after if they get an error and cannot easily work out what
> the problem is). Programs using this module should run in any Python IDE
> (including IDLE) and at the command line.
>
> Some documentation, tests and example programs are on the github page
> (including simple support for simulation of microbit state).
>
> It should work with any microbit program by changing the import
> statement to import "microbit_stub" instead of "microbit". There is also
> a sub directory in the release that uses "microbit" as the module name
> and, therefore, does not require any change to an existing program (you
> will see from the README that I am not undecided about which approach to
> take :).
>
> I may at some point extend the module to provide a graphical emulation
> (or the option of it). Peter Dring has produced a Web-based micro:bit
> Python simulator that could also be of interest (it is intended for a
> different usage to this module) -
> see: http://community.computingatschool.org.uk/resources/4479. And there
> is David Whale's minecraft micro:bit,
> see: https://github.com/whaleygeek/mc_microbit. There may be others.
>
> Nick
>
> Nick Cook
> Lecturer in Computing Science at Newcastle University
> and lead of CAS North East: http://casne.ncl.ac.uk/
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org<https://mail.python.org/mailman/listinfo/microbit>
> https://mail.python.org/mailman/listinfo/microbit
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160615/01017016/attachment-0001.html>

From andrewferguson500 at gmail.com  Wed Jun 15 11:53:57 2016
From: andrewferguson500 at gmail.com (Andrew Ferguson)
Date: Wed, 15 Jun 2016 16:53:57 +0100
Subject: [Microbit-Python] MicroBit Stack Exchange Proposal
Message-ID: <CAFvb365H2nK7WKLiTCQPgCssre9PV0wNRbUsDx2zbGtUpe=y2A@mail.gmail.com>

Hi everyone,

I logged into the proposal stack exchange site again, and after tactically
altering my votes and convincing a friend to sigh up, the MicroBit Stack
Exchange site is now into the proposal stage.

We now need as many people as possible to commit to helping the site take
off in the early days. Please go to
http://area51.stackexchange.com/proposals/96237/ and commit your support!

Andrew

P.S. Does anyone know the exact number of 'committed' supporters we need to
move into the Beta stage? I can't seem to find the exact number.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160615/27d5a9b8/attachment.html>

From nick.a.sarbicki at gmail.com  Wed Jun 15 12:10:41 2016
From: nick.a.sarbicki at gmail.com (Nick Sarbicki)
Date: Wed, 15 Jun 2016 16:10:41 +0000
Subject: [Microbit-Python] MicroBit Stack Exchange Proposal
In-Reply-To: <CAFvb365H2nK7WKLiTCQPgCssre9PV0wNRbUsDx2zbGtUpe=y2A@mail.gmail.com>
References: <CAFvb365H2nK7WKLiTCQPgCssre9PV0wNRbUsDx2zbGtUpe=y2A@mail.gmail.com>
Message-ID: <CAGuvt92hAW+xz1AXnXXgR7XojXPhW+tr29p2EPAS_T=NUU0cag@mail.gmail.com>

Committed. Will try source some people from my local Coder Dojo as well.

On Wed, Jun 15, 2016 at 4:54 PM Andrew Ferguson <andrewferguson500 at gmail.com>
wrote:

> Hi everyone,
>
> I logged into the proposal stack exchange site again, and after tactically
> altering my votes and convincing a friend to sigh up, the MicroBit Stack
> Exchange site is now into the proposal stage.
>
> We now need as many people as possible to commit to helping the site take
> off in the early days. Please go to
> http://area51.stackexchange.com/proposals/96237/ and commit your support!
>
> Andrew
>
> P.S. Does anyone know the exact number of 'committed' supporters we need
> to move into the Beta stage? I can't seem to find the exact number.
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160615/88d17a8c/attachment.html>

From leonaso43 at googlemail.com  Mon Jun 20 04:41:16 2016
From: leonaso43 at googlemail.com (Leona So)
Date: Mon, 20 Jun 2016 09:41:16 +0100
Subject: [Microbit-Python] [python-uk] Microbit motion sensors at PyCon
 UK Teachers' Day
In-Reply-To: <575F4828.8040505@stevesimmons.com>
References: <575F4828.8040505@stevesimmons.com>
Message-ID: <CABQC_xq8C7LrYxfoi0CLOLq1Ah+_AsKu6gYQnVzbg-7xDKhuBQ@mail.gmail.com>

Hi Stephen,

I teach Maths at a FE college, have general interest in programming
especially Python and would be more than happy to help. The only downside
is I don't have access to a microbit, it's hard to get hold of one. I used
it briefly during microbit training sessions with STEMNET, so I may be able
to provide some ideas!

Thanks.

Regards,


Leona

On Tue, Jun 14, 2016 at 12:56 AM, Stephen Simmons <mail at stevesimmons.com>
wrote:

> Hi everyone,
>
>
> Would anyone like to help me put together a microbit session for the PyCon
> UK teachers' day using motion sensors? My plan is to use python on the
> microbit to illustrate some motion-related maths/physics principles from
> accelerometer/gyroscope data.
>
> Ideally we would prepare some exercises with direct relevance to classwork
> that teachers could take back to their students and use right away.
>
> So if you know microbits and are keen to help, get in touch!
>
> If you are a teacher with ideas you'd to implement, or you know teachers
> with ideas, then get in touch too.
>
> The deadline for proposals is in 2 weeks...
>
> Cheers
> Stephen
>
> P.S. I have also submitted a proposal on sensor fusion algorithms for the
> main PyCon UK conference, using MetaWear PRO wearables. They can transmit
> 9-axis accelerometer/gyroscope/magnetometer data over Bluetooth in real
> time. The microbit, as I understand it (mine will arrive in 2 weeks...)
> doesn't have enough memory to load Python and Bluetooth together. So we
> will have to be more creative about logging/retrieving results. Plenty of
> time to work through this in July/August. First step is the proposal....
> _______________________________________________
> python-uk mailing list
> python-uk at python.org
> https://mail.python.org/mailman/listinfo/python-uk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160620/f544882a/attachment.html>

From mail at stevesimmons.com  Tue Jun 21 18:12:19 2016
From: mail at stevesimmons.com (Stephen Simmons)
Date: Tue, 21 Jun 2016 23:12:19 +0100
Subject: [Microbit-Python] [python-uk] Microbit motion sensors at PyCon
 UK Teachers' Day
In-Reply-To: <CACFDE8aMGdWMJbFA8=LT+XhLRTLXShGrtUEvOsGmnRc21HGPfw@mail.gmail.com>
References: <575F4828.8040505@stevesimmons.com>
 <CABQC_xq8C7LrYxfoi0CLOLq1Ah+_AsKu6gYQnVzbg-7xDKhuBQ@mail.gmail.com>
 <CACFDE8aMGdWMJbFA8=LT+XhLRTLXShGrtUEvOsGmnRc21HGPfw@mail.gmail.com>
Message-ID: <5769BBC3.2000000@stevesimmons.com>

Hi Steve, Leona,

Thanks for replying. I'll send an email followup shortly. The PyCon UK deadline proposal is Tues 28 June. Let's get a proposal together over the next few days.

Stephen


On 21/06/16 21:42, Stestagg wrote:
> Hi! I have a micro:bit and would love to help in any way possible. Feel free to get in touch if you would like to discuss Thanks Steve
>
> On Mon, 20 Jun 2016 at 09:42, Leona So via python-uk <python-uk at python.org <mailto:python-uk at python.org>> wrote:
>
>     Hi Stephen,
>
>     I teach Maths at a FE college, have general interest in programming especially Python and would be more than happy to help. The only downside is I don't have access to a microbit, it's hard to get hold of one. I used it briefly during microbit training sessions with STEMNET, so I may be able to provide some ideas!
>
>     Thanks.
>
>     Regards,
>
>
>     Leona
>
>     On Tue, Jun 14, 2016 at 12:56 AM, Stephen Simmons <mail at stevesimmons.com <mailto:mail at stevesimmons.com>> wrote:
>
>         Hi everyone,
>
>
>         Would anyone like to help me put together a microbit session for the PyCon UK teachers' day using motion sensors? My plan is to use python on the microbit to illustrate some motion-related maths/physics principles from accelerometer/gyroscope data.
>
>         Ideally we would prepare some exercises with direct relevance to classwork that teachers could take back to their students and use right away.
>
>         So if you know microbits and are keen to help, get in touch!
>
>         If you are a teacher with ideas you'd to implement, or you know teachers with ideas, then get in touch too.
>
>         The deadline for proposals is in 2 weeks...
>
>         Cheers
>         Stephen
>
>         P.S. I have also submitted a proposal on sensor fusion algorithms for the main PyCon UK conference, using MetaWear PRO wearables. They can transmit 9-axis accelerometer/gyroscope/magnetometer data over Bluetooth in real time. The microbit, as I understand it (mine will arrive in 2 weeks...) doesn't have enough memory to load Python and Bluetooth together. So we will have to be more creative about logging/retrieving results. Plenty of time to work through this in July/August. First step is the proposal....
>         _______________________________________________
>         python-uk mailing list
>         python-uk at python.org <mailto:python-uk at python.org>
>         https://mail.python.org/mailman/listinfo/python-uk
>
>
>     _______________________________________________
>     python-uk mailing list
>     python-uk at python.org <mailto:python-uk at python.org>
>     https://mail.python.org/mailman/listinfo/python-uk
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160621/a78e4887/attachment.html>

From carlos.p.a.87 at gmail.com  Tue Jun 21 18:41:00 2016
From: carlos.p.a.87 at gmail.com (Carlos P.A.)
Date: Tue, 21 Jun 2016 23:41:00 +0100
Subject: [Microbit-Python] [python-uk] Microbit motion sensors at PyCon
 UK Teachers' Day
In-Reply-To: <5769BBC3.2000000@stevesimmons.com>
References: <575F4828.8040505@stevesimmons.com>
 <CABQC_xq8C7LrYxfoi0CLOLq1Ah+_AsKu6gYQnVzbg-7xDKhuBQ@mail.gmail.com>
 <CACFDE8aMGdWMJbFA8=LT+XhLRTLXShGrtUEvOsGmnRc21HGPfw@mail.gmail.com>
 <5769BBC3.2000000@stevesimmons.com>
Message-ID: <CAC_p0yBPP0vjatD6deRCrSav=Bw=4HWU+6MDXgt+k0AzAYQ4sA@mail.gmail.com>

No need to hurry, I think the proposal deadline is only for the talk, you
can come up with a sprint in the last minute, but if it is submitted
beforehand it can get advertised on the website or whatever medium they
have for that.

On 21 June 2016 at 23:12, Stephen Simmons <mail at stevesimmons.com> wrote:

> Hi Steve, Leona,
>
> Thanks for replying. I'll send an email followup shortly. The PyCon UK
> deadline proposal is Tues 28 June. Let's get a proposal together over the
> next few days.
>
> Stephen
>
>
> On 21/06/16 21:42, Stestagg wrote:
>
> Hi! I have a micro:bit and would love to help in any way possible. Feel
> free to get in touch if you would like to discuss Thanks Steve
>
> On Mon, 20 Jun 2016 at 09:42, Leona So via python-uk <python-uk at python.org>
> wrote:
>
>> Hi Stephen,
>>
>> I teach Maths at a FE college, have general interest in programming
>> especially Python and would be more than happy to help. The only downside
>> is I don't have access to a microbit, it's hard to get hold of one. I used
>> it briefly during microbit training sessions with STEMNET, so I may be able
>> to provide some ideas!
>>
>> Thanks.
>>
>> Regards,
>>
>>
>> Leona
>>
>> On Tue, Jun 14, 2016 at 12:56 AM, Stephen Simmons <
>> <mail at stevesimmons.com>mail at stevesimmons.com> wrote:
>>
>>> Hi everyone,
>>>
>>>
>>> Would anyone like to help me put together a microbit session for the
>>> PyCon UK teachers' day using motion sensors? My plan is to use python on
>>> the microbit to illustrate some motion-related maths/physics principles
>>> from accelerometer/gyroscope data.
>>>
>>> Ideally we would prepare some exercises with direct relevance to
>>> classwork that teachers could take back to their students and use right
>>> away.
>>>
>>> So if you know microbits and are keen to help, get in touch!
>>>
>>> If you are a teacher with ideas you'd to implement, or you know teachers
>>> with ideas, then get in touch too.
>>>
>>> The deadline for proposals is in 2 weeks...
>>>
>>> Cheers
>>> Stephen
>>>
>>> P.S. I have also submitted a proposal on sensor fusion algorithms for
>>> the main PyCon UK conference, using MetaWear PRO wearables. They can
>>> transmit 9-axis accelerometer/gyroscope/magnetometer data over Bluetooth in
>>> real time. The microbit, as I understand it (mine will arrive in 2
>>> weeks...) doesn't have enough memory to load Python and Bluetooth together.
>>> So we will have to be more creative about logging/retrieving results.
>>> Plenty of time to work through this in July/August. First step is the
>>> proposal....
>>> _______________________________________________
>>> python-uk mailing list
>>> python-uk at python.org
>>> https://mail.python.org/mailman/listinfo/python-uk
>>>
>>
>> _______________________________________________
>> python-uk mailing list
>> python-uk at python.org
>> https://mail.python.org/mailman/listinfo/python-uk
>>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160621/29e16c8a/attachment.html>

From stestagg at gmail.com  Tue Jun 21 16:42:38 2016
From: stestagg at gmail.com (Stestagg)
Date: Tue, 21 Jun 2016 20:42:38 +0000
Subject: [Microbit-Python] [python-uk] Microbit motion sensors at PyCon
 UK Teachers' Day
In-Reply-To: <CABQC_xq8C7LrYxfoi0CLOLq1Ah+_AsKu6gYQnVzbg-7xDKhuBQ@mail.gmail.com>
References: <575F4828.8040505@stevesimmons.com>
 <CABQC_xq8C7LrYxfoi0CLOLq1Ah+_AsKu6gYQnVzbg-7xDKhuBQ@mail.gmail.com>
Message-ID: <CACFDE8aMGdWMJbFA8=LT+XhLRTLXShGrtUEvOsGmnRc21HGPfw@mail.gmail.com>

Hi!

I have a micro:bit and would love to help in any way possible.

Feel free to get in touch if you would like to discuss

Thanks

Steve

On Mon, 20 Jun 2016 at 09:42, Leona So via python-uk <python-uk at python.org>
wrote:

> Hi Stephen,
>
> I teach Maths at a FE college, have general interest in programming
> especially Python and would be more than happy to help. The only downside
> is I don't have access to a microbit, it's hard to get hold of one. I used
> it briefly during microbit training sessions with STEMNET, so I may be able
> to provide some ideas!
>
> Thanks.
>
> Regards,
>
>
> Leona
>
> On Tue, Jun 14, 2016 at 12:56 AM, Stephen Simmons <mail at stevesimmons.com>
> wrote:
>
>> Hi everyone,
>>
>>
>> Would anyone like to help me put together a microbit session for the
>> PyCon UK teachers' day using motion sensors? My plan is to use python on
>> the microbit to illustrate some motion-related maths/physics principles
>> from accelerometer/gyroscope data.
>>
>> Ideally we would prepare some exercises with direct relevance to
>> classwork that teachers could take back to their students and use right
>> away.
>>
>> So if you know microbits and are keen to help, get in touch!
>>
>> If you are a teacher with ideas you'd to implement, or you know teachers
>> with ideas, then get in touch too.
>>
>> The deadline for proposals is in 2 weeks...
>>
>> Cheers
>> Stephen
>>
>> P.S. I have also submitted a proposal on sensor fusion algorithms for the
>> main PyCon UK conference, using MetaWear PRO wearables. They can transmit
>> 9-axis accelerometer/gyroscope/magnetometer data over Bluetooth in real
>> time. The microbit, as I understand it (mine will arrive in 2 weeks...)
>> doesn't have enough memory to load Python and Bluetooth together. So we
>> will have to be more creative about logging/retrieving results. Plenty of
>> time to work through this in July/August. First step is the proposal....
>> _______________________________________________
>> python-uk mailing list
>> python-uk at python.org
>> https://mail.python.org/mailman/listinfo/python-uk
>>
>
> _______________________________________________
> python-uk mailing list
> python-uk at python.org
> https://mail.python.org/mailman/listinfo/python-uk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160621/7eeb1995/attachment-0001.html>

From antonywatts at me.com  Wed Jun 22 07:09:10 2016
From: antonywatts at me.com (Antony Watts)
Date: Wed, 22 Jun 2016 12:09:10 +0100
Subject: [Microbit-Python] Next coding steps - 'C'?
Message-ID: <FAB3A6F6-113D-4167-82EB-306E308D7531@me.com>

Hi

As I see it the programming experience is in steps

?Block? type visual editors
MicroPython editors and program code

What would seem to me to be the next step is a ?C? code editor and compiler. - Arduino IDE-like, stand alone, desk-top.

Do you know if anyone is working on this. In particular I have an application that needs a lower level access and to be able to use the ?radio? functions?

Reds

Antony Watts

From ntoll at ntoll.org  Wed Jun 22 08:22:00 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Wed, 22 Jun 2016 13:22:00 +0100
Subject: [Microbit-Python] Next coding steps - 'C'?
In-Reply-To: <FAB3A6F6-113D-4167-82EB-306E308D7531@me.com>
References: <FAB3A6F6-113D-4167-82EB-306E308D7531@me.com>
Message-ID: <576A82E8.8010906@ntoll.org>

On 22/06/16 12:09, Antony Watts wrote:
> Hi
> 
> As I see it the programming experience is in steps
> 
> ?Block? type visual editors MicroPython editors and program code
> 
> What would seem to me to be the next step is a ?C? code editor and
> compiler. - Arduino IDE-like, stand alone, desk-top.
> 

That depends. The whole point of MicroPython is that you don't have to
feel the pain of having to use C (i.e. a higher-level general purpose
language like Python is a lot easier to get stuff done it).

Having said that, C can be a lot of fun and if you're wanting to learn
about working at a lower level it's perhaps the thing to learn.

> Do you know if anyone is working on this. In particular I have an
> application that needs a lower level access and to be able to use the
> ?radio? functions?
> 

You should probably get in touch with ARM. Their mbed platform is C/C++
based and the mirco:bit is based upon their platform.

Also, we'll have a radio module in MicroPython very soon. We're
currently finalising the API, although Damien has a proof-of-concept
branch in the repos.

N.

> Reds
> 
> Antony Watts _______________________________________________ Microbit
> mailing list Microbit at python.org 
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160622/bf30755e/attachment.sig>

From Jonathan.Austin at arm.com  Wed Jun 22 08:40:08 2016
From: Jonathan.Austin at arm.com (Jonathan Austin)
Date: Wed, 22 Jun 2016 12:40:08 +0000
Subject: [Microbit-Python] Next coding steps - 'C'?
In-Reply-To: <FAB3A6F6-113D-4167-82EB-306E308D7531@me.com>
References: <FAB3A6F6-113D-4167-82EB-306E308D7531@me.com>
Message-ID: <956922DD-2FCD-4227-96ED-D68974FE079F@arm.com>

Hi Anthony,

> On 22 Jun 2016, at 12:09, Antony Watts <antonywatts at me.com> wrote:
>
> Hi
>
> As I see it the programming experience is in steps
>
> ?Block? type visual editors
> MicroPython editors and program code
>
> What would seem to me to be the next step is a ?C? code editor and compiler. - Arduino IDE-like, stand alone, desk-top.
>
> Do you know if anyone is working on this. In particular I have an application that needs a lower level access and to be able to use the ?radio? functions?
>

With the full disclosure that I work for ARM in the mbed group, I can recommend the ARM mbed online IDE :)

Start here:
https://developer.mbed.org/platforms/microbit/

You need to be signed up to mbed to use this.

Here are the docs that come with the DAL related to using the mbed online IDE including some introductions to what it is:
http://lancaster-university.github.io/microbit-docs/online-toolchains/


The microbit-samples program has a nice radio example:
https://developer.mbed.org/teams/BBC/code/microbit-samples/

(you need to enable that example by changing which code is built by editing the #defines in MicrobitSamples.h
https://developer.mbed.org/teams/BBC/code/microbit-samples/file/6b26df2a055a/source/MicroBitSamples.h )

I hope that helps. Feedback is welcome, and if you?d like to publish samples into the community micro:bit team, I can add you as a member (just let me know your mbed username)

Good luck,
Jonny

> Reds
>
> Antony Watts
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

From sparks.m at gmail.com  Wed Jun 22 08:42:31 2016
From: sparks.m at gmail.com (Michael)
Date: Wed, 22 Jun 2016 13:42:31 +0100
Subject: [Microbit-Python] Next coding steps - 'C'?
In-Reply-To: <576A82E8.8010906@ntoll.org>
References: <FAB3A6F6-113D-4167-82EB-306E308D7531@me.com>
 <576A82E8.8010906@ntoll.org>
Message-ID: <CAB+QZVBOzNLnJ8D6p_KDfpr46c9viKa4opk=8jfZnFVJH7YMYg@mail.gmail.com>

On 22 June 2016 at 13:22, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> On 22/06/16 12:09, Antony Watts wrote:
> > Hi
> >
> > As I see it the programming experience is in steps
> >
> > ?Block? type visual editors MicroPython editors and program code
> >
> > What would seem to me to be the next step is a ?C? code editor and
> > compiler. - Arduino IDE-like, stand alone, desk-top.
> >
>
> That depends. The whole point of MicroPython is that you don't have to
> feel the pain of having to use C (i.e. a higher-level general purpose
> language like Python is a lot easier to get stuff done it).
>

With respect, the point of the micro:bit is to allow precisely this sort of
learning curve. We do still need people to learn systems languages like
C after all :-)

It's utterly cool just how much you can do with micropython though - exceeds
everyone's wildest dreams :-)

Though one effect working on micro:bit has had for me is to realise that
just like Python and C are considered "proper" languages, so should visual
languages - however they've got a lot of catching up to do to be as
practical/useful :-)

For reference, one good starting point of how to get starting with C++ and
the micro:bit is here:

http://www.i-programmer.info/programming/hardware/9651-getting-started-with-cc-on-the-microbit.html

(Simple tutorial with links)


Michael.


> Having said that, C can be a lot of fun and if you're wanting to learn
> about working at a lower level it's perhaps the thing to learn.
>
> > Do you know if anyone is working on this. In particular I have an
> > application that needs a lower level access and to be able to use the
> > ?radio? functions?
> >
>
> You should probably get in touch with ARM. Their mbed platform is C/C++
> based and the mirco:bit is based upon their platform.
>
> Also, we'll have a radio module in MicroPython very soon. We're
> currently finalising the API, although Damien has a proof-of-concept
> branch in the repos.
>
> N.
>
> > Reds
> >
> > Antony Watts _______________________________________________ Microbit
> > mailing list Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160622/9f26c933/attachment-0001.html>

From ntoll at ntoll.org  Wed Jun 22 09:10:23 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Wed, 22 Jun 2016 14:10:23 +0100
Subject: [Microbit-Python] Next coding steps - 'C'?
In-Reply-To: <CAB+QZVBOzNLnJ8D6p_KDfpr46c9viKa4opk=8jfZnFVJH7YMYg@mail.gmail.com>
References: <FAB3A6F6-113D-4167-82EB-306E308D7531@me.com>
 <576A82E8.8010906@ntoll.org>
 <CAB+QZVBOzNLnJ8D6p_KDfpr46c9viKa4opk=8jfZnFVJH7YMYg@mail.gmail.com>
Message-ID: <576A8E3F.3050004@ntoll.org>

On 22/06/16 13:42, Michael wrote:
> With respect, the point of the micro:bit is to allow precisely this sort of
> learning curve. We do still need people to learn systems languages like
> C after all :-)

Of course... I wasn't suggesting this wasn't a valid learning curve,
just that there are several different curves: hence the "That depends". :-)

As I mentioned, C is a completely valid and fun thing to get into.

N.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160622/2addd49c/attachment.sig>

From sparks.m at gmail.com  Wed Jun 22 09:51:33 2016
From: sparks.m at gmail.com (Michael)
Date: Wed, 22 Jun 2016 14:51:33 +0100
Subject: [Microbit-Python] Next coding steps - 'C'?
In-Reply-To: <576A8E3F.3050004@ntoll.org>
References: <FAB3A6F6-113D-4167-82EB-306E308D7531@me.com>
 <576A82E8.8010906@ntoll.org>
 <CAB+QZVBOzNLnJ8D6p_KDfpr46c9viKa4opk=8jfZnFVJH7YMYg@mail.gmail.com>
 <576A8E3F.3050004@ntoll.org>
Message-ID: <CAB+QZVAUxFTpOmO7NVGmVk_E6UJuSb-_sDRs7ZTO+WKrJFXW0A@mail.gmail.com>

On 22 June 2016 at 14:10, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> On 22/06/16 13:42, Michael wrote:
> > With respect, the point of the micro:bit is to allow precisely this sort
> of
> > learning curve. We do still need people to learn systems languages like
> > C after all :-)
>
> Of course... I wasn't suggesting this wasn't a valid learning curve,
> just that there are several different curves: hence the "That depends". :-)
>
> As I mentioned, C is a completely valid and fun thing to get into.
>
>
Indeed, was taking the opportunity to say "yes you can" :-)

I think my reason really for replying was the fact that one thing I find
people sometimes think is

Blocks -> Python -> C/C++

Means:

Blocks  (not as good as)  Python  (not as good as)  C/C++

... that is that languages on the right are somehow more "valid" than
languages on the left. That's clearly not true for python vs C/C++,  but I
think it's also true for Block type languages. They're just at a ALGOL
level of development at the moment so to speak.

Indeed, surveys of children learning block based languages tend to assume
that, and that my personal experience of all this is that actually block
based languages are just as valid, and make complex things much easier than
the languages on the right. (I'm thinking concurrency)

And also I think there will be a lot of interesting work in the next
several years fleshing out things that are "missing" from block languages.

(This was something I didn't think when we first started down this road!
:-) )

Regards,


Michael.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160622/9b9920f4/attachment.html>

From antonywatts at me.com  Wed Jun 22 12:41:02 2016
From: antonywatts at me.com (Antony Watts)
Date: Wed, 22 Jun 2016 17:41:02 +0100
Subject: [Microbit-Python] Next coding steps - 'C'?
In-Reply-To: <CAB+QZVBOzNLnJ8D6p_KDfpr46c9viKa4opk=8jfZnFVJH7YMYg@mail.gmail.com>
References: <FAB3A6F6-113D-4167-82EB-306E308D7531@me.com>
 <576A82E8.8010906@ntoll.org>
 <CAB+QZVBOzNLnJ8D6p_KDfpr46c9viKa4opk=8jfZnFVJH7YMYg@mail.gmail.com>
Message-ID: <3BA8FEBA-8113-4C6A-B1A7-75227345A68A@me.com>

Thank you everybody for you inputs

- I chose to ask about ?C? as I have done quite a bit of programming on the Arduino, and the tool chain is very simple to use, and there are plenty of open source libraries. And there is a C radio module in the DAL?

- Be assured I do not regard the progression ?Block -> MicroPython-> C? as  in any way better, better, better. But I do think students should be encouraged to get into ?written? code (real life) ASAP, thus the importance of MicroPython.

- I am looking forward to  the Radio module in MicroPython. It will probably fit the bill for my project which needs lots of microbits ( maybe 100?s) to ping off signals to a central communication point.

- I will check out the bed on-line tools, but they better be simple to use or ...

Antony

> On 22 Jun 2016, at 13:42, Michael <sparks.m at gmail.com> wrote:
> 
> On 22 June 2016 at 13:22, Nicholas H.Tollervey <ntoll at ntoll.org <mailto:ntoll at ntoll.org>> wrote:
> On 22/06/16 12:09, Antony Watts wrote:
> > Hi
> >
> > As I see it the programming experience is in steps
> >
> > ?Block? type visual editors MicroPython editors and program code
> >
> > What would seem to me to be the next step is a ?C? code editor and
> > compiler. - Arduino IDE-like, stand alone, desk-top.
> >
> 
> That depends. The whole point of MicroPython is that you don't have to
> feel the pain of having to use C (i.e. a higher-level general purpose
> language like Python is a lot easier to get stuff done it).
>  
> With respect, the point of the micro:bit is to allow precisely this sort of
> learning curve. We do still need people to learn systems languages like
> C after all :-)
> 
> It's utterly cool just how much you can do with micropython though - exceeds
> everyone's wildest dreams :-)
> 
> Though one effect working on micro:bit has had for me is to realise that
> just like Python and C are considered "proper" languages, so should visual
> languages - however they've got a lot of catching up to do to be as
> practical/useful :-)
> 
> For reference, one good starting point of how to get starting with C++ and the micro:bit is here:
> 
> http://www.i-programmer.info/programming/hardware/9651-getting-started-with-cc-on-the-microbit.html <http://www.i-programmer.info/programming/hardware/9651-getting-started-with-cc-on-the-microbit.html>
> 
> (Simple tutorial with links)
> 
> 
> Michael.
> 
> 
> Having said that, C can be a lot of fun and if you're wanting to learn
> about working at a lower level it's perhaps the thing to learn.
> 
> > Do you know if anyone is working on this. In particular I have an
> > application that needs a lower level access and to be able to use the
> > ?radio? functions?
> >
> 
> You should probably get in touch with ARM. Their mbed platform is C/C++
> based and the mirco:bit is based upon their platform.
> 
> Also, we'll have a radio module in MicroPython very soon. We're
> currently finalising the API, although Damien has a proof-of-concept
> branch in the repos.
> 
> N.
> 
> > Reds
> >
> > Antony Watts _______________________________________________ Microbit
> > mailing list Microbit at python.org <mailto:Microbit at python.org>
> > https://mail.python.org/mailman/listinfo/microbit <https://mail.python.org/mailman/listinfo/microbit>
> >
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org <mailto:Microbit at python.org>
> https://mail.python.org/mailman/listinfo/microbit <https://mail.python.org/mailman/listinfo/microbit>
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org <mailto:Microbit at python.org>
> https://mail.python.org/mailman/listinfo/microbit <https://mail.python.org/mailman/listinfo/microbit>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160622/ea955802/attachment.html>

From andrewferguson500 at gmail.com  Wed Jun 22 15:13:57 2016
From: andrewferguson500 at gmail.com (Andrew Ferguson 500)
Date: Wed, 22 Jun 2016 20:13:57 +0100
Subject: [Microbit-Python] Next coding steps - 'C'?
In-Reply-To: <3BA8FEBA-8113-4C6A-B1A7-75227345A68A@me.com>
References: <FAB3A6F6-113D-4167-82EB-306E308D7531@me.com>
 <576A82E8.8010906@ntoll.org>
 <CAB+QZVBOzNLnJ8D6p_KDfpr46c9viKa4opk=8jfZnFVJH7YMYg@mail.gmail.com>
 <3BA8FEBA-8113-4C6A-B1A7-75227345A68A@me.com>
Message-ID: <70DA514B-7C82-42A8-A279-1997800CE413@gmail.com>

I haven't tried this myself yet, but the radio module is available in a blocks editor through the Microsoft Project Experience Toolkit (m.pxt.io).

(I know you are looking for a "written" language, but this may temporarily meet your needs).



On 22 Jun 2016, at 17:41, Antony Watts <antonywatts at me.com> wrote:

> Thank you everybody for you inputs
> 
> - I chose to ask about ?C? as I have done quite a bit of programming on the Arduino, and the tool chain is very simple to use, and there are plenty of open source libraries. And there is a C radio module in the DAL?
> 
> - Be assured I do not regard the progression ?Block -> MicroPython-> C? as  in any way better, better, better. But I do think students should be encouraged to get into ?written? code (real life) ASAP, thus the importance of MicroPython.
> 
> - I am looking forward to  the Radio module in MicroPython. It will probably fit the bill for my project which needs lots of microbits ( maybe 100?s) to ping off signals to a central communication point.
> 
> - I will check out the bed on-line tools, but they better be simple to use or ...
> 
> Antony
> 
>> On 22 Jun 2016, at 13:42, Michael <sparks.m at gmail.com> wrote:
>> 
>> On 22 June 2016 at 13:22, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:
>> On 22/06/16 12:09, Antony Watts wrote:
>> > Hi
>> >
>> > As I see it the programming experience is in steps
>> >
>> > ?Block? type visual editors MicroPython editors and program code
>> >
>> > What would seem to me to be the next step is a ?C? code editor and
>> > compiler. - Arduino IDE-like, stand alone, desk-top.
>> >
>> 
>> That depends. The whole point of MicroPython is that you don't have to
>> feel the pain of having to use C (i.e. a higher-level general purpose
>> language like Python is a lot easier to get stuff done it).
>>  
>> With respect, the point of the micro:bit is to allow precisely this sort of
>> learning curve. We do still need people to learn systems languages like
>> C after all :-)
>> 
>> It's utterly cool just how much you can do with micropython though - exceeds
>> everyone's wildest dreams :-)
>> 
>> Though one effect working on micro:bit has had for me is to realise that
>> just like Python and C are considered "proper" languages, so should visual
>> languages - however they've got a lot of catching up to do to be as
>> practical/useful :-)
>> 
>> For reference, one good starting point of how to get starting with C++ and the micro:bit is here:
>> 
>> http://www.i-programmer.info/programming/hardware/9651-getting-started-with-cc-on-the-microbit.html
>> 
>> (Simple tutorial with links)
>> 
>> 
>> Michael.
>> 
>> 
>> Having said that, C can be a lot of fun and if you're wanting to learn
>> about working at a lower level it's perhaps the thing to learn.
>> 
>> > Do you know if anyone is working on this. In particular I have an
>> > application that needs a lower level access and to be able to use the
>> > ?radio? functions?
>> >
>> 
>> You should probably get in touch with ARM. Their mbed platform is C/C++
>> based and the mirco:bit is based upon their platform.
>> 
>> Also, we'll have a radio module in MicroPython very soon. We're
>> currently finalising the API, although Damien has a proof-of-concept
>> branch in the repos.
>> 
>> N.
>> 
>> > Reds
>> >
>> > Antony Watts _______________________________________________ Microbit
>> > mailing list Microbit at python.org
>> > https://mail.python.org/mailman/listinfo/microbit
>> >
>> 
>> 
>> 
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>> 
>> 
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160622/3da3647c/attachment-0001.html>

From nigel.kendrick at gmail.com  Sat Jun 25 09:29:51 2016
From: nigel.kendrick at gmail.com (Nigel Kendrick)
Date: Sat, 25 Jun 2016 14:29:51 +0100
Subject: [Microbit-Python] [python-uk] Microbit motion sensors at PyCon
 UK Teachers' Day
In-Reply-To: <CACFDE8aMGdWMJbFA8=LT+XhLRTLXShGrtUEvOsGmnRc21HGPfw@mail.gmail.com>
References: <575F4828.8040505@stevesimmons.com>
 <CABQC_xq8C7LrYxfoi0CLOLq1Ah+_AsKu6gYQnVzbg-7xDKhuBQ@mail.gmail.com>
 <CACFDE8aMGdWMJbFA8=LT+XhLRTLXShGrtUEvOsGmnRc21HGPfw@mail.gmail.com>
Message-ID: <01b801d1cee5$a7826bb0$f6874310$@gmail.com>

Ditto. I may also be able to attend PyCon; they have me down as a potential general volunteer already.

 

-- Nigel Kendrick

 

From: Microbit [mailto:microbit-bounces+nigel.kendrick=gmail.com at python.org] On Behalf Of Stestagg
Sent: 21 June 2016 21:43
To: UK Python Users <python-uk at python.org>; mail at stevesimmons.com
Cc: Leona So <leonaso43 at googlemail.com>; microbit at python.org
Subject: Re: [Microbit-Python] [python-uk] Microbit motion sensors at PyCon UK Teachers' Day

 

Hi!

I have a micro:bit and would love to help in any way possible.

Feel free to get in touch if you would like to discuss

Thanks

Steve

 

On Mon, 20 Jun 2016 at 09:42, Leona So via python-uk <python-uk at python.org <mailto:python-uk at python.org> > wrote:

Hi Stephen,

 

I teach Maths at a FE college, have general interest in programming especially Python and would be more than happy to help. The only downside is I don't have access to a microbit, it's hard to get hold of one. I used it briefly during microbit training sessions with STEMNET, so I may be able to provide some ideas!

 

Thanks.

 

Regards,

 


Leona

 

On Tue, Jun 14, 2016 at 12:56 AM, Stephen Simmons <mail at stevesimmons.com <mailto:mail at stevesimmons.com> > wrote:

Hi everyone,


Would anyone like to help me put together a microbit session for the PyCon UK teachers' day using motion sensors? My plan is to use python on the microbit to illustrate some motion-related maths/physics principles from accelerometer/gyroscope data.

Ideally we would prepare some exercises with direct relevance to classwork that teachers could take back to their students and use right away.

So if you know microbits and are keen to help, get in touch!

If you are a teacher with ideas you'd to implement, or you know teachers with ideas, then get in touch too.

The deadline for proposals is in 2 weeks...

Cheers
Stephen

P.S. I have also submitted a proposal on sensor fusion algorithms for the main PyCon UK conference, using MetaWear PRO wearables. They can transmit 9-axis accelerometer/gyroscope/magnetometer data over Bluetooth in real time. The microbit, as I understand it (mine will arrive in 2 weeks...) doesn't have enough memory to load Python and Bluetooth together. So we will have to be more creative about logging/retrieving results. Plenty of time to work through this in July/August. First step is the proposal....
_______________________________________________
python-uk mailing list
python-uk at python.org <mailto:python-uk at python.org> 
https://mail.python.org/mailman/listinfo/python-uk

 

_______________________________________________
python-uk mailing list
python-uk at python.org <mailto:python-uk at python.org> 
https://mail.python.org/mailman/listinfo/python-uk



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160625/402740f7/attachment.html>

From mail at stevesimmons.com  Sun Jun 26 20:20:58 2016
From: mail at stevesimmons.com (Stephen Simmons)
Date: Mon, 27 Jun 2016 01:20:58 +0100
Subject: [Microbit-Python] PyCon UK proposal - Enriching Maths and Physics
 teaching with Micro:bit motion sensors
In-Reply-To: <57706E55.5090605@stevesimmons.com>
References: <57706E55.5090605@stevesimmons.com>
Message-ID: <5770716A.5090906@stevesimmons.com>

Hi everyone,

I mentioned on this list a couple of weeks ago an idea to run a session at PyCon UK Teachers' Day on using the Micro:bit's motion sensors.

A number of people - including Leona, Steve and Nigel (Cc-ed) - replied wanting to get involved.

Encouraged by this, I have just submitted the outline below. It hopefully gives the conference organisers enough to say "Yup, go for it" while leaving a lot of space for us to decide exactly what to present.

I am on holiday next week so will finally have time to email everyone who has expressed interest about working together sorting out the details.

Thanks
Stephen



*Title: *
Enriching Maths and Physics teaching with Micro:bit motion sensors

*What are you proposing? *
**A workshop for Teachers' Day
(duration/number of attendees are flexible. TBD with PyCon UK organisers)

*Abstract: *
**The BBC Micro:bit has powerful accelerometer and compass motion sensors. While they are fun for kids to play with, we show how they can also be used in class to bring some key Maths and Physics principles to life.

This workshop session is intended for teachers who want to learn about using  micro:bit in their classes. No specific knowledge of micro:bit or Python programming is assumed. People who already know Python and micro:bit are also welcome to join in, especially if you can help the teachers get started.

Teachers and helpers are asked to send their ideas for teaching examples to me at mail at stevesimmons.com well before the Teachers' Day. We will write up several examples to present in full, with some others as group exercises.

*Why will people be interested: *
**This is a practical session to help teachers integrate micro:bit into their classes. It can accommodate all levels of experience and teachers and non-teachers are welcome.

*What level of audience: *
**Novice

*More information about you (public): *
**Stephen has been a Python programmer since 2000. He trained as a mathematician and electrical engineer, with a PhD in signal processing for radar target detection. After a period as a management consultant, he worked for credit card companies in Australia and The Netherlands, running areas like marketing, risk, operations and strategy. Six years ago, he moved back into technology and joined JPMorgan in London, where his team uses Python to build trading, risk management and analytics systems.

*More information about you (private): *
**I presented the tutorial "Pandas from the Inside" at PyData London on 6 May 2016. I have also submitted a separate proposal on motion sensors data fusion for the main PyCon UK conference.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160627/812d41fc/attachment.html>

From l0c4rd at gmail.com  Mon Jun 27 06:52:42 2016
From: l0c4rd at gmail.com (Locard)
Date: Mon, 27 Jun 2016 11:52:42 +0100
Subject: [Microbit-Python] Pull Requests
Message-ID: <ff6a222c-31f9-9b6e-e3cf-cbcc358ce87b@gmail.com>

Hello,

Not sure if this is the right place to email - I've had a pull request 
on the main branch of uflash for like three weeks with no activity. 
What's going on? Are you guys maintaining uflash?

Cheers,
Locard


From ntoll at ntoll.org  Mon Jun 27 06:55:44 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Mon, 27 Jun 2016 11:55:44 +0100
Subject: [Microbit-Python] Pull Requests
In-Reply-To: <ff6a222c-31f9-9b6e-e3cf-cbcc358ce87b@gmail.com>
References: <ff6a222c-31f9-9b6e-e3cf-cbcc358ce87b@gmail.com>
Message-ID: <57710630.9020301@ntoll.org>

On 27/06/16 11:52, Locard wrote:
> Hello,
> 
> Not sure if this is the right place to email - I've had a pull request
> on the main branch of uflash for like three weeks with no activity.
> What's going on? Are you guys maintaining uflash?
> 
> Cheers,
> Locard
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

Hi,

Sorry, that's my fault. Put it down to
too-much-to-do-and-not-enough-time-to-do-it-in. I'll try to take a look
this evening when I get home for "real work" (tm).

In future, just ping me via GitHub.

N.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160627/4433a822/attachment.sig>

From nevil.hunt at hotmail.co.uk  Mon Jun 27 13:12:41 2016
From: nevil.hunt at hotmail.co.uk (Nevil Hunt)
Date: Mon, 27 Jun 2016 18:12:41 +0100
Subject: [Microbit-Python] PyCon UK proposal - Enriching Maths and
 Physics teaching with Micro:bit motion sensors
In-Reply-To: <5770716A.5090906@stevesimmons.com>
References: <57706E55.5090605@stevesimmons.com>,
 <5770716A.5090906@stevesimmons.com>
Message-ID: <DUB131-W76091A3E30884206151EF8C3210@phx.gbl>

Hi Stephen, Leona, Nigel,
 
If your ideas need extra sensors connected to the micro:bit I'm happy to send you some of the boards I've had made which make doing so easier (see attached photos)
 
zbit:builder bolts onto the bottom of the micro:bit and provides a grid for components to be soldered with access to all GPIO and power.
 
zbit:breadboard is similar but requires no soldering.
 
Also, I've just submitted a proposal to demonstrate some of my other zbit:connect boards on Teachers day at PyCon so I look forward to meeting you and anyone else involved with micro python on that day.
 
 
Regards,
 
Nevil
 
To: microbit at python.org
From: mail at stevesimmons.com
Date: Mon, 27 Jun 2016 01:20:58 +0100
Subject: [Microbit-Python] PyCon UK proposal - Enriching Maths and Physics teaching with Micro:bit motion sensors
CC: stestagg at gmail.com; leonaso43 at googlemail.com


  

    
  
  
    Hi everyone,

    

    I mentioned on this list a couple of weeks ago an idea to run a
    session at PyCon UK Teachers' Day on using the Micro:bit's motion
    sensors. 

    

    A number of people - including Leona, Steve and Nigel (Cc-ed) -
    replied wanting to get involved.

    

    Encouraged by this, I have just submitted the outline below. It
    hopefully gives the conference organisers enough to say "Yup, go for
    it" while leaving a lot of space for us to decide exactly what to
    present.

    

    I am on holiday next week so will finally have time to email
    everyone who has expressed interest about working together sorting
    out the details.

    

    Thanks

    Stephen

    

    

     

      Title: 

      Enriching Maths and Physics teaching with Micro:bit motion sensors

      

      What are you proposing? 

       A workshop for Teachers' Day 

      (duration/number of attendees are flexible. TBD with PyCon UK
      organisers)

      

      Abstract: 

       The BBC Micro:bit has powerful accelerometer and compass
      motion sensors. While they are fun for kids to play with, we show
      how they can also be used in class to bring some key Maths and
      Physics principles to life.

      

      This workshop session is intended for teachers who want to learn
      about using  micro:bit in their classes. No specific knowledge of
      micro:bit or Python programming is assumed. People who already
      know Python and micro:bit are also welcome to join in, especially
      if you can help the teachers get started.

      

      Teachers and helpers are asked to send their ideas for teaching
      examples to me at mail at stevesimmons.com
      well before the Teachers' Day. We will write up several examples
      to present in full, with some others as group exercises.   

      

      Why will people be interested: 

       This is a practical session to help teachers integrate
      micro:bit into their classes. It can accommodate all levels of
      experience and teachers and non-teachers are welcome. 

      

      What level of audience: 

       Novice

      

      More information about you (public): 

       Stephen has been a Python programmer since 2000. He
      trained as a mathematician and electrical engineer, with a PhD in
      signal processing for radar target detection. After a period as a
      management consultant, he worked for credit card companies in
      Australia and The Netherlands, running areas like marketing, risk,
      operations and strategy. Six years ago, he moved back into
      technology and joined JPMorgan in London, where his team uses
      Python to build trading, risk management and analytics systems.

      

      More information about you (private): 

       I presented the tutorial "Pandas from the Inside" at
      PyData London on 6 May 2016. I have also submitted a separate
      proposal on motion sensors data fusion for the main PyCon UK
      conference.

      

    
    

  


_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160627/c0ac91a1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ZbitBuilder_photo.jpg
Type: image/jpeg
Size: 360909 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/microbit/attachments/20160627/c0ac91a1/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ZbitBreadboard_photo.jpg
Type: image/jpeg
Size: 270374 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/microbit/attachments/20160627/c0ac91a1/attachment-0003.jpg>

From jeff at perfectmotion.co.uk  Thu Jun 30 09:47:21 2016
From: jeff at perfectmotion.co.uk (Jeff Young)
Date: Thu, 30 Jun 2016 14:47:21 +0100
Subject: [Microbit-Python] another maximum size of program thread
Message-ID: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>

Hi All

 

First time posting here.  Checked the archives and found my exact problem
outlined in a thread titled 'Maximum Size of Microbit Python Program' from
Jun '16.

I've tried a few things and I'm hitting the 'size of script' memory problem
as outlined in a post from Nicholas Tollervey.  Runtime memory is fine.

 

The program never starts and I just see;

 

MemoryError: memory allocation failed, allocating 3688 bytes

MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822

 

The thread doesn't really reach any solutions so I was wondering if anyone
had found a workround ?  I've tried Mu and online editors.  Same result.
I'm seeing the messages via REPL in Mu

 

My program is 127 lines working but add in another 8 lines and it breaks.
No comments in the code ;-)

 

As an aside I originally wrote it using python classes and objects but found
I quickly hit the runtime error limit after about 3 or 4 objects.  Rewrote
with simple lists and we're up to 20 objects before hitting the runtime
limit.  I'm thinking classes/objects consume a lot of memory.  Also
lists-of-lists seem quite memory hungry.

 

It would be great to be able to see how much memory is being consumed/free
during runtime.  Great to be able to see the size of objects etc in memory.

 

I'm also wondering it there is some way to re-balance the memory
partitioning between the block of memory that holds the code and the runtime
memory ? ie take a few kb from the run time partition and add it to the code
partition ?

 

Thanks

 

Jeff

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160630/4b4cabd4/attachment.html>

From ntoll at ntoll.org  Thu Jun 30 09:54:55 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Thu, 30 Jun 2016 14:54:55 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
Message-ID: <577524AF.9050208@ntoll.org>

Jeff,

A quick thought. If it's script length that's the problem, you could
just use the file-system. Viz:

https://microbit-micropython.readthedocs.io/en/latest/tutorials/storage.html#mainly-main-py

Hope this helps,

N.

On 30/06/16 14:47, Jeff Young wrote:
> Hi All
> 
>  
> 
> First time posting here.  Checked the archives and found my exact
> problem outlined in a thread titled ?Maximum Size of Microbit Python
> Program? from Jun ?16.
> 
> I?ve tried a few things and I?m hitting the ?size of script? memory
> problem as outlined in a post from Nicholas Tollervey.  Runtime memory
> is fine.
> 
>  
> 
> The program never starts and I just see;
> 
>  
> 
> MemoryError: memory allocation failed, allocating 3688 bytes
> 
> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
> 
>  
> 
> The thread doesn?t really reach any solutions so I was wondering if
> anyone had found a workround ?  I?ve tried Mu and online editors.  Same
> result.  I?m seeing the messages via REPL in Mu
> 
>  
> 
> My program is 127 lines working but add in another 8 lines and it
> breaks.  No comments in the code ;-)
> 
>  
> 
> As an aside I originally wrote it using python classes and objects but
> found I quickly hit the runtime error limit after about 3 or 4 objects. 
> Rewrote with simple lists and we?re up to 20 objects before hitting the
> runtime limit.  I?m thinking classes/objects consume a lot of memory. 
> Also lists-of-lists seem quite memory hungry.
> 
>  
> 
> It would be great to be able to see how much memory is being
> consumed/free during runtime.  Great to be able to see the size of
> objects etc in memory.
> 
>  
> 
> I?m also wondering it there is some way to re-balance the memory
> partitioning between the block of memory that holds the code and the
> runtime memory ? ie take a few kb from the run time partition and add it
> to the code partition ?
> 
>  
> 
> Thanks
> 
>  
> 
> Jeff
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 
are you in a meeting @be

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160630/0252def7/attachment.sig>

From jeff at perfectmotion.co.uk  Thu Jun 30 10:35:00 2016
From: jeff at perfectmotion.co.uk (Jeff Young)
Date: Thu, 30 Jun 2016 15:35:00 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <577524AF.9050208@ntoll.org>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
Message-ID: <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>

Good idea.  I gave it a try...

Installed microfs on my PC with a 'pip install microfs'
Flashed the microbit from the mu editor with a blank file. ( installed
runtime)
Uploaded the first test script to the microbit with 'ufs  put main.py'
Hit the restart button.
It worked perfectly with this basic script ( main.py )

from microbit import *
while True:
    display.scroll('Hello, World!')
    display.show(Image.HEART)
    sleep(2000)

Tried with my problem script getting smaller and smaller...

ufs put memory.py
MemoryError: memory allocation failed, allocating 3381 bytes

ufs put main.py
MemoryError: memory allocation failed, allocating 3087 bytes

ufs put main.py
MemoryError: memory allocation failed, allocating 2756 bytes

I even got past the point where the SAME code loads and runs from mu ! i.e
If I take the 2756bytes version above and load it into Mu and flash it
works.

Close but no cigar...

-----Original Message-----
From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
On Behalf Of Nicholas H.Tollervey
Sent: 30 June 2016 14:55
To: microbit at python.org
Subject: Re: [Microbit-Python] another maximum size of program thread

Jeff,

A quick thought. If it's script length that's the problem, you could just
use the file-system. Viz:

https://microbit-micropython.readthedocs.io/en/latest/tutorials/storage.html
#mainly-main-py

Hope this helps,

N.

On 30/06/16 14:47, Jeff Young wrote:
> Hi All
> 
>  
> 
> First time posting here.  Checked the archives and found my exact 
> problem outlined in a thread titled 'Maximum Size of Microbit Python 
> Program' from Jun '16.
> 
> I've tried a few things and I'm hitting the 'size of script' memory 
> problem as outlined in a post from Nicholas Tollervey.  Runtime memory 
> is fine.
> 
>  
> 
> The program never starts and I just see;
> 
>  
> 
> MemoryError: memory allocation failed, allocating 3688 bytes
> 
> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
> 
>  
> 
> The thread doesn't really reach any solutions so I was wondering if 
> anyone had found a workround ?  I've tried Mu and online editors.  
> Same result.  I'm seeing the messages via REPL in Mu
> 
>  
> 
> My program is 127 lines working but add in another 8 lines and it 
> breaks.  No comments in the code ;-)
> 
>  
> 
> As an aside I originally wrote it using python classes and objects but 
> found I quickly hit the runtime error limit after about 3 or 4 objects.
> Rewrote with simple lists and we're up to 20 objects before hitting 
> the runtime limit.  I'm thinking classes/objects consume a lot of memory.
> Also lists-of-lists seem quite memory hungry.
> 
>  
> 
> It would be great to be able to see how much memory is being 
> consumed/free during runtime.  Great to be able to see the size of 
> objects etc in memory.
> 
>  
> 
> I'm also wondering it there is some way to re-balance the memory 
> partitioning between the block of memory that holds the code and the 
> runtime memory ? ie take a few kb from the run time partition and add 
> it to the code partition ?
> 
>  
> 
> Thanks
> 
>  
> 
> Jeff
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 
are you in a meeting @be



From ntoll at ntoll.org  Thu Jun 30 10:38:15 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Thu, 30 Jun 2016 15:38:15 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
Message-ID: <57752ED7.9000403@ntoll.org>

I believe there is a max file length due to the constraints of the
device (Mark Shannon will be able to confirm this). Perhaps you're
hitting that? Why not modularise your code and import it as required in
main.py..?

Just guessing out loud here... YMMV.

:-)

N.

On 30/06/16 15:35, Jeff Young wrote:
> Good idea.  I gave it a try...
> 
> Installed microfs on my PC with a 'pip install microfs'
> Flashed the microbit from the mu editor with a blank file. ( installed
> runtime)
> Uploaded the first test script to the microbit with 'ufs  put main.py'
> Hit the restart button.
> It worked perfectly with this basic script ( main.py )
> 
> from microbit import *
> while True:
>     display.scroll('Hello, World!')
>     display.show(Image.HEART)
>     sleep(2000)
> 
> Tried with my problem script getting smaller and smaller...
> 
> ufs put memory.py
> MemoryError: memory allocation failed, allocating 3381 bytes
> 
> ufs put main.py
> MemoryError: memory allocation failed, allocating 3087 bytes
> 
> ufs put main.py
> MemoryError: memory allocation failed, allocating 2756 bytes
> 
> I even got past the point where the SAME code loads and runs from mu ! i.e
> If I take the 2756bytes version above and load it into Mu and flash it
> works.
> 
> Close but no cigar...
> 
> -----Original Message-----
> From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
> On Behalf Of Nicholas H.Tollervey
> Sent: 30 June 2016 14:55
> To: microbit at python.org
> Subject: Re: [Microbit-Python] another maximum size of program thread
> 
> Jeff,
> 
> A quick thought. If it's script length that's the problem, you could just
> use the file-system. Viz:
> 
> https://microbit-micropython.readthedocs.io/en/latest/tutorials/storage.html
> #mainly-main-py
> 
> Hope this helps,
> 
> N.
> 
> On 30/06/16 14:47, Jeff Young wrote:
>> Hi All
>>
>>  
>>
>> First time posting here.  Checked the archives and found my exact 
>> problem outlined in a thread titled 'Maximum Size of Microbit Python 
>> Program' from Jun '16.
>>
>> I've tried a few things and I'm hitting the 'size of script' memory 
>> problem as outlined in a post from Nicholas Tollervey.  Runtime memory 
>> is fine.
>>
>>  
>>
>> The program never starts and I just see;
>>
>>  
>>
>> MemoryError: memory allocation failed, allocating 3688 bytes
>>
>> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
>>
>>  
>>
>> The thread doesn't really reach any solutions so I was wondering if 
>> anyone had found a workround ?  I've tried Mu and online editors.  
>> Same result.  I'm seeing the messages via REPL in Mu
>>
>>  
>>
>> My program is 127 lines working but add in another 8 lines and it 
>> breaks.  No comments in the code ;-)
>>
>>  
>>
>> As an aside I originally wrote it using python classes and objects but 
>> found I quickly hit the runtime error limit after about 3 or 4 objects.
>> Rewrote with simple lists and we're up to 20 objects before hitting 
>> the runtime limit.  I'm thinking classes/objects consume a lot of memory.
>> Also lists-of-lists seem quite memory hungry.
>>
>>  
>>
>> It would be great to be able to see how much memory is being 
>> consumed/free during runtime.  Great to be able to see the size of 
>> objects etc in memory.
>>
>>  
>>
>> I'm also wondering it there is some way to re-balance the memory 
>> partitioning between the block of memory that holds the code and the 
>> runtime memory ? ie take a few kb from the run time partition and add 
>> it to the code partition ?
>>
>>  
>>
>> Thanks
>>
>>  
>>
>> Jeff
>>
>>  
>>
>>  
>>
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
> are you in a meeting @be
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160630/c20bb23a/attachment-0001.sig>

From l0c4rd at gmail.com  Thu Jun 30 10:44:20 2016
From: l0c4rd at gmail.com (Locard)
Date: Thu, 30 Jun 2016 15:44:20 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <57752ED7.9000403@ntoll.org>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
 <57752ED7.9000403@ntoll.org>
Message-ID: <e991175c-8f96-32e1-acee-3a42e95bacaf@gmail.com>

I've got something that might help you - was hoping to send you a link 
to it this afternoon, but despite been working on it all of yesterday 
and today, but it isn't quite finished yet.

So uh... bear with me a sec :)


Locard


On 30/06/2016 15:38, Nicholas H.Tollervey wrote:
> I believe there is a max file length due to the constraints of the
> device (Mark Shannon will be able to confirm this). Perhaps you're
> hitting that? Why not modularise your code and import it as required in
> main.py..?
>
> Just guessing out loud here... YMMV.
>
> :-)
>
> N.
>
> On 30/06/16 15:35, Jeff Young wrote:
>> Good idea.  I gave it a try...
>>
>> Installed microfs on my PC with a 'pip install microfs'
>> Flashed the microbit from the mu editor with a blank file. ( installed
>> runtime)
>> Uploaded the first test script to the microbit with 'ufs  put main.py'
>> Hit the restart button.
>> It worked perfectly with this basic script ( main.py )
>>
>> from microbit import *
>> while True:
>>      display.scroll('Hello, World!')
>>      display.show(Image.HEART)
>>      sleep(2000)
>>
>> Tried with my problem script getting smaller and smaller...
>>
>> ufs put memory.py
>> MemoryError: memory allocation failed, allocating 3381 bytes
>>
>> ufs put main.py
>> MemoryError: memory allocation failed, allocating 3087 bytes
>>
>> ufs put main.py
>> MemoryError: memory allocation failed, allocating 2756 bytes
>>
>> I even got past the point where the SAME code loads and runs from mu ! i.e
>> If I take the 2756bytes version above and load it into Mu and flash it
>> works.
>>
>> Close but no cigar...
>>
>> -----Original Message-----
>> From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
>> On Behalf Of Nicholas H.Tollervey
>> Sent: 30 June 2016 14:55
>> To: microbit at python.org
>> Subject: Re: [Microbit-Python] another maximum size of program thread
>>
>> Jeff,
>>
>> A quick thought. If it's script length that's the problem, you could just
>> use the file-system. Viz:
>>
>> https://microbit-micropython.readthedocs.io/en/latest/tutorials/storage.html
>> #mainly-main-py
>>
>> Hope this helps,
>>
>> N.
>>
>> On 30/06/16 14:47, Jeff Young wrote:
>>> Hi All
>>>
>>>   
>>>
>>> First time posting here.  Checked the archives and found my exact
>>> problem outlined in a thread titled 'Maximum Size of Microbit Python
>>> Program' from Jun '16.
>>>
>>> I've tried a few things and I'm hitting the 'size of script' memory
>>> problem as outlined in a post from Nicholas Tollervey.  Runtime memory
>>> is fine.
>>>
>>>   
>>>
>>> The program never starts and I just see;
>>>
>>>   
>>>
>>> MemoryError: memory allocation failed, allocating 3688 bytes
>>>
>>> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
>>>
>>>   
>>>
>>> The thread doesn't really reach any solutions so I was wondering if
>>> anyone had found a workround ?  I've tried Mu and online editors.
>>> Same result.  I'm seeing the messages via REPL in Mu
>>>
>>>   
>>>
>>> My program is 127 lines working but add in another 8 lines and it
>>> breaks.  No comments in the code ;-)
>>>
>>>   
>>>
>>> As an aside I originally wrote it using python classes and objects but
>>> found I quickly hit the runtime error limit after about 3 or 4 objects.
>>> Rewrote with simple lists and we're up to 20 objects before hitting
>>> the runtime limit.  I'm thinking classes/objects consume a lot of memory.
>>> Also lists-of-lists seem quite memory hungry.
>>>
>>>   
>>>
>>> It would be great to be able to see how much memory is being
>>> consumed/free during runtime.  Great to be able to see the size of
>>> objects etc in memory.
>>>
>>>   
>>>
>>> I'm also wondering it there is some way to re-balance the memory
>>> partitioning between the block of memory that holds the code and the
>>> runtime memory ? ie take a few kb from the run time partition and add
>>> it to the code partition ?
>>>
>>>   
>>>
>>> Thanks
>>>
>>>   
>>>
>>> Jeff
>>>
>>>   
>>>
>>>   
>>>
>>>
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>> are you in a meeting @be
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160630/f436441d/attachment.html>

From l0c4rd at gmail.com  Thu Jun 30 10:55:57 2016
From: l0c4rd at gmail.com (Locard)
Date: Thu, 30 Jun 2016 15:55:57 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <57752ED7.9000403@ntoll.org>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
 <57752ED7.9000403@ntoll.org>
Message-ID: <0046a8bc-72f5-04e9-f4db-9276f9245eec@gmail.com>

One other thing:

> It would be great to be able to see how much memory is being
> consumed/free during runtime.  Great to be able to see the size of
> objects etc in memory.


This you can do. try:


     from micropython import mem_info

     #print memory info
     mem_info()

     #print verbose memory info
     mem_info("whatever")



Should give you the info you're after.

Locard


On 30/06/2016 15:38, Nicholas H.Tollervey wrote:
> I believe there is a max file length due to the constraints of the
> device (Mark Shannon will be able to confirm this). Perhaps you're
> hitting that? Why not modularise your code and import it as required in
> main.py..?
>
> Just guessing out loud here... YMMV.
>
> :-)
>
> N.
>
> On 30/06/16 15:35, Jeff Young wrote:
>> Good idea.  I gave it a try...
>>
>> Installed microfs on my PC with a 'pip install microfs'
>> Flashed the microbit from the mu editor with a blank file. ( installed
>> runtime)
>> Uploaded the first test script to the microbit with 'ufs  put main.py'
>> Hit the restart button.
>> It worked perfectly with this basic script ( main.py )
>>
>> from microbit import *
>> while True:
>>      display.scroll('Hello, World!')
>>      display.show(Image.HEART)
>>      sleep(2000)
>>
>> Tried with my problem script getting smaller and smaller...
>>
>> ufs put memory.py
>> MemoryError: memory allocation failed, allocating 3381 bytes
>>
>> ufs put main.py
>> MemoryError: memory allocation failed, allocating 3087 bytes
>>
>> ufs put main.py
>> MemoryError: memory allocation failed, allocating 2756 bytes
>>
>> I even got past the point where the SAME code loads and runs from mu ! i.e
>> If I take the 2756bytes version above and load it into Mu and flash it
>> works.
>>
>> Close but no cigar...
>>
>> -----Original Message-----
>> From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
>> On Behalf Of Nicholas H.Tollervey
>> Sent: 30 June 2016 14:55
>> To: microbit at python.org
>> Subject: Re: [Microbit-Python] another maximum size of program thread
>>
>> Jeff,
>>
>> A quick thought. If it's script length that's the problem, you could just
>> use the file-system. Viz:
>>
>> https://microbit-micropython.readthedocs.io/en/latest/tutorials/storage.html
>> #mainly-main-py
>>
>> Hope this helps,
>>
>> N.
>>
>> On 30/06/16 14:47, Jeff Young wrote:
>>> Hi All
>>>
>>>   
>>>
>>> First time posting here.  Checked the archives and found my exact
>>> problem outlined in a thread titled 'Maximum Size of Microbit Python
>>> Program' from Jun '16.
>>>
>>> I've tried a few things and I'm hitting the 'size of script' memory
>>> problem as outlined in a post from Nicholas Tollervey.  Runtime memory
>>> is fine.
>>>
>>>   
>>>
>>> The program never starts and I just see;
>>>
>>>   
>>>
>>> MemoryError: memory allocation failed, allocating 3688 bytes
>>>
>>> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
>>>
>>>   
>>>
>>> The thread doesn't really reach any solutions so I was wondering if
>>> anyone had found a workround ?  I've tried Mu and online editors.
>>> Same result.  I'm seeing the messages via REPL in Mu
>>>
>>>   
>>>
>>> My program is 127 lines working but add in another 8 lines and it
>>> breaks.  No comments in the code ;-)
>>>
>>>   
>>>
>>> As an aside I originally wrote it using python classes and objects but
>>> found I quickly hit the runtime error limit after about 3 or 4 objects.
>>> Rewrote with simple lists and we're up to 20 objects before hitting
>>> the runtime limit.  I'm thinking classes/objects consume a lot of memory.
>>> Also lists-of-lists seem quite memory hungry.
>>>
>>>   
>>>
>>> It would be great to be able to see how much memory is being
>>> consumed/free during runtime.  Great to be able to see the size of
>>> objects etc in memory.
>>>
>>>   
>>>
>>> I'm also wondering it there is some way to re-balance the memory
>>> partitioning between the block of memory that holds the code and the
>>> runtime memory ? ie take a few kb from the run time partition and add
>>> it to the code partition ?
>>>
>>>   
>>>
>>> Thanks
>>>
>>>   
>>>
>>> Jeff
>>>
>>>   
>>>
>>>   
>>>
>>>
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>> are you in a meeting @be
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160630/a2ca9c2e/attachment-0001.html>

From jeff at perfectmotion.co.uk  Thu Jun 30 11:06:28 2016
From: jeff at perfectmotion.co.uk (Jeff Young)
Date: Thu, 30 Jun 2016 16:06:28 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <57752ED7.9000403@ntoll.org>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
 <57752ED7.9000403@ntoll.org>
Message-ID: <004601d1d2e0$faa50100$efef0300$@perfectmotion.co.uk>

Yes there is definitely some limit in place.  

You think it may be a limit on the size of a single file?

I'll try modularising as you suggest.

Just as a matter of interest I think the run time partition is 8Kb

from microbit import *
x=[]
for i in range(0,9999):
    print(i)
    x.append(2)

from .... REPL.....

1021
1022
1023
1024
Traceback (most recent call last):
  File "__main__", line 6, in <module>
MemoryError: memory allocation failed, allocating 8192 bytes
MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822

so a list containing 1025 integers breaks the microbit at 8kb exactly.

So we have 8kb runtime space
My script that breaks is around 4kb ( 130 lines ) from windows explorer.
Gives us 12kb.  Is micropython ~4kb by any chance ?
Being able to change the balance ie runtime 6kb/code 6kb would be helpful.



-----Original Message-----
From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
On Behalf Of Nicholas H.Tollervey
Sent: 30 June 2016 15:38
To: microbit at python.org
Subject: Re: [Microbit-Python] another maximum size of program thread

I believe there is a max file length due to the constraints of the device
(Mark Shannon will be able to confirm this). Perhaps you're hitting that?
Why not modularise your code and import it as required in main.py..?

Just guessing out loud here... YMMV.

:-)

N.

On 30/06/16 15:35, Jeff Young wrote:
> Good idea.  I gave it a try...
> 
> Installed microfs on my PC with a 'pip install microfs'
> Flashed the microbit from the mu editor with a blank file. ( installed
> runtime)
> Uploaded the first test script to the microbit with 'ufs  put main.py'
> Hit the restart button.
> It worked perfectly with this basic script ( main.py )
> 
> from microbit import *
> while True:
>     display.scroll('Hello, World!')
>     display.show(Image.HEART)
>     sleep(2000)
> 
> Tried with my problem script getting smaller and smaller...
> 
> ufs put memory.py
> MemoryError: memory allocation failed, allocating 3381 bytes
> 
> ufs put main.py
> MemoryError: memory allocation failed, allocating 3087 bytes
> 
> ufs put main.py
> MemoryError: memory allocation failed, allocating 2756 bytes
> 
> I even got past the point where the SAME code loads and runs from mu ! 
> i.e If I take the 2756bytes version above and load it into Mu and 
> flash it works.
> 
> Close but no cigar...
> 
> -----Original Message-----
> From: Microbit 
> [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
> On Behalf Of Nicholas H.Tollervey
> Sent: 30 June 2016 14:55
> To: microbit at python.org
> Subject: Re: [Microbit-Python] another maximum size of program thread
> 
> Jeff,
> 
> A quick thought. If it's script length that's the problem, you could 
> just use the file-system. Viz:
> 
> https://microbit-micropython.readthedocs.io/en/latest/tutorials/storag
> e.html
> #mainly-main-py
> 
> Hope this helps,
> 
> N.
> 
> On 30/06/16 14:47, Jeff Young wrote:
>> Hi All
>>
>>  
>>
>> First time posting here.  Checked the archives and found my exact 
>> problem outlined in a thread titled 'Maximum Size of Microbit Python 
>> Program' from Jun '16.
>>
>> I've tried a few things and I'm hitting the 'size of script' memory 
>> problem as outlined in a post from Nicholas Tollervey.  Runtime 
>> memory is fine.
>>
>>  
>>
>> The program never starts and I just see;
>>
>>  
>>
>> MemoryError: memory allocation failed, allocating 3688 bytes
>>
>> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
>>
>>  
>>
>> The thread doesn't really reach any solutions so I was wondering if 
>> anyone had found a workround ?  I've tried Mu and online editors.
>> Same result.  I'm seeing the messages via REPL in Mu
>>
>>  
>>
>> My program is 127 lines working but add in another 8 lines and it 
>> breaks.  No comments in the code ;-)
>>
>>  
>>
>> As an aside I originally wrote it using python classes and objects 
>> but found I quickly hit the runtime error limit after about 3 or 4
objects.
>> Rewrote with simple lists and we're up to 20 objects before hitting 
>> the runtime limit.  I'm thinking classes/objects consume a lot of memory.
>> Also lists-of-lists seem quite memory hungry.
>>
>>  
>>
>> It would be great to be able to see how much memory is being 
>> consumed/free during runtime.  Great to be able to see the size of 
>> objects etc in memory.
>>
>>  
>>
>> I'm also wondering it there is some way to re-balance the memory 
>> partitioning between the block of memory that holds the code and the 
>> runtime memory ? ie take a few kb from the run time partition and add 
>> it to the code partition ?
>>
>>  
>>
>> Thanks
>>
>>  
>>
>> Jeff
>>
>>  
>>
>>  
>>
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
> are you in a meeting @be
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 




From jeff at perfectmotion.co.uk  Thu Jun 30 11:20:06 2016
From: jeff at perfectmotion.co.uk (Jeff Young)
Date: Thu, 30 Jun 2016 16:20:06 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <0046a8bc-72f5-04e9-f4db-9276f9245eec@gmail.com>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
 <57752ED7.9000403@ntoll.org> <0046a8bc-72f5-04e9-f4db-9276f9245eec@gmail.com>
Message-ID: <004d01d1d2e2$e201b6a0$a60523e0$@perfectmotion.co.uk>

That is very cool.

 

stack: 432 out of 1800

GC: total: 9600, used: 5088,.....: 451

stack: 432 out of 1800

GC: total: 9600, used: 5088, free: 4512stack: 432 out of 1800

GC: total: 9600, used: 5088, free: 4512

No. of 1 out of 1800

GC: total: 9600, used: 5088, free: 4512

No. of 1-out of 1800

GC: total: 9600, used: 5088, free: 4512

No. of 1-blocks: 7, 

GC: total: 9600, used: 5088, free: 4512

No. of 1-blocks: 7, 2-GC: total: 9600, used: 5088, free: 4512

No. of 1-blocks: 7, 2-blocks: 1, 9600, used: 5088, free: 4512

No. of 1-blocks: 7, 2-blocks: 1, max blk sz: 5088,
freeThBTL.......h.....htttttt..........htttttttt20000230:

00230: htThBTL.......h.....htttttt..........httttttttttttttttttt00230:
htThBTL.......h.....htttttt..........htttttttttttttttttttt0230:
ht00BTL.......h.....htttttt..........httttttttttttttttttttt....h

00630: ......h....htttttt..........httttttttttttttttttttt....h

00630: ......httttttthttt..........httttttttttttttttttttt....h

00630: ......httttttthttttthttttttttttttttttttttttttttttt....h

(3 lines all free)

 

Just need to figure out what I'm looking at ;-)

 

From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
On Behalf Of Locard
Sent: 30 June 2016 15:56
To: For Pythonic MicroBit related discussions
Subject: Re: [Microbit-Python] another maximum size of program thread

 

One other thing:
 
> It would be great to be able to see how much memory is being 
> consumed/free during runtime.  Great to be able to see the size of 
> objects etc in memory.
 
 
This you can do. try:
 
 
    from micropython import mem_info
 
    #print memory info
    mem_info()
 
    #print verbose memory info
    mem_info("whatever")
 
 
 
Should give you the info you're after.
 
Locard

 

On 30/06/2016 15:38, Nicholas H.Tollervey wrote:

I believe there is a max file length due to the constraints of the
device (Mark Shannon will be able to confirm this). Perhaps you're
hitting that? Why not modularise your code and import it as required in
main.py..?
 
Just guessing out loud here... YMMV.
 
:-)
 
N.
 
On 30/06/16 15:35, Jeff Young wrote:

Good idea.  I gave it a try...
 
Installed microfs on my PC with a 'pip install microfs'
Flashed the microbit from the mu editor with a blank file. ( installed
runtime)
Uploaded the first test script to the microbit with 'ufs  put main.py'
Hit the restart button.
It worked perfectly with this basic script ( main.py )
 
from microbit import *
while True:
    display.scroll('Hello, World!')
    display.show(Image.HEART)
    sleep(2000)
 
Tried with my problem script getting smaller and smaller...
 
ufs put memory.py
MemoryError: memory allocation failed, allocating 3381 bytes
 
ufs put main.py
MemoryError: memory allocation failed, allocating 3087 bytes
 
ufs put main.py
MemoryError: memory allocation failed, allocating 2756 bytes
 
I even got past the point where the SAME code loads and runs from mu ! i.e
If I take the 2756bytes version above and load it into Mu and flash it
works.
 
Close but no cigar...
 
-----Original Message-----
From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
On Behalf Of Nicholas H.Tollervey
Sent: 30 June 2016 14:55
To: microbit at python.org
Subject: Re: [Microbit-Python] another maximum size of program thread
 
Jeff,
 
A quick thought. If it's script length that's the problem, you could just
use the file-system. Viz:
 
https://microbit-micropython.readthedocs.io/en/latest/tutorials/storage.html
#mainly-main-py
 
Hope this helps,
 
N.
 
On 30/06/16 14:47, Jeff Young wrote:

Hi All
 
 
 
First time posting here.  Checked the archives and found my exact 
problem outlined in a thread titled 'Maximum Size of Microbit Python 
Program' from Jun '16.
 
I've tried a few things and I'm hitting the 'size of script' memory 
problem as outlined in a post from Nicholas Tollervey.  Runtime memory 
is fine.
 
 
 
The program never starts and I just see;
 
 
 
MemoryError: memory allocation failed, allocating 3688 bytes
 
MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
 
 
 
The thread doesn't really reach any solutions so I was wondering if 
anyone had found a workround ?  I've tried Mu and online editors.  
Same result.  I'm seeing the messages via REPL in Mu
 
 
 
My program is 127 lines working but add in another 8 lines and it 
breaks.  No comments in the code ;-)
 
 
 
As an aside I originally wrote it using python classes and objects but 
found I quickly hit the runtime error limit after about 3 or 4 objects.
Rewrote with simple lists and we're up to 20 objects before hitting 
the runtime limit.  I'm thinking classes/objects consume a lot of memory.
Also lists-of-lists seem quite memory hungry.
 
 
 
It would be great to be able to see how much memory is being 
consumed/free during runtime.  Great to be able to see the size of 
objects etc in memory.
 
 
 
I'm also wondering it there is some way to re-balance the memory 
partitioning between the block of memory that holds the code and the 
runtime memory ? ie take a few kb from the run time partition and add 
it to the code partition ?
 
 
 
Thanks
 
 
 
Jeff
 
 
 
 
 
 
 
_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit
 

are you in a meeting @be
 
 
_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit
 

 
 






_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160630/fe6be186/attachment-0001.html>

From l0c4rd at gmail.com  Thu Jun 30 11:23:11 2016
From: l0c4rd at gmail.com (Locard)
Date: Thu, 30 Jun 2016 16:23:11 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <004d01d1d2e2$e201b6a0$a60523e0$@perfectmotion.co.uk>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
 <57752ED7.9000403@ntoll.org> <0046a8bc-72f5-04e9-f4db-9276f9245eec@gmail.com>
 <004d01d1d2e2$e201b6a0$a60523e0$@perfectmotion.co.uk>
Message-ID: <b6e9e3de-cd14-4d20-e6ad-f2d439b503a6@gmail.com>

if it helps, "stack" is how much of your allocated stack memory is being 
used,
"GC" is the garbage collector, so that's dynamically-allocated memory,

but all those 'h's and 't's?

... what exactly is your program doing?


Locard

On 30/06/2016 16:20, Jeff Young wrote:
>
> That is very cool.
>
> stack: 432 out of 1800
>
> GC: total: 9600, used: 5088,.....: 451
>
> stack: 432 out of 1800
>
> GC: total: 9600, used: 5088, free: 4512stack: 432 out of 1800
>
> GC: total: 9600, used: 5088, free: 4512
>
> No. of 1 out of 1800
>
> GC: total: 9600, used: 5088, free: 4512
>
> No. of 1-out of 1800
>
> GC: total: 9600, used: 5088, free: 4512
>
> No. of 1-blocks: 7,
>
> GC: total: 9600, used: 5088, free: 4512
>
> No. of 1-blocks: 7, 2-GC: total: 9600, used: 5088, free: 4512
>
> No. of 1-blocks: 7, 2-blocks: 1, 9600, used: 5088, free: 4512
>
> No. of 1-blocks: 7, 2-blocks: 1, max blk sz: 5088, 
> freeThBTL.......h.....htttttt..........htttttttt20000230:
>
> 00230: htThBTL.......h.....htttttt..........httttttttttttttttttt00230: 
> htThBTL.......h.....htttttt..........htttttttttttttttttttt0230: 
> ht00BTL.......h.....htttttt..........httttttttttttttttttttt....h
>
> 00630: ......h....htttttt..........httttttttttttttttttttt....h
>
> 00630: ......httttttthttt..........httttttttttttttttttttt....h
>
> 00630: ......httttttthttttthttttttttttttttttttttttttttttt....h
>
> (3 lines all free)
>
> Just need to figure out what I?m looking at ;-)
>
> *From:*Microbit 
> [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org] *On 
> Behalf Of *Locard
> *Sent:* 30 June 2016 15:56
> *To:* For Pythonic MicroBit related discussions
> *Subject:* Re: [Microbit-Python] another maximum size of program thread
>
> One other thing:
> > It would be great to be able to see how much memory is being
> > consumed/free during runtime.  Great to be able to see the size of
> > objects etc in memory.
> This you can do. try:
>      from micropython import mem_info
>      #print memory info
>      mem_info()
>      #print verbose memory info
>      mem_info("whatever")
> Should give you the info you're after.
> Locard
>
> On 30/06/2016 15:38, Nicholas H.Tollervey wrote:
>
>     I believe there is a max file length due to the constraints of the
>
>     device (Mark Shannon will be able to confirm this). Perhaps you're
>
>     hitting that? Why not modularise your code and import it as required in
>
>     main.py..?
>
>     Just guessing out loud here... YMMV.
>
>     :-)
>
>     N.
>
>     On 30/06/16 15:35, Jeff Young wrote:
>
>         Good idea.  I gave it a try...
>
>         Installed microfs on my PC with a 'pip install microfs'
>
>         Flashed the microbit from the mu editor with a blank file. ( installed
>
>         runtime)
>
>         Uploaded the first test script to the microbit with 'ufs  put main.py'
>
>         Hit the restart button.
>
>         It worked perfectly with this basic script ( main.py )
>
>         from microbit import *
>
>         while True:
>
>              display.scroll('Hello, World!')
>
>              display.show(Image.HEART)
>
>              sleep(2000)
>
>         Tried with my problem script getting smaller and smaller...
>
>         ufs put memory.py
>
>         MemoryError: memory allocation failed, allocating 3381 bytes
>
>         ufs put main.py
>
>         MemoryError: memory allocation failed, allocating 3087 bytes
>
>         ufs put main.py
>
>         MemoryError: memory allocation failed, allocating 2756 bytes
>
>         I even got past the point where the SAME code loads and runs from mu ! i.e
>
>         If I take the 2756bytes version above and load it into Mu and flash it
>
>         works.
>
>         Close but no cigar...
>
>         -----Original Message-----
>
>         From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
>
>         On Behalf Of Nicholas H.Tollervey
>
>         Sent: 30 June 2016 14:55
>
>         To:microbit at python.org <mailto:microbit at python.org>
>
>         Subject: Re: [Microbit-Python] another maximum size of program thread
>
>         Jeff,
>
>         A quick thought. If it's script length that's the problem, you could just
>
>         use the file-system. Viz:
>
>         https://microbit-micropython.readthedocs.io/en/latest/tutorials/storage.html
>
>         #mainly-main-py
>
>         Hope this helps,
>
>         N.
>
>         On 30/06/16 14:47, Jeff Young wrote:
>
>             Hi All
>
>               
>
>             First time posting here.  Checked the archives and found my exact
>
>             problem outlined in a thread titled 'Maximum Size of Microbit Python
>
>             Program' from Jun '16.
>
>             I've tried a few things and I'm hitting the 'size of script' memory
>
>             problem as outlined in a post from Nicholas Tollervey.  Runtime memory
>
>             is fine.
>
>               
>
>             The program never starts and I just see;
>
>               
>
>             MemoryError: memory allocation failed, allocating 3688 bytes
>
>             MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
>
>               
>
>             The thread doesn't really reach any solutions so I was wondering if
>
>             anyone had found a workround ?  I've tried Mu and online editors.
>
>             Same result.  I'm seeing the messages via REPL in Mu
>
>               
>
>             My program is 127 lines working but add in another 8 lines and it
>
>             breaks.  No comments in the code ;-)
>
>               
>
>             As an aside I originally wrote it using python classes and objects but
>
>             found I quickly hit the runtime error limit after about 3 or 4 objects.
>
>             Rewrote with simple lists and we're up to 20 objects before hitting
>
>             the runtime limit.  I'm thinking classes/objects consume a lot of memory.
>
>             Also lists-of-lists seem quite memory hungry.
>
>               
>
>             It would be great to be able to see how much memory is being
>
>             consumed/free during runtime.  Great to be able to see the size of
>
>             objects etc in memory.
>
>               
>
>             I'm also wondering it there is some way to re-balance the memory
>
>             partitioning between the block of memory that holds the code and the
>
>             runtime memory ? ie take a few kb from the run time partition and add
>
>             it to the code partition ?
>
>               
>
>             Thanks
>
>               
>
>             Jeff
>
>               
>
>               
>
>             _______________________________________________
>
>             Microbit mailing list
>
>             Microbit at python.org <mailto:Microbit at python.org>
>
>             https://mail.python.org/mailman/listinfo/microbit
>
>         are you in a meeting @be
>
>         _______________________________________________
>
>         Microbit mailing list
>
>         Microbit at python.org <mailto:Microbit at python.org>
>
>         https://mail.python.org/mailman/listinfo/microbit
>
>
>
>
>     _______________________________________________
>
>     Microbit mailing list
>
>     Microbit at python.org <mailto:Microbit at python.org>
>
>     https://mail.python.org/mailman/listinfo/microbit
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160630/9c43935c/attachment-0001.html>

From jeff at perfectmotion.co.uk  Thu Jun 30 11:24:45 2016
From: jeff at perfectmotion.co.uk (Jeff Young)
Date: Thu, 30 Jun 2016 16:24:45 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <b6e9e3de-cd14-4d20-e6ad-f2d439b503a6@gmail.com>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
 <57752ED7.9000403@ntoll.org> <0046a8bc-72f5-04e9-f4db-9276f9245eec@gmail.com>
 <004d01d1d2e2$e201b6a0$a60523e0$@perfectmotion.co.uk>
 <b6e9e3de-cd14-4d20-e6ad-f2d439b503a6@gmail.com>
Message-ID: <005801d1d2e3$88dda010$9a98e030$@perfectmotion.co.uk>

from micropython import mem_info <<!

from microbit import *

 

x=[]

for i in range(0,2000):

    print(i)

    mem_info(x) <<! With or without x

    x.append(2)

    sleep(10)

 

From: Locard [mailto:l0c4rd at gmail.com] 
Sent: 30 June 2016 16:23
To: jeff at perfectmotion.co.uk; For Pythonic MicroBit related discussions
Subject: Re: [Microbit-Python] another maximum size of program thread

 

if it helps, "stack" is how much of your allocated stack memory is being
used,
"GC" is the garbage collector, so that's dynamically-allocated memory,

but all those 'h's and 't's?

... what exactly is your program doing?


Locard

On 30/06/2016 16:20, Jeff Young wrote:

That is very cool.

 

stack: 432 out of 1800

GC: total: 9600, used: 5088,.....: 451

stack: 432 out of 1800

GC: total: 9600, used: 5088, free: 4512stack: 432 out of 1800

GC: total: 9600, used: 5088, free: 4512

No. of 1 out of 1800

GC: total: 9600, used: 5088, free: 4512

No. of 1-out of 1800

GC: total: 9600, used: 5088, free: 4512

No. of 1-blocks: 7, 

GC: total: 9600, used: 5088, free: 4512

No. of 1-blocks: 7, 2-GC: total: 9600, used: 5088, free: 4512

No. of 1-blocks: 7, 2-blocks: 1, 9600, used: 5088, free: 4512

No. of 1-blocks: 7, 2-blocks: 1, max blk sz: 5088,
freeThBTL.......h.....htttttt..........htttttttt20000230:

00230: htThBTL.......h.....htttttt..........httttttttttttttttttt00230:
htThBTL.......h.....htttttt..........htttttttttttttttttttt0230:
ht00BTL.......h.....htttttt..........httttttttttttttttttttt....h

00630: ......h....htttttt..........httttttttttttttttttttt....h

00630: ......httttttthttt..........httttttttttttttttttttt....h

00630: ......httttttthttttthttttttttttttttttttttttttttttt....h

(3 lines all free)

 

Just need to figure out what I'm looking at ;-)

 

From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
On Behalf Of Locard
Sent: 30 June 2016 15:56
To: For Pythonic MicroBit related discussions
Subject: Re: [Microbit-Python] another maximum size of program thread

 

One other thing:
 
> It would be great to be able to see how much memory is being 
> consumed/free during runtime.  Great to be able to see the size of 
> objects etc in memory.
 
 
This you can do. try:
 
 
    from micropython import mem_info
 
    #print memory info
    mem_info()
 
    #print verbose memory info
    mem_info("whatever")
 
 
 
Should give you the info you're after.
 
Locard

 

On 30/06/2016 15:38, Nicholas H.Tollervey wrote:

I believe there is a max file length due to the constraints of the
device (Mark Shannon will be able to confirm this). Perhaps you're
hitting that? Why not modularise your code and import it as required in
main.py..?
 
Just guessing out loud here... YMMV.
 
:-)
 
N.
 
On 30/06/16 15:35, Jeff Young wrote:

Good idea.  I gave it a try...
 
Installed microfs on my PC with a 'pip install microfs'
Flashed the microbit from the mu editor with a blank file. ( installed
runtime)
Uploaded the first test script to the microbit with 'ufs  put main.py'
Hit the restart button.
It worked perfectly with this basic script ( main.py )
 
from microbit import *
while True:
    display.scroll('Hello, World!')
    display.show(Image.HEART)
    sleep(2000)
 
Tried with my problem script getting smaller and smaller...
 
ufs put memory.py
MemoryError: memory allocation failed, allocating 3381 bytes
 
ufs put main.py
MemoryError: memory allocation failed, allocating 3087 bytes
 
ufs put main.py
MemoryError: memory allocation failed, allocating 2756 bytes
 
I even got past the point where the SAME code loads and runs from mu ! i.e
If I take the 2756bytes version above and load it into Mu and flash it
works.
 
Close but no cigar...
 
-----Original Message-----
From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
On Behalf Of Nicholas H.Tollervey
Sent: 30 June 2016 14:55
To: microbit at python.org
Subject: Re: [Microbit-Python] another maximum size of program thread
 
Jeff,
 
A quick thought. If it's script length that's the problem, you could just
use the file-system. Viz:
 
https://microbit-micropython.readthedocs.io/en/latest/tutorials/storage.html
#mainly-main-py
 
Hope this helps,
 
N.
 
On 30/06/16 14:47, Jeff Young wrote:

Hi All
 
 
 
First time posting here.  Checked the archives and found my exact 
problem outlined in a thread titled 'Maximum Size of Microbit Python 
Program' from Jun '16.
 
I've tried a few things and I'm hitting the 'size of script' memory 
problem as outlined in a post from Nicholas Tollervey.  Runtime memory 
is fine.
 
 
 
The program never starts and I just see;
 
 
 
MemoryError: memory allocation failed, allocating 3688 bytes
 
MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
 
 
 
The thread doesn't really reach any solutions so I was wondering if 
anyone had found a workround ?  I've tried Mu and online editors.  
Same result.  I'm seeing the messages via REPL in Mu
 
 
 
My program is 127 lines working but add in another 8 lines and it 
breaks.  No comments in the code ;-)
 
 
 
As an aside I originally wrote it using python classes and objects but 
found I quickly hit the runtime error limit after about 3 or 4 objects.
Rewrote with simple lists and we're up to 20 objects before hitting 
the runtime limit.  I'm thinking classes/objects consume a lot of memory.
Also lists-of-lists seem quite memory hungry.
 
 
 
It would be great to be able to see how much memory is being 
consumed/free during runtime.  Great to be able to see the size of 
objects etc in memory.
 
 
 
I'm also wondering it there is some way to re-balance the memory 
partitioning between the block of memory that holds the code and the 
runtime memory ? ie take a few kb from the run time partition and add 
it to the code partition ?
 
 
 
Thanks
 
 
 
Jeff
 
 
 
 
 
 
 
_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit
 

are you in a meeting @be
 
 
_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit
 

 
 







_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit

 






_______________________________________________
Microbit mailing list
Microbit at python.org
https://mail.python.org/mailman/listinfo/microbit

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160630/75377fcc/attachment-0001.html>

From jeff at perfectmotion.co.uk  Thu Jun 30 11:30:53 2016
From: jeff at perfectmotion.co.uk (Jeff Young)
Date: Thu, 30 Jun 2016 16:30:53 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <57752ED7.9000403@ntoll.org>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
 <57752ED7.9000403@ntoll.org>
Message-ID: <005d01d1d2e4$63fb3900$2bf1ab00$@perfectmotion.co.uk>

Just on the subject of modularising the code.  
Do I break the file up into 2 or 3 .py files one of which I call main.py.
Setup the imports in main.py etc.
Flash the microbit with a blank file.
Then 'ufs put'the 3 files over to the microbit
Hit reset and it will load main.py ?

-----Original Message-----
From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
On Behalf Of Nicholas H.Tollervey
Sent: 30 June 2016 15:38
To: microbit at python.org
Subject: Re: [Microbit-Python] another maximum size of program thread

I believe there is a max file length due to the constraints of the device
(Mark Shannon will be able to confirm this). Perhaps you're hitting that?
Why not modularise your code and import it as required in main.py..?

Just guessing out loud here... YMMV.

:-)

N.

On 30/06/16 15:35, Jeff Young wrote:
> Good idea.  I gave it a try...
> 
> Installed microfs on my PC with a 'pip install microfs'
> Flashed the microbit from the mu editor with a blank file. ( installed
> runtime)
> Uploaded the first test script to the microbit with 'ufs  put main.py'
> Hit the restart button.
> It worked perfectly with this basic script ( main.py )
> 
> from microbit import *
> while True:
>     display.scroll('Hello, World!')
>     display.show(Image.HEART)
>     sleep(2000)
> 
> Tried with my problem script getting smaller and smaller...
> 
> ufs put memory.py
> MemoryError: memory allocation failed, allocating 3381 bytes
> 
> ufs put main.py
> MemoryError: memory allocation failed, allocating 3087 bytes
> 
> ufs put main.py
> MemoryError: memory allocation failed, allocating 2756 bytes
> 
> I even got past the point where the SAME code loads and runs from mu ! 
> i.e If I take the 2756bytes version above and load it into Mu and 
> flash it works.
> 
> Close but no cigar...
> 
> -----Original Message-----
> From: Microbit 
> [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
> On Behalf Of Nicholas H.Tollervey
> Sent: 30 June 2016 14:55
> To: microbit at python.org
> Subject: Re: [Microbit-Python] another maximum size of program thread
> 
> Jeff,
> 
> A quick thought. If it's script length that's the problem, you could 
> just use the file-system. Viz:
> 
> https://microbit-micropython.readthedocs.io/en/latest/tutorials/storag
> e.html
> #mainly-main-py
> 
> Hope this helps,
> 
> N.
> 
> On 30/06/16 14:47, Jeff Young wrote:
>> Hi All
>>
>>  
>>
>> First time posting here.  Checked the archives and found my exact 
>> problem outlined in a thread titled 'Maximum Size of Microbit Python 
>> Program' from Jun '16.
>>
>> I've tried a few things and I'm hitting the 'size of script' memory 
>> problem as outlined in a post from Nicholas Tollervey.  Runtime 
>> memory is fine.
>>
>>  
>>
>> The program never starts and I just see;
>>
>>  
>>
>> MemoryError: memory allocation failed, allocating 3688 bytes
>>
>> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
>>
>>  
>>
>> The thread doesn't really reach any solutions so I was wondering if 
>> anyone had found a workround ?  I've tried Mu and online editors.
>> Same result.  I'm seeing the messages via REPL in Mu
>>
>>  
>>
>> My program is 127 lines working but add in another 8 lines and it 
>> breaks.  No comments in the code ;-)
>>
>>  
>>
>> As an aside I originally wrote it using python classes and objects 
>> but found I quickly hit the runtime error limit after about 3 or 4
objects.
>> Rewrote with simple lists and we're up to 20 objects before hitting 
>> the runtime limit.  I'm thinking classes/objects consume a lot of memory.
>> Also lists-of-lists seem quite memory hungry.
>>
>>  
>>
>> It would be great to be able to see how much memory is being 
>> consumed/free during runtime.  Great to be able to see the size of 
>> objects etc in memory.
>>
>>  
>>
>> I'm also wondering it there is some way to re-balance the memory 
>> partitioning between the block of memory that holds the code and the 
>> runtime memory ? ie take a few kb from the run time partition and add 
>> it to the code partition ?
>>
>>  
>>
>> Thanks
>>
>>  
>>
>> Jeff
>>
>>  
>>
>>  
>>
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
> are you in a meeting @be
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 




From ntoll at ntoll.org  Thu Jun 30 11:35:40 2016
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Thu, 30 Jun 2016 16:35:40 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <005d01d1d2e4$63fb3900$2bf1ab00$@perfectmotion.co.uk>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
 <57752ED7.9000403@ntoll.org>
 <005d01d1d2e4$63fb3900$2bf1ab00$@perfectmotion.co.uk>
Message-ID: <57753C4C.5050408@ntoll.org>

Correct. :-)

N.

On 30/06/16 16:30, Jeff Young wrote:
> Just on the subject of modularising the code.  
> Do I break the file up into 2 or 3 .py files one of which I call main.py.
> Setup the imports in main.py etc.
> Flash the microbit with a blank file.
> Then 'ufs put'the 3 files over to the microbit
> Hit reset and it will load main.py ?
> 
> -----Original Message-----
> From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
> On Behalf Of Nicholas H.Tollervey
> Sent: 30 June 2016 15:38
> To: microbit at python.org
> Subject: Re: [Microbit-Python] another maximum size of program thread
> 
> I believe there is a max file length due to the constraints of the device
> (Mark Shannon will be able to confirm this). Perhaps you're hitting that?
> Why not modularise your code and import it as required in main.py..?
> 
> Just guessing out loud here... YMMV.
> 
> :-)
> 
> N.
> 
> On 30/06/16 15:35, Jeff Young wrote:
>> Good idea.  I gave it a try...
>>
>> Installed microfs on my PC with a 'pip install microfs'
>> Flashed the microbit from the mu editor with a blank file. ( installed
>> runtime)
>> Uploaded the first test script to the microbit with 'ufs  put main.py'
>> Hit the restart button.
>> It worked perfectly with this basic script ( main.py )
>>
>> from microbit import *
>> while True:
>>     display.scroll('Hello, World!')
>>     display.show(Image.HEART)
>>     sleep(2000)
>>
>> Tried with my problem script getting smaller and smaller...
>>
>> ufs put memory.py
>> MemoryError: memory allocation failed, allocating 3381 bytes
>>
>> ufs put main.py
>> MemoryError: memory allocation failed, allocating 3087 bytes
>>
>> ufs put main.py
>> MemoryError: memory allocation failed, allocating 2756 bytes
>>
>> I even got past the point where the SAME code loads and runs from mu ! 
>> i.e If I take the 2756bytes version above and load it into Mu and 
>> flash it works.
>>
>> Close but no cigar...
>>
>> -----Original Message-----
>> From: Microbit 
>> [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
>> On Behalf Of Nicholas H.Tollervey
>> Sent: 30 June 2016 14:55
>> To: microbit at python.org
>> Subject: Re: [Microbit-Python] another maximum size of program thread
>>
>> Jeff,
>>
>> A quick thought. If it's script length that's the problem, you could 
>> just use the file-system. Viz:
>>
>> https://microbit-micropython.readthedocs.io/en/latest/tutorials/storag
>> e.html
>> #mainly-main-py
>>
>> Hope this helps,
>>
>> N.
>>
>> On 30/06/16 14:47, Jeff Young wrote:
>>> Hi All
>>>
>>>  
>>>
>>> First time posting here.  Checked the archives and found my exact 
>>> problem outlined in a thread titled 'Maximum Size of Microbit Python 
>>> Program' from Jun '16.
>>>
>>> I've tried a few things and I'm hitting the 'size of script' memory 
>>> problem as outlined in a post from Nicholas Tollervey.  Runtime 
>>> memory is fine.
>>>
>>>  
>>>
>>> The program never starts and I just see;
>>>
>>>  
>>>
>>> MemoryError: memory allocation failed, allocating 3688 bytes
>>>
>>> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
>>>
>>>  
>>>
>>> The thread doesn't really reach any solutions so I was wondering if 
>>> anyone had found a workround ?  I've tried Mu and online editors.
>>> Same result.  I'm seeing the messages via REPL in Mu
>>>
>>>  
>>>
>>> My program is 127 lines working but add in another 8 lines and it 
>>> breaks.  No comments in the code ;-)
>>>
>>>  
>>>
>>> As an aside I originally wrote it using python classes and objects 
>>> but found I quickly hit the runtime error limit after about 3 or 4
> objects.
>>> Rewrote with simple lists and we're up to 20 objects before hitting 
>>> the runtime limit.  I'm thinking classes/objects consume a lot of memory.
>>> Also lists-of-lists seem quite memory hungry.
>>>
>>>  
>>>
>>> It would be great to be able to see how much memory is being 
>>> consumed/free during runtime.  Great to be able to see the size of 
>>> objects etc in memory.
>>>
>>>  
>>>
>>> I'm also wondering it there is some way to re-balance the memory 
>>> partitioning between the block of memory that holds the code and the 
>>> runtime memory ? ie take a few kb from the run time partition and add 
>>> it to the code partition ?
>>>
>>>  
>>>
>>> Thanks
>>>
>>>  
>>>
>>> Jeff
>>>
>>>  
>>>
>>>  
>>>
>>>
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>> are you in a meeting @be
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20160630/4df20853/attachment.sig>

From jeff at perfectmotion.co.uk  Thu Jun 30 12:12:33 2016
From: jeff at perfectmotion.co.uk (Jeff Young)
Date: Thu, 30 Jun 2016 17:12:33 +0100
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <57753C4C.5050408@ntoll.org>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
 <57752ED7.9000403@ntoll.org>
 <005d01d1d2e4$63fb3900$2bf1ab00$@perfectmotion.co.uk>
 <57753C4C.5050408@ntoll.org>
Message-ID: <006301d1d2ea$36a46a20$a3ed3e60$@perfectmotion.co.uk>

Ok reporting back on modularising....

Moved 4 functions out of the main script into a files called support1.py
Renamed main script to main.py

So in a dos box we have...
30/06/2016  16:54             1,559 support1.py
30/06/2016  16:54             1,898 main.py

Loaded runtime only onto the microbit
Ufs put 2 files.
Ufs ls to check.
Reset.

Traceback (most recent call last):
  File "__main__", line 3, in <module>
MemoryError: memory allocation failed, allocating 1960 bytes
MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
Type "help()" for more information.

Line 3 of main.py is

1: from microbit import *
2: import random
3: from support1 import TakeUpSpace,make,move,update

Am I doing something stupid ?



-----Original Message-----
From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
On Behalf Of Nicholas H.Tollervey
Sent: 30 June 2016 16:36
To: microbit at python.org
Subject: Re: [Microbit-Python] another maximum size of program thread

Correct. :-)

N.

On 30/06/16 16:30, Jeff Young wrote:
> Just on the subject of modularising the code.  
> Do I break the file up into 2 or 3 .py files one of which I call main.py.
> Setup the imports in main.py etc.
> Flash the microbit with a blank file.
> Then 'ufs put'the 3 files over to the microbit Hit reset and it will 
> load main.py ?
> 
> -----Original Message-----
> From: Microbit 
> [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
> On Behalf Of Nicholas H.Tollervey
> Sent: 30 June 2016 15:38
> To: microbit at python.org
> Subject: Re: [Microbit-Python] another maximum size of program thread
> 
> I believe there is a max file length due to the constraints of the 
> device (Mark Shannon will be able to confirm this). Perhaps you're hitting
that?
> Why not modularise your code and import it as required in main.py..?
> 
> Just guessing out loud here... YMMV.
> 
> :-)
> 
> N.
> 
> On 30/06/16 15:35, Jeff Young wrote:
>> Good idea.  I gave it a try...
>>
>> Installed microfs on my PC with a 'pip install microfs'
>> Flashed the microbit from the mu editor with a blank file. ( 
>> installed
>> runtime)
>> Uploaded the first test script to the microbit with 'ufs  put main.py'
>> Hit the restart button.
>> It worked perfectly with this basic script ( main.py )
>>
>> from microbit import *
>> while True:
>>     display.scroll('Hello, World!')
>>     display.show(Image.HEART)
>>     sleep(2000)
>>
>> Tried with my problem script getting smaller and smaller...
>>
>> ufs put memory.py
>> MemoryError: memory allocation failed, allocating 3381 bytes
>>
>> ufs put main.py
>> MemoryError: memory allocation failed, allocating 3087 bytes
>>
>> ufs put main.py
>> MemoryError: memory allocation failed, allocating 2756 bytes
>>
>> I even got past the point where the SAME code loads and runs from mu ! 
>> i.e If I take the 2756bytes version above and load it into Mu and 
>> flash it works.
>>
>> Close but no cigar...
>>
>> -----Original Message-----
>> From: Microbit
>> [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org]
>> On Behalf Of Nicholas H.Tollervey
>> Sent: 30 June 2016 14:55
>> To: microbit at python.org
>> Subject: Re: [Microbit-Python] another maximum size of program thread
>>
>> Jeff,
>>
>> A quick thought. If it's script length that's the problem, you could 
>> just use the file-system. Viz:
>>
>> https://microbit-micropython.readthedocs.io/en/latest/tutorials/stora
>> g
>> e.html
>> #mainly-main-py
>>
>> Hope this helps,
>>
>> N.
>>
>> On 30/06/16 14:47, Jeff Young wrote:
>>> Hi All
>>>
>>>  
>>>
>>> First time posting here.  Checked the archives and found my exact 
>>> problem outlined in a thread titled 'Maximum Size of Microbit Python 
>>> Program' from Jun '16.
>>>
>>> I've tried a few things and I'm hitting the 'size of script' memory 
>>> problem as outlined in a post from Nicholas Tollervey.  Runtime 
>>> memory is fine.
>>>
>>>  
>>>
>>> The program never starts and I just see;
>>>
>>>  
>>>
>>> MemoryError: memory allocation failed, allocating 3688 bytes
>>>
>>> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
>>>
>>>  
>>>
>>> The thread doesn't really reach any solutions so I was wondering if 
>>> anyone had found a workround ?  I've tried Mu and online editors.
>>> Same result.  I'm seeing the messages via REPL in Mu
>>>
>>>  
>>>
>>> My program is 127 lines working but add in another 8 lines and it 
>>> breaks.  No comments in the code ;-)
>>>
>>>  
>>>
>>> As an aside I originally wrote it using python classes and objects 
>>> but found I quickly hit the runtime error limit after about 3 or 4
> objects.
>>> Rewrote with simple lists and we're up to 20 objects before hitting 
>>> the runtime limit.  I'm thinking classes/objects consume a lot of
memory.
>>> Also lists-of-lists seem quite memory hungry.
>>>
>>>  
>>>
>>> It would be great to be able to see how much memory is being 
>>> consumed/free during runtime.  Great to be able to see the size of 
>>> objects etc in memory.
>>>
>>>  
>>>
>>> I'm also wondering it there is some way to re-balance the memory 
>>> partitioning between the block of memory that holds the code and the 
>>> runtime memory ? ie take a few kb from the run time partition and 
>>> add it to the code partition ?
>>>
>>>  
>>>
>>> Thanks
>>>
>>>  
>>>
>>> Jeff
>>>
>>>  
>>>
>>>  
>>>
>>>
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>> are you in a meeting @be
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 




From dhylands at gmail.com  Thu Jun 30 13:31:37 2016
From: dhylands at gmail.com (Dave Hylands)
Date: Thu, 30 Jun 2016 10:31:37 -0700
Subject: [Microbit-Python] another maximum size of program thread
In-Reply-To: <004d01d1d2e2$e201b6a0$a60523e0$@perfectmotion.co.uk>
References: <002d01d1d2d5$ed501310$c7f03930$@perfectmotion.co.uk>
 <577524AF.9050208@ntoll.org>
 <003a01d1d2dc$956000f0$c02002d0$@perfectmotion.co.uk>
 <57752ED7.9000403@ntoll.org> <0046a8bc-72f5-04e9-f4db-9276f9245eec@gmail.com>
 <004d01d1d2e2$e201b6a0$a60523e0$@perfectmotion.co.uk>
Message-ID: <CABi1daHbpaPzMdN8wwdfvRY2L8k2nZ9d4kdF3MH6fH+2v0QZfQ@mail.gmail.com>

The portion with the h's and t's is showing you the heap. Each character
represents one heap block (on the pyboard this is 16 bytes - no sure for
the microbit).

The . is a free block, and any character is an allocated block. h means
that it's the head of a chain of blocks and t means its a tail block. So
160 byte allocation would consist of one h block followed by 9 t blocks.

Other letters are used to show different types of head blocks. The source
code is here:
https://github.com/bbcmicrobit/micropython/blob/master/source/py/gc.c#L732

T = tuple, L = list, D = dict, F = float, B = bytecode, M = module, m =
mark (I think that mark is part of the mark/sweep gc)

Dave Hylands

On Thu, Jun 30, 2016 at 8:20 AM, Jeff Young <jeff at perfectmotion.co.uk>
wrote:

> That is very cool.
>
>
>
> stack: 432 out of 1800
>
> GC: total: 9600, used: 5088,.....: 451
>
> stack: 432 out of 1800
>
> GC: total: 9600, used: 5088, free: 4512stack: 432 out of 1800
>
> GC: total: 9600, used: 5088, free: 4512
>
> No. of 1 out of 1800
>
> GC: total: 9600, used: 5088, free: 4512
>
> No. of 1-out of 1800
>
> GC: total: 9600, used: 5088, free: 4512
>
> No. of 1-blocks: 7,
>
> GC: total: 9600, used: 5088, free: 4512
>
> No. of 1-blocks: 7, 2-GC: total: 9600, used: 5088, free: 4512
>
> No. of 1-blocks: 7, 2-blocks: 1, 9600, used: 5088, free: 4512
>
> No. of 1-blocks: 7, 2-blocks: 1, max blk sz: 5088,
> freeThBTL.......h.....htttttt..........htttttttt20000230:
>
> 00230: htThBTL.......h.....htttttt..........httttttttttttttttttt00230:
> htThBTL.......h.....htttttt..........htttttttttttttttttttt0230:
> ht00BTL.......h.....htttttt..........httttttttttttttttttttt....h
>
> 00630: ......h....htttttt..........httttttttttttttttttttt....h
>
> 00630: ......httttttthttt..........httttttttttttttttttttt....h
>
> 00630: ......httttttthttttthttttttttttttttttttttttttttttt....h
>
> (3 lines all free)
>
>
>
> Just need to figure out what I?m looking at ;-)
>
>
>
> *From:* Microbit [mailto:microbit-bounces+jeff=
> perfectmotion.co.uk at python.org] *On Behalf Of *Locard
> *Sent:* 30 June 2016 15:56
> *To:* For Pythonic MicroBit related discussions
>
> *Subject:* Re: [Microbit-Python] another maximum size of program thread
>
>
>
> One other thing:
>
>
>
> > It would be great to be able to see how much memory is being
>
> > consumed/free during runtime.  Great to be able to see the size of
>
> > objects etc in memory.
>
>
>
>
>
> This you can do. try:
>
>
>
>
>
>     from micropython import mem_info
>
>
>
>     #print memory info
>
>     mem_info()
>
>
>
>     #print verbose memory info
>
>     mem_info("whatever")
>
>
>
>
>
>
>
> Should give you the info you're after.
>
>
>
> Locard
>
>
>
> On 30/06/2016 15:38, Nicholas H.Tollervey wrote:
>
> I believe there is a max file length due to the constraints of the
>
> device (Mark Shannon will be able to confirm this). Perhaps you're
>
> hitting that? Why not modularise your code and import it as required in
>
> main.py..?
>
>
>
> Just guessing out loud here... YMMV.
>
>
>
> :-)
>
>
>
> N.
>
>
>
> On 30/06/16 15:35, Jeff Young wrote:
>
> Good idea.  I gave it a try...
>
>
>
> Installed microfs on my PC with a 'pip install microfs'
>
> Flashed the microbit from the mu editor with a blank file. ( installed
>
> runtime)
>
> Uploaded the first test script to the microbit with 'ufs  put main.py'
>
> Hit the restart button.
>
> It worked perfectly with this basic script ( main.py )
>
>
>
> from microbit import *
>
> while True:
>
>     display.scroll('Hello, World!')
>
>     display.show(Image.HEART)
>
>     sleep(2000)
>
>
>
> Tried with my problem script getting smaller and smaller...
>
>
>
> ufs put memory.py
>
> MemoryError: memory allocation failed, allocating 3381 bytes
>
>
>
> ufs put main.py
>
> MemoryError: memory allocation failed, allocating 3087 bytes
>
>
>
> ufs put main.py
>
> MemoryError: memory allocation failed, allocating 2756 bytes
>
>
>
> I even got past the point where the SAME code loads and runs from mu ! i.e
>
> If I take the 2756bytes version above and load it into Mu and flash it
>
> works.
>
>
>
> Close but no cigar...
>
>
>
> -----Original Message-----
>
> From: Microbit [mailto:microbit-bounces+jeff=perfectmotion.co.uk at python.org <microbit-bounces+jeff=perfectmotion.co.uk at python.org>]
>
> On Behalf Of Nicholas H.Tollervey
>
> Sent: 30 June 2016 14:55
>
> To: microbit at python.org
>
> Subject: Re: [Microbit-Python] another maximum size of program thread
>
>
>
> Jeff,
>
>
>
> A quick thought. If it's script length that's the problem, you could just
>
> use the file-system. Viz:
>
>
>
> https://microbit-micropython.readthedocs.io/en/latest/tutorials/storage.html
>
> #mainly-main-py
>
>
>
> Hope this helps,
>
>
>
> N.
>
>
>
> On 30/06/16 14:47, Jeff Young wrote:
>
> Hi All
>
>
>
>
>
> First time posting here.  Checked the archives and found my exact
>
> problem outlined in a thread titled 'Maximum Size of Microbit Python
>
> Program' from Jun '16.
>
>
>
> I've tried a few things and I'm hitting the 'size of script' memory
>
> problem as outlined in a post from Nicholas Tollervey.  Runtime memory
>
> is fine.
>
>
>
>
>
> The program never starts and I just see;
>
>
>
>
>
> MemoryError: memory allocation failed, allocating 3688 bytes
>
>
>
> MicroPython v1.7-9-gbe020eb on 2016-04-18; micro:bit with nRF51822
>
>
>
>
>
> The thread doesn't really reach any solutions so I was wondering if
>
> anyone had found a workround ?  I've tried Mu and online editors.
>
> Same result.  I'm seeing the messages via REPL in Mu
>
>
>
>
>
> My program is 127 lines working but add in another 8 lines and it
>
> breaks.  No comments in the code ;-)
>
>
>
>
>
> As an aside I originally wrote it using python classes and objects but
>
> found I quickly hit the runtime error limit after about 3 or 4 objects.
>
> Rewrote with simple lists and we're up to 20 objects before hitting
>
> the runtime limit.  I'm thinking classes/objects consume a lot of memory.
>
> Also lists-of-lists seem quite memory hungry.
>
>
>
>
>
> It would be great to be able to see how much memory is being
>
> consumed/free during runtime.  Great to be able to see the size of
>
> objects etc in memory.
>
>
>
>
>
> I'm also wondering it there is some way to re-balance the memory
>
> partitioning between the block of memory that holds the code and the
>
> runtime memory ? ie take a few kb from the run time partition and add
>
> it to the code partition ?
>
>
>
>
>
> Thanks
>
>
>
>
>
> Jeff
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
> Microbit mailing list
>
> Microbit at python.org
>
> https://mail.python.org/mailman/listinfo/microbit
>
>
>
> are you in a meeting @be
>
>
>
>
>
> _______________________________________________
>
> Microbit mailing list
>
> Microbit at python.org
>
> https://mail.python.org/mailman/listinfo/microbit
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
> Microbit mailing list
>
> Microbit at python.org
>
> https://mail.python.org/mailman/listinfo/microbit
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>


-- 
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20160630/ece2702b/attachment-0001.html>