Some early work from UFID shows how even different Slic3rs can change the expected material properties of a filament.

Ask Hackaday: Material Databases

With more and more previously industrial processes coming online in the home shop, people are finding that getting the information that was previously provided by the manufacturer of a hundred thousand dollar machine for their three hundred dollar Shenzen special is not easy.

Some early work from UFID shows how even different Slic3rs can change the expected material properties of a filament.
Some early work from UFID shows how even different Slic3rs can change the expected material properties of a filament.

A common example is this, a hacker purchased themselves a brand new 3D printer off amazon for a price too good to be true. After a week of tinkering with it, a small fire, and a few replacement parts later, they get it to work. After they’ve burned through, perhaps literally, the few hundred grams of filament that came with the printer at the setting recommended by the manufacturer, they do a small blanket order of the different filaments out there. Now comes the trouble, each printer is a little different and each filament has different properties. Most people find that the second spool of filament they feed into their printer doesn’t work at all. What’s the quickest way to get the right temperature, cooling, and feed settings for your printer configuration?

This isn’t a problem for the expensive machines. Epilog, a manufacturer of laser cutters, provides a grid of settings for each material you’re likely to cut, tuned to the different properties of each model of laser cutter they sell. Same goes for the expensive industrial 3D printers, each (very expensive) spool of material has the setting sitting in a chip in the casing. When the spool is slotted in the machine, it reads the settings and adjusts accordingly. All the work of tuning was done in a lab somewhere and the print is, theoretically, guaranteed.

Your Oshpark order would get delayed, your lulzbot support case would be dropped, teensies would ship late, and the Amp Hour would just be the EEVBlog Podcast if this bar burnt down, but it was a great event!
Your Oshpark order would get delayed, your Lulzbot support case would be dropped, Teensies would ship late, and the Amp Hour would just be the EEVBlog Podcast if this bar burnt down, but it was a great event!

While we were at the Bay Area Makerfaire 2016, we had a chance to talk to [Gauthier de Valensart] and buy him a beer at the Hackaday Meet-up. [Gauthier] is from Belgium where he is the founder of a start-up with one of those fancy new TLDs: filaments.directory. The goal of filaments.directory is to create a database of 3D printer materials and link that up with a user’s 3D printer settings. The eventual goal being, much like the industrial printers, a user would be able to simply scan a barcode, or wave the spool over an RFID reader to input the needed settings into his slicing software or printer.

This sounded familiar to me, not the least because I had started work on it as an extension for repables.com when that was a larger focus in my life. In fact, I remember, while I was kicking the idea around to people at MRRF, that they kept telling me someone else was working on a similar project. I wanted to introduce [Gauthier] to the person who was working on the project back then. Since I was at a bar full of people in the industry, I sort of helplessly rotated in my spot trying to find someone who might remember. I spied [whosawhatsis], a common attendee of MRRF, and asked him. Okay, that was easy, [whosawhatsis] informed us that is was his project… introduction complete. Goes to show you what a good networking event buying a bunch of nerds beer can be.

They got a pretty okay logo while they were at it.
They got a pretty okay logo while they were at it.

The project was called, “Universal Filament Identification System,” and it proposed to, “… eliminate the guess-work,” by, “…developing a method for tagging, tracking, and identifying filament for 3d printing in machine-readable formats…” The project appears to be mostly dead now and its domain is a placeholder. I think it suffered from the standard open source feature creep, but the idea is sound.

Which gets us to the questions. There are a lot of difficulties with creating such a system. The first being the data collection. Who should be responsible for measuring the filaments, the materials for laser cutting, or any other process that needs tuned settings? The ideal track, of course, would be for the manufacturers to hold themselves accountable and report on the settings for their filaments. However, many filament manufacturers rely on the ignorance of users to sell dodgy products, it’s only in the interest of a few top-quality ones to do so. If the users do so, then how will the information provided be vetted? You definitely don’t want someone’s ignorance about a faulty thermistor to encourage you to run PLA at 280C.

More and more difficulties arise. How should the information be transferred, etc. What properties should even be recorded? UFID was going as far as to use a color sensor to keep track of colors between batches from 3D printer manufacturers. In the end it’s about creating standards in a standard-less industry by using crowdsourcing. Either way, take a look at what [Gauthier]’s doing (and send him some feedback), read the backlogs of UFID, think about how annoying it was to get the right settings for a laser cutter the last time you used one, and let us know your thoughts in the comments.

Pen-Plotter Firmware Written Completely In Ada

[Fabian Chouteau] built a plotter out of CD-ROM parts. Yawn, you say? Besides being a beautiful physical build, this one has a twist. He wrote the software and firmware for the entire project himself, in Ada.

Ada is currently number two on our list of oddball programming languages that should be useful for embedded programming. It’s vaguely Pascal-y, but with some modern object-oriented twists. It was developed for safety-critical, real-time embedded systems (by the US Department of Defense), and is used in things like airplanes, rockets, and the French TGV trains. If that sounds like overkill for your projects, [Fabian]’s project shows that it’s still very tractable.

In his GitHub, he re-implements the GRBL G-code generator and then writes a GUI front-end for it. In his writeup, he mentions that the firmware and its simulator for the front-end use exactly the same code which is quite a nice trick, and guarantees no (firmware) surprises when moving from the modelled device to the real thing.

We looked quickly around for Ada resources and came up with: GNAT, the GNU Ada compiler, and its derivatives: GNAT for ARM (STM32-flavor), ARM-Ada (LPC21xx flavor), AVR-Ada, and MSP430-Ada.

Any of you out there use Ada in embedded work? We’d love to hear your thoughts.

Continue reading “Pen-Plotter Firmware Written Completely In Ada”

Data Logging; Everyone’s Doing It, Why Aren’t You?

Between Tesla Motors’ automobiles and SpaceX’s rockets, Elon Musk’s engineers just have to be getting something right. In part, SpaceX’s success in landing their first stage rockets is due to analysis of telemetry data. You can see some of the data from their launch vehicles on the live videos and there is surely a lot more not shown.

An article in MIT Technology Review provides similar insights in how Tesla came from behind in autonomous vehicle operation by analyzing telemetry from their cars. Since 2014 their Model S received an increasing number of sensors that all report their data over the vehicle’s always-on cellular channel. Sterling Anderson of Tesla reported they get a million miles of data every 10 hours.

Image Credit Tesla
Image Credit Tesla

The same approach can help us to improve our systems but many believe creating a log of key data is costly in time and resources. If your system is perfect (HA HA!) that would be a valid assessment. All too often such data becomes priceless if analysis explains why your drone or robot wanted to go left into a building instead of right into the open field.

Continue reading “Data Logging; Everyone’s Doing It, Why Aren’t You?”

Self-Balancing One-Wheel Motorcycle Tears Up The Beach

[XenonJohn] wrote in to let us know about updates and a recent test drive of an Electric Self-Balancing One-wheeled Motorcycle, fresh from the beach where he says it proved to be great fun to ride. The design and build have been updated since we last saw it as a semifinalist entry in the 2014 Hackaday Prize. The original, he says, “looked cool but was slow, cumbersome and really dangerous to ride.”

electric self-balancing unicycle - thumbnailSince then it has been completely redesigned and now has a super fat kite-surfer wheel, a front crash skid with damper, and a variable geometry which allows it to steer properly despite just having one wheel. It does this by allowing the rider to shift their position relative to the wheel, instead of the seat always being rigidly locked directly above the axle.

That steering is a pretty clever upgrade, but we do wonder if the new crash skid will have an atlatl effect and really launch the rider in a crash. Our gut feeling aside, it is designed not to plant itself in the pavement, but to slide along (without ejecting the rider) until the vehicle loses all momentum.

There is something about self-balancing unicycles that attracts experimenters, each of whom takes a different approach. We see everything from this device constructed mainly from a Razor Scooter to this more polished-looking unit based on an earlier Segway clone design. [XenonJohn] reminds us that “there is still much to learn in this area and you can genuinely innovate even as a hobbyist. Also, you can only do so much on a computer, you then have to actually build something and see how well it works. [This recent test] shows what you can do if you just keep on experimenting.” Video of the test drive is below.

Continue reading “Self-Balancing One-Wheel Motorcycle Tears Up The Beach”

HDMI Extender Reverse Engineered

[danman] has been playing around with various HDMI video streaming options, and he’s hit on a great low-cost solution. A $40 “HDMI extender” turns out to actually be an HDMI-to-RTP converter under the hood.

He’d done work previously on a similar extender that turned out to use a quirky method to send the video, which he naturally reversed and made to do his bidding. But non-standard formats are a pain. So when he was given a newer version of the same device, and started peeking into the packets with Wireshark, he was pleasantly surprised to find that the output was just MPEG-encoded video over RTP. No hacking necessary.

Until now, streaming video over an IP network from an arbitrary HDMI output has been tricky, [danman] has been more than a little obsessed with getting it working on the cheap. In addition to the previous version of this extender, he also managed to get a stream out of a rooted Android set-top box. That costs a bit more, but can also record at the same time, should you need to.

None of this solves the HDMI HDCP encryption problem, though. You’re on your own for that one.

(Those of you Wireshark wizards out there will note that we just swiped the headline image from the previous version of the project. There were no good images for this one. Sorry about that.)

Hackaday Prize Entry: The Green Machine

For Hackers, rapid prototyping is made easier using basic building blocks such as the Raspberry Pi, Arduino and the huge variety of add on shields for home brew projects. But we don’t see too many real world Industrial applications or machines built using these off-the-shelf electronics. [SlyScience] built The Green Machine – an industrial grade, automated spray painting device to help coat polycarbonate tubes consistently.

The Green Machine is essentially a linear drive that can move a spray gun across a spinning clear tube and coat it evenly with the desired color. These tubes are used as color filters – they slide over standard T5, T8 or T12 fluorescent lamps – and are used in advertising, special effects, films and similar applications. For almost 10 years prior to this machine, the task was done manually. The HPLV (high pressure, low volume) spray gun used for this process needed skilled hands to get consistent results. It was easy to ruin a tube and cleaning them was not possible. [SlyScience] figured things out on the go – teaching himself and figuring out all of the software and hardware pieces of the puzzle. The welded steel frame is about the only “custom” part in this build. Everything else is COTS. Check out the video of The Green Machine in action below, and if you have any tips to help improve the build, chime in with your comments.

Continue reading “Hackaday Prize Entry: The Green Machine”

Rainbow Cats Announce Engagement

[ANTALIFE] is going to tie the knot sometime in 2017. Instead of sending out paper announcements or just updating his Facebook status, he wanted to give their family members something lasting and memorable, like a small trinket with a pair of light-up cats.

This project is pretty simple in theory. A pair of RGB LEDs cycle through the colors of the rainbow with the help of an ATtiny25 and resistors carefully chosen for each LED. But there are several challenges at play here. [ANTALIFE] wanted to design something quite small that would last at least a day on a single CR2032 coin cell. This project was his first foray into SMD/SMT design and construction. We think that this warrants its own congratulations, especially since it looks as though he made at least a dozen of these things.

[ANTALIFE] made things much easier for himself with the purchase of a cheap hot air rework station and used a chip clip to program the ‘tiny. The cats are a design from Thingiverse, which he modified to turn them into bride and groom. Watch a whole line of them glow after the break. We sincerely hope that a larger version of these cats end up on top of the wedding cake.

For anyone with an undying love blinkenlights and impending nuptials, don’t forget the light-up invitations, wedding attire, and centerpieces.

Continue reading “Rainbow Cats Announce Engagement”