Hi there !
This projet is awesome ! Quite a challenge to fit different components in such a small space.
Do you have any PCB left by any chance ? If so I'd like to buy one from you.
I recently sold the last PCBs of the initial order. Since there seems to be a steady demand, I'm considering ordering a second batch in the near future. Stay tuned!
I think I got a spare pcb left. Some parts as well iirc (mcu, ir receiver, ...). I will check this evening.
PM if you're interested.
Any update on new PCB's been dying to get one of these working
oi me too. would definitely get one or two if you do a second run!
Hi everyone,
I am wondering whether it is feasible to add a calculator to this using morse code input, identifying some syntax for special functions and control characters. Several problems:
- Polling for and decoding morse code could be expensive in terms of power
- Pushing buttons is tiresome
- To avoid having to push buttons, squeezing in a capsense would be difficult and would take up even more power
Does anyone more knowledgeable than I have ideas on this? Thanks
Alright well here's an initial interface idea that doesn't involve complicated timing.
- When you enter the watch app, there's an empty buffer of 6 chars into which you will type in DOTs and DASHs.
- Bottom right button = DASH, top left button = DOT
- As you type in DOTs, DASHs, the (stripes,bell,PM,24h,lap, backwards6) indicator lights come on, indicating how much of the buffer is filled.
- As you type, one of the top-row segment displays shows the alphanumeric the buffer represents in morse code right now.
- Once you've typed the char you want into the buffer, hit the Bottom Left button and the alphanumeric goes into the calculator stdin.
- If you screw up typing the DOTs and DASHs for the alphanumeric you want, fill the rest of the buffer up to 6 chars and the next char goes into the start of a totally reset buffer.
So all that's left is to just come up with a good alphanumeric syntax for calculator stdin. Special character sequences are needed for:
- execute current stdin
- scroll the previous stdout in the main display
- scroll the current stdin in the main display
- delete
- push to register
- pull from register
- pull previous stdout
- sin, cos, exp, ln, erf, Gamma, pi
Great to see people using pluto as a platform to implement the features they need on a watch. I've had this idea on my mind as well, but dismissed it as not useful enough / too fiddly too operate. If you're looking for a more practical watch to implement a calculator on, maybe Travis Goodspeed's goodwatch
https://github.com/travisgoodspeed/goodwatch is the thing for you.
Great to see people using pluto as a platform to implement the features they need on a watch. I've had this idea on my mind as well, but dismissed it as not useful enough / too fiddly too operate. If you're looking for a more practical watch to implement a calculator on, maybe Travis Goodspeed's goodwatch https://github.com/travisgoodspeed/goodwatch is the thing for you.
Going to make one of those next.
Do you (or does anyone else) have any left over PCBs I can buy or should I order my own?
Thanks
Alright, I've done a few things on my branches:
- Made a new board layout that replaces the now-obsolete MAG3110 magnetometer with a LIS3MDL. New layout is probably terrible for reasons over my head, it's the first time I've ever opened a board editor.
- Updated the target HAL for the LIS3MDL.
We'll see if any of this works when the board and parts come...
Boards just came today from elecrow. The yellow looks pretty cool IMO.
Should have time to solder them up this weekend.
I might also write a metronome app, it might actually be useful.
Very cool project!
Does anyone have extra PCBs you'd be willing to part with?
Hi, I've got all the components soldered onto the board and I believe it is ready to program, but when I plug my Launchpad into the computer and hook up "GND" and "VCC" to their respective pads on the target board, the LED on the Lauchpad turns off as though something is shorted.
Is there any reason this could be happening other than bad soldering/fried MCU?
Very cool project!
Does anyone have extra PCBs you'd be willing to part with?
I've just received 5 PCBs and obviously don't need them all, if you're still keen?
when I plug my Launchpad into the computer and hook up "GND" and "VCC" to their respective pads on the target board, the LED on the Lauchpad turns off as though something is shorted.
Well, is something shorted?
There was an issue with my launchpad or soldering I think. Fixed.
The calculator works now!!! Extremely pleased!
A few notes/questions
- I don't have any extra PCB's sorry, plus you probably don't want my version of the board since it uses a weird magnetometer component without exposed leads.
- Had an annoying time writing the dumb elf to the device. Finally managed to flash the MSP430FR6972 using the 4 connections necessary for 2Wire SBW onto a TI Launchpad. I used mspdebug's RF2500 driver but it didn't recognize the uc, so I wrote to it using a similar looking device `mspdebug rf2500 --fet-force-id MSP430FR5969'
- Is there any way short of a reflash to show in 12hr AM/PM instead of 24H? Also turning off the blinking colon?
- Magnetometer doesn't work, just displays 16 always. Either a bug in my firmware or bad soldering, either is possible. I really should have chosen a component that had exposed leads ... next time
- Buzzer doesn't make sound, even though it appears to be enabled in conf, and the component is in good shape (took it off a new f91w). Does that component have polarity? Could something be shorted?
Is there any way short of a reflash to show in 12hr AM/PM instead of 24H? Also turning off the blinking colon?
Nope, but it should be pretty easy to add a setting that at least displays the time in 12h format. Alarms aren't worth the trouble IMO.
Buzzer doesn't make sound, even though it appears to be enabled in conf, and the component is in good shape (took it off a new f91w). Does that component have polarity? Could something be shorted?
Check the waveform at the spring connecting to the piezo disc in the back. You should see voltage spikes up to 20...50V.
Hi there,
I think I have correctly soldered up a PCB and am now trying to program it. I'm trying to load just a simple LED blink program from code composer studio but the debugger comes up with an error saying it can't find the device. Am I right in saying I only need VCC, GND, TEST (P3) and RST (P4)? Also am I missing something obvious like first burning a bootloader?
Luke
Hi there,
I think I have correctly soldered up a PCB and am now trying to program it. I'm trying to load just a simple LED blink program from code composer studio but the debugger comes up with an error saying it can't find the device. Am I right in saying I only need VCC, GND, TEST (P3) and RST (P4)? Also am I missing something obvious like first burning a bootloader?
Luke
I programmed mine with those 4 pins through a launchpad. I programmed the target controller as it arrived, no extra steps needed. I never got the flasher to use the TI driver successfully. I think this was some issue with my laptop's operating system. See my previous post for what I did instead.
So switched to a Linux machine and am having some msp430-gcc issues....it can't find libraries like unistd.h or time.h when running the Makefile. I originally changed the Makefile to use the none elf versions of gcc, objcopy, gdb and size, so - msp430-gcc rather than msp430-elf-gcc as this is what I managed to install, but I guess I'm missing the step which tells msp430-gcc where to look for libraries? Can't find out how to do this though....any ideas?
Many thanks
Luke
I actually did get it from there! I think maybe its now the "msp430-gcc" toolchain rather than the msp430-elf-gcc toolchain. The following is in the README shell script for installation from source on that TI website:
# This directory contains the sources for gcc, newlib, binutils, and gdb used
# to build the "msp430-gcc" binary toolchain packages distributed by TI.
When I remove the "-elf" from the commands in your Makefile, the errors disappear apart from those about missing header files. I think I just need to work out how or where the msp430-gcc looks for include files.
Did you ever get it to work LukeB101?
