I'm just finding my feet with Arduino but have just bought the new CAN-Bus/GPS Shield from SK Pang together with the Serial LCD and OBDII cable.
The supplied example GPS and ECU sketches are great and work as far as they go but I'd like to combine the two and use the on-board joystick with a menu system to select CanBUS or GPS data and log all the data to a MicroSD card.
This is well over my head though, aside from the shield having a joystick and MicroSD card slot the examples do not use either and so I'm at a loss where to start.
As it is now, I can set up the sketch to report my chosen engine parameters and run it in CanBUS mode.
Or I can load the GPS Sketch and get Lat/Lon on the serial LCD.
So it's at least of some use as is.
I'll do what you suggest and get the joystick working with some simple text on the LCD and work from there.
It's great fun but coming at this as a newbie I may have bitten off rather too much, I have zero C or any other coding experience so lots of it, even with the tutorials, is as yet making no sense :-/
For reference, this is the shield, a very neat device.
Thanks, I've been working through the Earthshine .pdf book albeit not always understanding what is going on! I've also bought "Getting Started with Arduino" and "Practical Arduino".
My started kit is from Oomlout and that comes with a starter booklet and guide.
What I will do is trace back the joystick pins on the schematic and start slowly by working to be able to detect a movement in one plane say 'Joystick UP' and build from there.
Once I've understood that I can then get the joystick to trigger a change in the data displayed.
All sounds so simple but I guess this is the best way to understand it all. I managed to get a Sparkfun RTC module working thanks to some posts on this forum which was a major victory for me and I'm loving the whole Arduino thing.
Any pointers on the Joystick and any caveats/routines welcomed.
The Atmega controllers used for the Arduino contain an onboard 6 channel analog-to-digital (A/D) converter. The converter has 10 bit resolution, returning integers from 0 to 1023. While the main function of the analog pins for most Arduino users is to read analog sensors, the analog pins also have all the functionality of general purpose input/output (GPIO) pins (the same as digital pins 0 - 13).
Consequently, if a user needs more general purpose input output pins, and all the analog pins are not in use, the analog pins may be used for GPIO.
Pin mapping
The Arduino pin numbers corresponding to the analog pins are 14 through 19. Note that these are Arduino pin numbers, and do not correspond to the physical pin numbers on the Atmega chips. The analog pins can be used identically to the digital pins, so for example, the code would look like this to set analog pin 0 to an output, and to set it HIGH: