Plugin 133 VL53L0X I2C Ranging LIDAR

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
QcVictor
Normal user
Posts: 46
Joined: 23 Feb 2016, 00:47

Plugin 133 VL53L0X I2C Ranging LIDAR

#1 Post by QcVictor » 28 Jun 2018, 14:51

Hi Guys
Try to compile from the latest sources the VL53L0X plugin from playground but get this error

Code: Select all

In file included from /Users/Pascal/Downloads/ESPEasy/ESPEasy.ino:76:0:
sketch/ESPEasy-Globals.h:375:20: fatal error: I2Cdev.h: No such file or directory
 #include <I2Cdev.h>
                    ^
compilation terminated.
exit status 1
Error compiling for board WeMos D1 R2 & mini.
I looking for I2Cdev.h found here https://github.com/jrowberg/i2cdevlib/b ... v/I2Cdev.hbut no luck,
Some clue
Regards
Vic

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#2 Post by TD-er » 29 Jun 2018, 00:08

I guess we have to make some decision on those playground plugins, since a lot of users try to compile them but they are hardly maintained.
If you fetch the latest Mega source, you will have the I2C files and the accompanying library.

The status of these plugins is unknown (at least to me) and pulling them into the Mega branch will not only make those images too big, but also will most likely lead to an explosion of support questions.
But leaving them as unsupported and not maintained as they are now, is also not a good idea.

QcVictor
Normal user
Posts: 46
Joined: 23 Feb 2016, 00:47

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#3 Post by QcVictor » 29 Jun 2018, 00:25

OK I understand but with further investigation, it's not related to this plugin, with the latest source and or last fork untouched I have the same error.

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#4 Post by TD-er » 29 Jun 2018, 00:29

I guess you're compiling with the Arduino IDE?
I normally use PlatformIO (with Atom and also VScode) and I know the Arduino IDE has some issues finding files.
You could change the <> into "" to test, if you're sure you did install that library. (or use PlatformIO ;) )

QcVictor
Normal user
Posts: 46
Joined: 23 Feb 2016, 00:47

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#5 Post by QcVictor » 29 Jun 2018, 15:54

Ok I give it a try to platformio but no luck

Code: Select all

collect2: error: ld returned 1 exit status
*** [.pioenvs/normal_ESP8266_4096/firmware.elf] Error 1
:roll:

User avatar
grovkillen
Core team member
Posts: 3621
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#6 Post by grovkillen » 29 Jun 2018, 16:32

You might need to delete the .pioenv folder prior to compile.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

QcVictor
Normal user
Posts: 46
Joined: 23 Feb 2016, 00:47

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#7 Post by QcVictor » 30 Jun 2018, 18:34

grovkillen wrote: 29 Jun 2018, 16:32 You might need to delete the .pioenv folder prior to compile.
tks for the tips Grovkillen, it's working, have a good weekend.
Maybe another questions, I add the Plugin "_P133_VL53L0X.ino" in folder "src" add library required in the folder "lib" and start compilation, which version should contain the image file updated? ESP_Easy_mega-20180625_dev/_normal or _test

User avatar
grovkillen
Core team member
Posts: 3621
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#8 Post by grovkillen » 30 Jun 2018, 20:11

You also need to include it in the "define_plugin_sets.h"
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

TuWi
New user
Posts: 1
Joined: 22 Jul 2018, 16:03

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#9 Post by TuWi » 22 Jul 2018, 16:41

Hi
I need help. I get these errors when I try to upload (PIO upload/dev_ESP8266_4096)

Compiling .pioenvs\dev_ESP8266_4096\FrameworkArduino\core_esp8266_wiring_analog.c.o
C:/Users//ESPEasy_mega-20180720/Source/src/_P133_VL53L0X.ino: In function 'boolean Plugin_133(byte, EventStruct*, String&)':
C:/Users//ESPEasy_mega-20180720/Source/src/_P133_VL53L0X.ino:275:212: error: 'Plugin_133_begin' was not declared in this scope
Compiling .pioenvs\dev_ESP8266_4096\FrameworkArduino\core_esp8266_wiring_digital.c.o

Does anyone have an idea.

I intend to use VL53L0X for my wood pellet heating supplie. I have tested the HD-SR04 without good results.

drf10034
New user
Posts: 2
Joined: 07 Aug 2018, 20:15

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#10 Post by drf10034 » 15 Jan 2019, 16:04

I was able to upload the firmware to my device, but most of the time, the SW Watchdog resets the device for about 10 times in a row, before disabling the device.

Code: Select all

Soft WDT reset

ctx: cont
sp: 3ffffaf0 end: 3fffffd0 offset: 01b0

>>>stack>>>
3ffffca0:  00000002 00000001 3fff0da9 40201c5c
3ffffcb0:  00000001 00000001 3fff0da9 40201c5c
3ffffcc0:  00000029 00000000 4bc6a7f0 00000000
3ffffcd0:  00000000 3fff12a4 40106bb0 3fff12a4
3ffffce0:  00000000 3fff12a4 3fff0da9 402089bc
3ffffcf0:  0001dc6a 00000029 3fff0d98 402089e4
3ffffd00:  402a0d0c 0000001a 3ffffd30 4020bb9b
3ffffd10:  3fff1f4d 00000000 3fff12a4 4020bf1d
3ffffd20:  3fff1f4d 00000029 3ffffe80 4023c0ce
3ffffd30:  00000000 00000000 00000000 401006dc
3ffffd40:  3fff2f84 000004f3 000004f3 4010020c
3ffffd50:  3fff1c18 3fff5c0c 0000001f 0000001c
3ffffd60:  3fff2f84 000004f0 000004f0 4010020c
3ffffd70:  3fff1c18 00000003 3ffffdb0 401006dc
3ffffd80:  3fff1b24 3fff4a2c 3ffffdb0 40265778
3ffffd90:  00000000 00000000 402a0b10 40265794
3ffffda0:  3ffe91b4 3fff2084 402a0b10 40218d46
3ffffdb0:  00000000 00000000 00000000 0000002f
3ffffdc0:  3fff1c18 00000003 3ffffe80 40226e4c
3ffffdd0:  3fff55ac 0000000f 00000000 3fff55c4
3ffffde0:  0000000f 00000000 3fff55dc 0000000f
3ffffdf0:  00000000 3fff5bdc 0000000f 00000000
3ffffe00:  3fff5bf4 0000000f 00000000 00000000
3ffffe10:  00000000 00000000 00000000 00000000
3ffffe20:  00000000 00000000 00000000 00010000
3ffffe30:  3fff2f84 00000173 3ffffeb0 4026583d
3ffffe40:  0006485d 3ffe91b4 3ffffeb0 4026588a
3ffffe50:  3ffe91b4 00062b57 402b06c8 40265778
3ffffe60:  00000000 00000000 3ffffe80 3fff225c
3ffffe70:  3fff59ad 3fff1e14 3fff25fc 4024853e
3ffffe80:  3fff4024 0000000f 00000000 3fff3fa4
3ffffe90:  0000000f 00000000 3fff419c 0000000f
3ffffea0:  00000000 3fff557c 0000000f 00000000
3ffffeb0:  3fff5594 0000000f 00000000 00000000
3ffffec0:  00000000 00000000 00000000 00000000
3ffffed0:  00000000 00000000 00000000 00010000
3ffffee0:  00000000 00000000 00000000 00000000
3ffffef0:  0000000b 4bc6a7f0 19581062 00000000
3fffff00:  00062abd 000001a3 000001a3 4010020c
3fffff10:  00000001 3fff1dac 00000193 30000000
3fffff20:  3fff1b24 3fff263c 00000000 4022152d
3fffff30:  00000963 0001b263 3ffe87c8 30000000
3fffff40:  3fff1b24 00062b57 00000000 402486ce
3fffff50:  3fffdad0 00062a82 00000000 402022b5
3fffff60:  3fff1b24 00062a82 00000000 40261d15
3fffff70:  3fffdad0 00000193 402668f4 3fffefb0
3fffff80:  402022c0 00000001 3fff1c00 3fff2e28
3fffff90:  3fffdad0 00000000 3fff1c00 40261dfd
3fffffa0:  00000000 00000000 00000001 40266915
3fffffb0:  3fffdad0 00000000 3fff2e22 40266984
3fffffc0:  feefeffe feefeffe 3ffe87c8 40100721
<<<stack<<<
it sometimes does work, but I do not know why...

Any hints on where to look for the problem? Did something change in the plugin structure that causes this problem?
Frank

rmhoutz
Normal user
Posts: 36
Joined: 08 Sep 2017, 14:09

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#11 Post by rmhoutz » 16 Apr 2021, 01:29

TD-er wrote: 29 Jun 2018, 00:08 If you fetch the latest Mega source, you will have the I2C files and the accompanying library.
I feel like I must be missing something. I downloaded the latest Mega source and followed the instructions found here.https://espeasy.readthedocs.io/en/lates ... noIDE.html

But when attempting to compile I'm was seeing the missing I2Cdev.h after commenting it out of _Plugin_Helper I'm now getting this.

Code: Select all

In file included from sketch\_Plugin_Helper.h:36:0,
                 from F:\arduino-1.8.13P230\portable\sketchbook\ESPEasy\ESPEasy.ino:101:
sketch\src/Helpers/_Plugin_Helper_serial.h:5:27: fatal error: ESPeasySerial.h: No such file or directory
 #include <ESPeasySerial.h>
                           ^
compilation terminated.
exit status 1
Error compiling for board Generic ESP8266 Module.
Do I just need to keep adding new lib files?

User avatar
Ath
Normal user
Posts: 3415
Joined: 10 Jun 2018, 12:06
Location: NL

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#12 Post by Ath » 16 Apr 2021, 08:25

Are you sure you have the latest sources, cloned from Github?

Can we motivate you to set up VSCode with PlatformIO, that's a much easier way of building ESPEasy, IMHO.
/Ton (PayPal.me)

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#13 Post by TD-er » 16 Apr 2021, 08:35

rmhoutz wrote: 16 Apr 2021, 01:29 [...]
Do I just need to keep adding new lib files?
The libs you should get from the lib directory, not trying to install via the library manager of the Arduino IDE as some libraries do not exist in the Arduino Library manager and some have ESPEasy specific changes which are not present in the original libraries.

rmhoutz
Normal user
Posts: 36
Joined: 08 Sep 2017, 14:09

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#14 Post by rmhoutz » 16 Apr 2021, 15:05

[/quote]
you should get from the lib directory, not trying to install via the library manager
[/quote]

Hi TD-er

Confirmed I copied all the files from the first lib file found in the download as instructed here.
https://espeasy.readthedocs.io/en/lates ... noIDE.html

I can even find the ESPEasySerial folder containing the ESPeasySerial.h file but despite all that I am still getting the error in Arduino when attempting to compile.

Code: Select all

In file included from sketch\_Plugin_Helper.h:36:0,
                 from F:\arduino-1.8.13P230\portable\sketchbook\ESPEasy\ESPEasy.ino:101:
sketch\src/Helpers/_Plugin_Helper_serial.h:5:27: fatal error: ESPeasySerial.h: No such file or directory
 #include <ESPeasySerial.h>
                           ^
compilation terminated.
exit status 1
Error compiling for board Generic ESP8266 Module.
I feel like I missed a step or something when following the Arduino IDE tutorial.

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#15 Post by TD-er » 16 Apr 2021, 15:16

What is the content of your Custom.h file?

Please have a look at the file define_plugin_sets.h:

Code: Select all

/******************************************************************************\
 * Libraries dependencies *****************************************************
\******************************************************************************/
#if defined(USES_P049) || defined(USES_P052) || defined(USES_P053) || defined(USES_P056) || defined(USES_P071) || defined(USES_P075) || defined(USES_P078) || defined(USES_P082) || defined(USES_P085) || defined(USES_P087) || defined(USES_P094) || defined(USES_P102) || defined(USES_P108) || defined(USES_C018)
  // At least one plugin uses serial.
  #ifndef PLUGIN_USES_SERIAL
    #define PLUGIN_USES_SERIAL
  #endif
#else
  // No plugin uses serial, so make sure software serial is not included.
  #define DISABLE_SOFTWARE_SERIAL
#endif
As you can see, there is a number of plugins mentioned here that depend on the ESPEasySerial library.
So either you include your USES_P133 in that list, or you simply define PLUGIN_USES_SERIAL and undef DISABLE_SOFTWARE_SERIAL in your Custom.h file

Code: Select all

  #ifndef PLUGIN_USES_SERIAL
    #define PLUGIN_USES_SERIAL
  #endif
  #ifdef DISABLE_SOFTWARE_SERIAL
    #undef DISABLE_SOFTWARE_SERIAL
  #endif
Or if that doesn't work, try including one of those plugins that need the serial, so it is defined for sure.

Problem with Arduino IDE is that defines needed for libraries may need to be set before you compile (so not defined in a Config.h file) or else builds may fail.
See also here how to make global defines.

And the least issues compiling would be to use PlatformIO.

User avatar
Ath
Normal user
Posts: 3415
Joined: 10 Jun 2018, 12:06
Location: NL

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#16 Post by Ath » 16 Apr 2021, 15:40

Plugin P133 from the PluginPlayGround has been merged into the mega branch as P110 since a couple of weeks. No need to grab it from the playground anymore ;) Unfortunately there wasn't enough room in a testing build to have it included in that type of build, but in your Custom.h you should un-comment the "#define USES_P110" line. It is available in an ESP32 MAX build, but you'll need an ESP32 with 16MB flash to run that...

And, this plugin does not rely on a serial connection in anyway, as it's using I2C to communicate.
/Ton (PayPal.me)

rmhoutz
Normal user
Posts: 36
Joined: 08 Sep 2017, 14:09

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#17 Post by rmhoutz » 16 Apr 2021, 19:08

Hey Guys Thanks for all the Info.

I am attempting to use PlatformIO but I'm definitely not a programmer (but I'm a PC Analyst that's been playing with Arduino and ESP's for years so I'm not completely out of my element)
A few years ago I had used Arduino to create a custom bin but I no longer have access to the computer used. COVID 19 took my Job :(

When I open PlatformIO I feel like I'm 10 years old again sitting at a Win3.1 DOS prompt thinking ok now what. :(
And even when I get it to do something from the documentation I feel like ok what did I just do, and did it work?
The easiest is to go for the environment “env:custom_ESP8266_4M” and unfold that one. Then select “Build” to see if it will start building.
I did this and after some time thinking it's working I ended up seeing this.

Code: Select all

Building in release mode
Generating .pio\build\custom_ESP8266_4M1M\core\core_version.h
Compiling .pio\build\custom_ESP8266_4M1M\lib093\Adafruit GFX Library\glcdfont.c.o
Compiling .pio\build\custom_ESP8266_4M1M\lib72d\ESP8266WiFi\ESP8266WiFiGratuitous.cpp.o
C:\Users\myname\.platformio\packages\framework-arduinoespressif8266\libraries\ESP8266WiFi\src\ESP8266WiFiGratuitous.cpp:22:41: fatal error: lwip/init.h: No such file or directory
 #include "lwip/init.h" // LWIP_VERSION_*
                                         ^
compilation terminated.
Compiling .pio\build\custom_ESP8266_4M1M\lib330\ESP8266SdFat\FatLib\FmtNumber.cpp.o
Compiling .pio\build\custom_ESP8266_4M1M\lib61e\ESP8266WebServer\detail\mimetable.cpp.o
Compiling .pio\build\custom_ESP8266_4M1M\lib0bf\ccronexpr\ccronexpr.c.o
Compiling .pio\build\custom_ESP8266_4M1M\lib0bf\ccronexpr\ccronexpr_test.c.o
Compiling .pio\build\custom_ESP8266_4M1M\lib2be\Adafruit_BME680\bme680.c.o
Compiling .pio\build\custom_ESP8266_4M1M\src\src\DataStructs\CRCStruct.cpp.o
Compiling .pio\build\custom_ESP8266_4M1M\src\src\Globals\CRCValues.cpp.o
Compiling .pio\build\custom_ESP8266_4M1M\src\src\Globals\ResetFactDefaultPref.cpp.o
Compiling .pio\build\custom_ESP8266_4M1M\src\src\Helpers\ESPEasy_math.cpp.o
*** [.pio\build\custom_ESP8266_4M1M\lib72d\ESP8266WiFi\ESP8266WiFiGratuitous.cpp.o] Error 1
================================================================================================== [FAILED] Took 39.22 seconds ==================================================================================================
Environment          Status    Duration
-------------------  --------  ------------
custom_ESP8266_4M1M  FAILED    00:00:39.223
============================================================================================= 1 failed, 0 succeeded in 00:00:39.223 =============================================================================================The terminal process "C:\Users\myname\.platformio\penv\Scripts\platformio.exe 'run', '--environment', 'custom_ESP8266_4M1M'" terminated with exit code: 1.
Is that considered it's working?
If that’s working, you can open the file “pre_extra_script.py”
I apologize for the long rambling post I just need to get more time with PIO and when I started this endeavor I was just trying to start using Homie
with my OpenHAB 3 server.

rmhoutz
Normal user
Posts: 36
Joined: 08 Sep 2017, 14:09

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#18 Post by rmhoutz » 16 Apr 2021, 19:19

Ath wrote: 16 Apr 2021, 08:25 Are you sure you have the latest sources, cloned from Github?
Is this the latest source? https://github.com/letscontrolit/ESPEasy
If so then I'm sure I got the latest.

rmhoutz
Normal user
Posts: 36
Joined: 08 Sep 2017, 14:09

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#19 Post by rmhoutz » 16 Apr 2021, 19:29

TD-er wrote: 16 Apr 2021, 15:16 What is the content of your Custom.h file?
I don't know if this is still important if I'm going to try using PlatformIO but here is my Custom.h file.

Code: Select all

#ifndef ESPEASY_CUSTOM_H
#define ESPEASY_CUSTOM_H

/*
    To modify the stock configuration without changing the EspEasy.ino file :
    1) rename this file to "Custom.h" (It is ignored by Git)
    2) define your own settings below
    3) define USE_CUSTOM_H as a build flags. ie : export PLATFORMIO_BUILD_FLAGS="'-DUSE_CUSTOM_H'"
 */


/*
 #######################################################################################################
   Your Own Default Settings
 #######################################################################################################
    You can basically ovveride ALL macro defined in ESPEasy.ino.
    Don't forget to first #undef each existing #define that you add below.
    But since this Custom.h is included before other defines are made, you don't have to undef a lot of defines.
    Here are some examples:
 */

#ifdef BUILD_GIT
# undef BUILD_GIT
#endif // ifdef BUILD_GIT

#define BUILD_GIT           "My Build: "  __DATE__ " "  __TIME__


#define DEFAULT_NAME        "ESP_000000"                        // Enter your device friendly name
#define UNIT                99                                        // Unit Number
#define DEFAULT_DELAY       60                                       // Sleep Delay in seconds

// --- Wifi AP Mode (when your Wifi Network is not reachable) ----------------------------------------
#define DEFAULT_AP_IP       192, 168, 4, 1                           // Enter IP address (comma separated) for AP (config) mode
#define DEFAULT_AP_SUBNET   255, 255, 255, 0                         // Enter IP address (comma separated) for AP (config) mode
#define DEFAULT_AP_KEY      "configesp"                              // Enter network WPA key for AP (config) mode

// --- Wifi Client Mode -----------------------------------------------------------------------------
#define DEFAULT_SSID                         "MyWifi"            // Enter your network SSID
#define DEFAULT_KEY                          "mypassword" // Enter your network WPA key
#define DEFAULT_USE_STATIC_IP                false                   // (true|false) enabled or disabled static IP
#define DEFAULT_IP                           "192.168.0.50"          // Enter your IP address
#define DEFAULT_DNS                          "192.168.0.1"           // Enter your DNS
#define DEFAULT_GW                           "192.168.0.1"           // Enter your Gateway
#define DEFAULT_SUBNET                       "255.255.255.0"         // Enter your Subnet
#define DEFAULT_IPRANGE_LOW                  "0.0.0.0"               // Allowed IP range to access webserver
#define DEFAULT_IPRANGE_HIGH                 "255.255.255.255"       // Allowed IP range to access webserver
#define DEFAULT_IP_BLOCK_LEVEL               1                       // 0: ALL_ALLOWED  1: LOCAL_SUBNET_ALLOWED  2:
// ONLY_IP_RANGE_ALLOWED
#define DEFAULT_ADMIN_USERNAME               "admin"
#define DEFAULT_ADMIN_PASS                   ""

#define DEFAULT_WIFI_CONNECTION_TIMEOUT      10000 // minimum timeout in ms for WiFi to be connected.
#define DEFAULT_WIFI_FORCE_BG_MODE           false // when set, only allow to connect in 802.11B or G mode (not N)
#define DEFAULT_WIFI_RESTART_WIFI_CONN_LOST  false // Perform wifi off and on when connection was lost.
#define DEFAULT_ECO_MODE                     false // When set, make idle calls between executing tasks.
#define DEFAULT_WIFI_NONE_SLEEP              false // When set, the wifi will be set to no longer sleep (more power
// used and need reboot to reset mode)
#define DEFAULT_GRATUITOUS_ARP               false // When set, the node will send periodical gratuitous ARP
                                                   // packets to announce itself.
#define DEFAULT_TOLERANT_LAST_ARG_PARSE      false // When set, the last argument of some commands will be parsed to the end of the line
                                                   // See: https://github.com/letscontrolit/ESPEasy/issues/2724
#define DEFAULT_SEND_TO_HTTP_ACK             false // Wait for ack with SendToHttp command.

#define DEFAULT_AP_DONT_FORCE_SETUP            false  // Allow optional usage of Sensor without WIFI avaiable // When set you can use the Sensor in AP-Mode without beeing forced to /setup

// --- Default Controller ------------------------------------------------------------------------------
#define DEFAULT_CONTROLLER   false                                          // true or false enabled or disabled, set 1st controller
                                                                            // defaults
#define DEFAULT_CONTROLLER_ENABLED true                                     // Enable default controller by default
#define DEFAULT_CONTROLLER_USER    ""                                       // Default controller user
#define DEFAULT_CONTROLLER_PASS    ""                                       // Default controller Password

// using a default template, you also need to set a DEFAULT PROTOCOL to a suitable MQTT protocol !
#define DEFAULT_PUB         "homie/%unitname%/%devicename%/%valname%"       // Enter your pub
#define DEFAULT_SUB         "homie/%unitname%/%devicename%/%valname%/set"                   // Enter your sub
#define DEFAULT_SERVER      "192.168.2.4"                                   // Enter your Server IP address
#define DEFAULT_SERVER_HOST ""                                              // Server hostname
#define DEFAULT_SERVER_USEDNS false                                         // true: Use hostname.  false: use IP
#define DEFAULT_USE_EXTD_CONTROLLER_CREDENTIALS   false                     // true: Allow longer user credentials for controllers

#define DEFAULT_PORT        1883                                            // Enter your Server port value

#define DEFAULT_PROTOCOL    5                                               // Protocol used for controller communications
                                                                            //   0 = Stand-alone (no controller set)
                                                                            //   1 = Domoticz HTTP
                                                                            //   2 = Domoticz MQTT
                                                                            //   3 = Nodo Telnet
                                                                            //   4 = ThingSpeak
                                                                            //   5 = Home Assistant (openHAB) MQTT
                                                                            //   6 = PiDome MQTT
                                                                            //   7 = EmonCMS
                                                                            //   8 = Generic HTTP
                                                                            //   9 = FHEM HTTP

#define DEFAULT_PIN_I2C_SDA                     0
#define DEFAULT_PIN_I2C_SCL                     0
#define DEFAULT_I2C_CLOCK_SPEED                 400000            // Use 100 kHz if working with old I2C chips

#define DEFAULT_SPI                             0                 //0=disabled 1=enabled and for ESP32 there is option 2 =HSPI

#define DEFAULT_PIN_STATUS_LED                  (-1)
#define DEFAULT_PIN_STATUS_LED_INVERSED         true

#define DEFAULT_PIN_RESET_BUTTON                (-1)


#define DEFAULT_USE_RULES                       false             // (true|false) Enable Rules?
#define DEFAULT_RULES_OLDENGINE                 true

#define DEFAULT_MQTT_RETAIN                     false             // (true|false) Retain MQTT messages?
#define DEFAULT_MQTT_DELAY                      100               // Time in milliseconds to retain MQTT messages
#define DEFAULT_MQTT_LWT_TOPIC                  "homie/%sysname%/$state"                // Default lwt topic
#define DEFAULT_MQTT_LWT_CONNECT_MESSAGE        "ready"              // Default lwt message
#define DEFAULT_MQTT_LWT_DISCONNECT_MESSAGE     "lost"               // Default lwt message
#define DEFAULT_MQTT_USE_UNITNAME_AS_CLIENTID   0

#define DEFAULT_USE_NTP                         true             // (true|false) Use NTP Server
#define DEFAULT_NTP_HOST                        "192.168.2.2"                // NTP Server Hostname
#define DEFAULT_TIME_ZONE                       -300                 // Time Offset (in minutes)
#define DEFAULT_USE_DST                         true             // (true|false) Use Daily Time Saving

#define DEFAULT_LATITUDE                        0.0f              // Default Latitude  
#define DEFAULT_LONGITUDE                       0.0f              // Default Longitude

#define DEFAULT_SYSLOG_IP                       ""                // Syslog IP Address
#define DEFAULT_SYSLOG_LEVEL                    0                 // Syslog Log Level
#define DEFAULT_SERIAL_LOG_LEVEL                LOG_LEVEL_INFO    // Serial Log Level
#define DEFAULT_WEB_LOG_LEVEL                   LOG_LEVEL_INFO    // Web Log Level
#define DEFAULT_SD_LOG_LEVEL                    0                 // SD Card Log Level
#define DEFAULT_USE_SD_LOG                      false             // (true|false) Enable Logging to the SD card

#define DEFAULT_USE_SERIAL                      false              // (true|false) Enable Logging to the Serial Port
#define DEFAULT_SERIAL_BAUD                     115200            // Serial Port Baud Rate
#define DEFAULT_SYSLOG_FACILITY                 0                 // kern

#define DEFAULT_SYNC_UDP_PORT                   0                 // Used for ESPEasy p2p. (IANA registered port: 8266)


#define BUILD_NO_DEBUG


#define USES_SSDP


// #define USE_SETTINGS_ARCHIVE
// #define FEATURE_I2CMULTIPLEXER
// #define USE_TRIGONOMETRIC_FUNCTIONS_RULES


/*
 #######################################################################################################
   Special settings  (rendering settings incompatible with other builds)
 #######################################################################################################
 */

// #define USE_NON_STANDARD_24_TASKS

/*
 #######################################################################################################
   Your Own selection of plugins and controllers
 #######################################################################################################
 */

#define CONTROLLER_SET_NONE
#define NOTIFIER_SET_NONE
#define PLUGIN_SET_NONE


/*
 #######################################################################################################
 ###########     Plugins
 #######################################################################################################
 */

// #define USE_SERVO


// #define USES_P001   // Switch
// #define USES_P002   // ADC
// #define USES_P003   // Pulse
// #define USES_P004   // Dallas
// #define USES_P005   // DHT
// #define USES_P006   // BMP085
// #define USES_P007   // PCF8591
// #define USES_P008   // RFID
// #define USES_P009   // MCP

// #define USES_P010   // BH1750
// #define USES_P011   // PME
// #define USES_P012   // LCD
// #define USES_P013   // HCSR04
// #define USES_P014   // SI7021
// #define USES_P015   // TSL2561
// #define USES_P017   // PN532
// #define USES_P018   // Dust
// #define USES_P019   // PCF8574

// #define USES_P020   // Ser2Net
// #define USES_P021   // Level
// #define USES_P022   // PCA9685
// #define USES_P023   // OLED
// #define USES_P024   // MLX90614
// #define USES_P025   // ADS1115
// #define USES_P026   // SysInfo
// #define USES_P027   // INA219
// #define USES_P028   // BME280
// #define USES_P029   // Output

// #define USES_P031   // SHT1X
// #define USES_P032   // MS5611
// #define USES_P033   // Dummy
// #define USES_P034   // DHT12
// #define USES_P036   // FrameOLED
// #define USES_P037   // MQTTImport
// #define USES_P038   // NeoPixel
// #define USES_P039   // Environment - Thermocouple

// #define USES_P040   // RFID - ID12LA/RDM6300
// #define USES_P041   // NeoClock
// #define USES_P042   // Candle
// #define USES_P043   // ClkOutput
// #define USES_P044   // P1WifiGateway
// #define USES_P045   // MPU6050
// #define USES_P046   // VentusW266
// #define USES_P047   // I2C_soil_misture
// #define USES_P048   // Motoshield_v2
// #define USES_P049   // MHZ19

// #define USES_P050   // TCS34725 RGB Color Sensor with IR filter and White LED
// #define USES_P051   // AM2320
// #define USES_P052   // SenseAir
// #define USES_P053   // PMSx003
// #define USES_P054   // DMX512
// #define USES_P055   // Chiming
// #define USES_P056   // SDS011-Dust
// #define USES_P057   // HT16K33_LED
// #define USES_P058   // HT16K33_KeyPad
// #define USES_P059   // Encoder

// #define USES_P060   // MCP3221
// #define USES_P061   // Keypad
// #define USES_P062   // MPR121_KeyPad
// #define USES_P063   // TTP229_KeyPad
// #define USES_P064   // APDS9960 Gesture
// #define USES_P065   // DRF0299
// #define USES_P066   // VEML6040
// #define USES_P067   // HX711_Load_Cell
// #define USES_P068   // SHT3x
// #define USES_P069   // LM75A

// #define USES_P070   // NeoPixel_Clock
// #define USES_P071   // Kamstrup401
// #define USES_P072   // HDC1080
// #define USES_P073   // 7DG
// #define USES_P074   // TSL2561
// #define USES_P075   // Nextion
// #define USES_P076   // HWL8012   in POW r1
// #define USES_P077   // CSE7766   in POW R2
// #define USES_P078   // Eastron Modbus Energy meters
// #define USES_P079   // Wemos Motoshield

// #define USES_P080   // iButton Sensor  DS1990A
// #define USES_P081   // Cron
// #define USES_P082   // GPS
// #define USES_P083   // SGP30
// #define USES_P084   // VEML6070
// #define USES_P085   // AcuDC24x
 #define USES_P086   // Receiving values according Homie convention. Works together with C014 Homie controller
// #define USES_P087   // Serial Proxy
// #define USES_P088   // HeatpumpIR
// #define USES_P089   // Ping

// #define USES_P090   // CCS811
// #define USES_P091   // SerSwitch
// #define USES_P092   // DLbus
// #define USES_P093   // MitsubishiHP
// #define USES_P094   // CULReader
// #define USES_P095   // ILI9341
// #define USES_P096   // eInk
// #define USES_P097   // ESP32Touch
// #define USES_P098   // 
// #define USES_P099   // XPT2046 touchscreen

// #define USES_P100   // DS2423 counter
// #define USES_P101   // WakeOnLan
// #define USES_P102   // PZEM004Tv3
// #define USES_P103   // Atlas_EZO_pH
// #define USES_P104   // Atlas_EZO_EC
// #define USES_P105   // Atlas_EZO_ORP
// #define USES_P106   // BME680
// #define USES_P107   // Si1145
 #define USES_P110   // VL53L0X Time of Flight sensor
// #define USES_P111   // RF522 RFID reader


// Special plugins needing IR library
// #define USES_P016   // IR
// #define P016_SEND_IR_TO_CONTROLLER false //IF true then the JSON replay solution is transmited back to the condroller.
// #define USES_P035   // IRTX
// #define P016_P035_Extended_AC // The following define is needed for extended decoding of A/C Messages and or using standardised 
                                 //common arguments for controlling all deeply supported A/C units
// #define P016_P035_USE_RAW_RAW2 //Use the RAW and RAW2 encodings, disabling it saves 3.7Kb
// #define USES_P088   // Heatpump IR
// #define USES_P108   // DDS238-x ZN Modbus energy meters


/*
 #######################################################################################################
 ###########     Controllers
 #######################################################################################################
 */


// #define USES_C001   // Domoticz HTTP
// #define USES_C002   // Domoticz MQTT
// #define USES_C003   // Nodo telnet
// #define USES_C004   // ThingSpeak
// #define USES_C005   // Home Assistant (openHAB) MQTT
// #define USES_C006   // PiDome MQTT
// #define USES_C007   // Emoncms
// #define USES_C008   // Generic HTTP
// #define USES_C009   // FHEM HTTP
// #define USES_C010   // Generic UDP
// #define USES_C011   // Generic HTTP Advanced
// #define USES_C012   // Blynk HTTP
// #define USES_C013   // ESPEasy P2P network
// #define USES_C014   // homie 3 & 4dev MQTT
// #define USES_C015   // Blynk
// #define USES_C016   // Cache controller
// #define USES_C017   // Zabbix
// #define USES_C018   // TTN/RN2483


/*
 #######################################################################################################
 ###########     Notifiers
 #######################################################################################################
 */


// #define USES_N001   // Email
// #define USES_N002   // Buzzer


#endif // ESPEASY_CUSTOM_H

rmhoutz
Normal user
Posts: 36
Joined: 08 Sep 2017, 14:09

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#20 Post by rmhoutz » 16 Apr 2021, 21:42

I got it working.
I'm not positive what solved the problem but I removed the Arduino IDE from my PC to make sure I wasn't mixing the portable version and my local installed version.
After I posted I had the latest version of the source download I noticed it was a few days old, not more than 5 but still not the latest.

I followed the steps again on the Arduino IDE instructions and it allowed me to compile and flash it.

With that said I do still have a question.

Some of my settings like NTP server and Default MQTT PUB and SUB didn't get set any idea why that would be if the flash was successful?

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#21 Post by TD-er » 16 Apr 2021, 21:46

Yep, that Custom.h can still be used for Custom builds.
It is either using the Custom.h file or (exclusive OR) the custom Python file.
The build scripts detect if the Custom.h is present and then use that instead of the pre_custom_espNNN.py file.

Code: Select all

C:\Users\myname\.platformio\packages\framework-arduinoespressif8266\libraries\ESP8266WiFi\src\ESP8266WiFiGratuitous.cpp:22:41: fatal error: lwip/init.h: No such file or directory
 #include "lwip/init.h" // LWIP_VERSION_*
 
Not sure where this comes from.
Maybe the build script did not checkout the complete esp8266/Arduino branch with all sub branches.

Do you have Git client installed on your PC?
See: https://espeasy.readthedocs.io/en/lates ... requisites
See also: https://www.youtube.com/watch?v=ArqwMcY ... Noorlander

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#22 Post by TD-er » 16 Apr 2021, 21:48

rmhoutz wrote: 16 Apr 2021, 21:42 [...]
With that said I do still have a question.

Some of my settings like NTP server and Default MQTT PUB and SUB didn't get set any idea why that would be if the flash was successful?
Those will only be set when creating a new config.
Either a new install (NTP settings) or adding a new controller (MQTT pub/sub settings)

rmhoutz
Normal user
Posts: 36
Joined: 08 Sep 2017, 14:09

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#23 Post by rmhoutz » 17 Apr 2021, 15:14

TD-er wrote: 16 Apr 2021, 21:46 Do you have Git client installed on your PC?
I do now and I believe I did when I received that message.
But if I'm honest I did miss that part when I first tried to run PlatformIO.

I feel like I should start a new Subject since we are way off topic of I2C and LIDAR.
by TD-er » 16 Apr 2021, 15:48
Those will only be set when creating a new config.
So if I flash the blank_4MB.bin then flash my Custom.h the settings will be picked up?

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Plugin 133 VL53L0X I2C Ranging LIDAR

#24 Post by TD-er » 17 Apr 2021, 15:25

Of course you need to make a build with your Custom.h.
And you don't need to wipe the entire unit by writing a blank image to it, you should be able to flash the new build via the web interface (as long as you keep the same layout like "4M1M")

Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot], Bing [Bot] and 38 guests