KThanks man, i really appreciate your help
NNC Not connected? 
KXdxd no noooo
TWe will also be launching a series of videos in the server next week that help get around common problems encountered by different types of developers so be sure to keep an eye out for that!
K@Navadeep
I have been facing a trouble shoot with RFID interface NODEMCU
I have been facing a trouble shoot with RFID interface NODEMCU
Nokay, you're already shooting the trouble!
Ndid Umesh's suggestion help?
KStill expected output not there yet!
NWhat's happening now. Please explain.
KSure
KActually I'm trying to make my nodeMCU interfaced RFID reader, to read an RFID card or tag and to display the UDI of that particular card on the serial monitor!
K
KCode writing and compilation is done!
No error founded
No error founded
K
KBut I didn't find the expected output
NOkay, let's take this bit by bit:
- cross check if your SS pin defined in code and hardware are the same - that's the only variable I notice in the code.
- UID is from the RFID tag. Are you placing the card on top of the reader? The main loop continually keeps scanning.
- If you doubt over hardware or connections made, hook a logic-analyzer and check the SPI frame.
K"I'll give it a shot and I'll update you shortly."
NI suppose the system didn't find a card at all. If so, the "Card_UUID: " will defacto print in the serial terminal.
KBy the by
"Could you please send me the code?"
"Could you please send me the code?"
N
NI am seeing the code you shared.
KBut I'm asking another one
NTry these and let us know. You're doing right so far with the code.
KOkay!
K@Navadeep
What I found in the SERIAL MONITOR!
What I found in the SERIAL MONITOR!
N- is this with the same code?
- after what changes did this appear?
- did you try tapping the RFID card on the reader?
KI had modified the code, I mean I changed the SDA and RST PINs allocation
KYes I did!
NPlease note which pin in NodeMCU is SS. It should either be 15 or 11 based on which SPI instance you call on your code.
NTry SS pin as 11 for the SPI you're using.
KSERIAL monitor not working with NODEMCU
K"It leads to a different root."
NIn the serial monitor, pick 'NL and CR' mode from the selection below. This will get those junk characters out.
PI think we should, please, start discussing topics in the relevant channels to keep it clean
NOkay. True, that makes sense. Taking this over a thread now.
N@Phoenix do we have a way to move these conversations to a thread now?
KThe Tiny Scarab board is ready:
KGitHub
Tiny beetle board based on the CH32V003 10-cent chip. - GitHub - Embeetle/tiny-scarab: Tiny beetle board based on the CH32V003 10-cent chip.
K
KI'm going to do a small scale test production at Eurocircuits. Please let me know if you're interested in one of the prototypes.
TCongrats!
The server is happy to support the production of additional prototypes. Are you willing to make as many as people who want one, Kristof?
The server is happy to support the production of additional prototypes. Are you willing to make as many as people who want one, Kristof?
Plovely board, congrats @kmulier !
Flooks cool but eh looks super technical too. idk if i would be able to program it
TThere’s another coming based on RP2040 i believe. Our plan is to create demos and tutorials on top of these over time.
Fthat would be nice
T@K.L.NAGARAJU yeah we can move it under #mcu-mpu-and-kits . I’ll tag you.
T@Phoenix, target thread channel ID not being identified (1196129943084613753). Need assistance moving images. After resolved I can migrate the rest of the conversation.
KI can put the DevHeads logo on the board, along with an URL
KWhich URL should I put there?