internal connection problem

[Dementora]

Is there an existing issue for this?

• I have searched the existing issues

Describe your problem

i think its because of atmega32u4

Steps to reproduce

my wiring its ok but it doesn't run any thing and show internal connection problem error

What hardware are you using?

pro micro d1 mini

Anything else?

my wiring its ok but it doesn't run any thing and show internal connection problem error and when i remove config.h line 17 when i run command like:

DELAY 1000
GUI R
STRING CMD
ENTER
in serial monitor 115200 baud it come :

RECEIVED [SOT] 'DELAY 1000
' [EOT]
Interpreting: DELAY 1000
Replying with status {wait: 0,repeat: 0} [04 00 00 00 ]
RECEIVED [SOT] '' [EOT]

i dont know how to fix my wifiduck pls help.

[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

[ghost]

Hi, same issue need help please.

[aklehm]

I have the same problem, but I figured out, that it works, if I power both boards via USB and connect the I2C and GND from board to board.
If I power the ESP board from the AVR board (RAW --> 5V), I also get the "Internal Connection Problem".
The ESP gets a voltage of 4.7V with a current of 80mA and the wifi is working fine, so I would exclude an under-voltage.
This is far away from a solution, but maybe it helps someone to find one.

[prawinrai1993]

same issue for me too. im using with nodemcu still same issue as above

[prawinrai1993]

I see that just one line is received in the buffer. Other lines not receiving.

[ajayamola9]

Hi, same issue need help please.

[mttmela]

same :(

[aklehm]

Try to increase the first delay (line 19) in the esp_duck.ino file. I tried 10 seconds (delay(10000);) and it works well for me. This is maybe to long, so you can try to decrease it.
My sugestion is, that the default delay of 200ms is to short before the esp tries to connect to the other controller and in some cases, the controller hasn't finished its I2C setup, so a connection couldn't be established.

I haven't watch the code, but it would be helpful, if there were a reconnect function.

[mattybeens]

i have this isssue on both of my wifi ducks. one is the dstike and the other is the WeMos D1 Mini and AITRIP Pro Micro ATmega32U4. i tried aklehms method to no avail.

[prawinrai1993]

changing delay to 1000 works for me on line number 19 esp_duck.ino. Due to initialiasation taking more time

[Egor2101]

changing delay to 1000 works for me on line number 19 esp_duck.ino. Due to initialiasation taking more time

Does not work...

[mattBrighto]

in tools > diable debbugging and change protocol to serial. i mean now you dont have internal connection problem but it didnt work either. now you have like Running /scriptname but it doesnt run the script

[mattBrighto]

in tools > diable debbugging and change protocol to serial. i mean now you dont have internal connection problem but it didnt work either. now you have like Running /scriptname but it doesnt run the script

update: it could not work just on my atmega cuz i kinda broke it, the micro usb port just tore off when i was trying to take the cable out :/

[justusiv]

in tools > diable debbugging and change protocol to serial. i mean now you dont have internal connection problem but it didnt work either. now you have like Running /scriptname but it doesnt run the script

I tried this and appeared to have the same result as you. No "internal connection problem" however my scripts do not type anything as well.

[spacehuhn]

Hi, there seem to be multiple open issues about this so I'm just going to repeat what I found here:
#99

Disabling Debug and setting the protocol to I2C (instead of Auto) on the atmega_duck seems to lead to improvements:

[ismail424]

Hi, there seem to be multiple open issues about this so I'm just going to repeat what I found here: #99

Disabling Debug and setting the protocol to I2C (instead of Auto) on the atmega_duck seems to lead to improvements:

This didn't solve my problem. Is there something else I can do to solve this issue?

[uhuhuhuhuhuhuhuh]

Yeah is there another method to fix this issue

[mducq]

Hi,

i have the same problem, i have fixed it with "serial" protocol.
i don't have the message, i can run script without problem but... when i plug my nodemcu (aliexpresse version) on a windows computer, it's seen as serial converter and not as a keyboard.

do you have an issue for this please?

thanks

[sameerakhtari]

I am getting same issue, still don't know how can I resolve this but I think this issue is generated by Arduino pro micro(or any other version you are using). cause I programmed it before ESP12F(nodemcu or any other) and Arduino pro micro and it worked fine for a time, then I broke my pro micro port , so I had to change my pro micro , since then, I am getting this error. I haven't programmed ESP12F or wrongly wired them.
If anyone knows exact way to resolve this error, Kindly Help me out.

[dtuando]

OK I Figured out the issue. If you bought one recently most likely you will need to reflash the atmega.
Using arduino, add the boards from the GitHub install instructions.
Flash USING LEONARDO. not the Default DUSTIKE WiFi Duck Board option.

example

[matti377]

Is there still no fix?
I keep having the same issue

[matti377]

ok i found the error. You sould read the docs.
I followed an old guide from Seytonic and these connections arent actual anymore.

[NULL-BITS]

Have a look at my fork. I've had the same problem and maybe my solution also fit for you:
https://github.com/TomFang1/WiFiDuck_CJMCU_3212/tree/master

[MaxMls]

I have the same problem "internal connection problem" with the latest version.

This repo works for me:
https://github.com/spacehuhn/wifi_ducky/tree/master#installation

But I needed to use some additional steps from @NULL-BITS as described in the readme.
https://github.com/NULL-BITS/WiFiDuck_CJMCU_3212/blob/master/README.md

Flash Software

1. Download and install the Arduino IDE.
2. Start the Arduino IDE, go to File > Preferences.
3. At Additional Board Manager ULRs enter https://raw.githubusercontent.com/SpacehuhnTech/arduino/main/package_spacehuhn_index.json. You can add multiple URLs, separating them with commas.
4. Go to Tools > Board > Board Manager, search for wifi duck and install WiFi Duck AVR Boards and WiFi Duck ESP8266 Boards.
5. Download and extract this repository or git clone it. (use https://github.com/spacehuhn/wifi_ducky instead)

Flash ESP8266

1. Open esp_duck/esp_duck.ino with the Arduino IDE.
2. Under Tools > Board in the WiFi Duck ESP8266 section, select your ESP8266
3. Go to Tools > Disable Debug and choose I2C as connection
4. In conf.h change the values to this
5. Then under Sketch > export and compile bin (I'll include a precompiled bin in the future, so that you could skp this in the future)
6. after that copy the path from your exported bin
7. Download this tool https://github.com/nodemcu/nodemcu-flasher/blob/master/Win64/Release/ESP8266Flasher.exe
8. Then open it and under settings paste your copied path in the fist entry
9. then change your uploadrate to 9200 (9600 works fine)
10. reconnect your CJCMU3212 and select Arduino Leonardo in arduino
11. Flash this https://github.com/robertio/DM-3212-Badusb/blob/master/step1.ino
12. after that reconnect your CJMCU with the two metal bin on front connected with a cable etc
13. Now you should flash your previously exported bin with the tool from step 7 (kepp the metal pins connected till end)
14. remove the cable and reconnect your CJMCU3212
15. Now your ESSP8266 is reeady now we have to flash the atmega

Flash Atmega32u4

1. Open atmegaduck/atmega_duck.ino with the Arduino IDE.
2. Connect your CJMCU3212
3. Under Tools > Board select the normal arduino leonardo (not the wifi duck one)
4. Press Upload.
5. Finish

[Evil0000]

my script is not running on computer. it shows running but nothing happens