fossasia / pslab-hardware

PSLab Hardware Design and Schematics https://pslab.io
Apache License 2.0
1.64k stars 92 forks source link

Board Temperature #152

Closed CloudyPadmal closed 1 hour ago

CloudyPadmal commented 2 weeks ago

I just measured board temperature using in-built methods.

Old Prototype Board - Old Firmware Old Prototype Board - New Firmware New Board - New Firmware
OldBoard-OldFirmware Screenshot 2024-06-11 at 12 54 46 PM NewBoard-NewFirmware

New board MCU gets up-to 43 Celsius when the old prototype MCU is around 30-32 Celsius.

bessman commented 2 weeks ago

I don't think this is a problem in and of itself; 43 °C is not worrisome in the sense that it might damage anything. But it does indicate greater power consumption.

This may be related to the resettable fuse problem, and means that battery life in stand-alone mode will be shorter than it could be.

bessman commented 2 weeks ago

Any idea what might be causing it?

One thing that's different between the old and new prototype is the addition of the battery indicator LEDs. As noted elsewhere, they are VERY bright. I wonder if they could be the cause of the increased power draw? Would that manifest as greater MCU temperature?

CloudyPadmal commented 2 weeks ago

I'm not sure what could be the cause.

It looks like the RGB LED is mounted in reverse and may be it is drawing current. I plan to look more into this in this week.

CloudyPadmal commented 1 week ago

I rotated the RGB LED and looks like now it does not heat up anymore.

Screenshot 2024-06-14 at 1 46 20 PM

However, the RGB LED does not light up. I'll try to solder a new one and see as they are quite plasticky and highly possible to get damaged due to reworking with hot air.

bessman commented 1 week ago

I suppose this also explains why the RGB LED doesn't work on any of the recent prototypes.

mariobehling commented 1 week ago

Is this wrong in the schematics?

bessman commented 1 week ago

Looks correct to me: Screenshot from 2024-06-14 16-05-14 Screenshot from 2024-06-14 16-05-01

I wonder how it ended up backwards? :thinking:

cweitat commented 1 week ago

@bessman are u able to check the LED to see if it has the +- sides as the intended component? because sometimes the chinese made chips have reversed poles.

bessman commented 1 week ago

Will check tonight unless @CloudyPadmal checks first.

cweitat commented 1 week ago

One more thing to check. which colour of LED does it happened? White/Green/Blue

CloudyPadmal commented 1 week ago

This notch in the LED should face towards the MCU. It was like that in the early prototype Rafael sent over to us.

3D render Rafael Prototype
Screenshot 2024-06-14 at 8 30 20 PM Screenshot 2024-06-14 at 8 30 20 PM

But this is not the case with the new boards and somehow the LED is rotated. I just checked the position file and the rotation is 0 degrees as expected (D5 - Line 52).

Since this rotation causes the VCC and GND pins to swap, it might have fried the LED in the first place. Let me double check with a new WS2182B LED.

Screenshot 2024-06-14 at 8 46 55 PM
bessman commented 1 week ago

One more thing to check. which colour of LED does it happened? White/Green/Blue

It's the RGB LED. It can be any color. It should be purple in bootloader, green in application.

@bessman are u able to check the LED to see if it has the +- sides as the intended component? because sometimes the chinese made chips have reversed poles.

It's the same as in the datasheet: Screenshot from 2024-06-14 16-05-14

Previous prototype (correct orientation): image

Current prototype (wrong orientation): image

Comparison between previous and current prototypes with board traces marked in yellow and LED pins marked in red: 20240614_201328 20240614_201415

CloudyPadmal commented 1 week ago

Looks like the model got protection against reverse connections.

Screenshot 2024-06-14 at 8 57 04 PM
cweitat commented 1 week ago

What can we conclude from here? That the GERBER wasn't followed in regards to the LED direction and because of this, it resulted in faults of ____?

CloudyPadmal commented 1 week ago

What can we conclude from here? That the GERBER wasn't followed in regards to the LED direction and because of this, it resulted in faults of ____?

I will finalize this by tomorrow or the day after at the latest.

CloudyPadmal commented 1 week ago

So I was able to test again.

The RGB LED was burnt and I replaced it with a spare one and now it lights up.

I did a temperature test, and it seems normal with the new RGB LED.

tmp

Now the conclusion is that,

cweitat commented 1 week ago

I had a chat with the manufacturer side and they want to clarify few items: bf6dc1860bb889e78b76800b8d90abb does the yellow circle meant the direction of placement/polarity for the component?

More example of the schematics
305239b96e6b1eee908c50445a4f095 0d297eb0522aa5f91c7341b5d41fae5 e742145b6ff826ac330d29b478a79f8
cea5623be75f060a064681fa1328cee f14772f8f5351ea6953a584abbc6562
CloudyPadmal commented 1 week ago

The yellow circle marks the pin 1 in an IC or a component. Also on the silk screen, a special marking shows where a special marking of an IC or a component should align.

340600617-d89013c7-81d8-49e2-be30-79ccd2d89b49

In this figure I have marked such markings for the MCU and the RGB LED.

CloudyPadmal commented 1 week ago

The standard is that this special marking is next to pin 1. Apparently for WS2812B RGB LED, the special marking is next to pin 3. Maybe this is where it went off-road for the manufacturer.

WS2812B-Neopixel-LED-Pinout-pico

CloudyPadmal commented 4 days ago

Conclusion

The recently manufactured and assembled boards have an issue.

The issue is that the RGB LED (WS2182B) (D5) is mounted incorrectly, with the VCC (pin 1) and GND (pin 3) swapped. This creates a type of short circuit, rendering the board unusable unless the LED is manually removed and repositioned correctly according to the parameters in the provided PositionFile.csv.

It appears that the manufacturer missed the visual inspection step to verify that the IC pin markings align with the silk screen markings. This issue was caused by the manufacturer’s fault, as all the specifications and files we provided were correct.

@mariobehling @cweitat

cweitat commented 4 days ago

@CloudyPadmal only Gerber, BOM & pick and place zip file from the build was given to the manufactuerer. Is the positionfile.csv is in any of the zip folders?

CloudyPadmal commented 4 days ago

@cweitat Pick and Place and Position are the same file, with different names.

cweitat commented 2 days ago

Reply from them: Pick and Place procedure is not able to verify the direction of the components, only the positioning.

CloudyPadmal commented 2 days ago

Yes, and they got it wrong as it does not require a rotation (0 degrees)

Edit: in fact, pick and place says about rotation. Otherwise cannot get all the other ICs in right orientation.

cweitat commented 2 days ago

They followed the yellow dots as provided in the file as the standard practice as they did with their other customers. And it also impossible to see whether the direction was wrong with just look of it. Moreover, this was only highlighted more than 2 months after it was shipped out

bessman commented 2 days ago

They followed the yellow dots as provided in the file as the standard practice

They did not; standard practice is that the yellow dot marks the connection point for pin 1. They have connected pin 3 at the yellow dot.

it also impossible to see whether the direction was wrong with just look of it.

Incorrect. There are at least two ways to confirm correct orientation with visual inspection:

  1. Note the location of the triangular marking next to pin 3, as specified in the datasheet
  2. Ensure that the LED actually turns on when powered (as I believe we instructed them to do?)
cweitat commented 1 day ago

@bessman Yes. The file given them had the error of yellow dot placed at pin 3, not pin 1, which is what Padmal brought up earlier messages. So in this case, meaning the Gerber was wrong and they just followed in accordance to the file given.

Their scope is not to look through the schematics and all components datasheet to give feedback because the service engaged was just manufacturing and assembly.

There was no mention of how testing should be done other than LED lighting up. It was raised prior to the production and only the lighting up of LED was mentioned.

For point 2, yes the test was plug in power and see if the LED lights up. No particular instructions was mentioned as to which LED lights up etc. Also, there's no manual for test as well, other than an old one. In this case, the white LED lights up so it's considered as a pass.

CloudyPadmal commented 1 day ago

@bessman Yes. The file given them had the error of yellow dot placed at pin 3, not pin 1, which is what Padmal brought up earlier messages. So in this case, meaning the Gerber was wrong and they just followed in accordance to the file given.

I didn't say that the files we provided including the Gerber and pick and place was wrong. They are 100% correct and the manufacturer went in their own way to decide the orientation.

I just mentioned that the RGB LED doesn't have the pin marking in pin 1 unlike other ICs and it has the marking on pin 3 instead.

My bad for putting out too much information...

CloudyPadmal commented 1 day ago

I don't know how else to say that it was the manufacturer who messed up the assembly which took us some time to debug 🙆🏻‍♂️

Please don't misinterpret and the production files are still valid and 100% correct.

CloudyPadmal commented 1 day ago

And it also impossible to see whether the direction was wrong with just look of it.

Just looking at it is in fact the visual inspection stage where you identify ICs assembled in wrong orientations. Check my previous comments about silk screen markings.

This is the standard procedure with PCBWay and JLCPCB.

image

cweitat commented 1 day ago

AOI machine file for polarity testing comes from the provided Gerber (which had the dot on pin 3) as well. So the test would have passed any ways.

CloudyPadmal commented 21 hours ago

Dot is in pin 1 as mentioned earlier.

I'm repeating the same thing and I don't think this discussion yields anything.

cweitat commented 6 hours ago

@CloudyPadmal yes I understand that as well. Therefore I left the communication to the manufacturer with Mario now.

CloudyPadmal commented 1 hour ago

Sounds good. I'm closing this issue as now we know that the manufacturer did not follow the design files correctly and we will manually fix the LEDs with their supposed orientation before shipping out to customers.