Rizwan Hamid Randhawa
Rizwan Hamid Randhawa
Thank you so much for your help. I highly appreciate that. However, I am facing the following error now. My esp-idf is v4.4. Generated /mnt/sda2/Insync/[email protected]/Google-Drive/SEMPHOS/Projects/OnGoing/ValarSystems/Rizwan/Project_v3/build/bootloader/bootloader.bin [97/97] cd /mnt/sda2/Insync/[email protected]/Google-Drive/SEMPHOS/Projects/OnGoing/ValarSystems/Rizwan/Project_v3/build/bootloader/esp-idf/esptool_py && /home/rizwan/.espressif/python_env/idf4.4_py3.8_env/bin/python...
I think this problem pertains to the arduino component. which esp-idf and arduino component version are you using please?
Thanks a lot for your help. The issue is resolved. Solution: I have used idf-release/v4.4 branch for Arduino component and espidf4.4 from the FastAccelStepper repo with esp-idf branch release/v4.4. Kind...
Sure, I can check. Thanks for your help.
I think, it does not work without arduino library. Here is the output: model-h-idf-fastaccelstepper$ idf.py flash monitor Executing action: flash Serial port /dev/ttyUSB0 Connecting.... Detecting chip type... Unsupported detection protocol,...
I receive no response for HTTP Get request for the `http://httpbin.org/get` URL. Following is the output using the AT Command Tester from `https://m2msupport.net` ``` Checking registration status... AT+CREG? +CREG: 2,1,"912","3D73",0...
I receive no response for HTTP Get request for the `http://httpbin.org/get` URL. Following is the output using the AT Command Tester from `https://m2msupport.net` ``` Checking registration status... AT+CREG? +CREG: 2,1,"912","3D73",0...
yes I am doing that in shadow code only as follows: ``` while (NETWORK_ATTEMPTING_RECONNECT == rc || NETWORK_RECONNECTED == rc || SUCCESS == rc) { rc = aws_iot_shadow_yield(&mqttClient, 100) ;...
Hello Guys! I am working on SIM7070G development to replace the SIM7000 in our existing system. Has anyone tried to connect HTTP? In my case, the SHCONN command never succeeds....
Thank you so much. I contacted SIMCOM regarding this issue and they told me that it might be a timestamp issue of NTP or the firmware version. For the NTP...