@ElinhohHD This will limit to a toal of 2 Its, one of which is used for the module, so only one left for a client.
What's the reason for limiting to 2 clients? Why not use some form of authentication instead?
@robert-hh thanks, you already asked the correct question! I wanted to make sure that flashing the lastest firmware on the pytrack worked, so I connected it without any development board. I thought the (in my case fipy) is the shield, but it's vice versa that the fipy is the essential part right? Totally makes sense then, that it didnt work without the fipy. so together with the fipy it works, fine!
Sorry for the newby question and mistake. And thanks for the fast reply
@freddy said in SD card doesn't work on pysense:
I was getting the error on os.mount(sd, '/sd')
I found that cause the SD card was greater than 32GB that windows was only allowing it to be formatted to exFAT which doesn't work for the pycom. I had to delete all volumes of the SD card and create a new volume that was less than 32GB. Windows then could format to FAT32 and it worked from there
Thank you for answering, so I reviewed that other forum as well before and I am still a bit confused. I understand creating a server side script in python, php, etc. to execute the SQL queries, however, I’m lost at how to return the results over HTTP.
I see the other forum talks about sending data to a MQTT broker, is that something I would have to do? Send the query results from the database to the broker and then subscribe to the MQTT?
Sleep() function actually suspends the processing of the thread in which it is called by the operating system, allowing other threads and processes to execute while it sleeps. With multiple threads and processes, sleep() suspends your thread - it uses next to zero processing power.
@HenroRitchie If you have a single ESP32, machine.deepsleep() is sufficient. In combination with the Pycom expansion boards go_to_sleep() ensures proper deactivation of the respective sensors and set-up of the interrupt sources. It then switches off the power to ESP32. In summary, that results in a very low standby current - with the above side effect. Since the PIC on the expansion board also can control the EN (Reset) pin of the ESP32, it may pull that low before switching off the power. That may be a better solution than calling machine.deepsleep(), because it switches the ESP32 off immediately, and the PIC stays powered and therefore in a defined state during deepsleep.
Did you try with another USB cable?
Are you sure that you're using USB data cable not just charging USB cable?
Is there any dev file like /dev/tty.usb* after you connect PyTrack? (use Teminal to check that out)
Try on Windows machine maybe.