Beginners: please read this post and this post before posting to the forum.
0 Members and 1 Guest are viewing this topic.
Hello, I am wondering what would be a good (economical) control board to use to control a DC motor with a rotational encoder feeding back into simulink.My budged for the board is around $200, but would be nice if I can find something under $100. I am fairly new to having an actual physical element, but am well versed in the virtual side of control systems.
The biggest concern of mine is getting something that plays well with simulink for live control (I have seen it called rapid prototyping, but dislike that phrase)
I have looked into various arduino based boards and from what I can tell, getting them to play well with matlab/ simulink is a huge pain in the... well - you get where I am going. Do you know of anywhere that has more detailed info on how to get them to work well with the program?
Edit2: I may have found the solution to my question, I have possibly found a plug for matlab that exports simulink programming into readable code via MPLab (c code based?) Here is the link to the microchip page detailing the blocksets http://www.microchip.com/dspicblocksets any chance you could give it a quick read to double check that I am looking at the right thing? As I said, I am good at the simu part, and the mechanics, but its the electro hardware that I am lacking skill haha
I am looking for a rapid prototyping style board - If you need an example look up the Quanser Quarc boards - I guess you could call it 'plug 'n play'. I used those boards through university, and now just want to do some screwing around to learn more on the mechatronics part of my degree.
In essence I am looking for a board that there is with a set of blocks that will be able to translate simulink code in to a language that they can read, or a board that can read simulink code (I don't think that latter exists).
I am not sure how much you have used simu, but it is no easy - or realistically doable - task to create a translator to throw out C code (or whatever the board recognizes) in a format that is usable. We are talking a years worth of work by an engg team - which is why I don't really want to commit to making the blocks myself