Tags64-pixels adapter AVR battery bulb car customs DSO fireworks firmware good old days hack happy new year hardware IKEA import lecroy LED light lighting linux MBI5168 modding open source oscilloscope PCB power supply prototype PWM rant remote review RGB RoHS Samtid Seeedstudio SMD soldering teardown trigger upgrade WaveAce 224 weller WS2812B youyue
Real fireworks this time.
As You can see, there’s nothing of interest here. This post was cancelled due to lack of material & motivation. Please proceed to the next post in this mini-series. If you’re a user of headphones, you may want to turn down the volume a bit ;-)
In the meantime, you may find this scientific publication interesting:
This “beauty” appeared on my desk today. Just testing & playing with it. I used the arb sig-gen of a PicoScope 2204A for generating a unpleasant test-signal. Trying to trigger on it was “interesting” :-)
Well… the device I got at work was a sad case of “dead on arrival”.
Temperature regulation was totally crazy, touching the case moved the measured value from about 350°C to 60°C, with a subsequent massive overshoot.
So we have to wait until the replacement unit arrives… maybe an XMAS present.
Since I hear the effing aircrafts all the time, I might as well go and take a closer look at them, no?
An impromptu Sunday trip to ‘MUC’ (or FJS).
Still busy with stuff.
BUT, there is a functional dishwasher! What a great device !!!
Moving == carrying heavy boxes, lots of them.
Getting rid of stuff is imperative!
If You’re so inclined, You’ll find sloppy teardowns of 3 devices below. Mostly images and a bit of video footage at the end.
To make one thing clear, I was looking for a book describing the concept, methodology and application of “Six Sigma”. So you now know my expectations: facts, recipes, some math & statistics primer, NOT a lot of prosa / wall of text without content or just stating the blatantly obvious.
When buying a cheap device, I don’t expect a display with “Retina” quality, but it should still be usable and not something the engineers who designed it have to be ashamed about. It shouldn’t be a piece of shit (in this case it wasn’t). The same goes for all other parts. I can live with less memory, but it should not be defective. If a device claims “Quad Core” I expect it to be reasonably snappy and not turn into a hibernating grizzly every 5 minutes. Cheap devices require trade-offs, but general usability should not be among that.
When I got home today at about 5pm or so, I smelled the characteristic BBQ smell. Burning wood. Quite A LOT of burning wood. Very odd, or at least very unusual for this neighbourhood.
Upon entering the staircase the smell intensified by several orders of magnitude, which instantly spurred my curiosity. At least to find the source and “bitch” about neighbours BBQ-ing on a Friday evening. Oddly enough the smell seemed to originate in the cellar. Nobody should be BBQ-ing down there, or be lighting a wood stove / fire. There’s just way too much stuff down there that could catch on fire and ruin the weekend in a lasting manner.
Shooting in Munich.
As of now (2016-07-22 20:12 CET) not much is known about how many were hurt or killed. The media are going crazy.
Believe whatever you want. But please, make sure it stays inside the head. It’s your own private folly, no need to include everybody else.
It’s worth taking a look and having a go at it! You do know that you NEED a backup, don’t you?!?
I’ve been using dirvish (rsync based) for a good 10 years now. Once set up it is very reliable and can be expanded via pre/post server/client scripts (e.g. to calculate MD5-sums for everything). It supports file-level deduplication (using hard-links), but sadly that doesn’t help with large files that have changed only a tiny bit (like virtual machine disk images). Calculating MD5-sums takes quite some time, especially so as it is done on all backups, so the file-level deduplication saves disk-space but doesn’t help with the MD5-sums being recalculated all the time (on the very same data). A very time-consuming nuisance. Dirvish’s BIGGEST advantage from my point of view however is that the data is easily accessible, it’s just stored in the filesystem you choose (e.g. EXT4). There is no file-level encryption or compression, any system that can mount EXT4 can access the data. Today that is basically any Desktop linux out there.
Back to data deduplication. BORG on the other hand only calculates checksums for NEW chunks of data, so the process is very fast if only little has changed. Yes, I said chunks of data, not files. BORG chops up data into chunks, so it can even handle very large VM disk-images and save some space backing them up. BORG also supports archive compression, password protection and encryption. This immediately brings up the question of long-term accessibility of the data. You really really don’t want to end up with an old backup but vital backup that for some reason cannot be read anymore by new versions of BORG. Fortuitously the developers have released stand-alone versions (see github) that only have minimal requirements (a few standard libs). So far I’ve checked whether these binaries run on a live version of linux (PartedMagic 2015-01-13) and I’m glad to say that the answer is yes. That way it’s quite easily possible to pack a known-good OS / BORG combination onto an USB stick (or ISO image) for future use. In case of a backup that is not based on plain filesystems, it is absolutely VITAL to go that route.
Make a backup, use checksums, verify its integrity, make sure you can access it and restoring actually works. BE PARANOID about your data.
A small but helpful upgrade, if you’re into acquiring your own temperature calibration data. At some undetermined time in the future this might be expanded to a full multi-point calibration mode.
The config menu was amended with the parameter ‘display_adc_raw’. When this is set to 1, the display will show the raw ADC numbers. Temperature regulation is not affected by this, everything else works as usual.
With the help of an external high-temperature probe, you can now quite easily create a table of raw ADC reads vs. temperature measured where you need it, e.g. at the exit of the nozzle (of a certain diameter, for a certain fan speed).
For my device, this looks like this:
# Youyue 858D+ with V1.45 firmware 22.03.2016
# 7mm nozzle, measured coaxially right at the exit
# fanspeed: 4.5
# ---- setpoint / °C ---- ADC / raw ---- measured / °C ----
50 18 56
60 28 66
70 38 77
80 48 87
90 58 97
100 68 108
110 78 120
120 88 129
130 98 140
140 108 150
150 118 160
160 128 171
170 138 181
180 148 190
190 158 201
200 168 211
220 188 230
240 208 251
260 228 270
280 248 291
300 268 310
320 288 330
340 308 350
360 328 368
380 348 386
400 368 403
420 388 419
440 408 438
460 428 457
480 448 471
500 468 486
I’m glad to announce that the annoying watchdog issue has finally been fixed. It was a dumb error on my side, combined with a prevalence in some ATmega chips to have certain binary values in uninitialized registers after a cold start.
* Fixed “.init1” mistake –> watchdog_off_early.
Putting that into .init1 doesn’t work, as it requires R1 to be ZERO.
“eor R1,R1” comes later, so it blows up.
V1.44 release on Github.