Hi there,
I've decided it will be more practical to get someone to wright my code for me. I've had a play around and can get simple operations going but joining them to form a program is beyond me. I'm sure I could work it out but it would take me weeks, so ill leave it to someone who knows what they are doing 
http://forum.arduino.cc/index.php?topic=392101.0
here is a link to my previous post. the attachment explains what I would like to do with the program.
If your interested and have done this sort of thing before please send me a pm to discuss details, cheers
Sure I can help you but why start a new thread. What where you not getting from the previous one that you think you can get here aside from offering to pay for it ?
Drop me a PM or email with you existing code and what you want it to do and I will take look at if for you.
Cheers Pete.
Hi Pete,
I was just under the impression this is the section for this sort of question.
I can ask for it to be deleted if it's not required.
Sending you a pm now. cheers
Hmm.
In Arduino programming, you usually need a state transition diagram ratgher than a flowchart. But this flowchart converts pretty cleanly - those tight loops become states.
You might want a couple of blinky lights (although you could put a led and a resistor on the relay itself, I suppose). And you are missing an enclosing loop for a start/stop button.
When you detect the battery voltage, do you need to turn off the relay so as to get an accurate reading? How long do the relays need to be off for, to give the thing a moment to settle? Half a second? How often should this be done? Once a minute?
As it stands, your diagram cycles forever. At what point in the process do you take the battery out of the machine? I mean - you probably don't want to take the battery out when it's in the middle of a discharge cycle. So should it cycle for a number of cycles then stop? Should the user hit a button to say "ok, I want to remove the battery now"? Is it only supposed to happen once, and your diagram doesn't really indicate that?
Bainesbunch:
Sure I can help you but why start a new thread. What where you not getting from the previous one that you think you can get here aside from offering to pay for it ?
Well - that's the whole point. This subforum is specifically about jobs for money.
PaulMurrayCbr:
Well - that's the whole point. This subforum is specifically about jobs for money.
Actually no, is is not all about money, that is why it is called "Gigs and Collaborations"
Whilst most of the requests here are for paid help some are not. I do a fair amount of pro bono work from this forum. My question was not intended as sarcastic but simply trying to establish if there was another reason for asking in this forum, money aside.
Cheers Pete.
In Arduino programming, you usually need a state transition diagram ratgher than a flowchart. But this flowchart converts pretty cleanly - those tight loops become states.
You might want a couple of blinky lights (although you could put a led and a resistor on the relay itself, I suppose). And you are missing an enclosing loop for a start/stop button.
When you detect the battery voltage, do you need to turn off the relay so as to get an accurate reading? How long do the relays need to be off for, to give the thing a moment to settle? Half a second? How often should this be done? Once a minute?
Hi Paul,
Sorry i didn't check this thread after the first week but I still would like a hand.
I am not too sure what a state transition diagram is but I guess I can Google that.
As far as blinky lights the ss-relays i am using have leds built in so i can just label them. I'm sure i can refine the design latter though.
with the battery voltage reading a couple of seconds would probably be fine to measure the voltage and every five minutes would be a good start and i can easily change the values later if required maybe even add a small one or 2 second discharge to remove the static voltage. but worry about that later also.
when i have the basic sketch I'm sure i can understand how it works an then modify it as required. It is probably pretty simple for someone to bash it out that knows what they are doing.
Whilst most of the requests here are for paid help some are not. I do a fair amount of pro bono work from this forum. My question was not intended as sarcastic but simply trying to establish if there was another reason for asking in this forum, money aside.
Hi Pete,
yeah i probably should have made it more transparent that i was looking to pay for someone to help me out with the project. I appreciate people helping others but there is slim chance that I can help someone else on here and return the favor so i feel more comfortable paying .
To detect the battery polarity, rather than seeing if a0 was > .2, would it work better to check both A0 and A1? If they are both < .2v, then the sketch can't determine which way to charge.
Does this thing just sit there going charge/discharge forever? When do you take the battery out of the thing? After one cycle? when the operator presses a button? Or do you just turn the whole thing off?
Or perhaps it doesn't matter. The operator just watches the voltage indicator and pulls out the battery when it's correct. But doesn't this mean you need a "test" button to tempoarily disconnect the charger so that the current voltage can be read?
At present, there's no provision in the sketch for removing one battery and putting another one in - you'd have to turn it off.
You are aware that input on analog pins works with a reference voltage of +5v, and that some boards are 3.3v? You say "when voltage is >2.2v". Does this mean "when the input on A0 (or A1) is > 450" ? I'll assume that this is the case, and that ".2v" means "A0 (or a1) >40".
I"ll use pin 13 as a blinky light for at least some user feedback. Steady on for not charging, slow blink charging (short long one way, long short the other. maybe), fast blink for discharging, steady on when measuring the voltage.
As to moneys - I usually ask for a hundred bucks, which is my usual hourly rate at the day job. Arduino isn't my day job, but these projects usually take more than an hour (setting up the breadboard, github repo, etc).
The work will be on github under the "unlicense" - it becomes public domain. If you are happy with the work, drop the cash into my paypal (I'll PM you my paypal id).
PaulMurrayCbr:
You are aware that input on analog pins works with a reference voltage of +5v
unless of course you use the analogreference call to set the internal references available on the ATmel series of MCUs then you can set it to a known value and base your resister divider network on that. This will also then allow for fluctuation on the voltage driving the MCU to not effect the analog readings which would happen if you used Vcc as the voltage reference.
Cheers Pete.
Hmm - I thought I made a post 8 referencing the github project.
Oh well.
Project is at GitHub - PaulMurrayCbr/arduino_forum_392892 .
Main thing I'm concerned about is that the flowchart flicks the battery not simply from charging to discharging, but it reverses the polarity each cycle though. My sketch follows the flowchart. I hope that this is what the OP meant, and that reversing the charge cycle each time isn't going to make the battery blow up.
Ok.
Uploading demo video now to YouTube.