View Single Post
  #8   Spotlight this post!  
Unread 06-09-2010, 00:57
EricVanWyk EricVanWyk is offline
Registered User
no team
 
Join Date: Jan 2007
Rookie Year: 2000
Location: Boston
Posts: 1,597
EricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond repute
Send a message via AIM to EricVanWyk
Re: Working with the PSoC

Quote:
Originally Posted by PortugazD.Ace View Post
My idea follows all of the rules. the system is only for dectecting enviromental changes and telling the cRIO how to react using preprogrammed commands in the cRIO. that is all I want the PSoC to do. also, don't forget that those were last years rules. the rules could be different this year.
I see I don't need to give any of my standard warnings

For what it is worth (nothing), my understanding of last years rules agrees with (my understanding of) your understanding.


The best advice I can give you is to plan your project out into small, proveable chunks. At each step along the path, you should be able to point to something and say "this proves that it is working the way I think it is".

For example, it may be worthwhile to make a simple version in which it simply reports whether or not something is true using a simple pin. You can attach an LED or a multimeter to this and watch it blink.


Also, don't be intimidated by the PSoC's programming environment. If you already know C++, you are well on your way. Again, just start simple.

As to its hardware configuration, this is done graphically. The interface is relatively straight forward, but I'd do a tutorial or two first just to get a lay of the land.