We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hello to all. I am working todays on some projects that need controlling a solenoid valve with a at91sam7x256. I want to know what extra hard I need. I meen the driver of the solenoid valve. Actually I know we shall not connect that 2 pieces directly, but how and why? Another question is that which port of that micro best suits such a hardware if we need high speed serial communication. Thanks in advance for your attention.
What, exactly, do you mean by "working on" ?
Are you the project manager? the marketing guy? a hardware designer? a software designer? or what?
www.lmgtfy.com
"high speed serial communication"
What, exactly, do you mean by "high-speed" ?
What, exactly, do you mean by "serial communication" ? USB, SPI, I2C, Ethernet are all types of serial communications - as well as RS232...
About your questions: I aim to control watering of apartment flowers. It would be put into action by controling an electrical valve. This module itself embedded in a CAN(Control area network).
No, you didn't answer any of my questions.
To recap:
1. What, exactly, is your role in this project?
2. What, exactly, do you mean by, "high-speed" ?
3. What, exactly, do you mean by "serial communication" ?
He hight have thought about CAN for serial communication.
But if the specific chip happens to support CAN, then there should be no need to ask which pins to use for that task. Same should normally be true for UART, I2C, SPI, USB, Ethernet, ... so we do require more information.
then there should be no need to ask which pins to use for that task
Not only no need, but no possibility either. You do not want to bit-bang CAN. Not even on an ARM. Asynchronous multi-master serial communication with a requirement to check a CRC within a single bit time to decide whether to ACK may not be completely impossible --- but it would be enormously wasteful to try. Some goes, with even more certainty, for USB and Ethernet.
UART, SPI and I2C can often be handled by bit-banging, but you should still only do that if there are no dedicated peripherals available.
1-I must assemble a prototype, program uC for my use, and test my equipment. 2- Forget it. 3- Forget it, too.
"2- Forget it. 3- Forget it, too."
So you felt your original post to have been badly thought out, and instead of answering these two questions you prefer to dodge?
"1-I must assemble a prototype, program uC for my use, and test my equipment."
Why "must" you? What forces you to do this?
www.lmgtfy.com/
"2- Forget it."
OK - but why, then, did you mention it in the first place?
"3- Forget it, too"
Does anybody here actually understands what the OP is after? I'm lost.
Does the OP actually understand what (s)he is after??