RThe FFB is back on the dcs now, I plugged the pedal back on. Now both the VP-FFB boards are directly plugged into the computer, not via USB HUB. Thank you again Walmis, I'll forcus on USB moving forward. I really appreciate!!!
WTesting, mostly
NUh... I get this from the que bot this morning:
Nis that a minus or a ~?
Pit's approx 36 days
RHello, the axis on my unit do not appear to be reading. VP force sees that the USB in connected but no axis. Same goes with the webpage that pops up when you plug in the base. Does read any axis movement.
For background, I’m plugged directly into a known working USB on my computer.
Additionally, the female barrel power port on my unit has come untethered to the base. Not a very great design.
Any help appreciated.
For background, I’m plugged directly into a known working USB on my computer.
Additionally, the female barrel power port on my unit has come untethered to the base. Not a very great design.
Any help appreciated.
FI think both issues are related. Can you take a picture of the configurator screen and of the female barrel power port? My guess is that there's no power to the motors due to the power port issue.
CPutting this here for others with same issue. Had a problem with my beloved Rhino yesterday. It stopped reading the axes or moving. The potentiometer would still work. After a little bit of troubleshooting, I realized that the emergency stop knob seemed loose in its housing. After searching in vain for a YT video of someone taking apart one of these beasts, I gave up and started removing screws. I started on the top, which was.. wrong. Eventually I moved to the back side. After pulling away the side I discovered the knob had loosened enough to twist a little every time I turned it back on. The two wires twisted around each other until eventually one pulled free of its terminal connector. Repair would have been simple if I'd had the same terminal connector. Instead, after trying forever to uncrimp it, I just gave up, removed the wire, soldered it to the connector and reinstalled. I did my best to tighten the emergency stop knob back up, but it's hard to get a good grip on it, and I could see having to do this again in the future.
CVisual aid:
CI was tempted to try and fab away to keep the nut from rotating, but I couldn't bear the thought of drilling into my precious. Oh, and if anyone knows the part number or size of those terminal connectors, pass it along, so next time I don't need to solder.
WYeah so that's the symptom of no power to the unit. While USB powers the controller, there's no data from the motors. Make sure the DC plug is all the way in and e-stop switch is de-pressed.
Putting some superglue on the DC connector shell from 3 sides and inserting it back into the plastic shell will do the trick (apologies due to QC mistake) .
Putting some superglue on the DC connector shell from 3 sides and inserting it back into the plastic shell will do the trick (apologies due to QC mistake) .
WThe terminal is 2.8mm / 0.5mm
RThank you for the reply. Apologies if it sounded harsh. At this point I think I’ll need a new base-side plug. Would you be willing to provide a part number for the power plug?
Mis it normal to hear and feel a loud clicking when pushing against the spring in the Rhino ?
MHi, I have a problem after updating the firmware as prompted. Seemed to go fine but when I started DCS up, there was an error message about the firmware . In FFB config, it says I am at N/A version. When I try and update again, I can pair and connect, but pressing the "update firmware" button does nothing. And I have and error saying wrong firmware configuration version 182, expected 181........can someone help?
Mon the update tool it says device firmware is v1.0.17b3
MBut I only see v1.0.17b2 available on the list
WLatest firmware is b3
Latest app is b2
Get the latest app and it should be good. You're probably opening the old v16 app with the new firmware installed.
Latest app is b2
Get the latest app and it should be good. You're probably opening the old v16 app with the new firmware installed.
IQuestion about the limiter adapter, have a 20cm extension with the Rhino base, many times the fans start and the FFB resistance goes away after a prolonged dogfight with WWII planes in DCS, by adding a limiter adapter, will that reduce motor stress somehow and allows for longer dogfights before the fans kick in and the force goes away?
HIt all boils down to how much amps are applied at maximum deflection/spring. You can check that with the telemetry provided by the VP config. If you want to extend the time of unlimited force, you either need to increase cooling (pretty hard because the hardware doesn’t exactly excel at heat dissipation) or limit the power. (e.g. reducing the spring force gain)
HTo directly answer your question - no, limiting the throw on its own doesn’t help.
HWith the new fan control option, I would recommend to have always a small airflow around the motors. In other words, start earlier with the cooling.
HReducing Master Gain would also slow down heat buildup.
IHow do I get the new fan control option?
HLatest firmware updates and software updates.
IThanks will check them out
I
WUgh, that pesky bug
ISeems to be I already have the latest firmware since when I go with the mouse over Update Firmware does not do anything
WTry this fix,
Device Firmware: -PS C:\WINDOWS\system32> "HKLM:\SYSTEM\CurrentControlSet\Enum\USB\VID_FFFF&PID_2055&MI_03*\Device Parameters" -Name "DeviceInterfaceGUID" -Value "{DA10CDEF-26A6-47D9-970E-B3D561A277FA}"
At line:1 char:87
At line:1 char:87
- ... t\Enum\USB\VID_FFFF&PID_2055&MI_03*\Device Parameters" -Name "Device ...
~
Unexpected token '-Name' in expression or statement.
At line:1 char:93- ... D_2055&MI_03*\Device Parameters" -Name "DeviceInterfaceGUID" -Value ...
~~~~~
Unexpected token '"DeviceInterfaceGUID"' in expression or statement.
At line:1 char:115- ... MI_03*\Device Parameters" -Name "DeviceInterfaceGUID" -Value "{DA10C ...
~~
Unexpected token '-Value' in expression or statement.
At line:1 char:122- ... "DeviceInterfaceGUID" -Value "{DA10CDEF-26A6-47D9-970E-B3D561A277FA}"
~~~~~~~~
Unexpected token '"{DA10CDEF-26A6-47D9-970E-B3D561A277FA}"' in expression or statement.- CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
- FullyQualifiedErrorId : UnexpectedToken
IGet an error
IFix does not work for me
WCopy the full line, I see you pasted a truncated string
IPS C:\WINDOWS\system32> Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Enum\USB\VID_FFFF&PID_2055&MI_03*\Device Parameters" -Name "DeviceInterfaceGUID" -Value "{DA10CDEF-26A6-47D9-970E-B3D561A277FA}"
PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32>
IThis is good?
WYep, worked
IThanks
Iwhen trying to install latest configurator I got this message
I
WYou need to get back and update the firmware now, see if the Web page now allows to update after the powershell fix
IIt does not allow the update
WDid you replug USB and/or reboot ?
IYes
Ieven rebooted
IDid it again now works
IUpdated to latest firmware and software, so in fan control you recommend I setup the fans to start earlier at lower temps?
I
Iwhat settings would you recommend here?