I picked up an Arduino UNO and a couple of shields a couple of months back. After the requisite Hello World projects, I had nothing better to do with it.
Inability to write descriptive comments! Inability to name variables! Nonlinear, graphical programming interface: Messy, horribly hard-to-follow programs! Wires everywhere! Extreme difficulty to insert new commands into an established program without ruining the organization structure! Frakking impossible to debug! Computer processors operate linearly anyway– LABVIEW IS LYING! Sequence structures–the most cumbersome way possible for the Lab View creators to have tried to rectify the problem that sometimes YOU JUST NEED TO EXECUTE COMMANDS IN ORDER JUST LIK ONVENTIONAL PROGRAM, DAMMIT! Mouse sensitivity! As in, my programming ability should not have to rely on my skill to accurately position the mouse over some of those frakking tiny terminals! Timing structures– THEY DO NO SUCH THING! The fact that it has to rebuild all its data acquisition sub- VIs every time I want to make a tiny change to the sampling mode! Shift registers and sequence instances! The saddest excuses for variables on the planet–and they contribute to the messy wiring problem! It handles arrays in an extraordinarily clunky manner–and when you’re taking data, the role Lab View is best suited for, MOST OF THE TIME YOU CAN’ T POSSIBLY AVOID USING ARRAYS! MY LAB RUNS ON IT AAAAAAAAAAAAAAAAAAAAHHHHHHHH! Like this: Like Loading. Related.
Battery fuel gauges are the unsung hero of the battery world. There’s more to it than just measuring the voltage on the battery terminals. These little chips are microcontrollers (tiny computers, essentially) that sit inside the battery pack and keep tabs on the battery’s performance for the life of that battery pack. Texas Instruments makes battery fuel gauges that are small enough to fit in the circuitry of a cell phone, and one of the most common ones that uses this technology are i Phone batteries. These batteries use a single-wire interface called HDQ (which stands for High- Speed Data Queue). It may sound similar to Dallas Semiconductors’ 1- Wire protocol, but the two are completely different and incompatible with each other. Protocol details The HDQ protocol can be emulated with a serial port and a little bit of external circuitry. The protocol can be emulated with a serial port at 57600 baud with 8 data bits, no parity bit and 2 stop bits. Because this is a bi-directional bus, an open-drain configuration is needed. Most TTL serial ports are not open-drain, so some circuitry is required to do this. TI’s application note suggests using a CMOS inverter and an N-channel MOSFET along with a 1 k Ohm pull-up resistor, but this can be cut down with a 74 HC07 open-drain buffer and pull-up resistor. [ EDIT: June 13, 2015 – Corrected schematic] The HDQ protocol uses a short pulse to indicate a logic 1, with a longer pulse to indicate a logic 0. The data is sent LSB (least significant byte) first, with a 7-bit address and an eighth bit to indicate if the operation is a read or write (0 is read, 1 is write). If it is a read operation, the fuel gauge will respond with one byte of data. As you might think, this is a very slow means of communication; the typical bus speed is 5-7 kilobits per second, but the actual usable throughput will be less than this. The hack in this is that.
Download Now