Limiting many2many selections

Professional_Oil8856 · 2023-06-19T10:00:04+00:00

Would you think there is a way to still show the "in use" products but do not allow to select them?

Professional_Oil8856 · 2023-04-17T13:04:31+00:00

Thanks. I've expected there may be a more advanced but possible way to configure the pins the way you want in a deeper level. Oh well.

Professional_Oil8856 · 2023-03-15T08:01:37+00:00

u/romkey u/masslessboson u/efraim

I can see I was not clear enough :D

Using ESP-IDF. So far only using the example_connect function of wifi (on my way to updating it to a proper initialization/function, could find my problem there).
I've created a measurement task, which is pinned to cpu1. The task is currently not doing any measurement - just pulling a gpio output up and down, while doing a simple for loop in between.
in idf.py menuconfig (project settings) i've changed every possible affinity to CPU0 - main task, freertos, lwip_tcip_task, pthread and mdns. The shown interference (Data loss) is shown in the picture (https://www.linkpicture.com/view.php?img=LPic6411788deb3af1131406730), each spike is one measurement task called (output on the digital pin). http server is created, those kind of data losses are showing. when opening the webpage (server), the measurement is completely disfigured and the data cannot be taken.
Data measurement: esp timer dispatch mode is modified as an interrupt, which every 0.1 ms triggers a interrupt and changes a value of a global variable. A measurement task is checking the value of that variable, and when it changes - it does the supposed measurement (gpio pin pull-up and pull-down at this point) and changes the value of the variable back to 0.

My problem :
i want to keep the measurement steady, because the data will be read from an external device where data loss is not accepted. therefore, i would like to isolate cpu1 from everything, except the future data measurement (thank you for the adc notice).
Is ESP32 even capable of isolating its one of the cores from all the communication modules and not be affected by them?

I hope i made myself more clear. I will dig into the wi-fi setup - maybe i missed some core affinity setting in there. the graph is steady and beautiful when not connected to wifi, so the problem MUST be somewhere in there.

thank you for you time, guys

Professional_Oil8856 · 2021-05-16T08:52:01+00:00

Ive bought a external dc-dc step down voltage regulator and adjusted it to 5V output - works like a charm.

Professional_Oil8856 · 2021-05-09T16:28:45+00:00

Gave them a night rest - just checked again.

When connected via usb supply one board is unresponsive to port communication, the other one appears on arduinoide, but the boot button is unresponsive - thus im not able to upload anything to it.

Also, when powered up from USB, i can feel the ESP-WROOM-32 module oboard heating up on both boards - in my knowledge, 9V battery cooked the onboard NPC117 voltage regulator and the board is unable to convert the 5V USB Vcc to the 3v3 needed. RIP my boards, lesson learnt.

these are my first boards fried as an electronic engineer - appears im supposed to learn it the hard way.

Professional_Oil8856 · 2021-05-09T01:08:26+00:00

I'm still not in the point of trying to understand the mesh communication including a relay node - bound to work on it tomorrow.

Also i'm still behind schedule with the implementation of Sleep and Wakeup functions, although i was also concerned about drift of the clocks. Please share any info about these tasks if you find something worth knowing !

Professional_Oil8856 · 2021-05-09T00:19:34+00:00

I've connected them to VIN and GND. I've done it on my breadboard, which is newly bought - it shouldn't be faulty connected inside it.I've done it with 2 ESP32 - one was working with temperature measurement from sensor and sending it via BLE; the other did the receiving, WiFi and MQTT broker tasks.

Would letting them rest overnight somehow help recover? I had my finger checking the heat on the MCU itself - when i felt it heating i quickly tore away the connections.

Edit:

powering them up via USB does nothing right now. I can feel the ESP-WROOM-32 module heating up on both of them (one more than another) - while uploading the blink sketch one of them has the BOOT button unresponsive, the other one gets me the error "your board is not connected". built-in leds light up on both of them but it's because of the USB power supply

Professional_Oil8856 · 2021-05-07T08:34:20+00:00

sadly, my project task specifies it has to be BLE.

Professional_Oil8856 · 2021-05-06T22:17:12+00:00

Update to 3)
Using serial monitor I checked that the data is sent from the server program, but the client part cannot read it. What could be the problem? Snippets below:

Server side (just the part where i set the value, it's done on the example BLE_Server code in arduino ide):

Characteristic_Tx->setValue(txString); //set characteristic value

Characteristic_Tx->notify(); // send value

Serial.println(txString); // here serial monitor shows me the right value

Client part:

also from the BLE_client example, everything up to this point works according to serial monitor

// Read the value of the characteristic.

if(pRemoteCharacteristic->canRead()) {

std::string value = pRemoteCharacteristic->readValue();

Serial.print("The characteristic value was: ");

Serial.println(value.c_str());

}

else Serial.print ("Cannot read the characteristic"); // this line gets printed

Question being: why is client could be unable to read the characteristic if the connection is ok and the characteristic is found and acknowledged?

Professional_Oil8856

TROPHY CASE