-
• #2
Thanks - I'll take a look at this...
-
• #3
Without testing the code, did you try to set throttle in options communications ?
I have had same problem with other modules, and that helped. -
• #4
JumJum, am sorry - I don't know what that means, or what to do !
It looks to me like there is a problem in big_number itself somewhere.
Pat
-
• #5
Fixed - just flash again and it should work.
-
• #6
Flash 1.60 ?
-
• #7
Oh - sorry. No need to flash - just click 'Send to Espruino' again
-
• #8
Works :) Brilliant. Thanks ever so. Absolutely amazed at your responsiveness !
-
• #9
How does this actually work without me actually re-flashing ? Does
require("big_number") actually reference something dynamically on the web when you press "Send to Espruino" ? Damn clever ! What is it actually calling ?
-
• #10
It is here : http://www.espruino.com/modules
Or take the WebIDE, click on settings, select communications and you will see. -
• #11
Yes - certain things (filesystem, graphics, http) are built in to Espruino - but most other things that you use
require
for are just bits of JavaScript. When you typerequire
and then clickSend to Espruino
, the Web IDE tries to find the JavaScript module with that name where @JumJum mentioned, and if it finds it then it'll copy it into Espruino first :)The Espruino is smart enough to do it itself as well (without the Web IDE) - but you need either to have the modules on an SD card, or to be connected to the internet via something like a CC3000.
-
• #12
Thanks, have never looked there before so was blissfully unaware of it !
-
• #13
Thanks Gordon. I had not taken the time to understand the mechanism at all. Now clear :) Thanks !
-
• #14
or to be connected to the internet via something like a CC3000.
This is in now? I remember you talking about this as a "sometime in the future" - but I don't see anything in the changelog about it...
-
• #15
Thanks, I just checked... Yes - that still needs implementing.
-
• #16
Cool.
Honestly, I'm not sure how valuable of a feature it even is, since people will typically program it with the IDE (and not have to worry about modules), or if running autonomously, they'll have either save()'ed with the modules they need loaded, or put them on the SD card.
And if it's running on it's own, you probably don't want it picking up any version of the module other than the one you developed with anyway. I could see it being done to save RAM (load a module, use it, kill it, then load the next module, because you can't fit all the modules in RAM, or something like that), but the sd card or eeprom is likely a better fit for that use case)
(sorry for bringing this off topic)
-
• #17
Yeah, it's a good point. Low priority anyway :)
Display works fine on I2C. Trying this code
but get this ..
Any ideas ?