When you are responding to quotes from someone, it really is easier to follow if you use separate quotes and put your comments in between the sets of quotes instead of inserting your comment inside someone else's quote. It's easier to follow who is saying what than looking at "*****" at the beginning of your response to the person's quote.
[u]Tell me if you see the difference:[/u]
Unless I am misunderstanding your list:
On the h-bridge controllers you only allocate one pin to control direction of the motors, but the L298 requires two pins to properly control one DC motor (one pin for direction, the other pin for on/off/pwm) - while for a stepper motor, you need all four pins. Also note that on the L298, you can configure it to either operate two DC motors, or one DC motor in "parallel" mode, or a single bipolar stepper motor (one h-bridge per coil).
Yes, you are right - I initially did not allocate enough pins - fixed this now
Most of your control flow seems laid out in that list; you basically just need a bunch of functions for the motors and sensors, then other functions for the interrupts, checks, and operations - plus the menu selection and such (btw - you don't list the menu requirements - which would be important to scope out a better time and cost estimate for your programmer).
Good suggestion - will do -
I think this project will take some time ultimately; between coding the initial pieces, running individual tests and checks, the passing of the code back and forth (so it can be checked on a real machine - instead of just LEDs and such that the coder would have - btw, what kind of LCD display? most use more than one pin; even one for SPI) - I think 80-120 hours might be in the ballpark for everything needed of the project (that would be for a final debugged and polished firmware), unless you are just looking for some quick-n-dirty coding to get things rolling that you can polish afterward.
Quick and dirty coding is going to be OK for now as the prototype is only for proof of concept to show investors and manufacturers (already assigned) for this product. Later can smooth out the rough parts.
It would probably have to be broken into stages anyway - something like 8-12 hours for all of the base functions, 4-8 hours each for each "operation", 8 each for the checks, etc; note that I am approaching this from an experience level of 20+ years in software development (but nothing embedded) - I might be high on my estimates, or way too low (I would probably err on the latter - as I imagine that there would be weird debugging sessions where the code seems to work ok, but fails on the real machine, possibly due to weird power glitches or any number of other possibilities).
I think I am looking at about 80-120 hours even to get the basics done by myself - progress sloooww! :(
This sounds like a fun project, though. I wish I had the time - I would probably offer my services on it.
What would it take to convince you? This is a very cool product... big industry! Hope to be in production by Q3 this year. Can disclose more under NDA to tempt u?
I am a little vexed however with the overall structure - so many paths it seems to go down. I know I gotta figure out interrupts and Booleans some more that I will work on next. I am looking through a whole lot of code to get some starting points. If I can t find someone to assist will have to nut it out regardless.
If you had an algorithm it would be much easier. It is a common misconception by non-programmer types that writing the algorithm is more work and it is easier to skip it. Would you like the pilot of the jetliner you are flying in to skip the pre-flight checklist because it is easier ?