Aloft Forums
Welcome to Aloft Forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Program Xact servos for Sbus protocol
- Thread starter Sloglider
- Start date
Link for the current OpenTX LUA script:
Konrad
Very Strong User
Isn’t it really F-Bus? F-Bus supports S-Bus, but as the interface really is different from S-Bus, I’d think claiming that the servo is an S-Bus servo would cause more issues (like the ones we see here).
Now a link on the sales page as to what F-Bus is, might be rather helpful.
Now a link on the sales page as to what F-Bus is, might be rather helpful.
We probably need to look at our product listings on our site closer. At one point I was going to take over the servo branch for FrSky and had many changes planned for the servos, but it didn't happen. So should take a new look at our quick and dirty product write ups and improve them. They are a really nice set of servos with great potential and piss poor instructions and no marketing.
Thank you Wayne and others. I am trying to program 6 Xact HV5611/12 servos for a uber lite F5J build. In the past I have used SD1 converters and ran Sbus. I am using a Taranis Access X9D Plus 2019 and a GR6 Access receiver, both of which have their latest firmware. I have managed to program 3 Xact HV5611 servos to respond to channels using F.port2 and Lua Script 1.01. But using the same procedure, a strange sequence of discovering and deleting sensors and running Lua script, I have had no luck programming the other three servos. I have since tried using Lua 1.02 which hasn't worked at all. Lua 1.02 offers one more programming option "Center", but the center option won't populate or respond to input, and the flashing progress bar stops well short of its end. I am thinking that these Lua scripts may be faulty or not up to the task. Of the three servos that I did get to "work", only one worked as I had instructed it to. the other two would be set for servo 2, but actually activate servo 5, etc. The RCGroups Frsky Xact Servo thread has been helpful, but I don't see anyone claiming to have really figured this out. One person has suggested using FrSky's STK with new firmware as a work around. I'm going to try this...just ordered one. If you would like a link to the most helpful RCGroup posts, I will post them. If I have any sucess, I will post. I bet there is someone who knows Lua Script that could debug this. Sure would like to just use the Channel changer.
@Wayne if you are considering updates to your FrSky product pages, I would like to suggest you add direct links to the manuals/downloads page, or the details page, I am not sure which would be the better link.
i.e. https://www.frsky-rc.com/product/hv5600-series/ & https://www.frsky-rc.com/xact-5600-series/
i.e. https://www.frsky-rc.com/product/hv5600-series/ & https://www.frsky-rc.com/xact-5600-series/
I really hate how Frsky has listed the Xact servos on their site. If I, a FrSky dealer have issues making heads or tales out of it, how well are others figuring things out?
That and they have changed the part numbers and details on some of them. Total confusion. SNAFU
I try not to link to their site as they make changes to addresses and or their site goes down from time to time. But mostly, we like to write our own copy and try to be very honest on a product. Often times a manufacturer will make claims and in our testing we are not able to back up that claim, we simply do not make that claim on our site!
With the Exact servos, we do need to take another pass at our write ups on our site and give some better details. Just have not had the man hours to do this yet, and FrSky still seems to be making some changes to things. My advice to Frsky was to cut way down on the number of servos they are offering and concentrate on the few important ones and get them all perfect and build a reputation. As we can see, they ignored that..
That and they have changed the part numbers and details on some of them. Total confusion. SNAFU
I try not to link to their site as they make changes to addresses and or their site goes down from time to time. But mostly, we like to write our own copy and try to be very honest on a product. Often times a manufacturer will make claims and in our testing we are not able to back up that claim, we simply do not make that claim on our site!
With the Exact servos, we do need to take another pass at our write ups on our site and give some better details. Just have not had the man hours to do this yet, and FrSky still seems to be making some changes to things. My advice to Frsky was to cut way down on the number of servos they are offering and concentrate on the few important ones and get them all perfect and build a reputation. As we can see, they ignored that..
SUCCESS! A clean F.bus connection to 6 Xact 5611/12 servos with telemetry! The Lua scripts were not up to the task. The Frsky STK doggle and FreeLink app were an easy and straight forward solution. Plus, I could see the hash the Lua script approach had made. The STK I just ordered from Aloft and the FreeLink app is a recent download for PC. They linked up perfectly. Still being unclear about the differences between the "Servo ID" and "S.Port Channel ID", I chose to make them all the same, ie: left aileron... channel 2... Physical ID: 2...Servo ID: 2...S.Port Channel ID: 2 and so on. Hope this helps. Can't wait to get my hands on Xact HV 5711/12's. I love all the Frsky products and all the amazing things they do and you can make them do.... especially if you enjoy puzzles and problems... Steve
Konrad
Very Strong User
That is the solution FrSky just gave me last night. STK and FreeLink. Glad it worked for you. It is my understanding you will want a separate Servo ID and seperate S.Port ID for each servo. This way you will be able to see the telemetry from each servo. When they all share the same, the radio will not know what servo is reporting what.
Landru
Strong User
Totally bamboozled
Hey @Wayne or @Sloglider or any other good Samaritan, can you point me to step-by-step instructions for using the STK to configure Xact servo settings?I've got the FreeLink app running on Win10, my STK shows up as a serial port, Windows reports that the drivers are up to date, but I've had zero success in reading or writing settings from / to Xact HV5611 or Xact 5701 servos. What's the secret? After I click the 'Configure' button in the app, all the setting fields remain blank as shown below. I've tried the 'Save to Flash' function, too (after typing settings into the fields). No dice.
Prior to trying the FreeLink app, I upgraded all my Xact servos to the latest firmware via the S.Port on my QX7 ACCeSS. Did that doom me?
Gosh, FrSky manuals can be on the slim side. Did I say manuals? Pardon the abuse of that noun. Someone deliver me from this frustration, please!
In mostly good humour,
Andrew
Last edited:
Landru
Strong User
I stumbled on a step-by-step guide in the 'Instructions' tab on this FrSky Webpage.
No joy, however. The settings from the servo are not read, nor are they modifiable.
Also, the info in the FreeLink app itself gives different instructions from the Website.
No joy, however. The settings from the servo are not read, nor are they modifiable.
Also, the info in the FreeLink app itself gives different instructions from the Website.
Landru
Strong User
Today I tried the FreeLink app with a different PC. Lo and behold, reading and writing the Xact settings worked. Well, it worked most of the time. In about ten attempts with five different Xact servos, the process failed one time. I have no idea what caused the failure. I used the same procedure in all attempts.
I made note of the CP210x driver version and went back to trying on the first PC. Despite a fair effort -- and researching the SiLabs Website -- I was unable to update the CP210x driver on the first PC to the same version as worked on the second PC. That said, in all cases on both machines a virtual com port was created and did seem accessible. In about 30 attempts on the first PC, I succeeded in reading all the data from a servo on two occasions, and part of the data on several other occasions. On one occasion, plugging in the STK caused my USB wireless mouse receiver dongle to go AWOL.
Debugging USB issues in Windows is way above my pay grade. Judging from SiLabs info, I got the impression that there might be a problem with "USB enumeration". I suppose such a problem might explain the intermittent success on both the PC I tried. It's worth mentioning that, even when reading the data failed, a log file was often generated that contained some data -- possibly the device settings?
Bottom line: STK + Xact is funky.
P.S. If anyone at FrSky is interested, I can provide details on the CP210x drivers, log files, and so on.
I made note of the CP210x driver version and went back to trying on the first PC. Despite a fair effort -- and researching the SiLabs Website -- I was unable to update the CP210x driver on the first PC to the same version as worked on the second PC. That said, in all cases on both machines a virtual com port was created and did seem accessible. In about 30 attempts on the first PC, I succeeded in reading all the data from a servo on two occasions, and part of the data on several other occasions. On one occasion, plugging in the STK caused my USB wireless mouse receiver dongle to go AWOL.
Debugging USB issues in Windows is way above my pay grade. Judging from SiLabs info, I got the impression that there might be a problem with "USB enumeration". I suppose such a problem might explain the intermittent success on both the PC I tried. It's worth mentioning that, even when reading the data failed, a log file was often generated that contained some data -- possibly the device settings?
Bottom line: STK + Xact is funky.
P.S. If anyone at FrSky is interested, I can provide details on the CP210x drivers, log files, and so on.
