I've been doing a bunch with 32u4 based arduinos recently (pro
micro/leonardo/ss micro/etc).

With these, there's a bit in the start up to make sure that it doesn't
crash when talking to an uninitialized serial port, something like:

while( !Serial );

Or, you could check it with something like:
if( !Serial ) { return; }

and so on.  In any case, it's been my observation that when it's sitting in
these tight loops checking the hardware, the thing is basically running
all-out full speed.  Even just the ( Serial.available() ) function in these
situations can be super laggy.  Even just putting a delay in there helps a
ton.  eg:
while( !Serial ) { delay( 50 ); }

or somesuch.

It might not be the cause of the power drain, but there's a chance it is.
 maybe?

In my experience, those calls checking the serial port seemed to block the
system entirely and cause bad behaviors... :/

-s


On Wed, Jan 30, 2019 at 12:34 PM Brian White <[email protected]> wrote:

> I got Jimmy's code working on Teensy 3.5 & 3.6, and on Adafruit Feather
> 32u4 Adalogger
> And modified my copy somewhat. I was playing with getting the top-right
> corner of TS-DOS to display the current working directory, and reducing the
> power drain.
> Some changes are just gratuitous refactoring to suit myself, so that I
> could then make the functional changes.
>
> In this video there is a little mystery where the power drain is a little
> high on initial power-on, but behaves properly as soon as you actually talk
> to the device at least once. I think I figured that out and the current
> version behaves properly right from power-on.
>
> Teensy 3.5/6 and the Adafruit device are quite different and have
> different quirks. I never pulled both versions together into a single
> modular code base yet. I have some messy code to try to make the same code
> handle different devices by configurable options amd macros, but it's not
> really worked out and so it's still two separate branches, one for each
> device.
>
> I haven't done anything further since then.
>
> https://youtu.be/_lFqsHAlLyg
>
> My mods are in the two different branches here. The master branch is
> Jimmy's original code.
> https://github.com/aljex/SD2TPDD
>
> --
> bkw
>
> On Wed, Jan 30, 2019 at 3:52 AM VANDEN BOSSCHE JAN <
> [email protected]> wrote:
>
>> Someone was working on a TPDD emulator on Arduino. Is there any progress?
>> And/Or photos?
>>
>> As I'm starting a course on Arduino programming, I am now even more
>> interested. This could become the cheapest stand-alone TPDD emulator yet.
>>
>>
>> Greetings from the TyRannoSaurus
>> Jan-80   |\      _,,,--,,_
>> @ work  / ,`.-'`'   ._  \-;;,
>>        |,4-  ) )_    .;.(  `'-'
>>       <---''(_/._)--'(_\_)
>>
>> VIVAQUA et HYDROBRU ont fusionné.
>> VIVAQUA est votre société d'eau en Région de Bruxelles-Capitale.
>>
>> VIVAQUA en HYDROBRU zijn gefusioneerd.
>> VIVAQUA is uw waterbedrijf in het Brusselse Hoofdstedelijk Gewest.
>>
>> [http://www.vivaqua.be/facebook.png] Rejoignez-nous sur Facebook - Volg
>> ons op Facebook
>>
>> DISCLAIMER
>> Pensez à l'environnement, n'imprimez cette page et ses annexes que si
>> c'est nécessaire. Ce message électronique, y compris ses annexes, est
>> confidentiel et réservé à l’attention de son destinataire.  Si vous n'êtes
>> pas le destinataire de ce message, merci de le détruire et d’en informer
>> l’expéditeur. Toute divulgation, copie ou utilisation de ce mail est dans
>> ce cas interdite. La sécurité et l'exactitude des transmissions de messages
>> électroniques ne peuvent être garanties.
>> Denk aan het milieu; druk deze pagina en de bijlagen alleen af als het
>> nodig is. Dit e-mailbericht (inclusief zijn bijlagen) is vertrouwelijk en
>> is uitsluitend bestemd voor de geadresseerde. Als dit bericht niet voor u
>> bestemd is, wordt u verzocht het te wissen en de afzender te informeren.
>> Het is in dat geval niet toegestaan dit bericht te verspreiden, te kopiëren
>> of te gebruiken. We kunnen niet garanderen dat de gegevensoverdracht via
>> het internet veilig en nauwkeurig is.
>>
>
>
> --
> bkw
>


-- 
Scott Lawrence
[email protected]

Reply via email to