-
-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I connect to the wifi duck it says that there is an internal connection problem #50
Comments
Thanks for opening your first issue here! 🎉 |
I've tried connecting them with jumper wires and I still get the same issue. |
Hello, I have the same problem, found a solution? |
Hi. It would be really helpful if you could share pictures of your setup, so we can see the hardware connections. |
|
Hi, i also got the same issue as @M-a-c-a-r-o-o-n .. Please find the connection diagram attached. Also as @Nikakz said, my WS2812B is not working even when i had selected LED as ON. The diagram for the LED connection is not attached . Also in case the image is not visible Arduino Wemos D1 Mini Also, i had to install EasyAsyncTCP and EasyAsyncWebServer from github as the same were not available on arduino library, which were of the latest version. The library version might be the issue ? |
Also, I was able to get it working once but once I get the internal connection error, the device remains in the same state. And after reinstalling wifi duck it works again. |
The connections seem correct. But it could be an issue with the jumper cables or the breadboard. Maybe one of them has a loose contact or something like that. |
Hallo,
but that gets into a loop and then disconnects. I am using cheap boards so that is probably causing it. Going to try with a Wemos D1. Tschüss |
@spacehuhn I had thought the same. But it happens everytime. I had permanently soldered all the connection and check it with a multimeter. In some cases I got it working if I disconnected the two wires except the power connections and reconnected them back. But not always possible. Will try it again when I get some new wemos board. Btw has someone used this with other boards like nodemcu ? If possible lemme know |
So an update to the above... the code is working fine for NODEMCU 12E version. SO you guys can switch. Btw i'll be using the board for the whole day tommorow and give you all an update |
Hello, when I had this problem, but it was with a esp12 and then with an MCU node, it was not with the wemos D1 mini, it was a matter of energy that the esp consumes and is generating this page as you reported and I gave up on the esp 12 and node mcu and already with wemos I had stability and there were no problems with the connection. |
|
Sadly... i am facing issues with the nodeMCU too :'(.. It worked fine for some hours n it stopped working. |
@spacehuhn Same issue like @hunny1389 on the NODE MCU for Az-Delivery |
@KatzeMau You missing the Atmega32u4: README.me#hardware |
@spacehuhn can you please provide a link for an esp8266 with a atmega32u4 chip or would this be okay ? https://www.aliexpress.com/item/4000256143274.html |
Right now there isn't a cheaper option that is as compatible as the DSTIKE WIFI Duck |
Yeah, bought one :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Have there been any updates on this? I am having the same "Internal Connection Problem" issue. I have tried with a Pro Micro and D1 Mini as well as a genuine Leonardo and ESP8266 NodeMCU. |
Have a look here: #94 (comment) |
hello, I have the same problem |
Hey 👋 I am a littlebit confused. So if I have an esp8266 then I don't need the Atmega32u4? |
Não
Sandra Viana
Enviado do meu iPhone
Em seg., 1 de jan. de 2024 às 13:05, luxkatana ***@***.***>
escreveu:
… Hey 👋 I am a littlebit confused. So if I have an esp8266 then I don't
need the Atmega32u4?
—
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFFRWZ6ECTRVT6W5BOERFWLYMLNCZAVCNFSM4PYVHTO2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBXGMZTQMRYGUYA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
So I do need the Atmega32u4? |
Describe the error
After connecting to the duck there is a yellow bar at the top saying that there is an internal connection problem. There is no output to the serial monitor and I can't type anything using the duck
Environment:
Attempts
I have tried connecting to the serial monitor without success and I have checked all the solder connections which are fine
Does anyone have any idea what the issue might be?
The text was updated successfully, but these errors were encountered: