Internal connection problem

[prawinrai1993]

WiFiDuck/esp_duck/esp_duck.ino

Line 19 in 4045626

delay(200);

please update the delay to 1000ms to resolve the internal connection issue

[welcome]

Thanks for opening your first issue here! 🎉
👉 Be sure to:
1. 📖 Have a look at the Wiki and README for information
2. 🔍 Search for similar issues (open and closed)
3. ✍️ Provide enough information to understand, recreate and help out with your problem
4. ℹ️ Let us know if you find a solution
5. 📕 Close the issue when your problem has been solved

[Egor2101]

WiFiDuck/esp_duck/esp_duck.ino

Line 19 in 4045626

delay(200);

please update the delay to 1000ms to resolve the internal connection issue
Does not work...

[mattybeens]

Didnt work for me either :(

[prawinrai1993]

Didnt work for me either :(

try increasing delay. I am using nodemcu, for me worked. for other user 10000ms worked, who is using a d1 mini. not facing internal connection issue any more. Also scripts working super smooth.

[mattybeens]

i tried both of those times. I also have a dstike wifi duck V2 that has the same issue after updating.

[justusiv]

Tried both the 1000 and 10000 and i am having the same issue.

[slash128v6]

Same issue for me.

[spacehuhn]

I did some testing, and with debug enabled, I could reproduce the issue sometimes. Try disabling Debug if it isn't already.

[slash128v6]

I have tried with Debug enabled and disabled. I tried on my DSTIKE board and now that board is no longer working. It appears to be an issue with I2C. I can run scripts via Serial between ESP and 32U4, albeit very slow.

[spacehuhn]

Using I2C (or serial given the right hardware) instead of the Auto mode also seems to make a difference sometimes. I have a growing suspicion that the atmega32u4 is partly responsible, as it seems to be very sensitive.

[justusiv]

ok so that got me working... set both debugs to disable and both protocols to I2C.
Gonna play around but thanks for the info!

[slash128v6]

That seems to be working for me now too, thank you!

…

________________________________ From: justusiv ***@***.***> Sent: Monday, January 24, 2022 4:07:27 PM To: SpacehuhnTech/WiFiDuck Cc: Jason Granat; Comment Subject: Re: [SpacehuhnTech/WiFiDuck] Internal connection problem (Issue #99) ok so that got me working... set both debugs to disable and both protocols to I2C. Gonna play around but thanks for the info! — Reply to this email directly, view it on GitHub<#99 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFB2GSDFJTODFRF4ZEIIQGTUXXST7ANCNFSM5L53SJTQ>. You are receiving this because you commented.Message ID: ***@***.***>

[spacehuhn]

Hopefully, that's it 🤞 . I updated the Wifi Duck AVR boards so that these options are set by default from now on.

[slash128v6]

So far so good, I've reflashed a few times just to confirm and it's still working on both my DSTIKE board and DIY setup. Appreciate the help!

…

________________________________ From: Stefan Kremser ***@***.***> Sent: Monday, January 24, 2022 4:14:54 PM To: SpacehuhnTech/WiFiDuck Cc: Jason Granat; Comment Subject: Re: [SpacehuhnTech/WiFiDuck] Internal connection problem (Issue #99) Hopefully, that's it 🤞 . I updated the Wifi Duck AVR boards so that these options are set by default from now on. — Reply to this email directly, view it on GitHub<#99 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFB2GSC5S6YDOBZSZMNT2ODUXXTP5ANCNFSM5L53SJTQ>. You are receiving this because you commented.Message ID: ***@***.***>

[slash128v6]

I just tried on an ESP8266 connected to genuine Arduino Leonardo and it did not work, unfortunately. But the other setups are still working. Just wanted to let you know.

…

________________________________ From: Jason Granat Sent: Monday, January 24, 2022 4:19:14 PM To: SpacehuhnTech/WiFiDuck; SpacehuhnTech/WiFiDuck Cc: Comment Subject: Re: [SpacehuhnTech/WiFiDuck] Internal connection problem (Issue #99) So far so good, I've reflashed a few times just to confirm and it's still working on both my DSTIKE board and DIY setup. Appreciate the help!

________________________________ From: Stefan Kremser ***@***.***> Sent: Monday, January 24, 2022 4:14:54 PM To: SpacehuhnTech/WiFiDuck Cc: Jason Granat; Comment Subject: Re: [SpacehuhnTech/WiFiDuck] Internal connection problem (Issue #99) Hopefully, that's it 🤞 . I updated the Wifi Duck AVR boards so that these options are set by default from now on. — Reply to this email directly, view it on GitHub<#99 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFB2GSC5S6YDOBZSZMNT2ODUXXTP5ANCNFSM5L53SJTQ>. You are receiving this because you commented.Message ID: ***@***.***>

[mattybeens]

https://www.amazon.com/dp/B08BJTS2N8?ref=ppx_yo2_dt_b_product_details&th=1
https://www.amazon.com/dp/B07S5HL54T?psc=1&ref=ppx_yo2_dt_b_product_details

Mines not working either :(

[slash128v6]

https://www.amazon.com/dp/B08BJTS2N8?ref=ppx_yo2_dt_b_product_details&th=1 https://www.amazon.com/dp/B07S5HL54T?psc=1&ref=ppx_yo2_dt_b_product_details

Mines not working either :(

try disabling debug on both sketches and hard set protocol to I2C on both sketches. That got me working with the same hardware from Amazon.

[mattybeens]

https://www.amazon.com/dp/B08BJTS2N8?ref=ppx_yo2_dt_b_product_details&th=1 https://www.amazon.com/dp/B07S5HL54T?psc=1&ref=ppx_yo2_dt_b_product_details
Mines not working either :(

try disabling debug on both sketches and hard set protocol to I2C on both sketches. That got me working with the same hardware from Amazon.

I got it, i was dumb and had to use the "generic esp8266" board

[prawinrai1993]

The solution works fine with disabling debug and selecting i2c. Also my board required generic esp8266 selection in ide before flash. works for both d1 wemos mini and esp8266.

Thanks for help @spacehuhn