Lair Of The Multimedia Guru

January 11, 2016

Thermoelectric cooler

A while ago searching around on ebay for geeky/nerdy toys i found some Thermoelectric coolers/peltiers for around 2$ with free shipping. So i bought a few of them …

They all worked fine, one had a hole in its silicon sealant though which ive “fixed” with hot glue (first heated the element up to reduce moisture inside then re-sealed it), i dont remember why i didnt use silicon …

I experimented a bit around with 1 and 2 stage TECs on a old heat-sink + fan that was laying around, the best combination interestingly was 2 stages first at 12V 2nd at 5V. though the gain for 2 stages over 1 stage was disappointingly small, IIRC a little over 10°C. Its also interesting to note that my chinese IR thermometer was not able to measure the temperature of the frosted top, it displayed way too low values. Actual real lowest value achieved was measured with a Type K thermocouple, frozen onto the TEC in a drop of water and frosted over for a while (the snowy stuff that forms should provides some extra isolation).
The 2 TECs in above are attached with cable ties, which was very limiting in what could be placed on top

For some reason yesterday i decided to test using the TECs for heating instead of cooling by reversing the input polarity.
That indeed worked and the same device happily boiled drops of water. I didnt think too deep about what the maximum temperature for the TECs was, i didnt expect failure below 180°C, but the top element died at probably around 120-130°C (K type thermocouple in drop of oil on top).
Not entirely believing the apparent facts, i picked another unused separate TEC1-12706 and retried, heating it to 160°C
which seems to have done no harm to it. Though i used the IR thermometer for measuring the 160°C, i should retry this probably with both thermometers but then according to the ebay article page they are max 70°C ;)

Breaking my TEC cooler toy i took it and the failed TEC element apart, Its failure mode was that it showed >10megohm resistance. Cutting its sealant away, it looked like this:
IMG_0460-1280 IMG_0461-1280

And separating it further with a tiny bit of heat and force (probably only heat was needed)

Also interestingly none of the remaining individual elements tested open, they all had low resistance. I know nothing about TEC failure modes but i wonder if one little part had just cracked from the heat and maybe mechanical stress. They are all in series so one cracking the wrong way should show similar symptoms …

To rebuild the TEC2-toy now ver2, i placed a piece of aluminum on top and tried to attach it with cable ties, but this proofed frustratingly unstable

My next idea of fixing it with screws, bolts, nuts or such wasnt an option as i lacked parts of sufficient length with non ridiculous diameter. So i cut 2 pieces of the same aluminum stuff and fixed it with 4 springs created out of a single larger spring separated by some foamy stuff for isolation:
IMG_0465-1280 IMG_0468-1280 IMG_0467-1280

In action:

Also i tested cooling and heating of a glass container with a liquid. (for cooling a drop of water was used as thermal component between glass and aluminum for heating a drop of minnaral oil). Without isolation, the temperature fell to +9.5°C in 1 hour and with some isolation to prevent the warm air from the fan hitting the container, to +2°C in another hour. Iam quite sure sub zero is achievable with a real attempt to prevent coolness loss but i kind of lost patience.
on the hot side i achieved 67°C with the TEC itself being at around 100°C, so if one would risk damaging the unit it might be possible to boil water in a container with it.

Filed under: Electronics,Hardware,Off Topic — Michael @ 5:00

December 25, 2015

Bluetooth tracking devices/tags/”key” finders battery lifetime

6 weeks ago (11th november) i switched both the tags i have on and put them in the same drawer in my kitchen, i then tried to connect to them when i remembered about it and tried to make them beep remotely. the itag failed to connect the next day but worked again after removing the battery for a moment, the day after that it failed again and no longer recovered after removing the battery (which was at 2.897V but apparently could not supply enough current anymore for the tag to power up), on last connection it showed 100% battery. Powering the itag off a bench power supply showed that it still worked fine.
Meassuring its current draw, shows 3uA when switched off, and around 1.1mA when on, considering that the tag has to be on to be of any use, that renders it useless as it eats batteries too quick.
the smart finder / “small lovely” continued working till when i tried it yesterday when a connection was no longer successfull, pushing its button it still produced a silent click which on repeated presses got weaker. so it too used up its battery after about 4-6weeks (i had last tried it 2 weeks ago when its battery was shown at 100% in bluthooths stuff).
Meassuring its current consumption, it draws 2.4uA when off, and when on after some initial higher draw fluctuates between 2.7uA and around 88 uA with an apparent average of 39uA.
Note, the current draws depend significantly on the voltage for the itag at least (i tested at about 3V), also the uA meassurements where at the edge of what my multimeter could show so they should all be considered approximate.

In summary, the itag i got eats its battery in 2 days, the smart finder thingy in about 4-6 weeks. I would have tested more tags but these where the only 2 i received. another one i ordered off ebay was lost in shipping apparently

Filed under: Electronics,Off Topic — Michael @ 23:20

November 27, 2015

Modifying a 80-250V AC Volt/Amp/Power meter to make it work for 0-250V AC

A while ago i bought an old variac on ebay, it was in good shape but lacked any meter, originally that model had a analog voltmeter or something. That was missing, some cut wires sticking out of where it was. As i got it it also had a 6.5Amp fuse in a fuse holder marked as 4A and its output wires connected straight bypassing the fuse.
When i bought it my plan was to stick a cheap digital meter to it, which is what i did and also a modern and correct “fuse”.
The meter i found and got supported 80-250VAC, i failed to find one supporting AC voltages down to 0V. I originally had not planed to modify it, as it didnt seem a big issue, but it was just annoying that around 70V it dropped out and displayed junk and then went dark.
Inside it looks like this:
I saw 2 obvious ways to make this work with lower voltages, first is to make its AC->5vdc supply work with a wider range of AC voltages, the other is to split the voltage sensing off the supply. As my variac provides around 250VAC in addition to the variable and isolated output, using that seemed to be the easier solution.
But before i continue, a warning, do NOT try this unless you understand what you are doing, mains voltage can be dangerous and can injure or kill. Also not all similar looking such meters are neccessary identical and this modification might result in undefined behaviour in that case.
The voltage is sensed through R3 which is 1Mohm, removing it:
Results in a working amp meter with 0V:
Next we need an additional connector for the separate AC power and AC sense input, to get that we just need to clear 2 from solder and cut the 2 connected pins on the other side using a file. Note, if you try this modification double check that the new freed up pin is not connected to anything else by some tracks below, it wasnt in the meter i had but that doesnt imply its not in yours.
Now its tempting to use the same or a new 1meg ohm resistor for the new sense wire added below (and i did and it worked) but this is probably not safe, first you should clear the conductive parts of the logo which are below, off the board and use 2 resistors in series as there is about 230VAC over it, yes it was already before any modifications but still.
You can also slightly adjust the value of this resistor to adjust/finetune the volt-meter.
The other side of the resistor is connected with a mod wire to the newly freed up pin on the other side. Again using a file to make some cut in the board to nicely route the wire around.
The new connector is then connected like this:

  1. Variac secondary tap 1
  2. Variac secondary tap 2 and Load/Output connection A
  3. Variac secondary tap 3
  4. Load/Output connection B

Testing, works:

Filed under: Electronics,Hardware,Off Topic — Michael @ 0:11

November 9, 2015

Bluetooth tracking devices/tags/”key” finders

A while ago in coverity while fixing FFmpeg bugs there was a some kind of Nominate a bug, win a prize thing, i didnt ever nominate one but this was when i learned about the existence of tile which would have been the prize one could win. A BLE device that can be attached to something valuable and that can then be searched and found with a recent android or iPhone, or the other way around using the device to find your phone.
This seemed potentially useful to me, though i personally have never lost my keys or phone for more than a few seconds, i know someone who does have that problem. So i thought buy a tile or 2 they might come in handy for something but then i saw the price, non replaceable, non rechargable battery and thought ok, didnt expect someone would be that lame. I guess one should not expect any company not to attempt to rip its customers off to the maximum extend possible.

Lucky there are many similar devices, so the goal was to find the cheapest that works and is not just tied to a ridiculous business model. So i bought some of the cheapest i could find (they of course all have user replaceable batteries …)
First is something that identifies itself as


The above one is one example of these, they come in many different shapes, cost less than 5$ with free shipping. The first i got had a different shape and came with a dead battery and also ate a new battery within a day. The second i got is the one pictured above, which worked more or less.
When Off, A long press on its large surface switches it on with 2 beeps.
When On or connected a long press switches it off with a long beep (this renders it useless as its easy to press by mistake)
When on but not connected its led also continuously blinks, draining the battery but making finding easier, it also at least once hanged and required the battery to be disconnected for a moment to function again.
On the BT protocol side setting immedeate alert to 2 results in 30 beeps and led blinks, setting link loss to 0 or 2 has no effect, the device always beeps on unintentional connection losses as far as i could figure out. pressing the button results in a notify with value 0x01 on 0000ffe0-0000-1000-8000-00805f9b34fb / 0000ffe1-0000-1000-8000-00805f9b34fb.
To make the itag only blink and not beep on immedeate alert, 0000fff0-0000-1000-8000-00805f9b34fb/0000fff1-0000-1000-8000-00805f9b34fb can be set to 0x00, this is remembered over disconnects but not over switching the tag off. All other values seem to cause blinking and beeping.
To identify it this may be helpfull:

  • 0x2A29: CEVA
  • 0x2A24: BT 4.0
  • 0x2A25: 12x07x2012
  • 0x2A27: SM-1
  • 0x2A50: Bluetooth SIG Company: Ceva, Inc. (formerly Parthus Technologies, Inc.)
    Product Id:13330
    Product Version: 26369

Smart Finder

The above is another sub 5$ tag, which appears identical (minus the logos) to tags on amazon from chirotronix and ikee.
The official software for android (“small lovely”) has a rather long list of unneeded permissions like for the previous tag (“iTracing”) but for this theres also no inofficial sw i could find for android which supports these tags, which is why i reverse engeneered the protocol
When off a long press switches it on with a long beep, to switch it off again 5 rapid short presses are needed (resulting in 3 beeps).
When in On mode pressing the button results in 2 beeps this also causes the “#255 Manufacturer Specific Data” to change from 0x58,0x48,0x52 to 0x58,0x48,0xFF for a few seconds, apparently to identify which of potential several devices one wants to connect to. Switching the device off also seems not possible while it is connected. On connect and disconnect its led flashes once.
Protocol wise neither “link loss” nor “immedeate alert” have any effect that i could identify. To make the device beep and blink a command must be written to 0000fff0-0000-1000-8000-00805f9b34fb / 0000fff1-0000-1000-8000-00805f9b34fb. A single 0xAA results in some short beeps and blinking. Its also possible to write a 5 byte command 0xAA 0x03 count duration1 duration2. The count is the number of beeps, the 2 durations are the beep and non beep durations in milli seconds, i dont know what the 0x03 does or if there are other interesting commands.
To detect button presses the device can send notifies on 0000fff0-0000-1000-8000-00805f9b34fb / 0000fff1-0000-1000-8000-00805f9b34fb with a 3 byte value, it is either (0x01 xx 0x00) xx = number of short button presses or (0x02 0x00 xx) xx = number of seconds button is hold
To identify it this may be helpfull:

  • 0x2A29: SIGNAL
  • 0x2A24: BT A8105
  • 0x2A25: 00001
  • 0x2A26: F4F5V02
  • 0x2A27: A8105F4
  • 0x2A28: 1030627

The name of teh device is “AMIYJ_5B68”, i dont know if this is true for all these devices, google seemed not to have any hits on that.
It seems using a A8105, (the ITAG seems using a BK3431) datasheets can be found with google.
Interestingly theres also a entry for “Heart rate” on the bluetooth level, so i guess this shares some code with some other devices.


Hope something above is useful to someone

Update: 2015-11-09: corrected itags link loss behavior
Update: 2015-11-10: Added names of the official apps
Update: 2015-11-14: Added itag blink only info (found by and thanks to Joachim Schäfer)

Filed under: Electronics,Hardware,Off Topic,Reverse Engineering — Michael @ 3:16

June 7, 2015

Loongson 3A heat and noise

The Loongson 3A box i have is loud, which was a bit of a surprise to me. Subjectively the noise from its CPU fan is significantly louder than my 2 overclocked 6core i7 boxes together though nowhere near the hurricane level of the powermac.
Originally i had planned to run the box 24/7 or similar and submit results to But for a box standing in my living room the noise level was too high for that.
Obvious solution rip the fan out and stick a less noisy one in,
its a standard 60x60x15.5mm fan, i choose the Noctua NF-A6x25 FLX as replacement, i didnt pick the PWM variant because for some reason the 4pin cpu fan connector was unused and the old fan used a 3pin sys fan connector, so it felt safer to me to use the same.
To remove the old fan t he board must be removed, as the screws cant be undone without holding their behind.
With the screws and the fan, the heatsink comes off too:
The old thermal compound seemed not entirely uniform, part of it looked more solid than the rest. I intended to apply new anyway so that doesnt matter though, with the stuff cleaned off it looked this way:
As the noctua fan is thicker the screws cant be put all the way through the fan as they would be too short, putting them only through the bottom part makes them stick out at the bottom of the main board a bit more but there is enough space, ive also slightly bent the outtermost heatsink fins a tiny bit inward so they rest on the rubber part of the fan and added some o rings around the screws for a bit of extra vibration decoupling which was probably useless.
Thats how the result lookes:
and theres the old fan:

Does it still work ? yes and it still passes fate
What about heat? before /proc/cputemp was between 40 and 42°C and now its between 38 and 41 °C both while running fate.
For noise testing i put a microphone 3cm in front of the closed box (thats far away from all fans). I was too lazy to switch my other boxes off though:

sys-off-spectrum old-spectrum


Loongson Box switched off Original (AVC) fan New (Noctua) fan
Filed under: FFmpeg,Hardware — Michael @ 3:30

May 22, 2015

FFmpeg FATE tests on Loongson

After the patches from loongson yesterday, FFmpegs full fate testset passed.

time make fate -j4 -k >& fatelist8
real 28m32.631s
user 98m50.422s
sys 12m53.547s

Filed under: FFmpeg,Hardware — Michael @ 17:16

May 8, 2015

Loongson MIPS Box

Loongson very generously donated a MIPS box with “ICT Loongson-3A V0.5 FPU V0.1” CPU, 500gb 7200rpm WD Caviar Blue HDD, 4gb RAM and a power cable with Chinese plug to FFmpeg. Picture of the inside of the box:
Quick power meassurments show

  • ~1W when OFF
  • ~44W when IDLE
  • ~48W when running fate tests

Quick FFmpeg build benchmark with gcc (GCC) 4.8.3 20140624 (Red Hat 4.8.3-1):

  • 4m49.192s for time ./configure --enable-gpl --enable-pthreads --samples=/home/loongson/fate/ --enable-nonfree --enable-version3 --assert-level=2 --cpu=loongson3a --enable-loongson3
  • 19m31.114s for make -j4
Filed under: FFmpeg,Hardware — Michael @ 4:00

February 28, 2015

New computer

I got a new computer, it has 2 liquid cooled CPUs, a Samsung 850Pro SSD, 9 cooling fans, 2 network adapters, >1kw power supply and weighs about 22kg. Its a Power Mac G5, (late 2005 model, which is apparently the last model that was built) and i got it at a good price, i guess because it looked a bit dented from outside but interrestingly on the inside it showed nearly no signs of use or damage, there was not even vissible dust inside.
It came with OSX on some western digital HDD with a apple logo on it. I replaced that one with the SSD which mysteriously didnt work on my first try but when i conected it to the 2nd SATA connector it worked fine. And as i quickly realized OSX is too outdated on PPC to be usable, so i installed debian on it which worked fine but took a bit long to install for unknown reasons, i expected it to finish in maybe 30min or so on a SSD but it took much longer, dont remember exactly how long. So far the only real issue i noticed is that one of the CPUs gets too hot causing the kernel to reduce its speed. I saw no signs of leaked coolant though. I guess as long as it works and i see
no leakage i wont spend more time on that issue though
FFmpeg build and fate also passed on it :)

Filed under: Hardware — Michael @ 2:26

January 12, 2015

Seagate barracuda

2 Days ago shortly after i woke up, i heared a squeek, klick, squeek, … noise from my computers. A quick run of smartctl didnt reveal anything majorly wrong, and the noise stopped for a moment. when it started again, i systematically tried putting disks in sleep mode with hdparm to identify which if any hdd was making these noises. But no hdparm command affected the noise, then slowly waking up, i realized that i actually had more disks in the box than i got results from smartctl, also a look in syslog confirmed that ata2 was not healthy, teh first failed command was at 12:25:54, ata2.00: failed command: IDENTIFY DEVICE, a minute later ata2: reset failed, giving up. Restarting the box and reconnecting the cables did not help either.
My last smartctl output of it from 2 month ago listed it at 20687 Power_On_Hours and 2504 Reallocated_Sector_Ct, none of the values was above their thresholds.
This disk was used for half my fate clients before i moved them to a more powerfull box and it itself was a replacement for a failing 1tb samsung disk, well ironically the samsung disk that the 1tb seagate disk should replace still works though with 3458 pendng sectors.
Iam not sure if iam imagining it but it seems like the quality of disks is getting worse each year
Though luckily this one had nothing important on it, or at least nothing i remember ;)

Filed under: Uncategorized — Michael @ 21:39

January 6, 2015

WordPress spam filters

Many years ago the spamfilter i used for this blog was spam karma 2, it was free, it worked and it worked well. Sadly it hasnt been maintained or updated by anyone since a really long time, which did not improve its ability to keep spams away as spambots and spammers evolved. Also with each update of wordpress it started falling apart more until finally with the update to 4.1 spam karma 2 stoped working, assinging every spam a large positive karma value
So i enabled akismet and bad behavior which where already installed. If anyone has difficulty posting a comment due to them, please email me and ill try to look into it.

Filed under: Uncategorized — Michael @ 1:54
Next Page »

Powered by WordPress