VKB-SIM

Hey guys,

some while ago, my MK V rudder pedals stopped working. I've tried various attempts at fixing it (flashing new firmware, setting to default, re-calibrating etc., using a different connection cable), but nothing has worked.
In the configurator, the pedals are connected, but there is no response.

When I've plugged them in, I just saw that today that only one of the LEDs in the back lights up when I plug in the RJ45 cable (i.e. the one connecting the pedal unit to the black box). Is that normal? IIRC, both LEDs used to light up. Might this be a hardware defect, and if yes, something I might be able to fix myself?

Thanks in advance

Attach your profile (in the archive), without it it is difficult to find the error.

Here's an image of my profile. Hope that helps.

This is not a profile, this is a screenshot of one tab from the profile. A profile is a configuration file with the *.cfg extension, which is created and saved on the drive using the Save button in the Action tab. This is what needs to be archived and attached to the post.
But even this screenshot shows errors that prevent the pedals from working.
Usually, pedals connected to one BB with GF are placed on the 7th axis.
But you do not have the En and Vs checkboxes there, which allow them to work.
I also draw your attention to the fact that none of the axis (most likely the trigger axis on the VC2) is calibrated.
Therefore, it is impossible to talk about adequate operation of the joystick in this case.
I advise you to read the manual and the video from official VKB sources for further bug-free operation of any devices of this company.

Thanks for the reply, but for some reason, the forum doesn't allow me to upload .cfg files (hence the screenshot). I'll try if I can rename it and attach it under a different name.

Before posting here, I've tried numerous things. Here's a setting I found on a different website (picture of the profile tab ), but that didn't work either. I've also checked the En and Vs checkboxes, but that didn't work either.

Well here's the thing, the software doesn't let me calibrate my device. When I click on calibrate and move the axis, nothing happens. In the VKB Joy tester, I don't see any reaction either.
I've tried flashing it with the latest firmware and setting it to default with the Config software a number of times, but calibration isn't possible.

I've tried setting the pedals up as described in the manual on pages 15 and 18 (physical and logical axes), but that didn't work either.

Zip your *.CFG file and attach it to the post.

Here you are.

With the pedals connected to one BB with GF, do the following:
1. reset to default using the button in the configurator
2. after rebooting, agree to the offer to auto-configure the connected devices
3. after auto-configuration, agree to the offer to calibrate all axes, having first smoothly pressed the metal trigger on the MCG handle from the Armed position (lowered down) to the stop and smoothly released to the center, during calibration, smoothly press again to the stop->release to the center->throw up
calibration can be done "in the dark", without opening the Test tab, just move all the axes within the desired range
4. after this process, archive the new profile again and attach it to the post

Thanks for your quick reply. I followed the steps you described.
The configuration file is attached. Unfortunately, it still doesn't work.

In your new profile, the En and Vs checkboxes are inactive and again, none of the axes are calibrated.
Check these boxes, press Set to write the changes to the controller and calibrate all the axes.

Do you have a stick connected? If not, the black box reporting as "Gunfighter Modern Combat Pro" after default/autoconfig could point to the rudder pedals not being detected by the black box. That could be anything from a defective cable to an issue with the controller board on the pedals.

Can you give us a screenshot of the external devices test window? Select test at the bottom of the window, then external on top of the config item box, right underneath the toolbar. If the hardware is working, all items should show up in green with near-zero values on all the bargraphs, if they are all red then we should look into hardware troubleshooting.

You don't reset to default, that's where the problems come from.
Or after reset you upload the old profile.

I can reproduce the situation (En and Vs off on logical 7) on a BB3 with no connected bus device. Autoconfig gets ignored, calibration leads to "twist not present" popup, confirming that popup leads to an unassigned axis.

Delta, can you record a video where it will be visible that after default there are no checkboxes and there are four devices in Global-External?

Delta wrote:Do you have a stick connected? If not, the black box reporting as "Gunfighter Modern Combat Pro" after default/autoconfig could point to the rudder pedals not being detected by the black box. That could be anything from a defective cable to an issue with the controller board on the pedals.

I disconnected the stick before testing. I have a VKB stick, but it has a USB connection.
When I flash the firmware, the pedals show up as "VKB T-Sim rudder". Then the configurator tells me that I need to configure the controller. Up until then, box #7 is still checked.

I click on yes.

I click on start calibration, with all the axes checked, then move the pedals around and click on end calibration. I hear a disconnect- and reconnect sound over USB, and then the designation changes to „VKBSim Gunfighter“ in the top window. Then the configurator tells me I need to configure the controller. I click on yes, and it tells me that the „twist module is missing or blocked“ and asks me to fix it. When I click on yes, box #7 disappears.

Can you give us a screenshot of the external devices test window? Select test at the bottom of the window, then external on top of the config item box, right underneath the toolbar. If the hardware is working, all items should show up in green with near-zero values on all the bargraphs, if they are all red then we should look into hardware troubleshooting.

Here's a screenshot of what it looks like.

I've tried different connector cables and different USB ports, all with the same result so far.