[StefVan]

I heard quite a lot about the Kiwi Wifi diagnostic interface, so I had to try it out on my car .

Honestly, I wasn’t expecting too much from this interface but surprisingly, I found this product rather good and it was giving some essential data of the F430.



This interface connects directly on the OBD connector and uses a wireless 802.11 WIFI network to exchange data with an IPhone or IPad. The device has a small switch to turn the Kiwi on/off. As the OBD connector has a Vbatt +12V (permanently powered), this small power switch can be useful if you want to leave the Kiwi interface connected.

The only other notable features of the interface are a red light indicating the device power state and a green “LINK” light that indicates an iPhone/iPod connection is present.




To complete the setup, you need go to "Settings" on your iPod or iPhone device. A new wireless host named “PLXDevices” will be displayed. Connect to that device and in the “Static”section, enter the IP address 192.168.0.11 and the subnet mask of 255.255.255.0.




Kiwi Wifi Specifications:

SSID: PLXDevices
IP: 192.168.0.10
Subnet: 255.255.255.0
Port: 35000
Range: 50 ft (line of sight)
Antenna: Internal
Power Consumption: 0.7 Watts
Wifi Standard: 802.11a/b/g
Operating Temp: -15 to 100° C
Dimensions: 2.75x1.25x0.6 Inches


The Kiwi interface is supported by several applications from the iTunes store. I’ve tested the main applications : Dash Command, Rev and FuzzyCar. All were able to connect to the Kiwi interface. I preferred Dash Command from Palmer Performance. It is based on the DashXL platform and supports all OBD-II protocols: SAE-J1850 (PWM and VPW), ISO-9141, ISO-14230 (KWP2000), and ISO-15765 (CAN).





Dash Command Features:

• Full support for OBD-II diagnostics
• Find out why your check-engine light is on
• Read and clear diagnostics trouble codes (DTCs)
• Supports over 220 OBD-II parameters
• Display sensor data directly from the factory computer in your vehicle
• Record and playback log files showing OBD-II data and also skidpad/race track data simultaneously
• Vehicle manager helps you keep track of different vehicles and log files automatically

Grace to the DashXL platform, you can download for free some other existing gauges from http://www.dashxl.net/. If you feel so, you can even create your own gauges or dashboards with the free DashXL Skin Editor : http://www.palmerperformance.com/products/skinxl/


For those who wants to dig deeper in this system, don’t miss this document : http://www.palmerperformance.com/download/CALC_PID_Reference.pdf

User manuals can be found here :
DashCommand_Quick_Start_Guide.pdf
DashCommand_WiFi_Setup_Guide.pdf
DashCommand_User_Manual.pdf


Dash Command has also a very good Data Logging system. You can send your logged data by email to your PC and use the free PLX Logger software to upload the log file and analyse the data. PLX logger 3.0 can be found here : http://www.plxdevices.com/support/software/logger3_0.html


Now back to the F430. I put together a list of all the supported PID’s. Despite the announcement of the 260 supported PID’s, a generic OBD tool like the Kiwi will support only a limited number of them on the F430.


SAE.MIL : Malfunction Indicator Lamp Status
SAE.DTC_CNT : Number of emission-related DTC’s stored in this ECU
SAE.MIL_DIST : Distance travelled while MIL is activated
SAE.MIS_SUP : Misfire monitoring support
SAE.FUEL_SUP : Fuel system monitoring support
SAE.CCM_SUP : Comprehensive component monitoring support
SAE.MIS_RDY : Misfire monitoring status
SAE.FUEL_RDY : Fuel system monitoring status
SAE.CCM_RDY : Comprehensive component monitoring status
SAE.CAT_SUP : Catalyst monitoring support
SAE.HCAT_SUP : Heated catalyst monitoring support
SAE.EVAP_SUP : Evaporative system monitoring support
SAE.AIR_SUP : Secondary air system monitoring support
SAE.ACRF_SUP : A/C system refrigerant monitoring support
SAE.O2S_SUP : Oxygen sensor monitoring support
SAE.HTR_SUP : Oxygen sensor heater monitoring support
SAE.EGR_SUP : EGR system monitoring support
SAE.CAT_RDY : Catalyst monitoring status
SAE.O2S_RDY : Oxygen sensor monitoring status
SAE.HTR_RDY : Oxygen sensor heater monitoring status
SAE.OBDSUP : On board diagnostic system type
SAE.CIM_SUP : Compression ignition monitoring supported
SAE.FUELSYS1: Fuel system 1 status
SAE:FUELSYS2 : Fuel system 2 status
SAE.SHRTFT1 : Short term fuel trim – Bank 1
SAE.SHRTFT3 : Short term fuel trim – Bank 3
SAE.LONGFT1 : Long term fuel trim – Bank 1
SAE.LONGFT3 : Long term fuel trim – Bank 3
SAE.LOAD_PCT : Calculated load value
SAE.TP : Absolute throttle position
SAE.ECT : Engine coolant temperature
SAE.IAT : Intake air temperature
SAE.MAF : Air flow rate from MAF sensor
SAE.RMP : Engine rpm
SAE.VSS : Vehicle speed sensor
SAE.SPARKADV : Ignition timing advance for Cylinder 1
SAE.O2SLOC11 : Oxygen sensor location bank 1 – sensor 1
SAE.O2SLOC12 : Oxygen sensor location bank 1 – sensor 2
SAE.O2SLOC13 : Oxygen sensor location bank 1 – sensor 3
SAE.O2SLOC14 : Oxygen sensor location bank 1 – sensor 4
SAE.O2SLOC21 : Oxygen sensor location bank 2 – sensor 1
SAE.O2SLOC22 : Oxygen sensor location bank 2 – sensor 2
SAE.O2SLOC23 : Oxygen sensor location bank 2 – sensor 3
SAE.O2SLOC24 : Oxygen sensor location bank 2 – sensor 4
SAE.O2S12.O2SV : Oxygen sensor voltage bank 1 – sensor 2
SAE.WO2S11_B.LAMBDA : Oxygen sensor wideband bank 1 – sensor 1 equivalence ratio lambda
SAE.WO2S11_B.O2SC : Oxygen sensor widebank bank 1 – sensor 1 current mA
Vehicle.Voltage : Vehicle voltage



Conclusion:
I found this tool quite interesting to visualise or log some OBD data from the F430 but also to manage better the situation when you have a CEL somewhere far away from home. Without needing a laptop, just with your iPhone, you can find out immediately the reason why you have a CEL and evaluate how serious it is. Don't forget to download the error codes pdf file on your iPhone to find out more about the DTC error code you may have. (F430 Error Codes list - Ferrari Life)

[wetpet]

that could be handy on the road.

[stevely]

Great review Stefvan. Just wanted to add my 2c since I recently purchased the device as well.

I ue the Kiwi Wifi with Harry's Lap Timer Pro on an iPhone 4 and embed F430 gauges using Dashware. Although useful, I found that the Kiwi didn't cycle fast enough for accurate RPM and speed data (1hz). I believe other people have coupled their iphone and another GPS system (TomTom) to get more faster cycles (10 hz I believe). It is adequate for the track, but definitely doesn't replace the more accurate Traqmate et al.

Here's an example of someone else using a similar setup on a Merc. (I have my own video but would rather not post for obvious reasons)
Mercedes w203 c200k video data loggin part 9- dashware delay problems - YouTube

[Anders T]

Thanks again Stefvan. Just read. Can I use this for all cars? Or just F cars?

all the best

PS - I realy like this DIY library. Great. Nothing disaperes and easy to find.

[StefVan]

Originally Posted by Anders T

Thanks again Stefvan. Just read. Can I use this for all cars? Or just F cars?

all the best

PS - I realy like this DIY library. Great. Nothing disaperes and easy to find.

Hi Anders, the KIWI should work on all 1996-up vehicules as it is using the standard OBD2 protocol. Although, on my BMW 330xi, I get only the rpm PID, speed PID and VIN (in addition to the CEL management) while on the Serie 1, you get many PID's... But for the BMW, I found a great iPhone software that can go much deeper than OBD and will connect to all the BMW ECU's. It's called BMWhat! Made by a German guy. BMWhat-BMW diagnosis

I agree regarding the articles and books sections. That's the other reason why I came over here

I will update soon the shift light guide with the installation instructions as I succeeded to complete this project today

All the best Anders,
Stef

[Tio]

Just Wow!!!

How cool is that!

Definitely handy but can you imagine showing this off to your friends?
You can pull out your iPhone and tell your friends, let me call my car and see how it's doing!
:-)

I love this Stef, where did you get it from?

[StefVan]

Thanks Harry . Your idea is really funny. Soon yes, you'll be able to talk to your car and ask him how he's going. We watched "The Moon" again last night and Gerty the computer is very advanced OBD reader maybe one day our cars will talk to us like Gerty

You can find the KIWI in UK on their website :
Welcome to PLX Devices product page - www.plxdevices.co.uk ( English Version ) or Welcome to PLX Kiwi WiFi Homepage - www.kiwiwifi.co.uk ( English Version )

I bought it on a local Swiss website. Nice little New Year's gift

[Killer58]

They are available on eBay as well.

[Tio]

Thanks so much Stef!
I will order one today!
It goes under the Christmas tree as well,
mind you the tree will most probably be Dow by the time it arrives!
:-)

[Anders T]

Same for me. Will order both this and a sequential shift light this weekend.
Thanks again Stefvan. Would be rather boring to own a Ferrari if you weren´t around.

[StefVan]

Originally Posted by Tio

Thanks so much Stef!
I will order one today!
It goes under the Christmas tree as well,
mind you the tree will most probably be Dow by the time it arrives!
:-)

Originally Posted by Anders T

Same for me. Will order both this and a sequential shift light this weekend.
Thanks again Stefvan. Would be rather boring to own a Ferrari if you weren´t around.

Thanks guys, you're very welcome The F430 is a hell of a car to explore and the challenge stands in the fact that not much information is available regarding the Ecu's and Can Bus data communication which makes it even more exciting

If I can find some time, I will design and develop a specific F430 dashboard for the Dash Command software.

From the available PID's list above in this thread, which PID's would you like to monitor on a specific F430 dashboard?

[cribbj]

Stef, it would be great to have this for the older V8/V12 cars (355/456/550) as well. Do you know if this works with their Motronics v5.2 ECU's?

I think having the OBDII PID's from my 550 on a wireless iPad would be too cool. I have limited access now with the ScanXL Pro software from scantool.net, and their WiFi/Bluetooth interface, but I haven't had the time or inclination to fool with developing it further.

[StefVan]

Hi John, as long as these cars have a compliant ISO 9141 K and L line on resp. Pins 7 and 15 of the OBD2 connector, the Kiwi interface should work. When I had the 355, I was at that time able to access the OBD PID's after having resolved the ground pin issue. But it's difficult to guess how many PID's the Dash Command software will be able to access on these cars. Someone will have to test it out I'm afraid

[cribbj]

Hi Stef, I do presently connect to my OBDLink WiFi (not Bluetooth) interface (ScanTool.net LLC - OBDLink WiFi Scan Tool / Interface / Adapter - ScanTool.net) using the ISO 9141-2 protocol, so I'm thinking I probably just need to pick up the Dashboard software and have a play with it.

The connection over WiFi is reliable enough, but I wasn't impressed with the scan times - it seems they're only every 1.5 seconds or perhaps even slower. Maybe it's better with a mobile device like the iPhone/iPad.

[Anders T]

This is one of the best DIY instructions I have ever read. Thanks Stefvan. Will sit down tonight and order both this and also the gear shift light. Then hopefully I will have time at the end of Jan.

[StefVan]

Originally Posted by cribbj

The connection over WiFi is reliable enough, but I wasn't impressed with the scan times - it seems they're only every 1.5 seconds or perhaps even slower. Maybe it's better with a mobile device like the iPhone/iPad.

John, here's a snapshot of some data frames I captured with the KIWI WIFI. In the entire log file, the average frame time was 120ms which is about 8 data captures per second. Each frame contains about 60 captures values (PID's and CALC's). I found this not bad at all for an OBD based solution transmitting data over WIFI .

[cribbj]

Thanks Stef; that's MUCH faster than my setup. I'll have to try this new reader and/or the software. Something in my setup isn't performing as it should. Could be the nut behind the keyboard is cross threaded....