I thought the driver/library for the VEML6075 UV Sensor might have been similar to the VEML6070 UV Sensor, however they appear to be very different.
Has anyone already developed a driver for this sensor for ESPEasy?
Any love for VEML6075 UV Sensor?
Moderators: grovkillen, Stuntteam, TD-er
-
- Normal user
- Posts: 125
- Joined: 28 Feb 2018, 07:40
- Location: Melbourne, Australia
Any love for VEML6075 UV Sensor?
Friends with kangaroos and some time koala rescuer.
Re: Any love for VEML6075 UV Sensor?
Well I have them here in my drawer for just this reason, but have not yet found any time to update the plugin for it.
Re: Any love for VEML6075 UV Sensor?
I have found in the Playground the Plugin _P130_VEML6075.ino
I have the DFROBOT_VEML6075.
It works but i don´t know if the correct values are displayed.
I see in the settings:
#define ACoef 3.33
#define BCoef 2.5
#define CCoef 3.66
#define DCoef 2.75
I change it to the DFROBOT_VEML6075 lib but without the f:
#define UVA_A_COEF 2.22f
#define UVA_B_COEF 1.33f
#define UVA_C_COEF 2.95f
#define UVA_D_COEF 1.74f
Is this correct? Must i change something else?
Thanks a lot!
I have the DFROBOT_VEML6075.
It works but i don´t know if the correct values are displayed.
I see in the settings:
#define ACoef 3.33
#define BCoef 2.5
#define CCoef 3.66
#define DCoef 2.75
I change it to the DFROBOT_VEML6075 lib but without the f:
#define UVA_A_COEF 2.22f
#define UVA_B_COEF 1.33f
#define UVA_C_COEF 2.95f
#define UVA_D_COEF 1.74f
Is this correct? Must i change something else?
Thanks a lot!
Re: Any love for VEML6075 UV Sensor?
I assume you just set the values and are still using the "old" names of these defines?
Re: Any love for VEML6075 UV Sensor?
Ahh
P130_VEML6075.ino
#define ACoef 2.22
#define BCoef 1.33
#define CCoef 2.95
#define DCoef 1.74
This is right i think.
Yet the second thing:
P130_VEML6075.ino
enum IT {
IT_50 = 0, // 50 ms
IT_100 = 1, // 100 ms
IT_200 = 2, // 200 ms
IT_400 = 3, // 400 ms
IT_800 = 4 // 800 ms
};
// Specify VEML6075 Integration time
uint8_t IT = IT_100;
uint16_t UVData[5] = {0, 0, 0, 0, 0}; // UVA, Dummy, UVB, UVComp1, UVComp2
float UVAComp, UVBComp, UVIndex;
bool HD = 0;
and in the DFRobot_VEML6075.ccp
const float UvaResponsivityList[5] = {
UVA_RESPONSIVITY_100MS / 0.5016286645, // 50ms
UVA_RESPONSIVITY_100MS, // 100ms
UVA_RESPONSIVITY_100MS / 2.039087948, // 200ms
UVA_RESPONSIVITY_100MS / 3.781758958, // 400ms
UVA_RESPONSIVITY_100MS / 7.371335505 // 800ms
};
const float UvbResponsivityList[5] = {
UVB_RESPONSIVITY_100MS / 0.5016286645, // 50ms
UVB_RESPONSIVITY_100MS, // 100ms
UVB_RESPONSIVITY_100MS / 2.039087948, // 200ms
UVB_RESPONSIVITY_100MS / 3.781758958, // 400ms
UVB_RESPONSIVITY_100MS / 7.371335505 // 800ms
};
How must this a change?
P130_VEML6075.ino
#define ACoef 2.22
#define BCoef 1.33
#define CCoef 2.95
#define DCoef 1.74
This is right i think.
Yet the second thing:
P130_VEML6075.ino
enum IT {
IT_50 = 0, // 50 ms
IT_100 = 1, // 100 ms
IT_200 = 2, // 200 ms
IT_400 = 3, // 400 ms
IT_800 = 4 // 800 ms
};
// Specify VEML6075 Integration time
uint8_t IT = IT_100;
uint16_t UVData[5] = {0, 0, 0, 0, 0}; // UVA, Dummy, UVB, UVComp1, UVComp2
float UVAComp, UVBComp, UVIndex;
bool HD = 0;
and in the DFRobot_VEML6075.ccp
const float UvaResponsivityList[5] = {
UVA_RESPONSIVITY_100MS / 0.5016286645, // 50ms
UVA_RESPONSIVITY_100MS, // 100ms
UVA_RESPONSIVITY_100MS / 2.039087948, // 200ms
UVA_RESPONSIVITY_100MS / 3.781758958, // 400ms
UVA_RESPONSIVITY_100MS / 7.371335505 // 800ms
};
const float UvbResponsivityList[5] = {
UVB_RESPONSIVITY_100MS / 0.5016286645, // 50ms
UVB_RESPONSIVITY_100MS, // 100ms
UVB_RESPONSIVITY_100MS / 2.039087948, // 200ms
UVB_RESPONSIVITY_100MS / 3.781758958, // 400ms
UVB_RESPONSIVITY_100MS / 7.371335505 // 800ms
};
How must this a change?
Who is online
Users browsing this forum: Google [Bot] and 112 guests