When connecting a single motor you have to disable the axis that you won't be using in the configura

When connecting a single motor you have to disable the axis that you won't be using in the configurator or it won't read any motor data.

Ff14billy When connecting a single motor you have to disable the axis that you won't be us...

Jarmak•1/24/25, 6:16 AM

did that

f14billyOP•1/24/25, 6:17 AM

Have you tried disabling the other one? Maybe the axis in the motor was mislabeled. It's happened before.

Jarmak•1/24/25, 6:19 AM

Yes I tried both

Jarmak•1/24/25, 6:19 AM

f14billyOP•1/24/25, 6:20 AM

A picture of the board connection would help just to rule out any cable connection issues.

f14billyOP•1/24/25, 6:21 AM

Maybe the power is connected to motor 1 but the data cable is connected to motor 2 in the board or viceversa.

Jarmak•1/24/25, 6:21 AM

This doesn't seem like the led behavior walmis has described should be happening

Jarmak•1/24/25, 6:22 AM

Board looks good, the motor itself is acting like it's connected

rn_image_picker_lib_temp_43ff0ef7-a7ae-4eaf-95d7-c5b4d8d334f8.jpg

f14billyOP•1/24/25, 6:24 AM

Just in case I'd try switching the connections to motor 2 and see if you still get the same issue. Then hopefully someone here can help you.

Jarmak•1/24/25, 6:27 AM

Tried swapping the data as well

f14billyOP•1/24/25, 6:28 AM

Power and data to motor 2 and if you still get the same issue regardless of the connection then hopefully someone here can help you troubleshoot.

Jarmak•1/24/25, 6:31 AM

20V is 20V, power isn't the issue. I think it's probably a motor firmware issue and needs @walmis

f14billyOP•1/24/25, 6:33 AM

I meant to try and connect the motor power and data cables to motor 2 just in case for some reason motor 1 wasn't working well in the board

walmis•1/24/25, 6:35 AM

@Jarmak DM'd the instructions. The motor ID wasn't set for some reason.

Wwalmis @Jarmak DM'd the instructions. The motor ID wasn't set for some reason.

Jarmak•1/24/25, 6:38 AM

Thanks! Will follow and try again in the morning

pju38•1/24/25, 4:28 PM

DYI FFB Rhino kit. Windows 11 Family 24H2 26100.2894.

Rhino X/Y axes are working in Windows game controller.
Rhino auto calibration has been done without throw limiter (installed after calibration),
as documented in assembly Ref manual

Rhino X and Y axis cannot be selected in Condor3 simulator.

After Windows game controller calibration (X/Y now able to reach
Windows game controller corners), Rhino X and Y axis can be selected in Condor3.

Manual 2.2.3 throw limiter adapters : "Recalibrate the controller for the new throw ranges."

Does it mean Rhino auto calibration followed by Windows game controller calibration or
just Windows game controller calibration ?

Thanks

pju38•1/24/25, 4:28 PM

pju38•1/24/25, 4:30 PM

TheAmazinGreat•1/24/25, 4:36 PM

Per Walmis from another thread: “VP configurator currently deletes any calibration of the axes it finds in the registry, to avoid undefined behaviour with FFB…”

So the windows calibration shouldn’t matter. The reason it isn’t reaching the corners is because you are calibrating in VP software before you install the limiter. I know the manual says to calibrate prior to limiter install but try doing the calibration in the VP software with the limiter installed and then try condor again.

TheAmazinGreat•1/24/25, 4:38 PM

With limiter installed and calibration done in VP software the windows controller should see the full corners. But the windows controller shouldn’t need any calibration.

TheAmazinGreat•1/24/25, 4:41 PM

@pju38 ^

Wwalmis @Jarmak DM'd the instructions. The motor ID wasn't set for some reason.

Jarmak•1/24/25, 6:37 PM

This solved the issue, thanks!

Padinn•1/24/25, 10:02 PM

Hey guys, I noticed the covers for the cogs aren't sticking too well to the base - we had a lot of cold weather here recently and I suspect that cauesd the glue to weaken. Any ideas on how I can secure them better?

Jarmak•1/24/25, 10:12 PM

Hey stupid question: trying to mark the motor's center of rotation by setting endpoints to 0 and 4096 and turning on the spring... but it's displaying an X value of 0048 with the spring on...shouldn't it be 2048?

Jarmak•1/24/25, 10:14 PM

nm it was a stupid question, I'm looking at the wrong x value, raw x is showing 2072

Rocco Thamanoidis•1/25/25, 12:58 AM

Walmis, I'm onto something for the motor disconnect/timeout failure that occurs so often to some users incl. myself while flying DCS: Most likely its TelemFFB looking for Microsoft Flightsimulator and trying to connect to SimConnect!!

Rocco Thamanoidis•1/25/25, 12:59 AM

Rocco Thamanoidis•1/25/25, 1:00 AM

So the solution meanwhile is to disable "MSFS 2020/2024 Support" while running DCS:

Rocco Thamanoidis•1/25/25, 1:02 AM

I was testing for the past 8hr and didnt have a single motor timeout/disconnect. Usually the Rhino shuts itself down like every 10-30min.

Rocco Thamanoidis•1/25/25, 3:27 PM

Also today not a single shutdown, man thats so amazing. All those painfull weeks of troubleshooting, crashes due to disconnections. I was almost about to send the Rhino back for repair. I assume the rapid and constant searching for the simconnect connection makes it so unstable.

Bob Bushman•1/25/25, 3:48 PM

for the time being.
I'd say PIN THIS!

Reed•1/25/25, 5:41 PM

Who is running a PCIE card that adds USB’s I’ve got a four port USBPCIE card that I want to install in my open PCI slot so I can move some of my controllers back to the main PC. I’ve got a powered at USB hub is full and I’m adding a couple of more controllers to my pit has anyone seen any performance derogation if that PCIE slot is on the same lane as one of your M.two drives

Nathan Woodward•1/26/25, 12:49 AM

Having a problem I can't figure out. After setting up and installing my Rhino, DCS will not load past the initial splash screen. The instant I unplug the Rhino USB, DCS gets past the splash screen and loads up. If I plug the Rhino back in at this time, no buttons on the stick are recognized ..... It DOES show up on the Controls list as a device, however no button presses are recognized.
Within the Rhino software, all button presses are recognized.
Thoughts/help??

Priest•1/26/25, 2:56 AM

try rescan devices button within DCS?

PPriest try rescan devices button within DCS?

Nathan Woodward•1/26/25, 3:02 AM

While this may help it register within DCS, I don't think it will solve the primary problem, that of freezing DCS at the splash screen.

Number481•1/26/25, 3:05 AM

1st suggestion is to look at the DCS log to look for errors when it is initializing the joystick devices
Barring any obvious errors in the log....
- if its on a USB hub, try direct attach to PC
- remove any mods
- slow repair DCS

Nathan Woodward•1/26/25, 4:04 AM

Looks as if I've fixed it. I rolled the software back to the prior Beta version, and it's been working since. Not sure if there's something wrong with that .2 beta version software, but there certainly seemed to be, for me

Nozzledude•1/26/25, 7:06 AM

Recent rhino install in dcs, all has been fine till tonight it would suddenly “beep” and shut off. Did it every 10-15 mins. On debug page see undervoltage error:

Nozzledude•1/26/25, 7:06 AM

Nozzledude•1/26/25, 7:07 AM

Comes back after cycling the red button.

NiccoSWE•1/26/25, 9:50 AM

I had TelemFFB working fine, and then I installed Simhub and it stopped working. I get no telemetry data from DCS, and from what I can tell the export.lua file seems to be set up correctly. Feels like I'm missing something, can someone point me in the right direction? I'm getting a lot of this in the dcs.log: 2025-01-26 10:37:26.516 ERROR Lua::Config (Main): Call error LuaExportAfterNextFrame:[string "C:\Users\nikla\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\lib\io\UDPSender.lua"]:30: attempt to call method 'send' (a nil value)
stack traceback:
[C]: in function 'send'
[string "C:\Users\nikla\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\lib\io\UDPSender.lua"]:30: in function 'send'
[string "C:\Users\nikla\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\lib\io\UDPServer.lua"]:45: in function 'send'
[string "C:\Users\nikla\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\lib\ConnectionManager.lua"]:64: in function 'send_packet'
[string "C:\Users\nikla\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\lib\ConnectionManager.lua"]:54: in function 'send_queue'
[string "C:\Users\nikla\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\lib\BIOSStateMachine.lua"]:156: in function 'step'
[string "C:\Users\nikla\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\BIOS.lua"]:226: in function 'SimLuaExportAfterNextFrame'
[string "C:\Users\nikla\Saved Games\DCS.openbeta\Scripts/TelemFFB.lua"]:1587: in function 'PrevLuaExportAfterNextFrame'
[string "C:\Users\nikla\Saved Games\DCS.openbeta\Scripts/TacviewGameExport.lua"]:70: in function 'W'
[string "Luraph"]:1: in function <[string "Luraph"]:1>.

Tomsk•1/26/25, 4:27 PM

Hi I received my VP Force Rhino a month or so ago and broadly it's great. The only problem I'm having is with the VKB Adapter I bought to go with it: I'm finding that sometimes the buttons in my VKB Gunfighter MCP work okay .. but sometimes they don't. The VKB Gunfighter MCP stick works perfectly on its own VKB provided base, so that doesn't seem to be the issue. I've tried really seating the gunfighter into the VKB adapter as best as possible and really screwing it in tight so it doesn't move at all and have issues with the contacts. However, I'm still finding it very unreliable. My sense is the adapter is not making good contact with the 3 pins on the stick and so is cutting in and out. I've tried cleaning the contacts on the adapter with a cloth, but that doesn't seem to have helped much either.

Is this a known issue? Is there a way to fix it? Or should I seek to return my VKB Adapter as defective and get a replacement?

Vakarian•1/26/25, 4:50 PM

The actual mechanism with those pogo pins is a hit/miss. That's likely why VKB went with another revision to fix those intermittent connection issues. I've had it for a while with the VKB base, changed few of those contact plates sent from VKB, but it was all fine until the pins made some gouges and then the issues started to appear.

The way I see it you have 2 fixes.
1. Less intrusive.
Just add some solder on the pads to increase the contact area. It should help
2. Taking sledgehammer approach.
Directly solder the wires coming from the adapter to the wires coming from the grip. Upside, no frigging way you'll lose contact. Downside, changing grips is "problematic" to put it mildly unless you go nuts and add additional connectors to be able to separate them.

This is what I did, option 2. Wouldn't recommend it outright, but as I only have one grip (MGCU), this was a result of some thinking. Ever since I've done that, 0 connection issues have happened.

Tomsk•1/26/25, 4:52 PM

Yeah I did think the VKB pins look like a crappy design. I'll definitely consider attacking it with a soldering iron. I also only have one grip and soldering it to the black box unit wouldn't be a terrible loss from my POV.

VVakarian The actual mechanism with those pogo pins is a hit/miss. That's likely why VKB w...

Tomsk•1/26/25, 4:56 PM

I'm guessing it's fairly obvious which wires to connect?

Vakarian•1/26/25, 4:57 PM

Walmis drew the pinout diagram somewhere in the discord, but it's easy to follow it up if you take a bit of care when removing the small PCBs where the pads and pogo pins are. Those are marked with + / - / data lines, so just connect them and you're fine

Vakarian•1/26/25, 4:58 PM

IIRC, Red is +, Black is - and the Yellow one is the data

GettinBetter•1/26/25, 10:44 PM

I've ordered a couple of motors in the FFB kits, will there any cables in the box?

GGettinBetter I've ordered a couple of motors in the FFB kits, will there any cables in the bo...

smitty•1/26/25, 10:47 PM

you will need USB-A to USB-B cables

smitty•1/26/25, 10:48 PM

and however you want to hook up the 24v can be whatever connector you like

When connecting a single motor you have to disable the axis that you won't be using in the configura

Similar Threads