Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Attiny pin & PWM use #1

Open
spanner888 opened this issue Aug 8, 2012 · 4 comments
Open

Attiny pin & PWM use #1

spanner888 opened this issue Aug 8, 2012 · 4 comments

Comments

@spanner888
Copy link

From Edward with the initial code: However, I would like to bring up that in the newer design, instead of use up all 4 PWM channels with 4 pin controlling the motor, we decided to use only 2 pwm pins controlling the enabled pin and 4 other pins controlling the directions of the motor -- a total 6 pins been taking up controlling the motors but we are left with 2 more pwm pins.
@spanner888
Copy link
Author

If we are really short of pins can even save two more just by permanently enabling the driver as is done in the XCJ motor driver shield, or just connect the PWM signal to BOTH enable and one drive pin. Could even save a third pin by using the same PWM signal for both motors - which means that each motor would be fixed at the same speed.

@lumi3005
Copy link
Member

I got an idea about the different development states. Why we don't keep the PCB with the Attiny and the L293 and develop another board in parallel. The new one could include an Atmega168/328 and another motor driver and being used ans the advanced "drone" besides the "workers" with the little Attiny brain.
Just make it two separate projects, Attiny and Atmega drones. This sounds to complicate or will split our resources?

@spanner888
Copy link
Author

didn't we already say we were doing this in recent topics :)

I am focussing on getting everyone active & partkeepr and running
workshop next weekend, then I can start "doing" more.

On 10/08/12 12:52, Lutz wrote:

I got an idea about the different development states. Why we don't
keep the PCB with the Attiny and the L293 and develop another board in
parallel. The new one could include an Atmega168/328 and another motor
driver and being used ans the advanced "drone" besides the "workers"
with the little Attiny brain.
Just make it two separate projects, Attiny and Atmega drones. This
sounds to complicate or will split our resources?

—
Reply to this email directly or view it on GitHub
#1 (comment).

@lumi3005
Copy link
Member

No we did not but it was just an upcoming idea. Right now we just have the old design and I think we should go with that for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@spanner888 @lumi3005