Omega2+ hot hot hot



  • Just managed to set-up my first one. This chip doing nothing gets extremely hot. Anybody else noticed this?
    Honestly I have experiences with other chips/boards and this feels like it sits easily at 50C. Basically it cannot be left alone without a fan



  • @Francesco-Pessolano 50C operating-temperature isn't going to burn it up. The SoC has been rated for +55C ambient temperature when operating, which means the SoC itself could be something around 70C-80C. Yes, it does get warm to the touch, but it shouldn't be anything to worry about.



  • @WereCatf Honestly for fun is ok, but for proper deployment I would put a fan on it making it less fun to deploy.



  • @Francesco-Pessolano As WereCatf notes, 50 C should be within the spec limits. That said, if that's the temperature of the metal cover, it sounds quite a bit warmer than I would guess for mine. Mine is slightly warm to the touch, but not particularly hot. It definitely doesn't need a fan.

    If you have the ability it might be worth measuring current draw and comparing with others. In quick search I found one poster seeing 170 mA. I'll to remember to measure and post mine a bit later.



  • Mine on metal is rather warm.It does not burn my lips but it gets close to it



  • @Francesco-Pessolano said in Omega2+ hot hot hot:

    It does not burn my lips but it gets close to it

    Welllll....obvious solution is to not put your lips on it! ;)



  • @Mark-B said in Omega2+ hot hot hot:

    If you have the ability it might be worth measuring current draw and comparing with others. In quick search I found one poster seeing 170 mA. I'll to remember to measure and post mine a bit later.

    Just to follow up on this. With my Omega2+ running on a proto-board with nothing but a linear regulator I got the following data points. This is monitoring current with a inexpensive USB voltmeter which has questionable accuracy at low current levels and updates about twice per second.

    • idle current ~= 110 mA

    • current running cpu intensive task* ~= 170 mA

    • current running wifi task** ~= 280 mA average, peaks around 350 mA - board is noticeably warmer to the touch, but not hot

    I think this suggests that CPU activity doesn't matter much. If an Omega2 is particularly warm (and not otherwise defective) it's likely because the wifi activity is high for some reason.

    * - Python for cpu task gives near 100% cpu

    import random
    import math
    x = 0
    for m in range(0,1000000): x = x + math.sin(random.uniform(0.0,1.0))
    print(x)

    ** - Python for wifi task run via ssh over wifi gives about 50% cpu load

    for k in range(0,10000):
    __ for m in range(0,k): print(m,k)

    Edit to add: I see similar numbers for my Omega 2 (not plus) except "wifi" numbers are higher, with and average of about 330 and peaks up to 420 mA.

    Also, the current spikes are apparent in the boot process where the serial debug suggests wifi activity with the first about 20 seconds into boot.



  • Hi

    My Omega2+ board gets really hot and I see that it consumes around 1.8 Amps continuous current eeven when idle. Just want to know if this behavior is normal?



  • 1.8A current is not normal.
    There may be some type of shortage.
    Please use a magnifier to visually check if there are solder bridges/shorts on both sides of the circuit board.

    ccs_hello



  • @ccs-hello -- I have checked and did not find any shortage as far as back of the board is concerned. FYI, I am not using any docks and directly powering the omega2+ from a power supply on VCC and GND pins. Do you think there is some manufacturing defect with the board, please advise



  • If you only use two pins (3.3V to Vcc and Gnd to Gnd) and still getting the 1.8A reading, the Omega2 is dead.
    Asking for a RMA is the route to take.

    ccs_hello



  • @ccs-hello .. I understand but the board is working fine, I can ssh to it, open is webpage and connect to cloud, only thing is that it consumes 1.8 Amps continuously after switching on. Any comments on that?



  • @Akshat-Mehra You have a short somewhere.



  • re: still functional but consumes 1.8A
    It sounds like driving a car at 60 MPH, while hand-brake pulled and motor oil completely leaked out.

    ccs_hello



  • yes, It may have short somewhere but I can't locate it.



  • Something like that can't be a direct short across a power rail, otherwise the system wouldn't be functional.

    Instead it would need to be a short between a component and a power rail, a damaged section of a chip, or (part of?) a chip that is habitually operating in latchup, perhaps as a result of previous damage such ESD, overvoltage on the power supply or an I/O, etc.



  • @Chris-Stratton Thanks for the explanation. I suspect that it may be an overvoltage on the power supply. If that is the case, then I guess there is no remedy except to throw away the board.. Correct?



  • @Akshat-Mehra What are you using for a power supply? Have you verified that the voltage at the Omega power pins is 3.3 V?



  • @Mark-B Now, I am using a bench-top power supply and I have checked that it supplies a 3.3 Volts using a DMM. But earlier I used a USB to serial 3V3 FTDI cable to supply power to omega2+ without checking its output. Although it was rated 3V3 but the output was +5V as shown on a DMM, which may have damaged the board.



  • It;s live and learn, unfortunately.
    These active semiconductor devices cannot tolerate severe over-voltage, even in several seconds range.
    It is just that fast, poof (can't hear it and no smoke coming out though) it's a goner.

    P.S. there is no fuse protection nor Zener diode clamping down the supply voltage thus it's all on the end users' due-diligence.

    P.S. 2 I even have a very old $$$$ HP lab bench power supply which will exhibit higher voltage when I power it off. It did cook some of my premium toys (much more than $9 Omega 2+.) I have since added a second power cut-off switch on its output side. Live and learn too,.

    ccs_hello


Log in to reply
 

Looks like your connection to Onion Community was lost, please wait while we try to reconnect.