Invalid and non-unique UUID

Tagged: mayfly, UUID, variables, yosemitech

This topic has 4 replies, 2 voices, and was last updated 2021-07-18 at 8:19 PM by Shannon Hicks.

Viewing 4 reply threads

Author

Posts

2021-07-15 at 3:00 PM #15687

Liz

Participant

Hello, I am trying to program my mayfly off the simple_logging example code, starting with the on board sensors.

I am can get the program to build and upload but when I run it, I get a message

SampNum has a non-unique UUID!
Battery has an invalid UUID!
BoardTemp has an invalid UUID!
 -> SampNum
 -> FreeRam

SampNum has a non-unique UUID!

Battery has an invalid UUID!

BoardTemp has an invalid UUID!

-> SampNum

-> FreeRam

It will still calculate the proper numbers for each of these variables. But I am unsure how to get them to have an unique UUID. When I try to add my Y510 yosemitech turbidity sensor It will do this as well.

this is the code I have for the yosemite sensor and the on board sensors

byte y510ModbusAddress = 0x0B;  // The modbus address of the Y510
const int8_t y510AdapterPower  = -1;  // RS485 adapter power pin
                                                  // (-1 if unconnected)
const int8_t  y510SensorPower = A3;               // Sensor power pin
const int8_t  y510EnablePin   = -1;  // Adapter RE/DE pin (-1 if not applicable)
const uint8_t y510NumberReadings = 5;
// The manufacturer recommends averaging 10 readings, but we take 5 to minimize
// power consumption

// Create a Y510-B Turbidity sensor object
YosemitechY510 y510(y510ModbusAddress, y510AdapterPower, modbusSerial, y510SensorPower, y510EnablePin, y510NumberReadings);

// Create turbidity and temperature variable pointers for the Y510
Variable* y510Turb =
    new YosemitechY510_Turbidity(&y510, "716006f0-9a1d-4330-9207-34ef302d571c");
Variable* y510Temp =
    new YosemitechY510_Temp(&y510, "716006f0-9a1d-4330-9207-34ef302d571c");
/** End [y510] */
#endif



// ==========================================================================
//  Creating the Variable Array[s] and Filling with Variable Objects
// ==========================================================================
/** Start [variable_arrays] */
Variable* variableList[] = {
    new ProcessorStats_SampleNumber(&mcuBoard),
    new ProcessorStats_FreeRam(&mcuBoard),
    new ProcessorStats_Battery(&mcuBoard, "vbat"),
    new MaximDS3231_Temp(&ds3231, "airtemp"),

    // Additional sensor variables can be added here, by copying the syntax
    //   for creating the variable pointer (FORM1) from the
    //   <code>menu_a_la_carte.ino</code> example
    // The example code snippets in the wiki are primarily FORM2.
};

const char *UUIDs[] =                                                      // UUID array for device sensors
{
};
const char *registrationToken = "716006f0-9a1d-4330-9207-34ef302d571c";   // Device registration token
const char *samplingFeature = "2637ae26-0834-4b16-a05b-abe0b2ee035f";     // Sampling feature UUID


// Count up the number of pointers in the array
int variableCount = sizeof(variableList) / sizeof(variableList[0]);

// Create the VariableArray object
VariableArray varArray;
/** End [variable_arrays] */

byte y510ModbusAddress = 0x0B; // The modbus address of the Y510

const int8_t y510AdapterPower = -1; // RS485 adapter power pin

// (-1 if unconnected)

const int8_t y510SensorPower = A3; // Sensor power pin

const int8_t y510EnablePin = -1; // Adapter RE/DE pin (-1 if not applicable)

const uint8_t y510NumberReadings = 5;

// The manufacturer recommends averaging 10 readings, but we take 5 to minimize

// power consumption

// Create a Y510-B Turbidity sensor object

YosemitechY510 y510(y510ModbusAddress, y510AdapterPower, modbusSerial, y510SensorPower, y510EnablePin, y510NumberReadings);

// Create turbidity and temperature variable pointers for the Y510

Variable* y510Turb =

new YosemitechY510_Turbidity(&y510, "716006f0-9a1d-4330-9207-34ef302d571c");

Variable* y510Temp =

new YosemitechY510_Temp(&y510, "716006f0-9a1d-4330-9207-34ef302d571c");

/** End [y510] */

#endif

// ==========================================================================

// Creating the Variable Array[s] and Filling with Variable Objects

// ==========================================================================

/** Start [variable_arrays] */

Variable* variableList[] = {

new ProcessorStats_SampleNumber(&mcuBoard),

new ProcessorStats_FreeRam(&mcuBoard),

new ProcessorStats_Battery(&mcuBoard, "vbat"),

new MaximDS3231_Temp(&ds3231, "airtemp"),

// Additional sensor variables can be added here, by copying the syntax

// for creating the variable pointer (FORM1) from the

// <code>menu_a_la_carte.ino</code> example

// The example code snippets in the wiki are primarily FORM2.

};

const char *UUIDs[] = // UUID array for device sensors

{

};

const char *registrationToken = "716006f0-9a1d-4330-9207-34ef302d571c"; // Device registration token

const char *samplingFeature = "2637ae26-0834-4b16-a05b-abe0b2ee035f"; // Sampling feature UUID

// Count up the number of pointers in the array

int variableCount = sizeof(variableList) / sizeof(variableList[0]);

// Create the VariableArray object

VariableArray varArray;

/** End [variable_arrays] */

2021-07-15 at 3:06 PM #15689
Liz
Participant
In my code I have the yosemitech sensor set up but in the serial monitor it does not address the sensor at all? Why would that be. I am very new to programming especially the Mayfly data logger and platformio.
2021-07-15 at 3:10 PM #15690
Shannon Hicks
Moderator
When you register a site on Monitor My Watershed you can set it up with various sensor parameters, and once you’ve got all of them entered on the website, you click the “View Token UUID List” button at the top of your site page and you’ll get a list of all the UUIDs in the exact format and order in which you need to paste them into your sketch. If you’re not planning to transmit data to Monitor My Watershed or upload the file manually, then it’s okay to leave them as generic, non-unique UUIDs, but since you’ve got a unique registration token and sampling feature listed in your posted sketch, then I assume you’re intending to send data to MMW.
2021-07-15 at 3:13 PM #15691
Liz
Participant
I am going to using just the SD card for my project. I thought I would need a unique UUID regardless so that was my first attempt at trying for that. So if I am using just the SD I can ignore the Non-unique UUID message? what about the invalid UUID, can that be ignored too?
2021-07-18 at 8:19 PM #15706
Shannon Hicks
Moderator
You can ignore the warnings to the serial monitor about the UUIDs if you never intend to send data to MMW. The warnings are just there to help people in case they were using the generic ones when they didn’t intend to. But since that’s what you want to do, it’s okay to ignore the warning.

Author

Posts

Viewing 4 reply threads

You must be logged in to reply to this topic.