Novedad: el cortafuegos de IA supervisa toda la plataforma y explica cada incidente con palabras sencillas. Vea cómo funciona

Two «NodeMCU» boards that look different and one of them never shows a COM port

Two «NodeMCU» boards that look different and one of them never shows a COM port

Resuelto 3 3

I’m building simple part counters for two packaging lines (a photo-eye pulse into a NodeMCU, count sent to Hermetry every minute). I ordered «NodeMCU ESP8266» from two sellers and got two different boards. One is narrow with a square-ish chip near the USB port that says SILABS CP2102, the other is wider with a chip marked CH340G and an extra pin labelled VU.

The narrow one shows up as COM5 and flashes fine. The wide one: nothing in Device Manager at all, no new COM port, Arduino IDE says no port. Different cable, same thing. Is the wide one broken, or are these different products? Which one should I standardise on for 6 more counters?

♥ 2

I had the CH340 one too, I had to install a driver before Windows saw it. Not sure that’s your issue though.

Timestamps in UTC or it didn't happen.
♥ 0

Rachel’s guess is the likely one. Same module, different carrier board. Both have an ESP-12E with the ESP8266 on it, so your sketch and pins are the same.

The narrow one is the «v2» style (Amica design): CP2102 USB-serial chip, fits a standard breadboard with a row free on each side.

The wide one is the «v3» style (LoLin): CH340G chip, wider so it covers all the holes of a normal breadboard, and the VU pin, which is the 5 V from USB. Handy if your photo-eye’s interface needs 5 V.

Windows 10/11 usually has the CP2102 driver, not always the CH340 one. Install the CH340 driver from the chip maker (WCH), unplug and replug, and it’ll appear as a COM port. If it still shows nothing, try a cable you know carries data, a lot of short USB cables are charge-only.

For the six counters: pick one and stick with it so wiring and enclosures are the same. I’d take the narrow v2 if you prototype on breadboards and the v3 if you want the VU pin. And count the pulses with an interrupt, then send one number per minute, not one message per pulse.

Timestamps in UTC or it didn't happen.
Solución aceptada♥ 1

Driver fixed it, COM7 appeared straight away. Going with the wide ones because the photo-eye interface runs on 5 V and the VU pin saves me a buck converter. Already counting on an interrupt and sending count once a minute.

♥ 0
Viendo 4 entradas – de la 1 a la 4 (de un total de 4)
  • Debes estar registrado para responder a este debate.

Únete a la conversación

Inicia sesión para preguntar y responder, dar me gusta a las publicaciones útiles y marcar la respuesta que resolvió tu problema. Cada aportación suma puntos y niveles.

Compartir