I don’t know what the range can be either and frankly, I forgot about this so I’m proposing a different method. Why not just use Vixen. For a channel that you want to set, tie the output low. Now use the sequencer to program the selected channels.
For each channel:
Byte 1 – Mode (0 = Disabled, 1 = Standard, 2 = Extended.)
Byte 2 – Minimum pulse width (times 10)
Byte 3 - Maximum pulse width (times 10)
Byte 4 – Neutral position (times 10)
Byte 5 – Change rate (set the speed at which the servo moves)
Byte 6 – …
Store in E2.
You can use the pulse width values to ignore anything outside this range so the servo doesn’t get stuck a just draw excessive current or set the span so you can always use 0 to 100% in Vixen.
Pull the jumper(s) and you’re done.
I'm not sure how "right" I am in reading this. But I have an idea, granted I could, (and probably am) COMPLETELY WRONG!
RENARD WIKI PAGE wrote:1) If this byte is less than 128 (0x80), it is for some protocol that this firmware cannot handle (reserved for future use).
The command/address byte is retransmitted, as are all the remaining bytes in the packet.
Couldn't you set the PIC to read a command byte of something less than 128, which would just get sent through any current controllers (so I think).
If the PIC saw a command/address byte set for servo control. It would read the values for each channel, and then set the servo option based on that. Theoretically you could program up to 256 types of servos? Unsure as to how the PIC's internal memory and/or the firmware could be written.
However, this does add into account the fact that somehow you would have to transmit this lower byte, either by a plug-in, or scripted sequence (possible?) or separate (spelled it right Chris, just for you :P) to set the servo positions, and then the only difficult part would be converting 0-100% to your PWM values for the servo while sequencing (a small calc app would be useful (I could do that =).
Edit (4/20/09 1:50ish AM EST)
I don't mean to denounce any particular talked about methods, I'm just trying to think of a non jumper idea for those of us that are either too lazy, or have controllers that lie under snow for various amounts of time. I for one fall under the too lazy portion, while many of our members fall under the snow blankets.
Gents,
This entire project is based on the RENARD comm protocal....ie. no changes within Vixen...
Ernie,
There is no need to pull the jumpers. I already have a 8 position DIP switch setup to handle the input parameters with a transistor "switch" killing power to these inputs.
However, it seems that you may be assuming that all 8 servos are the same. At this point, Don and I are NOT making this assumtion. In fact, I cannot bank of the fact that all servos can be run at 5.0V or 6.0 (most all seem to work at 4.3V).
What Don and I have not discussed is "grouping" like servos..for instance, all extented range servos must start at Position 8 and go down...then in the jumper input becomes the changeover value in binary. This is just a thought as we try to work through things.
Don is a bit busy right now with his group buy so I am just banging ideas around.
Would anyone be opposed to only using one brand of servos with each board????
Chris
chilloutdocdoc wrote:I'm not sure how "right" I am in reading this. But I have an idea, granted I could, (and probably am) COMPLETELY WRONG!Couldn't you set the PIC to read a command byte of something less than 128, which would just get sent through any current controllers (so I think).
If the PIC saw a command/address byte set for servo control. It would read the values for each channel, and then set the servo option based on that. Theoretically you could program up to 256 types of servos? Unsure as to how the PIC's internal memory and/or the firmware could be written.
However, this does add into account the fact that somehow you would have to transmit this lower byte, either by a plug-in, or scripted sequence (possible?) or separate (spelled it right Chris, just for you :P) to set the servo positions, and then the only difficult part would be converting 0-100% to your PWM values for the servo while sequencing (a small calc app would be useful (I could do that =).
Edit (4/20/09 1:50ish AM EST)
I don't mean to denounce any particular talked about methods, I'm just trying to think of a non jumper idea for those of us that are either too lazy, or have controllers that lie under snow for various amounts of time. I for one fall under the too lazy portion, while many of our members fall under the snow blankets.
i have gotta say i allways thought this was how it should be done in an ideal world. but i think there would be some issues with things like the renards not sending data back to the pc. and also there would need to be pc side software written for this. but yes ideally this would be great and i think it was the original intention of the "128" character in the renard protocol.
but having said that the current scheme would work, just not as nice IMHO.
scorpia wrote:i have gotta say i allways thought this was how it should be done in an ideal world. but i think there would be some issues with things like the renards not sending data back to the pc. and also there would need to be pc side software written for this. but yes ideally this would be great and i think it was the original intention of the "128" character in the renard protocol.but having said that the current scheme would work, just not as nice IMHO.
Not saying any design is nicer than any other, if it works, and it's repeatable, it's a far more than acceptable design. But as Chris said, and I neglected to remember at nearly 2am, the goal is for no changes to the Renard Comms.
And I would assume that most people stick to one brand of servo's, and if they don't they could probably just use the larger of the settings on the boards, and be sure to underrun the smaller servos, or risk burning them out. or just build 2 boards
g2ktcf wrote:In fact, I cannot bank of the fact that all servos can be run at 5.0V or 6.0 (most all seem to work at 4.3V).
All of the RC servos that I've seen will operate at 5V. Most have an operating range somewhere between 4V and 6V. Sometimes they will list specs at something like 4.3V to show the minimum torque. At a higher voltage they will have higher torque and speed, up to the maximum voltage. Here is a Futaba chart that shows specs for their servos at 4.8V and 6V. I have a couple of servo controllers and they both operate at 5V and are not adjustable.
Most servo's I've seen (YMMV) are spec'd at Either 4.8V, 5V, 6V, or a combination of the listed. However, if you were to build the board and somebody were to use a lower power servo, couldn't you put a resistor inline to lower the voltage?
Hey Don,
Any updates on this project?
Sorry, but I've been very busy lately with some remodeling projects that are, as usual, taking way longer than expected. Our kitchen floor currently consists of temporary plywood laying across the floor joists. My wife won't let me work on any BF things until I finish her floor. I haven't forgotten about this, I just haven't had the time to finish it. I started to set it up on a breadboard but I was missing a couple of parts. I have all of the parts now, so it's just a matter of trying to find time.
Not a problem. I know exactly what you mean about finding the time. I currently have several projects that are in progress (lawn, sprinklers, deck, etc...). I hadn't seen anything on this thread and was just checking up on it.
Thanks for all that you have done so far.
