![]() |
Signal Generator
Not sure where this goes, but it is basically two duinos. One (the plain chip and crystal) has been programmed in arduino to simulate a vehicle vss and injector signal, and the other is running the mpguino code. The test code is at the bottom. Now it isn't single digit microsecond accurate, but it also isn't limited by the number of timers either. With this approach you can generate a lot of different signals, i.e. buttons, etc. And since both the guino and the signal generator are connected to the computer simultaneously it is quite possible to have a PC program with all kinds of scenarios that tell the signal generator what to generate and get the result from the gunio to see if it is correct.
http://ecomodder.com/wiki/images/c/c...generator1.JPG http://ecomodder.com/wiki/images/d/d...generator2.JPG http://ecomodder.com/wiki/images/4/4c/TestWiring.gif PHP Code:
|
What is the signal logic on the VSS and injector line? I'd like to make an interface for my carputer to do FE calculations.
|
It is basically a 5 volt square wave defined by these lines in the code:
#define sig1PinOffTime 2444 #define sig1PinOnTime 25333 #define sig2PinOnTime 16000 #define sig2PinOffTime 2180 sig1 (simulating the injector signal) is off for 2444 microseconds and on for 25333 microseconds, roughly. sig2 (simulating the vss signal) is on for 16000 microseconds and off for 2180 microseconds, roughly. So you going to start from scratch, or can you help us troubleshoot the guino? It would be downright trivial to send the instant raw data out the serial port on the guino and collect it on the carpc and make sense out of it there. I do it all the time for debugging. |
You beat me to the end. :thumbup: My 555 is working, but not very precisely. While its accurate, without a scope, I'm having trouble zeroing in on trustworthy streams.
So, let me get this straight, you have a basic ATMEGA168 chip, that you loaded using your Freeduino board, or the load cable, then placed that code loaded chip to your solderless breadboard with the bare bones components for a functioning chip. You then power it from the same place as the MPGuino and tap its outputs. I may just have to break down and buy some more Freeduinos to catch up. :o My soldering iron is heating up so I can migrate my LCD and input interfacing components to a proto shield. I'm trying to make mine look less like a spaghetti ball on the bench. |
Quote:
NCK had some chips with bootloaders on them, but no crystals, and when I looked they did not have chips in stock, so as hokey and painful as the parallel programmer can be to get working, it has proved to be invaluable. It's brought back a couple chips after experiments that have gone wrong and cost me nothing :) Course the real nice thing about this arrangement is that I can create cheap little devices, but anybody with a duino can also use what has been written very easily. Edit: I was just checking out the iduino and noticed that fundamental logic, http://www.spiffie.org has atmegas with bootloaders preloaded and crystals, as well as a breadboard usb duino kit for $18! I had to get one at that price (plus a couple more atmegas and crystals) |
Great work DCB. Thanks for all your help on this project as far as debugging the software (and writing it hahaha).
I may build one of these with my spare board. I always buy spares when it comes to components....I've got a habit.... |
I got my cluster of wires pushed to the proto shield from NKC. But, then ran into several issues.
The first was the size of the holes are tight for the Zener diodes, or if you have larger watt resistors. Not a big deal, but does require some persuasion and the small area makes it challenging. The second problem is more of an issue. Basically, the trace across the center of the board for 5V is not connected, just solder pads; the ground is OK. I contacted NKC and they acknowledged my find. They were prompt, but I would wait for a new generation board before getting another proto shield from them. All in all, it went great, aside from the issues with "placement on the fly". And, it looks good, piggy backed on the Guino. Still not as compact as a custom PCB setup, but very friendly for plug-and-go with any Freeduino board, snap in, snap out. I'm waiting for my other Freeduino's to arrive so I can assemble the generator and get back to testing this thing. |
Have you changed or updated your generator code? I've got it running on a 2nd Freeduino, straight inputs, not resistors.
It looks like I'm showing 55-58 mpg. Is that what you are getting? I show MH 40.0x and MG ~57. Not related directly to the generator, when I display the CPU % screen, it seems to revert back to the startup, like a reset as the MI reverts back to near 0. I get it if I cycle left once, or right 6 times. I'm not quite sure if it's the code somehow resetting the CPU or something else. Version 0.61. The generator makes it nice to see it actually running. |
I've not touched the signal generator code since fixing the 72 minute issue. I do keep messing with the microseconds per gallon and vssTicsPermile though but 57/58 mpg @40mph sound just right for the last version.
re:reset, currently , hitting left button and middle button simultaneously will reset the tank trip, hitting right and middle will reset the current trip. Is it possible that the middle button is getting "fat fingered" when hitting the left or the right button? |
I've checked and the buttons don't appear to be solder bridged or anything. And the buttons are far enough apart to not likely be fat fingered. But, it also happens if I right button to that screen, also.
But it appears to be resetting the program, ie running setup() again. With my current configuration, if I press the reset button on the Freeduino the LCD goes "one line" on me - known issue. This doesn't happen, so I'm not quite sure it's a full on restart, but like it's just running setup() again somehow. I went looking through the Guino code, looking for a possible hosed pointer or something, something where a memory address is getting trounced. Nothing jumped out at me. It could be a memory corruption or allocation/deallocation issue within the arduino program code. A bit far fetched maybe. Does it not happen for you? |
All times are GMT -4. The time now is 09:44 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
Content Relevant URLs by vBSEO 3.5.2
All content copyright EcoModder.com