mpymike

There is MPY which is very easy to use (he says shamelessly), it uses a subset of Python to program a Launchpad. Or there is the Micro Python board which runs a full implementation of Python. http://micropython.org/ Python is now the most popular introductory language.

Hi, The Console window is the bottom window of the mpyEditor it has a tab label of 'Mpy'. You should see

Hi, There is no specific library for SPI or NRF24l01. The only support for serial devices is the interrupt_setup() command (see here) This sets up the uart on the msp430 to receive data on pin P1.1 at 9600 baud. For the time being you would need to write your own driver.

For me the motivation for using Python is that it is an easier language to introduce to kids. A full Python implementation is a higher level more sophisticated language, has higher level constructs, more abstraction is possible, more compact code, easier to understand, easier to maintain, faster development time. (ie the usual arguments between language benefits) I would not claim that the Python implementation would be any more efficient, in memory or performance. Looked at Lua some time back, I like the language a lot, and probably a better language for a uC than Python but for

Thanks t0mpr1c3, interesting reading, I shall keep an eye on how uJava progresses. First thoughts, the memory footprint does look smaller than MicroPython, which could be due to many reasons. My original motivation for using the 430 Launchpads: 1) The price - when it was $4.30 2) Simple architecture that is easy to understand and explain. 3) DIL component that can be plugged into a breadboard, making it more useful for building electronic projects. Now however the ARM products are ubiquitous... Anyone know of a standalone ARM uC in a DIL package?

@@t0mpr1c3 I think it depends on the size of the bytecode VM. As I remember, Forth is fairly simple and can fit onto a small uC. But I wasn't aware of any Java VM that can fit onto a small uC. If anyone knows of one I'd like to look at it. May even be suitable forJython. (which is Python running on a Java VM) @@rockets4kids The source is not released yet, but from his kickstarter page he describes it as: Micro Python has the following features: Full implementation of the Python 3 grammar (but not yet all of Python's standard libraries). Implements a lexer, parser, compiler, virtua

MicroPython is a pretty full python implementation of the language. Setting aside the large memory footprint overhead, the main issue will be that it will lack all the libraries and especially the hardware libraries (at least initially) It will have a long way to go to catchup with the extensive Arduino/Energia selection. IMO describing Python as a scripting language is a bit meaningless. More relevant is the fact that most python implementations including MicroPython are byte code interpreted. The virtual machine is running on the microcontroller. That must account for a hefty

I had to go for it! I signed up for one of the MicroPython boards. Really like the small breadboard friendly footprint and SD socket. For me the beauty of Python is that it is compact, readable, intuitive, and easy to learn. There are free libraries for just about everything. IMO using python is the quickest way of developing software. So porting it to microcontrollers is the holy grail. It is a shame that Python requires such a large memory footprint to run, putting it out of reach for the modest msp430s. With the MicroPython project the author has completely rewritten Pytho

No, at the moment mpy is for MSP430 only

Thankyou everyone! I had a whole lot of fun doing this project. Halloween evening started out really well, I also brought out the mpy creeper and zombie models and programmed up some other Launchpads with flashing led displays. There was a lot going on. However my poor ghost was so busy shuddering and rushing up and down the garden that by about 8:00pm the motor started straining for some reason, and then the string snapped :crazy: I think part of the problem was the ultrasonic detector started triggering sporadically. So at the end it was triggering and constantly on the g

MPY Halloween Ghost Project This project is a scary ghost for halloween. It is setup in the front garden to scare away the hordes of trick-or-treaters. When a passing trick-or-treater approaches the ghost will scream and move back and forth along side the garden path. Go to the projects page for more details http://forum.43oh.com/topic/4524-mpy-halloween-ghost-project/ Also see the video: http://youtu.be/80EAMJM0L7k

MPY Halloween Ghost Project This project is a scary ghost for halloween. It is setup in the front garden to scare away the hordes of trick-or-treaters. When a passing trick-or-treater approaches the ghost will scream and move back and forth along side the garden path. It uses two MSP430s, One for the Ghost to detect passing trick-or-treaters and a second MSP430 to pull the Ghost on a loop of string. See it in action in the video. The Ghost The msp430 in the ghost is mounted onto a breadboard with a battery pack stuck to the back. An HC-SR04 ultrasonic detector is used to de

@b# I'm ok, I have Launchpads coming out of my ears!

Yeah Its a ghost suspended on a loop of string running from front gate to front door. Launchpad #1 mounted in the ghost detects trick-or-treaters (ping detector) Flashes LEDs, screams through a speaker, sends signal (RF Tx module) Launchpad #2 receives signal (RF Rx module) and switches on the motor which pulls the ghost on the string towards the front door along side the trick-or-treaters They freak out and run away never to be seen again. Still waiting for my rf modules from elecrow.com though

Sounds fun! I might have a go. If I can find the time that is.

Coil design for metal detectors is a big subject. As you say there are lots of designs. I came across this site for some general guidelines on coil size vs detection http://www.lammertbies.nl/electronics/PI_metal_detector.html He describes coils for Pulse Induction type of detector but I think it applies equally to all detectors.

A planar inductor with the same number of turns is about half the Inductance http://www.66pacific.com/calculators/coil_calc.aspx I was aiming for the maximum air-wound inductance to give maximum sensitivity to nearby metal objects. That's how conventional metal detector coils seem to be designed.

I played around with the response time and the min sensor frequency settings but neither helped very much. All my testing was indoors so I was surrounded by 60Hz mains interference, and I made no attempt to shield the coil. The datasheet doesn't explain in detail how the Proximity value is calculated, but I suspect that the loop gain of the oscillator is controlled by the Rp_min and Rp_max register values. My guess is that during operation the loop gain is alternately set by the Rp_min and Rp_max values. When the LC tank is driven with Rp_min the amplitude of oscillation will grow

Here are some piccies that mysteriously got dropped from my previous post. The EVM split with 0.1" header pins added. (Attaching the header on the contoller part was quite a pain as the pads lifted and the tracks joining the pads broke. But I managed to repair it.) The large 50 turn 930uH coil

Got my EVM and spent yesterday winding a coil and playing around with it. On the whole this is a great little peripheral and very suitable for close proximity detection. but as a metal detector it suffers too much from pickup and interference First I split the EVM into controller, LDC1000 and coil adding 0.1" header connectors. The controller to LDC1000 needed a 5x2 header which made it unfriendly for direct plugging into a breadboard. I then wound a 15cm coil suitable for a metal detector, 50 turns of 26awg magnet wire wound on the bottom of a plastic bottle. I measured

@hilpka, Nice write up. I'm still waiting for mine. I assume you used the inductor on the EVM which is rather small for metal detector use. The detector distance is going to be related to the size of the coil. Large diameter and High-Q is probably what is needed.

Yes a boosterpack would be great. Upon closer inspection the MSP430F5528 on the dev board is not easily programmable, none of the jtag/sbw pins are hooked up.

I like this inductance sensor a lot. A really sensitive metal detector springs to mind (mpy powered of course) But I see the dev board is $30, if it were sub $10 then it would be a game changer!

To elaborate on MPY a little if I may MPY is an ultra easy to use language for microcontrollers based on a subset of Python. It is aimed at simple projects using the MSP430 Launchpads. The syntax is very clean and simple. I claim that programs written in MPY are more compact and easier to write than the Arduino style C programs written using sketch/wiring. Its currently limited to integer variables but there is a full range of hardware functions to control the main peripherals: IOs, ADC, Interrupts, Timers, PWM, Print. Plus there is full access to the MSP430 named Registers

Sorry, only the MSP430 chips supplied with the Launchpad are currently supported by the mpyEditor. I'll take a closer look at the code to see if there is a workaround to allow the other chips to be used.