Open question: is there any potential for either the Rhino software or the TelemFFB to cause a CTD f
Open question: is there any potential for either the Rhino software or the TelemFFB to cause a CTD for the other person in a multi crew module?
WYou mean on the other end of a network cable? No chance
AI’ve played CP/G in the Kiowa in DCS a couple of times now, and with different people in the pilot seat. Every single time, the game has crashed on the pilot’s end.
Other people in the group have played the Kiowa without experiencing this, and AFAIK no one else has a Rhino.
It’s a long shot and likely caused by the Kiowa just being unstable, but just gotta ask
Other people in the group have played the Kiowa without experiencing this, and AFAIK no one else has a Rhino.
It’s a long shot and likely caused by the Kiowa just being unstable, but just gotta ask
AAight, it did seem far fetched, but had to ask just to rule it out
TI assume you’ve mapped pilot’s commands, as well as co-pilot’s? It’s not supposed to let those commands go through if someone is in the other seat, but maybe it is and that’s breaking something? Only flown SP in the Kiowa so far but it’s fun!
OJust finished installing my Rhino, running cables, etc. I noticed that it runs pretty well in DCS just with FFB checked. What do people tend to run for default/basic settings in Rhino configurator?
Bhow do i roll back the firmware, it broke my rhino
Awhat broke? (not sure how to roll back, tbh)
Bi think the issue was i chose to update the firmware before updating ffb configurator, seems fixed now
Bthanks!
Aword, glad you got it sorted -- but yeah -- i assume once you've flashed the firmware, you will require the new configurator software or else it probably won't know how to talk to the rhino
OJust tried the new beta firmware and the fan control is a godsend for my ears 
Question though - any advice on fan settings to use or avoid? Can we raise the fan start temperature to 40 or 45 or not recommended? Is 25% starting fan ok or again not recommended.
Just some general parameters that the motor should be operating under would be helpful to understand whats ok and not ok with the fan control (I'm pretty sure I didn't see this in the change log - apologies if its there).
And thanks again for implementing this! I personally feel its a really nice QoL upgrade as the fan was very loud before and now its much much quieter (even if it runs for longer now).
Question though - any advice on fan settings to use or avoid? Can we raise the fan start temperature to 40 or 45 or not recommended? Is 25% starting fan ok or again not recommended.
Just some general parameters that the motor should be operating under would be helpful to understand whats ok and not ok with the fan control (I'm pretty sure I didn't see this in the change log - apologies if its there).
And thanks again for implementing this! I personally feel its a really nice QoL upgrade as the fan was very loud before and now its much much quieter (even if it runs for longer now).
HThe earlier and the more you cool the better. If you NEED all the cooling depends a lot on what you do. When you just fly helicopters you won't need much cooling. When you do a lot of high-G dogfighting (in an F-16 e.g.) You want all the cooling all the time if you ask me.
HThe problem is, that the temperature that is actually measured is the one of the motor-driver. The motor themselves serve as giant heatsinks. Which is nice for short temp-spikes of the drivers because they cool down again very quickly. Once the motors themselves are heated up though..... A continuous light cooling would be best in my opinion, so that they don't heat up that much in the first place.
OThanks. I'll start the fans from an early temp then (maybe 35) but at a lower speed so that there's at least constant airflow 
HI think that's reasonable. My plan as well. Just have them running constantly but almost inaudible and have them ramp up at their usual treshold (50 C I think).
HJust help to cool down the thermal mass a little all the time.
RSomething went off, I've got joystick and pedal going on but only one of the board can be connected after the firmware update. Any way to fix this? I checked the PID is unique to each joystick(2055) and pedal(2052).
RI should have said ''one at a time'. The second one gets detected as USB as beep goes, but it gets ignored on configurator, then USB gets disconnected on second board after a while.
WDo you use a USB hub?
What does USBDevView show? https://www.nirsoft.net/utils/usb_devices_view.html
What does USBDevView show? https://www.nirsoft.net/utils/usb_devices_view.html
NirSoft
USBDeview is a software that lists all USB devices that connected to your computer, and allows you disable, enable or uninstall them.
RThank you for looking into this, I have a Sabrent powered USB hub. I'm trying the USBDview now, I see [Rhino FFB Pedal] (Green) while the Rhino FFB Joystick is disconnected and Pedal connected. When I connected the joystick, beep sounds but no [Rhino FFB Joystick] shows up. I noticed that [Port#0004.Hub#0013] is going red when I connected the joystick, and goes gray when disconnected. I disconnected the pedal and connected the joystick, the line [Port#0004.Hub#0013] changes to Rhino FFB Joystick.
WTry connecting one board to hub and another directly to PC or some other combination
RGot it, trying now...
RRThe quick device selector dialog is now asking which device to work on, select Joystick...worked, close the configurator and start again, select the Pedal...worked. TelemFFB launched as normal. I think I'm good now. Thank you for helping me on this, I really appreciate!
WWhat kind of hub is it? USB 2.0 high speed/full-speed/3.0 ?
RI believe the Sabrent hub is USB3.0 but I think I connected a USB2.0 hub in between to see if I can get around the USB Endpoint issue. So far I haven't seen 'Not enough resources' message after I did it. I have too many USB devices, the way how resources are being managed are quite complicated.
WYeah, the new firmware added a couple of extra auxilliary endpoints, maybe that exhausted the hub resources.
RMy brain can understand just little part of the endpoint calculation but yes, that explains! Thank you again for saving my weekend, and introducing me the USBDeview, I was been using Microsoft USB Device Viewer but the USBDeview gives far better idea of what's going on.
QI’ve been reading through the old posts about the F4 pitch up issue and checking things list axis conflicts (I have none) and other settings. The only solution I’ve found that works is to disable FFB in DCS but then you don’t get stick trim that stays in place. Was a solution ever found that allowed both to work? I’m using TelemFFB and VPforce with a Winwing adapter and extension
MIs the joystick supposed to show up as a mounted drive in the windows toolbar (like I could click eject on it as if it was a memory card)
WYeah, that's a bug in Windows
NI don't understand. The issue that was being discussed the other day was related to having FFB enabled in DCS but not using a FFB joystick.
The F4 works just fine, trim and all, when using the Rhino.
The F4 works just fine, trim and all, when using the Rhino.
HYeah, here as well. No problems with the Phantom. Everything works as expected for me. (Rhino Stick and ffb pedals)
OWorking great so far
OMig-29 feels a little FBW, which it isn't. But I haven't used configurator or telemffb at all yet
HDid anyone have any buttons on their grip stop working after updating to 'v1.0.17b1'? I have a VPC MongoosT-50 CM2 grip connected to my Rhino. The forward and aft inputs of the 2-way+push on the right side have stopped working after the Rhino update yesterday. When connected to my Virpil CM2 base it works normally (confirmed by VPC Configuration Tool and Windows Game Controller), but when connected to the Rhino base, the fore and aft presses aren't detected. Downward press still works. I have VPC T-50 CM2 selected in the Grip Type drop down just as I did before updating. I noticed that the fore and aft presses are detected when I select Generic Grip or most of the other VPC choices, but using those can cause other conflicts. If it helps, the non detected inputs are normally listed in Windows Game Controller as 18 and 19, and 28 and 29 in VPC Configuration Tool.
ONope, just mapped those today actually
HHmm. Guess I'll play around with the settings, then. It's just weird that it's only with it on the Rhino, only with the CM2 grip type selected, and only after yesterdays update.
P@walmis hey m8, sorry again for ping. Is there a trick to removing the 3d printed grip attachment part? It seems to be on there really tight & I'm worried about damage to the gimbal??
Pshould I remove the metal shaft first?
Pok got the 3d part off but there is now way to install the new cable without cutting the plug end off & I don't have the tools to redo a plug like that?? 
PI got it sorry I'm a bit slow sometimes 
F@hectik me either
PAny idea what size screws I need for attaching the cable head to the new cnc bit?
W
KM3 x 8 mm Countersunk work well.
Pcheers m8
HJust for clarification, you mean you're having this problem too?
FYeah, I also uses cm2 grip and 2-way is not working after the firmware update
HSame here - not working after the firmware-update. It's probably an easy fix once identified. Let us know what we can do to help, Walmis 
