greeeg

@@spirilis, True, I think for "Made in Australia" the last major manufacturing step must occur within Australia. So PCBs/ICs from USA/China/Korea are fine, so long as your PCBs are assembled in Australia. In fact just assembling Chinese Assembled PCBAs into enclosures probably counts as a major assembly step.

I'd never heard of ToF arrays. Really interesting way to create a 3d camera. Here's the application diagram from the datasheet.

Nice! the white PCBs are a good choice. Are you still planning to use a diffuser over the PCB? Those LEDs look very bright to me. (maybe that's just the camera) I'm curious about the "Made in Canada" given that you mentioned the PCBs were made in Korea.

The problem is in the FAT implementation. 4Gb is the limit of 32 bit memory addresses. It's been alittle while since I played with FAT stuff. But I'm pretty sure that's what you're hitting here.

I believe that the BSL ROM pre-dates the USCI module. It seems to use the TA capture compare pins. So changing to the USCI would take extra effort, and possible break backwards compatibility. But I do understand your frustration.

Wow that does look really cool. Simple too. If this were made with MSP, you could use a CC430

I was going to give PCBway a shot too, but smart-prototyping turned out to be cheaper. and they'll do the metal stencils too (saves shipping) Alot of services are cheaper than others for particular projects. In my experience PCBs from: Seeedstudio, Itead, elecrow, smartprototyping, dirtyPCBs are all exactly the same quality. Not surprising since they probably all end up at the same fabs in china anyway.... Your PCBs are looking great @@zeke. I think I could have a few uses for the Thermocouple board, primarily for my reflow oven...

My setup is still very simple. A small vacuum pump from ebay, a pack of glue dispensing syringe tips, and some PVC tubing. It's not perfect by any means, but the whole thing only cost $20 or so. I'm planning to improve on it when I find some time.

I find mine is quicker than my particular toaster oven was. and I set and forget mine. The profile I have runs for 7 Minutes. My workflow goes like this: Apply Solder paste to 4 PCBs PnP components for 1 PCB (manually with vacuum pickup tool, and tape laid out flat) Place PCB in Oven, run cycle Continue to (2) if more PCBs remaining. The vacuum pickup tool has halved my manual placement time. Highly recommend over tweezers. Note the temperature of IR heating elements isn't ideal for PCB reflow*. Because it's Radiation heating vs Convection heating. The thermocouples generally d

Nice addition! I've got the same one. Just for fun one weekend long ago I decided to load up the custom firmware available for it. https://github.com/UnifiedEngineering/T-962-improvements/wiki It makes the UI a bit nicer, and add some extra settings. If it's working well for you now, there might be no need.

This is actually what my system needs to do! Yeah, it's alittle overwhelming, the datasheet does a pretty decent job I thought of showing the module configuration steps. It's true it's not baked into the timer module like the MSP, but in some ways it makes it much more flexible. not only with which pins can cause a timer capture (all of them!) but other perhepials could too, like a UART receive or DMA transfer. I still love the MSP, but these ATMEL parts just fit the needs of this particular project better.

A project for work had me looking for more power than the current AVRs could offer. (actually newer AVRs contain the event system too, which is cool) So I've been digging deep into the SAMD20/D21 lineup. If you know what you're doing, you can configure things at a register level if you want. In fact sometimes API's don't let you do everything a peripheral might have to offer. The Event system is actually one of the reasons this MCU will fit so well with my current project. I've only just started the system design, and have just finished routing a PCB. So I'm not deep into the programmi

The G2553 has a ROM based BSL. (Boot Strap Loader, essentially a bootloader). By default that's the only way to re-program the device without using an external programmer. It should be noted that the BSL doesn't use USCI_A0 hardware, alas unfortunately does share a pin. P1.1 and P1.5 are used for TX and RX. As @@roadrunner84 mentioned, you have the freedom to 'roll your own'. Since all the 'G' series enable the CPU to erase and program internal FLASH. You can find guide for writing bootloaders out there, unfortunately it's generally a very application specific and is tailored to your hard

Realized I haven't done much work on these for alittle while. It's very close to a working product, so yesterday I devoted to push it over the line. Dissembling a my first battery allowed me to clone the wire lengths, a small amount of kapton is used to insulate the terminals and PCB A snug fit. If another version is to be made I think I'd make some small alterations to the PCB shape. Grey unit, showing the LED windows and custom molded button. I'm bad at performing regular commits. I'm trying to improve this. I hadn't even committed the final PCB layout, even though I or

Back in 2013 TI announced they would be releasing the G2744 in PDIP 40 package. http://43oh.com/2013/03/ti-announces-bigger-and-better-value-line-msp430-controllers/ But later they removed that option and never distributed them. It appears that only Olimex have them. Which makes it very difficult to justify IMO. It basically means, for every project you can't just by a single IC, you would need to buy the whole dev-board from Olimex. It is unclear if Olimex is just sitting on stack now, or if TI actually still make the PDIP chips for them.

Good solution. The larger msp chips feature a flag to move interrupt vectors into the top of RAM. This is used for the same purpose. But removes a few cycles of overhead.

Just yesterday I was battling with a atmega328pb (more internal peripherals than standard atmega328p). Specifically I wanted to use the UART1 port to receive data from a GPS. My old setup uses a software serial implementation. After a whole day of debugging this second port not working. I'd concluded UART0 TX and RX worked fine. UART1 TX worked fine, but no RX. My scope was showing the serial stream from the GPS. All the pins were correct. Turns out the AVR wasn't registering the HIGH level from the GPS (3v) as HIGH because it's running from 5v. /facepalm Didn't even consider it a fac

Too much effort/not funny for a April fools joke. Interesting that the schematics are date 11 Mar. (for rev 1.1) That's a pretty impressive turn around time. It's interesting they have the SD card connected directly to the voltage rail of the super cap. Some SD cards I've tested use in excess of 20mA when writing. Most are in the 2-5mA range, but that's still a significant draw. Probably can't be using SD and the supercap in the same application.

Frankly I would recommend designing circuits so that no matter the state of IO line nothing will be destroyed/damaged. This is usually pretty easy with digital electronics.

Havent had too much time to polish off the software side. But I've been thinking about adding a bootloader to the project. Now I know that the MSP430F55xx series includes a DFU style BSL. But since my application already exposes as a MSC what if a new firmware could be drag and dropped into tho drive? (Because windows is actually handling the FAT stuff at this stage it's difficult/impossible to determine if a fimware file has been loaded on the SD.) Upon unplugging of the drive or maybe just 'Ejecting" it, the MSP will look for the new fw. Possibly do a CRC/other check to see if it'

It should work fine. The fact that you can program the chip suggests that it may be a problem with the code energia is producing. I'm thinking that some energia libraries may be reliant on the 32khz crystal being present. (it is on the launchpad) It may be stuck in initialization code trying to get that started... If code is working fine in CCS, it might be easier to just use that. Maybe some energia users can provide more insightful info.

Hey @@tonyp12 I love seeing people implement multi-tasking things. Many full implementations of RTOS's include so many extra things that it becomes difficult to actually see the the implementation of the task switching itself. Nice simple elegant approach. I like it.

Thanks! This one isn't a code, so it will likely be disabled after today. Worked for me in AUS. (which funnily enough Pi day was yesterday for us. Also, aside. 3/14/16 [3.1416] is actually closer to the real value of pi than last year [3.1415])

Wow this is really cool. I'd never heard of txtzyme before. What extra commands have you added in your version? I skimmed the code and I see [] Conditional branches !@ store and fetch Logical operators along with alot more IO stuff, analog/digital My first micro controller experience was the PICAXE platform. and it was developed in a similar way. You would write BASIC code. it was 'compiled' into something like this (maybe less human readable) and loaded into the PIC's EEPROM via a UART connection. It was then run by an interpreter which was actually the code inside the PIC's memory

I've been around on the forums for awhile now. I really enjoy seeing other peoples projects. Especially how they go about solving problems that I would hove done differently. I think there is great value in that. That's why I try to post about my projects too. I'm in my final year of my EE degree. And information I've gained from this forum has definitely influenced my thought pattern for the better when approaching new problems. But also unfortunately there are people who upon seeing the same project will just be thinking of ways they could profit from others work. There might not act