ESP8266 Community Forum

- Mon Mar 16, 2015 7:05 am #12050 Thanks Vitoa for the link. Going to try the integer version today.
@alon24 this is Travis-CI.
2 versions one with float enabled, and the other with float disabled only using integers.
Floating point uses more memory, not allowing code that worked on firmware builds without float enabled to load on float enabled firmware without memory issues.

- Mon Mar 16, 2015 7:34 am #12052 Thanks for the info.

So what is the entry point here with Travis.CI?
How can I use this or what can I get from it?

If you know...

- Sun Apr 05, 2015 8:25 am #13550 So the floats missing might be the cause of my current problem?

http://www.nodemcu.com/docs/node-module ... -readvdd33

Here it says it will output 3.315, but instead it just outputs 3, where node.readvdd33() does return 3315

Code: Select all-- Convert mV to V.
    v = node.readvdd33() / 1000
    print(v)
    v=nil
-- Output
3.315

- Wed Aug 05, 2015 9:52 am #25087 That appears to be the reason, yes.

How big of a difference in performance are we looking at between the float and integer firmware versions? I'm not planning on doing anything complicated, but if there's a drastic change I may stick with integer.

I'm going to control some ws2812 and a couple weather related sensors, so as long as there is still accurate timing, I can use float.

Does anyone have any input?