NEWBIE: I need A Partner In Crime
Frankfern123
Posts: 35
Hi All,
As much fun as I'm having jumping into the Propeller world, I simply don't have the time to learn the language. If there is anyone out there that may want to co-collaborate on my project which i have every intention to bring to market I'd love to hear from you.
The final product will be for the automotive market so I need someone who has an understanding of that area and the reasons why certain "hardware issues" need to be a certain way.
I have resources for initial production runs and I will make it very well worth your while. I will have to have whomever decides to come on-board sign an NDA though.
Please PM me if your interested.
As much fun as I'm having jumping into the Propeller world, I simply don't have the time to learn the language. If there is anyone out there that may want to co-collaborate on my project which i have every intention to bring to market I'd love to hear from you.
The final product will be for the automotive market so I need someone who has an understanding of that area and the reasons why certain "hardware issues" need to be a certain way.
I have resources for initial production runs and I will make it very well worth your while. I will have to have whomever decides to come on-board sign an NDA though.
Please PM me if your interested.
Comments
Yes I do, there are certain constraints that need to be adhered too for THIS application due to a staggering amount of "noise" the circuitry may be subjected too.
Thanks Jonny, If you can recommend a better way for me I'd love to hear it. Too much dissimilar information out there and I cannot seam to find a good rooted base to take my learning curve from cradle to grave.
Please give me your thoughts .............
Thank you in advance. Also consider the can of worms you may be opening by offering it to me. LOL
Last thing - I sincerely hope I didnt come off sounding like this guy, my apologies If I did - http://forums.parallax.com/showthread.php/112859-NEEDED-Propeller-Expert-Partner-for-new-product-idea-...
PEK (Propeller Education Kit) here and here. It's downloadable for free if you don't need the paper manual.
Look at the application notes and other information here.
http://www.parallax.com/ProductInfo/Microcontrollers/PropellerGeneralInformation/PropellerMediaPage/tabid/832/Default.aspx
...and get the first Propeller manual, v1.01, it contains a detailed tutorial which was left out of v1.2 on blinking LED's, setting up time delays, and similar basic intro stuff. It's worth doing because it uses some of the weirder Spin conventions; Spin's expression evaluator is incredibly powerful and terse and a superset of almost everything else out there, and it's worth learning it because it will enhance your understanding of how all other languages work. But nowhere else will you find that VAR~ sets VAR to 0 while VAR~~ sets it to -1 and !VAR as a command does a NOT. Once you blink some LED's you'll be ready to hook up a demoboard to a monitor or keyboard and really get rolling, which is key because those interfaces are also your debugging channels in Propellerland.
Obviously too many viewings of the Rocky Horror Picture Show. Hey, at least I didn't graft on a furter!
ROTFL - Oh No !!!!! Wow you just brought back some memories, Midnight Showings Of The Rocky Horror in the old Island Twin Theater, replete with bags of rice, toasted bread, rolls of TP and the High School drama club who'd show up in costume............. Wow, been years since i thought of that.
I did a quick search and found..http://forums.parallax.com/showthread.php/146538-Powering-the-prop-from-an-automotive-12v-source.?highlight=Spin+automotive
I'm sure you will find help here.
Believe me, it's a can of fun! Just last night I was at a B'nai Mitzvah party and a group of us in the FX business were talking about how much fun the Propeller is to use. There are some really great folks here in this forum that can guide you. Continuing my blunt streak (grin)... I think you'll find you'll get more enthusiastic guidance by showing a willingness to jump in. I guess you could say the forum helps those who attempt to help themselves!
Again, it's fun -- don't deny yourself that pleasure. If you get stuck, help is here.
I began in buying the Prop BOE board, not the Prop In Class kit. I ran through all the lessons and luckily only had a few wiring hiccups. I understand the base concepts behind it all, my problem is assembling a working system in how everything will interact. This is where I keep losing my place. FYI - I did study electronics and got a degree from De'Vry back in the late 80's. So my understanding of the hardware is ok, but even in college I terribly flunked out the one programming course we were given. Hmm, Mental Block maybe ????
Now on the issue of programming from a GUI I have no problems at all IE, automotive, control systems, robotics, etc etc. But with every a GUI I've worked with, I'm simply making changes externally to a pre-defined system, Hmmm, another possible mental block..........
I feel structuring the interaction is my downfall, I have every circuit working independently, but i cant seam to string it all together.
Please give me your thoughts .............
The LM2940-3.3 is pretty good. Go with that or something that has specs and features better than that. http://www.ti.com/lit/ds/symlink/lm2940-n.pdf
With the trash on the power line behind you, the rest is pretty much about code.
IMO, the bast way to start building a project with unknowns is to start with one small piece. Get it working, test it hard, refactor, repeat until thoroughly tested. Then move on to the next chunk. Continue down this path until you have tested all interfaces. Next, integrate the well tested code chunks into a cohesive application. Working in way will cause you to build an abstracted and extensible code base.
if you need help along the way - Just ask.
Start with One peripheral device.
Put multiple devices together, add one at a time.
REMEMBER! Be sure a given device is REALLY doing what you need before you add another unknown. You want to work with at most 1 unknown when ever possible, or you will get blow away by the combinatorial explosion from multiple variables. Very messy.