Scale NFC no longer scans a tag...

[ShadyantGH]

Hello everyone!

I was wondering if anyone else has run into this issue...

I've had Spool Ease built and in service since 0.5.0 was still beta and 0.3.5 was the stable version... I installed 0.3.5 and then immediately updated console and scale to 0.5.0

Everything worked flawlessly both the console and the scale scanned tags as expected

I typically scan via the console and rarely use the scale to scan so I'm not 100% sure when my issue arose.

It's during this time I had not attempted to scan a tag with the scale since 0.5.0 was installed and know to be worked as expected.

When I saw 0.5.2 available as an OTA update I updated both console and scale...

Then I saw 0.5.3 available a few days ago and updated the console (Initially I inadvertently only updated the console and not the scale)

It's here I noticed I can no longer scan a tag with the scale.
All other scale functions appear to be working. The scale still weighs spoils and the console can communicate with it.

So far what I've done to troubleshoot is;
Rebooted the scale and console confirming all communications have reconnected (issue persists)
Removed the scale cover to confirm the NFC power LED is lit (yes it is, issue persists)
Confirmed all wire connections in the scale are still in tact at all pin points (issue persists)
I'd purchased spare NFC tags so I soldered a new NFC chip and installed that into the scale (issue persists)
Here is when I noticed the scale was still on 0.5.2 so I updated the scale to 0.5.3 and confirmed a successful update (issue persists)

I'm out of ideas as to why the scale NFC chip no longer scans a tag but the console scans as expected.

Anyone else had this happen? Any suggestions on what else I can do to TS?

Respectfully
Anthony

[yanshay]

It should work.
Place something on the scale and see you see weight showing on the console to verify they are connected.

Then scan a tag.

If it doesn't work upload scale (not console) logs from time of boot including a tag scan.

To see how to collect logs check the documentation.

Upload the logs here or on Discord (note that the scale logs include the security key so if it matters to you remove it first or DM directly to me - yahshay, on Discord).

[ShadyantGH]

Thanks for the super speedy reply!!

Yes, all other scale functions are working. It communicates with the console when I’m weighing a spool…it just won’t scan a tag

I’ll definitely grab the logs when I get home and post them.

Thanks in advance.

[yanshay]

Probably something disconnected - soldering of the PN532 or something else.

[yanshay]

Also, if there are errors in the PN532 I think it's reported to the console and appears on the terminal screen (swipe down to expose the terminal screen above). It is prefixed there with "[S]".

[ShadyantGH]

I’m home to grab logs.

Prior to posting I’d soldered a new spare PN532 and had the issue still even after double checking the pins.

I don’t recall seeing any errors in the terminal screen.

I’m reviewing again now

[yanshay]

Check the dip switches as well

[ShadyantGH]

Yes, I already ensured the dip switch was in the correct config on both the old and new PN532 I'm trying

[yanshay]

I had cases when the DuPont connectors were not touching well. That can be another reason.

Anyway, see if the log reports any error on initialization.

[ShadyantGH]

Here's some videos while I grab logs next...

https://youtube.com/shorts/ODzGRjVOSzg?feature=share

https://youtube.com/shorts/UKChFVxe_Gw?feature=share

https://youtube.com/shorts/aLza7u5c5L4?feature=share

https://youtube.com/shorts/7tSc81X1cOk?feature=share

[ShadyantGH]

Immediately in the live logs I see "Challenging PN532 initialization (59)

So the PN532 is not initializing... but I've tried 2 different PN532's and ensured both dip switches are in the correct config...

It's very odd that the original PN532 worked as expected for almost 2 weeks before it started having this initialization issue...

[ShadyantGH]

esp-web-tools-logs.txt

[ShadyantGH]

I wonder if I should try a clean flash/install of the 0.5.3 from the website...if I don't find any internal connection issues upon a new inspection I'm about to do.

[ShadyantGH]

Side question Yanshay... is it possible the ESP32 is the root cause?

I ask because interestingly the first ESP32 I purchased for this build from AliExp was DOA... it would show up on the serial port as available but would never flash after attempting ALL troubleshooting you list and after trying the couple issues previously found in here...
The first ESP32 never had any LEDs lit despite me verifying continuity on pin 48 and the red pins after soldering the RGB

I ordered a new ESP32 from Amazon and that one immediately worked as expected after soldering the RGB...

Could it too have gone bad to cause a failed PN532 initialization?

[yanshay]

Theoretically yes but not likely.

[yanshay]

Yes, it's the PN532.

It can be one of:

1. Wiring / soldering / dip switches etc. can also be mistake in wiring (ignore colors - consider only pins to signals), make sure no mistake it PIN numbers - I also made mistakes after several times doing that.
2. Not enough power (bad power supply) / usb not touching well
3. Defected PN532
4. DuPont connectors cables connectivity
5. Defect in the Esp32 (pin not working) - less likely
6. Let it heat for some time - seen that happen.

I don't see how it can be software - it runs on many devices.

[yanshay]

Not sure how you connected things but maybe you can swap PN532 between the console and scale.

[ShadyantGH]

I used solder on the console and the Dupont connectors on the scale... so not as easy to swap the PN532 between devices.

[ShadyantGH]

I'm tearing down the scale now to triple check all connections are still made on PN532 and the ESP32 pins

[yanshay]

If you have a spare set of wires to replace between the Esp32 and pn532, try another set

[ShadyantGH]

Yes, I do have more Dupont wires and was thinking the same thing... after tearing down and checking connections I still have an initializing error for PN532 in logs

[ShadyantGH]

I've made some progress but this is still very strange... I'm almost fully convinced it's either the ESP32 or some sort of an interference issue at this point...

After tearing the scale down to check everything and swapping all the 7 Dupont wires for new ones... I plugged the scale into my Mac to view logs and success, the PN532 initialized multiple times back to back...
I should mention the table where my Mac is located is across the room from the original location I had the scale placed...

The strange thing is as soon as I unplugged the scale, put the covers and parts back together and placed it back where it was sitting initially since it was built... the scale booted and the PN532 failed to initialize again...

I brought it back over to my Mac table to view logs again and the logs showed the PN532 failing initialization again.

I chose to re-flash the scale software fresh from the website... and just finished the configuration again and it's sitting on my Mac table not in it's original placement and it's currently WORKING

I'm almost afraid to try it back over where I had it before lol

[ShadyantGH]

For 2 weeks this scale worked 100% as expected and PN532 initialized... then all of a sudden I'm not able to initialize the PN532 in that same location

I have to move it further from the console and P1S for the PN532 to initialize now...

[ShadyantGH]

I supposed I could just leave it next to my Mac on this table but maybe next week I'll move it back again and see if it fails again closer to the console and P1S where I used to have it since I guilt it :)

[ShadyantGH]

At this point I'm leaning towards an ESP32 issue... I tested moving the scale back to the old orig place and it wouldn't connect to the console but WIFI was working and it connected successfully to the console and showed weights when something was placed on it...

Now I moved it back further away from the console and P1S and the PN532 initializes however, the scale will not reconnect to the console even after both devices have been rebooted several times it just won't connect now but ping tests in Terminal show the scale and console have 0 packet loss...

I'm buying 3rd ESP32 and will see how that goes once that's installed lol

[yanshay]

If it's a location issue - are you using the same power source in both locations?

Interference I've seen was usually WiFi related and not PN532.

[ShadyantGH]

Yes. Both had the exact same power source.
both had a 15 foot USB-A to C cable and both USB-A sides plugged into the same outlet by way of a combo plug and ISB port
Both USB ports used were a 2.4a rating

Essentially I’m running the exact same internal parts and power source I did in the beginning when it worked for about 2 weeks before stopping.

The only difference is the scale location

the console and scale used to be about 3.5 feet away from each other

now they’re across the room from each other

on a side note. I got my neighbor to buy and build this after I did
he had an issue immediately after flashing where the PN532 on his console stopped responding and it took resetting the console from the menu before the PN532 worked again

[yanshay]

Interesting.
Try another power supply, don't go based on spec. Find one that's surely good (like Mac/PC one - way more than needed but usually quality and stable).

Also I would try putting the scale in its original location and moving the console away and see if that works to see if its interference between them or just some interference in that location.

I know they interfere wifi wise but never saw them interfere one with another Pn532 wise.

[yanshay]

Btw - maybe it's temp difference beteeen the spots. I know that for me sometimes it takes it a couple of minutes until it initializes properly and from that point on even after turning power off it's immediate. I think there's an element of heat because nothing else I could think of that could explain it.

[ShadyantGH]

@yanshay I finally was able to get it back to stable ( I think) even using all the old original parts and Chips... just in a different location...

Can you see anything out of the ordinary with these latest logs?

esp-web-tools-logs (3).txt

[yanshay]

There are some read errors but that's normal when scanning nfc. It's normal for some failures. If things are functional that's ok.

[ShadyantGH]

Thanks so much!