Andy627
Germany
Asked
— Edited
Hello, I have a question .
I have these servos in my robot and have now bought the EZ-B V4.
But if it does not get to work, can the Ez b control these servos?
The servos are all connected and the controller only has 1 cable
greetings
[color=#442e5f][size=3][font=OpenSans, -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Helvetica Neue, Arial, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol, Noto Color Emoji]do you have any video about this project with the ubt robot?
[/font][/size][/color]
[/font][/size][/color]
I need to know more about interfacing its servos. I saw there's a plug-in and some hardware information.
I need to know, (I hope somebody in the forum has experienced these matters) :
Hardware : I'm attaching a photo, where 4 3-pin JST plugs can be seen. I think each of them drives , by 4 independent serial buses, some of the servos .
Which pins are +,-, rx/tx pin ? how to connect these 4 buses to ezb ? I saw in the forum a simple scheme, but more detail is needed.
Software: the plug-in I found in this forum is designed for such 4-bus hardware , so to control , by ezb, each servo separately ?
attachment
What's going on ?
What's going on?
It looks like the plugin uses a more recent or non existent class/object in an older ARC version.
Keep your ARC updated, is a good recipe to avoid trivial issues.
The latest ARC beta will technically run on Windows 7 but it’ll give a warning because it’s not recommended. Windows 7 was discontinued by Microsoft and no longer supported. This means new features of ARC are absolutely impossible to be supported in Windows 7 because Microsoft doesn’t support it.
*note: do not duplicate post.
I intend to test alpha 1S servos with ezb v4. The servo plugin seems to work. Now I have only this old PC available for this test.
I need information about the hardware connection of those 16 servos to ezb. I asked for this in another post. Can you help ?
Somebody has certainly tested this connection, but I don't know how to communicate with him. I hope he will reply to this post.
If you read this conversation thread as i stated, you will find that there is a link that discusses the ID's and how it works. You will need to put a little leg work in to get it rock'n. Each servo has an ID. The lowest ID is 1. I'm sure the UB Tech software shows what ID is for what servo. If not, you'll have to experiment and try.
Connect them as described by the plugin. To the UART that you choose and power and gnd. I don't have a servo, but it would be pretty easy to look and see what wires are for what. Or, use google to research and find it. That's all i can do to help
I think all the 16 servos should work on a single control line. I'll study the plugin information , looking for details., i.e.:
1) Direct connection of one digital or UART ezb port to a single servo control line, with 16 servos on it ?
2)Control wire is bi-directional. What happens if ezb sends bytes to servos while servos themselves are sending bytes on the control line ?)
I hope that experienced members could explain . In lack of information , I'll look at the control pins with an oscilloscope a let everybody know.
The timing is set so the servos and the EZ Robot board always send and receive at the right times.
You can use the IO Tiny with a camera to make this robot do much more than it could before.
Alpha robot has 4 jst plugs with 4 separate 3-wire cables to the servos (as you can see in a previous post of mine). I think they are separated only for mechanical convenience of wiring, but probably they are all connected together in the pcb. I see no logic reason to control several groups of servos independently by the controller.
I assume that the ezb v4 (uart or digital pin) can drive the common line of all the 16 ubtech servos.
Do you know which jst pins are +,-, rx/tx ?
I looked around and can't seem to find any info on which wire is + or GND or signal. I'm guessing you can figure it out by looking at the board OR probing the connector with a volt meter
I connected one of the jst plugs and tested the ezb plugin . It was able , by the real time control in the frame screen, via UART and V3,V4,V5, the 3 servos of one arm. The other plugs are probably for the other arm and the two legs.
The movement is slow and weak. Those servos, when operated from their controller, are quite fast and strong.
I made an action with 2 different frames alternating , pausing for of 500 ms, but it doesn't work. The servos remain in one of the frames.
I haven't found in this thread someone who has done such tests. I'd like to hear from someone who did .
I hope that DJ could have one servo and some time to do a test , to understand what happens.
here is my research and what I found :
Baud rate:115200
Data bit:8
Stop:1
Check:0
Flow control:NONE TTL multi-layer connection,shared-bus
ID:1-240
Feedback:position:deviation adjustment,version information
Serial parameter:115200,8,n,1,1
Protocol analysis
EMBEDDED LED
// FA AF 01 04 00 00 00 00 05 ED switch on led light // no LED on mine
// FA AF 01 04 01 00 00 00 06 ED switch off led light// no LED on mine
RESPONSE AA + id // not tried yet as I cannot see with my proto board
GET VERSION
FC CF {id} 01 00 00 00 00 {sum} ED // not tried yet
RESPONSE FC CF {id} {V-1} {V-2} {V-3} {V-4} {sum} ED
this can be used to check if servo exist in a loop "for id"
MOVE servo
// FA AF {id} 01 {angle} {time} {T1} {T2} {sum} ED whre T1=0 and T2= {time}= TIME to execute in ms / 20 0 to 255(FF) ie 5.12 second to execute
RESPONSE AA + id // not tried yet as I cannot see with my proto board
GET POSITION
// FA AF {id} 02 00 00 00 00 {sum} ED // not tried yet
REPONSE FA AF {id} 00 {angle} 00 {real} {sum} ED // not tried yet as I cannot see with my proto board
SET OFSET ANGLE
// FA AF {id} D2 00 00 {A1} {A2} {sum} ED where A1 adjValue/256 and A2 adjValue%256 // not tried yet
RESPONSE FA AF {AA + id} 00 00 00 00 {sum} ED
GET OFSET ANGLE
// FA AF {id} D4 00 00 00 00 {sum} ED // not tried yet
RESPONSE FA AF {AA + id} D4 00 00 {A1} {A2} {sum} ED where A1 adjValue/256 and A2 adjValue%256
All works now, just think to cross wire in the daisy chain, else GND become DATA on next servo and block all transmission....
Any hint? Thanks!