Export data from Xively to CSV

I’ve been using Xively (back then it was Cosm) for my data logging Arduinos since 2012, so when they announced that “LogMeIn has made the decision to retire Xively Personal from its current line of products effective January 15, 2018 at 12:00PM ET“, I thought I’d better get my data out of there.

Unfortunately it doesn’t look like they have a tool/api that can export everything easily. They do however have an api call that’ll let you get 1000 entries in one go, so I hacked together a bash script that’ll get the data in 6 hour chunks and put them together in CSV files (Update: As Al from the comments noticed, the script only did half a days worth of data, its now updated to grap whole days! Thanks Al!):

# d = start date
# e = end date
# api = api key
# feed = feed id
# data = data stream
# name = filename for output
while [ "$d" != "$e" ]; do
echo "----- New day -----"
echo $d" - T00:00:00"
echo "http://api.xively.com/v2/feeds/"$feed"/datastreams/"$data".csv?key="$api"&start="$d"&duration=6hours&interval=1&limit=1000&interval_type=discrete"
wget "http://api.xively.com/v2/feeds/"$feed"/datastreams/"$data".csv?key="$api"&start="$d"&duration=6hours&interval=1&limit=1000&interval_type=discrete" -O - >> "$name".csv
echo " " >> "$name".csv
echo $d" - T06:00:00"
echo "http://api.xively.com/v2/feeds/"$feed"/datastreams/"$data".csv?key="$api"&start="$d"T06:00:00&duration=6hours&interval=1&limit=1000&interval_type=discrete"
wget "http://api.xively.com/v2/feeds/"$feed"/datastreams/"$data".csv?key="$api"&start="$d"T06:00:00&duration=6hours&interval=1&limit=1000&interval_type=discrete" -O - >> "$name".csv
echo $d" - T12:00:00"
echo "http://api.xively.com/v2/feeds/"$feed"/datastreams/"$data".csv?key="$api"&start="$d"T12:00:00&duration=6hours&interval=1&limit=1000&interval_type=discrete"
wget "http://api.xively.com/v2/feeds/"$feed"/datastreams/"$data".csv?key="$api"&start="$d"T12:00:00&duration=6hours&interval=1&limit=1000&interval_type=discrete" -O - >> "$name".csv
echo $d" - T18:00:00"
echo "http://api.xively.com/v2/feeds/"$feed"/datastreams/"$data".csv?key="$api"&start="$d"T18:00:00&duration=6hours&interval=1&limit=1000&interval_type=discrete"
wget "http://api.xively.com/v2/feeds/"$feed"/datastreams/"$data".csv?key="$api"&start="$d"T18:00:00&duration=6hours&interval=1&limit=1000&interval_type=discrete" -O - >> "$name".csv
d=$(date -I -d "$d + 1 day")

Now that you have the data in a CSV format you can open it directly in a spreadsheet like Excel, or you can import it to other databases!

DiggDeliciousGoogle BuzzSlashdotRedditShare
Posted in Linux | Tagged , , , , | 8 Comments

Alfa Romeo type numbers (codes)

Just a list of Alfa Romeo models with type numbers

Model Type Years Source
“Future Coupé and Spider” 963 ?? – ?? autoedizione
“Future SUV-C” 962 2017 – ?? autoedizione
“Future E segment” 961 ?? – ?? autoedizione
4C 960 2013 – ?? Wikipedia
MiTo 955 2008 – ?? Wikipedia
Giulia 952 2015 – ?? ANE
Stelvio “Future SUV-D” 949 2016 – ?? ANE
Giulietta 940 2010 – ?? Wikipedia
Brera & Brera Spider 939 2005 – 2010 Wikipedia
Alfa 159 939 2005 – 2011 Wikipedia
Alfa GT 937 2003 – 2013 Wikipedia
Alfa 147 937 2000 – 2010 Wikipedia
Alfa 166 936 1998 – 2007 Wikipedia
Alfa 156 932 1997 – 2007 Wikipedia
Alfa 146 930 1995 – 2000 Wikipedia
Alfa 145 930 1994 – 2000 Wikipedia
ARNA 920 1983 – 1987 Wikipedia
Spider 916 1995 – 2006 Wikipedia
GTV 916 1995 – 2005 Wikipedia
Alfa 33 (Series 2) 907 1990 – 1995 Wikipedia
Alfa 33 905 1983 – 1989 Wikipedia
Alfasud Giardinetta 904 Alfasud-Giardinetta
Alfasud Sprint 902 1976 – 1989 Tim Rauen
Alfasud 901 1971 – 1983 Tim Rauen
155 167 1992 – 1998 Wikipedia
164 164 1987 – 1998 Wikipedia
Alfa 90 162A 1984 – 1987 Wikipedia
Alfa 75 161 & 162B 1985 – 1992 Wikipedia
Alfa 6 119 1979 – 1986 Wikipedia
Giulietta 116 1977 – 1985 Wikipedia
+ GT, GTV & GTV6
116 1972 – 1987 Wikipedia
GT 1600 Junior Zagato 115.24 1972 – 1976 Wikipedia
GT 1600 Junior 115.03
From 1974 115.34
RHD 105.05
1972 – 1976 Wikipedia
Montreal 105.64 1970 – 1977 Wikipedia
1750 Berlina
+ 2000 Berlina
105 1967 – 1977 Wikipedia
Spider 105 & 115 1966 – 1993 Wikipedia
GT 1300 Junior Zagato 105.93 1969 – 1972 Wikipedia
GTA 1300 Junior 105.59 1968 – 1973 Wikipedia
1750 GT Veloce 105.44
RHD 105.45
USA 105.51
1967 – 1971 Wikipedia
Giulia Sprint GT Veloce 105.36
RHD 105.37
1965 – 1968 Wikipedia
GT 1300 Junior 105.30
RHD 105.31
1965 – 1967 Wikipedia
Giulia Sprint GTC 105.25RHD 105.29 1964 – 1966 Wikipedia
2000 GT Veloce 105.21
RHD 105.22
USA 115.01
1971 – 1976 Wikipedia
Giulia Sprint GT 105.02 1963 – 1966 Wikipedia
Giulia 105 1962 – 1978 Wikipedia
Giulietta 705 & 101 1954 – 1965 Wikipedia
SZ & RZ ES-30 1989 – 1991 (SZ)
1992 – 1994 (RZ)

Currently unknown: 8C Competizione & 8C Spider, but it might be 920 (like the ARNA(!)), judging by this ad for a 2009 ALFA ROMEO 8C COMPETIZIONE COUPÉ – Chassis no. ZAR92000000040895 Engine no. 1390.

DiggDeliciousGoogle BuzzSlashdotRedditShare
Posted in Auto, Road cars | Tagged , , , , , , , | Leave a comment

Electric Imp driving a small OLED display

Electric Imp driving an OLED display

Electric Imp driving an OLED display

I made some little functions for the Electric Imp to make it easier to drive a OLED display rom Digole (for example the 0.96″ Serial: UART/I2C/SPI 128×64 OLED Module Blue CN (DS12864OLED-2B), but they also come in other sizes and colours). They cost around $10, so it’s a pretty cheap display option that’s also easy to work with and looks nice. The display on the picture is a 1,3″ white OLED (DS12864OLED-3W).

The functions should be self explaining, eg. to draw a rectangle you use “LCDRect(x,y,width,height)” where x & y are the starting coordinates and width & height are the size of the figure. An example could be “LCDRect(5,40,100,10);“. They go in the “Device” tab in the Electric Imp environment.

But before you use the functions you need to setup the communication with the display like this:

hardware.uart12.configure(9600, 8, PARITY_NONE, 1, NO_RX);

Then the functions:

function LCDClear()

function LCDSetFont(fontnr)

function LCDWriteMessage(LCDMessage)
hardware.uart12.write(“TT” + LCDMessage);

function LCDNewLine()

function LCDRot(Rot)
hardware.uart12.write(“SD” + Rot);

function LCDRect(x,y,width,height)
x2 <- x + width;
y2 <- y + height;

function LCDRectFilled(x,y,width,height)
x2 <- x + width;
y2 <- y + height;

function LCDCircle(x,y,r,f)

DiggDeliciousGoogle BuzzSlashdotRedditShare
Posted in Electric Imp, Electronics | Tagged , , , | 4 Comments

Logging statistics from a power meter with an Arduino and a LDR

My electrical power meter has a pale yellow LED that flashes once for ever watt hour used. Inspired by power.labitat.dkjespereklund.blogspot.com/2011/10/elmaler-overvagning-med-arduino.html and other projects, I set out to count the flashes with an Arduino and output some nice graphs showing my electricity consumption.

Power Meter schematics (LDR Arduino)

Power Meter schematics (LDR Arduino)

I wanted to use an LDR (LDR’s on Amazon) to “see” the flashing LED on the power meter, but none of the example circuits I found online seemed to work. Well, they worked if I flashed a bright LED at them, but the LED on my power meter was apparently too weak. After some experimentation I came up with the curcuit on the right. It only uses the LDR two resistors (4.7 k Ohm and 10 k Ohm) and one transistor (547), you might have to vary the resistor values according to your LDR and light source.

This is the process from breadboard to reader mounted on the power meter:

  1. The reader part set up on the breadboard for testing
  2. The “rear” side of the reader PCB. The pins at the top are (left to right): 5v, Pin 2, Gnd.
  3. The “front” of the reader PCB with the LDR that’ll be positioned in front of the blinking LED on the power meter.
  4. The Arduino hanging below the Raspberry Pi (temporary setup). I made a quick “shield” for the Arduino with a cable running to the reader PCB.
  5. The reader PCB mounted (with tape) on the power meter.

I used the Arduino code from jespereklund.blogspot.com and modified it slightly, so that it outputs a slightly different string in the serial console, and so it outputs it once for every new blink, instead of on a fixed schedule. My version of the sketch is here: PowerMeter_nkh_20131006.rar

This is the output of the sketch:

Count= 1 | Error: 0 | wCur= 414.79 | wAvg= 414.79 |
Count= 2 | Error: 0 | wCur= 415.94 | wAvg= 415.37 |
Count= 3 | Error: 0 | wCur= 418.51 | wAvg= 416.41 |
Count= 4 | Error: 0 | wCur= 412.65 | wAvg= 415.46 |
Count= 5 | Error: 0 | wCur= 417.05 | wAvg= 415.78 |
Count= 6 | Error: 0 | wCur= 414.79 | wAvg= 415.62 |
Count= 7 | Error: 0 | wCur= 415.85 | wAvg= 415.65 |

Currently the Arduino UNO (Arduino Uno R3 on Amazon) is connected to a Raspberry Pi (Raspberry Pi on Amazon), and everything is set up a bit hackish… at some point I hope to move the setup to an Arduino Yún (Arduino Yun on Amazon), so the Raspberry Pi won’t be needed. Anyways, on te Raspberry Pi I first run a line of code that listens to the Arduino and then adds the output to a text file:

cat /dev/ttyACM0 >> poweroutput2.txt

Then I run a bash script that reads the last line of poweroutput2.txt and if it’s changed since the last read it’ll post the new values to Xively. This is powermeter.sh:

# Listens for new input from the Arduino then writes the results to a DB


while [ $i = 0 ]
count=`tail -n 2 poweroutput2.txt | awk ‘{print $2}’`
if [ "$count" != "$countold" ]; then
error=`tail -n 2 poweroutput2.txt | awk ‘{print $5}’`
wCur=`tail -n 2 poweroutput2.txt | awk ‘{print $8}’`
wAvg=`tail -n 2 poweroutput2.txt | awk ‘{print $11}’`

# Post result to xively
wget –no-check-certificate -O – –header=”X-Http-Method-Override:put” \
–post-data “wCur,$wCur
error,$error” \
–header “X-ApiKey: INSERT_YOUR_API_KEY” \
–verbose \


This will populate the database at Xively and you should (after a while) see a graph something like this:

Xively power meter example

Example from Xively. The peaks is an oven turning on and off

Voila, it works! :D

While trying to make this work, I’ve come across a number of websites that have been helpful and/or served as inspiration:

DiggDeliciousGoogle BuzzSlashdotRedditShare
Posted in Arduino, Electronics, Linux, Raspberry Pi | Tagged , , , , , , , , | 8 Comments

Dual booting Android (Jellybean) and Linux (Ubuntu) on the Asus Eee Pad Transformer (TF101)

These are my own notes, so I have a chance of remembering how to do this :)

First of all BACKUP EVERYTHING!!! I use Titanium Backup Pro (and buy the pro key), and backup everything to an miniSD card, that way the apps and userdata can be restored in the new android rom (even if it’s a diffirent rom).

Grap the latest version of Tubuntu from the thread “[Win32/64][Dual Boot][Mount-Loop] Tubuntu – 1 click installer SBK1 & SBK2! *2/1/2013*” on XDA forums.

Locate the “Prime ROM” on the same page and download it (rename it “system.img”).

Find and download the Linux image you want (on the same page I choose “Lubuntu v1.2 (12.10)”). Rename it “ubuntu.img”.

Download the linux kernel you wan to run, I’ve had success with “2.6.36 – [cpu 1.4 ghz] [gpu 300mhz]“. Rename it “linux.img”. (I don’t get wifi if I use the kernel that comes in the tubuntu package, therefore this is needed for me).

Put all the *.img files in /tubuntu/images/

Backup the tablet!

Start Tubuntu Put the tablet into APX mode (hold “vol up” + “power”), the red text in the upper right hand corner turns green.

Remember to select the correct SBK!.

When you’re raedy click “Flash” and sit back and wait. (THIS WILL ERASE EVERYTHING ON THE TABLET!)



Asus Eee Pad Transformer TF101

Asus TF101 flashing NVflash Tubuntu

When it’s done flashing, let it boot into the Android prime rom and finish the setup (it’s important to go through all the setup and reboot to android a couple of times, even if you’re going to install another rom in a minute).


When that’s done you can boot into Ubuntu (press “vol down” + “power”, then “vol up” when it askes you to), and set up Linux.

The first thing to do is to resize the linux partition (otherwise you’ll run out of space in about 30 seconds). Open a terminal and type:

sudo resize2fs /dev/mmcblk0p8

Now install the kernel supplements, go to the root in a terminal and run:

sudo wget http://novaspirit.com/tubuntu/kernel_sup.tar.gz /

sudo tar zxvf /kernel_sup.tar.gz

Reboot to linux a couple of times and make sure everything is working (it should be!).


Now we’re ready to deploy the Android ROM of choice. I choose the TeamEOS3 Jellybean ROM. Download the ROM and Gapps and put them on a miniSD card.

Connect the tablet to the computer again, fire up Tubuntu (select the correct SBK), put the tablet into APX mode. Go to the Advanced tab in Tubuntu and click to top flash button. This will flash a recovery image that can be used to change the android rom. When it’s done flashing but the tablet into recovery mode (“vol down” + “power”, then when it asks, “vol up”). Do a “Factory reset”, then install the TeamEOS3 ROM. Restart the tablet and run through the setup process in Android. Restart to Android a couple of times more to make sure everything is working, then go back to the recovery mode and install the Gapps. Start android once again and make sure everything is working correctly (including Gmail, Maps and so on, you may have to find them in the store though).

The final step is to connect the tablet to the computer in APX mode one last time and click “Flash” again in the Advanced tab in Tubuntu (if you’ve had it closed in between flashing the recovery image, the button will say “Reflash”). When it’s done you should have a tablet with both Android Jellybean and Ubuntu! :o )

DiggDeliciousGoogle BuzzSlashdotRedditShare
Posted in Android, Linux, Tablets | Tagged , , , , , , , , | 4 Comments

Logging system stats from NAS to Cosm.com

Cosm.com (formerly Pachube) is an online database that lets you store values and plot them over time. One use is to log system stats from a computer or NAS (in this case a Qnap 419p).

First setup an account on Cosm and add a new Feed, this will give you a feed id which you’ll use in your script. You’ll also need to create an API key.

Then create a script in the /home/ directory on your nas:

cd /home/
nano cosm_sysinfo.sh

Enter the following into the file (put your API key and Feed id in the script towards the end):

loadAvg5min=`cat /proc/loadavg | sed 's/\([0-9]*\.[0-9][0-9]\) \([0-9]*\.[0-9][0-9]\) \([0-9]*\.[0-9][0-9]\)\(.*\)/\1/'`
loadAvg10min=`cat /proc/loadavg | sed 's/\([0-9]*\.[0-9][0-9]\) \([0-9]*\.[0-9][0-9]\) \([0-9]*\.[0-9][0-9]\)\(.*\)/\2/'`
loadAvg15min=`cat /proc/loadavg | sed 's/\([0-9]*\.[0-9][0-9]\) \([0-9]*\.[0-9][0-9]\) \([0-9]*\.[0-9][0-9]\)\(.*\)/\3/'`

upDays=`uptime | cut -f 4 -d " "`
memFree=`free | grep Mem | awk '{print $4}'`
swapFree=`free | grep Swap | awk '{print $4}'`
processes=`ps aux | wc -l`
freeSpace=`df -m | grep /dev/md0 | awk '{print $4}'`
totalSpace=`df -m | grep /dev/md0 | awk '{print $2}'`
ptcSpace=`df -m | grep /dev/md0 | awk '{print $5}' | sed 's/%//'`
temp=`cat /proc/tsinfo/systemp`

hdd1temp=`/sbin/get_hd_temp 1`
hdd2temp=`/sbin/get_hd_temp 2`
hdd3temp=`/sbin/get_hd_temp 3`
hdd4temp=`/sbin/get_hd_temp 4`


wget -O - --header="X-Http-Method-Override:put" \
--post-data "updays,$upDays
hdd4temp,$hdd4temp" \
--header "X-ApiKey: YOU_API_KEY_HERE" \
--verbose \


Make the file executable:

chmod +x cosm_sysinfo.sh

And test the script by running it:


This should give you an output that looks something like this:

[/home] # ./cosm_sysinfo.sh
--2013-01-27 11:32:27-- http://api.cosm.com/v2/feeds/xxxxx.csv
Resolving api.cosm.com..., 2001:470:1f10:333::2
Connecting to api.cosm.com||:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1 [text/plain]
Saving to: `STDOUT'

100%[==============================================================================================================================>] 1 --.-K/s in 0s


2013-01-27 11:32:28 (34.5 KB/s) - `-' saved [1/1]

Now head over to cosm.com and look at your feed, it should now be populated with values. Of course, it’s not much fun if this isn’t getting updated regulary, so we’ll set up crontab to update the feed every 5 minutes:

nano /etc/config/crontab

Enter this entry somewhere in the file (this will run the script every 5 minues):

*/5 * * * * /home/cosm_sysinfo.sh

Save the file and load the changes:

crontab /etc/config/crontab

Then all we need to do is restart cron:

/etc/init.d/crond.sh restart

The NAS should now populate the cosm database every 5 minutes and after a while you’ll get something that looks like this:

DiggDeliciousGoogle BuzzSlashdotRedditShare
Posted in Linux, NAS | Tagged , , , , , , , | 1 Comment

Showing info on the Qnap NAS LCD

With inspiration from lcd_tool and lcdmond on 419P I thought I’d make a little script that shows the hard drive temperatures on the display on a Qnap NAS (in this case a 419p):

So, lets go to the home directory and create a file called ‘showonlcd.sh’:

cd /home
nano showonlcd.sh

Then enter the following into the file:

hdd1temp=`/sbin/get_hd_temp 1`
hdd2temp=`/sbin/get_hd_temp 2`
hdd3temp=`/sbin/get_hd_temp 3`
hdd4temp=`/sbin/get_hd_temp 4`

lcd_tool -1 "HDD1 $hdd1temp HDD2 $hdd2temp" -2 "HDD3 $hdd3temp HDD4 $hdd4temp"

To save the file in nano press [ctrl] + [o] and to exit nano press [ctrl] + [x].

Make the file executable:

chmod +x showonlcd.sh

Now we need to stop the LCD manager (as described in the link above):

/sbin/daemon_mgr lcdmond stop /sbin/lcdmond

And now we can run the script and enjoy seeing the individual hard drives temperature on the LCD:


DiggDeliciousGoogle BuzzSlashdotRedditShare
Posted in Linux, NAS | Tagged , , , , , , | 2 Comments

Alfa Romeo Giulia (2014) – News and rumors

The replacement for the Alfa Romeo 159 (which went out of production in 2011), has been on it’s way for years (on/off). Now that we’re getting closer to an actual car, I’ll start to collect the news and rumors here. The car has long been rumored to revive the name of the 60s and 70s Giulia, so I’ll continue to use it here.

DiggDeliciousGoogle BuzzSlashdotRedditShare
Posted in Auto, Road cars | Tagged , , , , , , | 1 Comment

New Alfa Spider – 2015 Duetto

Pininfarina 2uettottanta

Pininfarina 2uettottanta concept from 2010

Rumours (dreams?) of a Duetto inspired Alfa Spider has been around ever since the last type 105 Spider S4 rolled out of the factory in 1994. They had died out a bit, but after we’ve had the 4C concept presentation, the Spider guesses are starting once again. I’ll try to update this post as the news drops in…

[Update 2012-05-23] – Fiat and Mazda announce that they intent to build the next Alfa Spider and Mazda MX-5 (Miata) on the same platform. Hopefully the result will be better than the last time Alfa collaborated with a Japanese manufacture.

  • Alfa Spider 2015, photoshop from Car Magazine

    Alfa Spider 2015, photoshop from Car Magazine

    2012-08-10 Car Magazine - Alfa Romeo Spider and Mazda MX-5 (2015): the new sports cars revealed‘The study calls for both Mazda and Fiat to develop two differentiated, distinctly styled, iconic and brand-specific light weight, roadsters featuring rear-wheel drive,’ the companies have confirmed. ‘The Mazda and Alfa Romeo variants will each be powered by specific proprietary engines unique to each brand.

    ‘The project assumption is that both vehicles will be manufactured at Mazda’s Hiroshima, Japan, plant with production for Alfa Romeo envisaged starting in 2015.’

  • 2012-07-13 AutoEdizione - Next Alfa Romeo Spider will be named DuettoAccording to the American source Car&Driver the future Alfa Romeo Spider which is planned for 2015 will be named Duetto. So no additions, only the old nickname as the official name. The name Spider is maybe preserved for a larger model (6C Spider?). A very cautious conclusion that the stunning Duettotanta by Pininfarina (2010) was a sign for future products by Alfa Romeo.
  • 2012-05-30
    Alfa Spider - AutoExpress.co.uk photoshop

    Alfa Spider - AutoExpress.co.uk photoshop

    Alfa Spider - AutoExpress.co.uk photoshop

    Alfa Spider - AutoExpress.co.uk photoshop

    AutoExpress.co.uk - New Alfa Romeo SpiderThe rear-drive chassis will be incredibly light, making use of Mazda’s advanced SKYACTIV technology, so expect the Spider to weigh less than 1,000kg. And the front-mounted engine will be positioned as close to the centre of the car as possible to ensure great handling.
    Thanks to that low weight, the Spider won’t need a huge engine, and in keeping with the back-to-basics philosophy of the MX-5, the car is expected to feature a 1.4-litre four-cylinder turbo, with power ranging from 135bhp to 175bhp.
    However, it’s possible that any high-performance Cloverleaf version would have the upcoming 4C coupé’s 1.75-litre turbo, with well over 230bhp.
    There’s no word on cost just yet, but the Alfa Spider is expected to sit slightly above the new MX-5, with a starting price of around £20,000. A soft-top and folding hard-top are likely to be available. Production of the new sports car will start in 2015.

  • 2012-05-29 AutomotiveNewsEurope - An Alfa built in Japan is not such a bad thing
  • 2012-05-28 AutomotiveNewsEurope - Alfa adds rwd roadster from Japan to U.S. lineup for 2015Alfa and Mazda will co-develop the lightweight chassis for the two roadsters. Each brand will get its own styling and engines.
  • 2012-05-23 CarMagazine.co.uk - Alfa Romeo roadster to be twinned with Mazda MX-5
  • 2012-05-23 TopGear.com – Alfa and Mazda to build new roadsterThe two companies announced the co-operation this morning. They even announced that they expect to get the Alfa into production in 2015, in Mazda’s own factory”
    • high-tech 1.8-litre engine, which will also power the mid-engined 4C
  • 2012-05-23 AutomotiveNewsEurope - With Mazda, Alfa may have the right partner for a Spider revival
    • Luca Ciferri: “The agreement to use the MX-5 underpinnings is nothing new. In 2008, Alfa’s CEO at the time, Luca De Meo, first suggested the idea, but when Fiat entered into a strategic alliance with Chrysler in 2010, the plan changed. That same year, Alfa said it was planning to launch a new Spider in 2013, possibly co-developed with Chrysler and built in the United States or Canada. In 2011, Alfa CEO Harald Wester announced the model would be delayed by a year, without clarifying who the partner would be. I really hope that the announcement by Fiat and Mazda is the final decision on the future of the Alfa Spider. While a 2015 launch date is not exactly tomorrow, it is better than nothing.”
  • 2012-05-23 AutomotiveNewsEurope – Fiat and Mazda plan to jointly develop roadster based on next MX-5
    2010 Mazda MX-5

    2010 Mazda MX-5

    • Joint developed with Mazda (next MX-5 platform)
    • Launch 2015 (globally)
    • Production at Mazda’s factory in Hiroshima
    • Engineers from both companies are studying how to cooperate on a joint vehicle that will be an “iconic,” lightweight, rear-drive roadster with differentiated design and identity for each brand, a joint statement said. The car would be based on MX-5 architecture.
  • 2012-05-23 Alfa Romeo press release - Fiat and Mazda announce co-operation program
    • “Fiat Group Automobiles  S.p.A. (Fiat) and Mazda Motor Corporation (Mazda) have signed a non-binding Memorandum of Understanding (MoU) for the development and manufacturing of a new roadster for the Mazda and Alfa Romeo marques based on Mazda’s next-generation MX-5 rear-wheel-drive architecture.”
    • “The Final Agreement is expected be signed in the second-half of 2012.”

  • Pre Mazda announcement rumors:
  • 2012-01-09 Auto Edizione – Alfa Romeo plans 6C for 2014 together with Dodge:
    • Name: 6C - plausible
    • Engine: straight six cylinder - doubtful! a V6 is must more likely
    • Drive train: rear-wheel driven shared with Dodge - plausible

    They also go on to talk about a possible collaboration for the next Dodge Viper and a successor to the 8C Competizione

  • 2011-11-14 AutoExpress.co.uk – New Alfa to target MX-5
    Speculation of a Duetto (105) inspired new Alfa Spider, which is suppose to compete with the Mazda MX-5. Key figures are: £25.000, 150 HP (from a detuned 1750 TBI??, why not the 1.4 MultiAir?), 1000 kg, 2013.
DiggDeliciousGoogle BuzzSlashdotRedditShare
Posted in Auto, Road cars | Tagged , , , , , , , , , , | 1 Comment

Alfa Romeo 4C – The production version

Similar to how we followed the 4C concept rumors, I’ll here try to follow the rumors surrounding the production version of the Alfa 4C.

DiggDeliciousGoogle BuzzSlashdotRedditShare
Posted in Auto, Road cars | Tagged , , , , , , , , | 2 Comments