ROWSFIRE SUPPORT

How can we help?

Find setup guides, troubleshoot your panel, or get in touch.

Search quick answers and guides, or choose a topic below.

01 · Find help

Find product support.

Choose the exact panel. Read the label on the rear; do not open the case to find it. If the revision is unclear, send a label photo and use Unknown rather than guessing firmware.

Overhead & control panels

Displays & instruments

Frames & stands

Choose your model to see available guides. For an unlisted model or uncertain revision, contact support →

Troubleshoot by symptom

What’s happening?

Choose a symptom to follow guided checks.

View all problems ↓
Browse the help library

All guides and answers.

Search a symptom or choose your model. For repair instructions or an unlisted hardware revision, contact support with a photo of the rear label.

Choose a model · all panels
FixWhere do I download the Rowsfire App, drivers and configuration files?
Get the current Rowsfire App and release notes from the official App page. Use the Resource Hub or the QR card supplied with your panel for model-specific instructions and files. For legacy MobiFlight configurations, confirm the exact panel, hardware version and aircraft first. If a file is missing, contact support; not every historical configuration is a public download.
FixMy panel is not detected by the computer (no COM port)
  1. Read the rear label and follow that model’s cable diagram. Connect one panel with a known-good data cable.
  2. Open Windows Device Manager before and after connecting it. Look for the expected USB/input device or COM port. Some device workflows do not use a COM port.
  3. If nothing changes, try another data cable and rear motherboard USB port. If Windows shows a warning, record its exact message before choosing a model-specific driver.
  4. If Windows sees the device but the App does not, close other software using the same port and check the supported model/revision in the current App guide.

Result: note whether Windows detection, App identification or both fail. If still unresolved, include the label photo, before/after Device Manager screenshots and the cables/ports tested. A missing COM port alone does not identify a failed part.

FixThe Rowsfire App says "no Rowsfire device detected" the first time I use it
A “no device detected” message can have several causes: cable or driver issues, a COM port already in use, or firmware that does not match the selected workflow. Check the current panel installation instructions first. Identify the exact model and hardware version before selecting any firmware. Do not treat every first-use detection failure as normal or flash firmware merely to try it. If the correct option is unclear, send support a photo of the label.
FixWhich firmware should I flash? (hardware version on the label)
Match the firmware to the exact model and hardware revision on the rear label using the current installation instructions. Similar product names or V1/V1.1/V2 labels are not interchangeable. If the label and App dropdown do not clearly match, send both photos to support before uploading. Do not try several firmware revisions as a detection test.
FixKnobs turn the wrong way or show wrong values (A109, A111, A112, A113)
Incorrect firmware or profile selection is one possible cause. Check the model and hardware version against the firmware already installed, and check the aircraft profile. Connect one panel at a time to identify its COM port. Use the App Debug page to observe the affected control, then compare it in the supported aircraft. Only upload firmware once the matching file has been confirmed. If it still behaves incorrectly, send the test video, label photo, aircraft and App version to support.
FixThe App only detects some of my panels / can I run the Rowsfire App and MobiFlight together?
Two applications cannot open the same panel’s COM port at the same time. Close the application using that port before testing. For separate devices, Rowsfire App 3.2 and later provides Settings → General → Ignored COM ports: add ports that belong to other devices or another workflow. Do not change a device’s firmware just to make the App ignore its port. See the current App guide.
FixThe panel disconnects, restarts, or the screen dims after a while
Insufficient USB power can cause disconnects, but it is not the only cause. Test one panel with a known-good data cable on a rear motherboard USB port using its supplied wiring guide. Record whether reducing backlight changes the symptom, and whether inputs continue appearing while nobody touches the controls. Keep the hub model, power-label photo and connected-device count. If mounting a bracket or tightening a screw triggers USB faults, disconnect power and stop installation; send photos to support. Do not connect a hub power adapter to the panel.
FixEverything works in the App's Debug test, but nothing happens in the simulator
  1. Confirm the exact panel revision, simulator and aircraft add-on in the current compatibility matrix.
  2. In the App, select the intended panel/profile. Test the affected input and output separately in the supported Debug hardware test.
  3. Load the supported aircraft and follow the current bridge/module installation guide for that simulator. Compare the same control locally and in the virtual cockpit.

Result: a successful local test narrows the next checks to the selected profile, bridge and aircraft mapping; it does not prove every hardware function works. If unresolved, send both test results, App/simulator/add-on versions and the exact error or exported log.

FixSome buttons or lights do not work: how to tell hardware from software
Select the correct product and software workflow first. Test the affected input and the affected light separately using the supported local test. A response in Debug does not confirm every output or simulator mapping. For an older A101 with no light outputs, skip an unavailable LED test rather than treating it as a failure. Record what happens locally and in the simulator, including unexpected inputs while idle. Send the hardware label, software versions and comparison video if the issue remains.
FixThe backlight does not turn on, but everything else works (V3 panels)
A101A105A106A107A109
For a supported panel and aircraft profile, backlight behaviour can depend on the simulated electrical supply and lighting controls. Check the aircraft power state and panel brightness setting, then use the supported App hardware test to separate local lighting from simulator mapping. V3 is not a single specification across every model. If the test or expected behaviour is unclear, send the exact panel revision, aircraft and App version to support.
FixThe A107 V3 backlight looks weak
Brightness depends on panel revision, the aircraft lighting state and the panel’s lighting setting. In a dim room, compare the panel with the aircraft’s integral lighting and panel brightness controls adjusted appropriately. Use the current App hardware test where supported. If the panel remains unusually dim, send a photo and hardware version to support. Do not assume a front USB port is adequate because the backlight is dimmer.
FixLight leaks around a button (A107 V3)
A107
Send a photo of the affected button and your A107 hardware label to support. The fitting method depends on the revision. Support will confirm the appropriate adjustment or replacement; keep the case closed until you receive instructions for your unit.
FixA107 Pro: why do some buttons need to be pressed twice?
Latching controls retain their physical position, so their starting state may differ from the virtual cockpit. Compare the physical and simulator positions before a flight. Rowsfire App 3.2 and later includes Debug → State check: select the intended starting state and check for differences, as described in the App guide. Persistent double presses may also depend on hardware revision or the aircraft mapping; send support a video if alignment does not help.
FixThe cockpit in the sim changes when I click Run / start the App
When the App starts communicating, physical switch positions may be sent to the simulator. Set the panel to match the aircraft’s intended starting state before connecting. In App 3.2 and later, use Debug → State check to identify differences where supported. If controls still change unexpectedly, record the panel, profile, starting state and App version for support.
FixAPU and BAT 1-2 buttons do not latch or need a hard press
A102A106A107
Check the button behaviour described in the guide for your exact panel revision. Press gently in the centre; do not use extra force to make a control latch. Compare its physical action with the supported local input test and the aircraft state. If it sticks, fails to latch or feels damaged, send a short video and hardware-label photo to support.
FixThe A107 APU button clicks or sounds harsh
A107
Press gently in the centre of the button and check that it returns freely. Do not force a binding or damaged button. Send support a short video, the hardware revision and a description of whether the issue is the physical action or the simulator response.
FixA107: IR 1-3 show "OFF" instead of "ALIGN", or MODE SEL shows "OFF"
A107
Printed legends and simulator annunciations can differ between A107 hardware revisions and aircraft add-ons. A difference in wording alone does not establish an electrical fault. Compare the exact panel layout with the intended aircraft/profile. Send photos of the label, printed legend and simulator state if you need confirmation.
FixA107 Pro lights look dim
Compare the aircraft lighting state and panel brightness setting, then test the relevant lights in Debug where supported. Brightness can differ by hardware revision and lighting conditions. If the result is unexpected, send a photo or video with the hardware revision, App version and test conditions so support can assess your unit.
FixA knob is loose or slips on its shaft
Photograph the cap and shaft without opening the case. A loose cap, a broken shaft and an electronic input fault need different handling. Do not force a control beyond its stop or apply glue as a general fix: adhesive entering an encoder can damage it. Ask support for the matching part and fitting instructions. B107 brightness controls differ by revision: earlier encoder designs and later limited-travel potentiometers must not be treated alike.
FixA toggle switch handle (flat lever tip) is missing
A101A102A106A107
Check the packing list and loose-parts bags, then send support your order number, panel revision and a photo of the switch. Support will confirm the matching handle and fitting procedure. Do not force a handle onto a powered panel or use instructions for a different switch design.
FixA part is missing or arrived damaged
  1. Check the packing list, small-parts bags and all parcels for your order. Large frames and panels may travel separately.
  2. Keep the packaging. Photograph the product label, affected part, parcel and shipping label; note which ordered item or part is missing.
  3. Use the support form below and choose “Damaged or missing part”. Add the order number if available and viewable photo/video links.

Next step: support will confirm parcel status and the applicable part, repair or return route. Do not force a damaged control or send a return before the destination and procedure are confirmed.

FixThe A107 red button frame came off
Send support a photo of the detached frame and panel version. Support can confirm whether it can be refitted or requires a replacement. Do not apply glue until the fitting method and material are confirmed.
FixA107 keeps disconnecting when I turn a knob or press a button
Test a known-good USB data cable and a rear motherboard USB port using the supplied wiring guide. If a particular control consistently triggers disconnection, stop repeating the fault and send support a short video plus the hardware label. The symptom alone does not identify the board or part that needs repair.
FixA107 button does not latch / the panel looks pressed in
A107
Stop forcing the button. Send support photos of the panel surface and hardware label plus a short video of the physical action. Support will assess whether shipping damage, fitting or another fault is involved and confirm the appropriate next step.
FixWhich screws fit the VESA mount? My M4 screw is tight / too long
Use the fasteners specified for your exact panel revision and bracket. Screw length and safe insertion depth are not interchangeable; bracket thickness also matters. Do not use a single length limit for A107, A107 Pro and B107 or force a tight screw. Send the product label, bracket, hole position and screw measurements to support if uncertain. If mounting causes USB faults or suspected contact with the board, disconnect power and stop installation until support reviews it.
FixThe panel surface looks scratched or old
Check whether the visible marks are on removable protective film before judging the panel surface. Do not peel a bonded display or printed layer. If the correct layer is unclear, send a photo to support before removing it.
FixHow do I update the firmware?
Identify the model and hardware revision, then follow the firmware procedure linked from the official App page or the Resource Hub. Back up any custom configuration first. If an upload fails, record the full error and stop; ask support for revision-specific recovery instructions. Do not reset an unidentified board or try firmware for a different revision.
FixThe Rowsfire App installer or update shows an error
Record the full installer message. If it reports a directory link/junction, check the actual MSFS package location rather than guessing a drive or folder. Follow the current App installer guide for the correct Community/bridge location. Close the App and simulator before retrying a file-in-use update. If bridge installation is skipped, the App may install but simulator communication still needs the correct bridge. Send support the error, App version and simulator edition if uncertain.
FixWindows Defender or antivirus flags the Rowsfire App
Download only from the official Rowsfire App page and its linked repository. Record the exact detection name and file version if Windows or antivirus blocks installation. Do not assume every warning is a false positive, and do not disable antivirus or add a broad exclusion as a standard fix. Ask Rowsfire support to verify the specific file and warning before proceeding.
FixSomething stopped working after updating MobiFlight
Back up your custom MobiFlight configuration and note the last working versions. Compare your exact panel/aircraft combination with the current Rowsfire App compatibility list before changing workflows. A legacy configuration may need a matching update; ask support which file and version to use. Do not assume every historical MobiFlight configuration is actively maintained or that every product can migrate to the App.
FixConflict with Winwing SimAppPro / WinCtrl
For a legacy MobiFlight setup, another application may already be opening or scanning the panel’s port. Close the conflicting application and test MobiFlight with one panel first, then reconnect other devices one at a time. Match COM-port ownership to the intended workflow. Do not reflash firmware just because another brand’s utility is installed.
FixMobiFlight (legacy): using several panels or several aircraft at once
A102A103A107
Back up your configuration first. In legacy MobiFlight versions that provide File → Merge, open the first matching configuration and merge the next panel’s file as described in that version’s guide. Confirm each module/serial assignment and test one panel at a time. A non-working panel or warning can also have other causes; it does not prove the files were not merged. Do not merge several aircraft profiles indiscriminately. Send the MobiFlight version, aircraft and supplied filenames if uncertain.
FixMobiFlight (legacy): a red warning switches between OVHD LT and OVHD LT(off)
A101A105A106A107A109
In some legacy configurations, mutually exclusive lighting conditions can leave an inactive output flagged. A red warning is not automatically harmless: inspect its exact message, the affected output and the matching configuration. If lighting does not follow the intended aircraft state, send the warning screenshot and configuration/version details to support.
FixMobiFlight (legacy): A103 lights do not come on when pressed
A103
Confirm the A103 revision, aircraft and matching MobiFlight configuration. An interrupted import is one possible cause; compare the import steps with the supplied guide before re-importing. If the light still fails, record the local output test and simulator result separately and send them to support.
FixMobiFlight: knobs send changing values while untouched
First record the hardware revision, MobiFlight version and matching configuration. Leave the panel untouched and capture an input log: note which knobs generate events and whether backlight position changes the behaviour. Historical sensitivity/filter changes are not a universal fix across A111, A112 and A113 revisions. Do not copy a sensitivity value or rewrite PWM settings from another model. Send the log and label photo to support before changing firmware or opening the panel.
FixA102: which configuration file should I use?
A102
A102 only works with the A102 file. Do not use the A101 or A106 files.
FixA108 is not recognised / the screen shows no image
  1. Identify the exact A108 revision and whether its instructions use an HDMI pop-out or a supported App instrument-display mode.
  2. Follow that revision’s cable diagram. In Windows display settings, check whether the screen is detected and can show an image.
  3. If the Windows desktop is visible but instruments are missing, check the selected aircraft, instrument window and layout/binding instructions.
  4. Test USB/button detection separately from video. A working image does not confirm the controls are connected.

Result: tell support which stage fails: display detection, image signal, instrument layout or controls. Include the label, cable connections, Windows display settings and software/aircraft versions. Do not add an unspecified power supply or flash firmware just to fix a missing instrument window.

FixA108 layout is not saved and must be adjusted every time
Record the software version, layout name and what happens after saving and restarting. Older A108 instructions require a name made only of letters and underscores; try a new name such as fenix_a320_layout when checking that older workflow. This is not a confirmed restriction for every current version. Keep a screenshot and contact support if a newly named layout still fails to persist.
FixA108 PFD / ND is laggy or slow to refresh
Update from the official App page and check the release notes for screen-mirroring improvements. Confirm the supported aircraft, display connection and layout settings, then compare the behaviour again. If lag remains, send the App version, simulator, aircraft version and a short video; an update does not guarantee every display-delay issue is fixed.
FixB107: the two displays are blank or show 0 with PMDG (LAND ALT / FLT ALT = 0)
For the supported PMDG 737 setup, missing data broadcast can leave LAND ALT / FLT ALT blank or at zero. Follow PMDG’s instructions for the active aircraft installation and back up the configuration first. For versions that use 737_Options.ini, confirm whether PMDG requires an [SDK] section with EnableDataBroadcast=1. File location and applicability depend on the simulator/PMDG version. Restart the simulator after a confirmed change. Ask support if you cannot identify the active file; do not edit every copy found on the PC.
FixB107: the EGT or APU needle is not at zero
For the matching B107 revision, open Settings → Calibration in the App, select B107 and open its port. Use the calibration Move control to bring the needle to zero, then select Set Zero, as described in the supplied guide. Use the movement step specified in the guide for your hardware revision. Stop if the needle or controls behave unexpectedly; send support a video and your versions. Do not move the physical needle by force.
FixB107: dimming does not work with PMDG 737
B107
Check the current release notes and the exact B107/PMDG 737 combination on the App page. Compare the simulator brightness setting with the supported local lighting test. If dimming still fails, send the panel revision, App and PMDG versions and a short video. An App update alone is not a guaranteed fix for every dimming fault.
FixB107 V1: some lights do not turn on in the App test
Use the correct B107 revision and supported App hardware test. Record which lights fail, the hardware label and a short test video. A failed light alone does not identify a chip or establish that board modification is required. Support must diagnose the unit before any internal repair.
FixB107: the displays update slowly when I turn a knob
Use the current App and check the release notes, then record which display lags, how the knob is moved, and the aircraft/version. Send support a short comparison video. Include your App version and whether the delay also happens when using the on-screen control.
FixB107: the EMER EXIT LIGHTS guard turns the switch to ON instead of ARMED
First distinguish physical movement from simulator mapping. If closing the physical guard pushes the real switch into an unexpected position, stop forcing it and send a close-up video plus the B107 revision. If the physical switch is correct but the virtual control differs, compare the local input test with the supported aircraft/profile and record the App and add-on versions. These two symptoms need different checks.
FixB107: a switch came out of the panel
Stop using the detached switch and send support photos of the switch, panel and hardware label. Support will confirm the appropriate replacement part, repair or return route. Do not force it back into the panel. Soldering or dismantling should follow the approved procedure for your unit.
FixA107 Pro is not recognised although I installed FSUIPC7 and MobiFlight
For A107 Pro, follow the Rowsfire App installation instructions for the exact hardware revision. MobiFlight or FSUIPC installation alone does not configure the Rowsfire App workflow. Check USB/driver recognition and whether another application owns the COM port. Do not assume either program’s presence is itself the fault.
FixA101 V3 does nothing in the A310
A101
A101 V3 currently lists Fenix A320, FBW A32NX and ToLiss A319/A320/A321 in the published App matrix; that matrix does not establish A310 support. Check it again for your installed App version before troubleshooting mappings. Seeing an aircraft name in a selector does not itself confirm support. If you use a legacy/custom A310 profile, send its name and version so support can assess that separate workflow.
FixWhich version is my A105: V3.0 or V3.1?
A105
Start with the rear hardware label and the supplied order/model documentation. Compare the control shown in the guide with your unit, without forcing a knob past its stop. Physical knob travel can be a clue on some A105 revisions, but should not be the sole basis for selecting firmware. If the revision is missing or unclear, send support the rear-label photo and a full front-panel photo before uploading.
FixD104 G1000 MFD is not recognised
Confirm whether Windows detects the D104 USB/input device separately from the display. Use the supplied connection guide and record the exact hardware label, software workflow and error. If firmware recovery is needed, have support confirm the matching file and procedure for this revision before uploading. Do not flash an unknown QR-folder file as the first detection test.
FixA117 and Winwing (WinCtrl) EFIS: what does "compatible" mean?
A117
Check physical size, mounting and software support separately. Placing an A117 beside a Winwing/WinCtrl EFIS does not confirm shared drivers, direct mechanical attachment or every aircraft mapping. Compare the current drawings and the supported profile for each device. Send support both exact models and your intended arrangement before ordering mounting parts.
FixI want to return my order
Read the current return policy, then choose “Return / warranty” in the support form. Include the order number if available, the item, reason for the request and relevant photos or fault details. Support will confirm eligibility, the correct destination and next steps. Keep the packaging and do not ship a return to an unconfirmed address.
Q&AAre the panels plug and play? Do I need MobiFlight?
Panels and aircraft combinations listed for the Rowsfire App can use that workflow without MobiFlight or FSUIPC. Start with the current compatibility and installation instructions. A firmware change is not a mandatory first step for every unit. Legacy devices and custom MobiFlight setups need their own matching instructions and configuration.
Q&AWhich aircraft are supported?
Compatibility depends on panel model, hardware revision, simulator and aircraft add-on. Use the Rowsfire App compatibility matrix as the maintained reference rather than a series-wide yes/no answer. It includes revision-specific and partial-support notes. A107 Pro’s older “default A320 not yet supported” statement has been superseded by later App updates; check the exact aircraft entry and limitations.
Q&ADoes it work with MSFS 2024? With X-Plane? With Xbox?
Support is combination-specific: select the panel revision, simulator and aircraft in the current App compatibility list. Rowsfire App currently runs on Windows 10/11; it is not an Xbox application. Do not generalize a listed X-Plane 12 combination to X-Plane 11 or to every panel. If a combination is not listed, ask support before purchasing or changing firmware.
Q&ADoes A107 support FSLabs, FBW or "Phoenix" A320?
Use the current compatibility matrix for your A107 revision and the exact Fenix, FBW or FSLabs aircraft. “Phoenix” is sometimes used when a customer means Fenix; confirm the aircraft name. Some functions can be limited by the add-on’s exposed interfaces. Custom mappings require their own tested profile and are not a guarantee of full support.
Q&ACan I use Rowsfire panels with Winwing devices?
Separate devices can be used in the same cockpit when each has a supported connection and configuration. Check physical mounting separately from software compatibility. For legacy MobiFlight conflicts, test one device and application at a time and check COM-port ownership. Do not promise that every Winwing/WinCtrl utility version is conflict-free.
Q&ACan A221 be used on both the captain and first officer side?
A221
Yes. A221 is symmetrical and black on both sides: assemble it mirrored for the first officer side.
Q&AAre the black angled end pieces of the A220L glareshield included?
Check the packing list for the exact A220L variant you ordered. End pieces, printed parts and downloadable files can be supplied separately depending on the option. Send support the order number and product photo to confirm what is included and which files are available.
Q&ADo panels need external power or batteries?
Follow the wiring diagram supplied with your exact model and hardware revision. USB control panels, display units and motorised devices can have different video, data and power requirements. Do not infer the power socket or adapter from another product in the same series. If the diagram is missing, send the hardware and supply labels plus a photo of the connectors to support before adding power.
Q&AHow do I mount the panel? Which VESA size?
Use the current mounting drawing for the exact panel revision and bracket. VESA spacing, screw diameter, bracket thickness and safe insertion depth must all match; one panel’s dimensions do not apply to the whole series. If the drawing is missing or a screw binds, stop and send support the label, bracket/hole photos and screw measurements.
Q&AIs there a stand for A107 / A103 / A108 / A109?
Use the Resource Hub or contact support to find a stand for your exact panel revision and desk/floor arrangement. Confirm the mounting interface, included fasteners and current availability before ordering. An older A107 packing list does not establish what is included with an A107 Pro.
Q&AIs A101 1:1 scale?
A101A109
Check the dimensions and photographs of the exact A101 variant before planning a full-size cockpit. Button size and overall panel scale are different specifications. If 1:1 fit is essential, send support the product revision and the mounting-space measurements for confirmation.
Q&AWhich aircraft does A101 support?
For A101 V3 with Rowsfire App, use the current version-specific matrix. Other A101 revisions and legacy/custom configurations need their own matching instructions. Check the aircraft add-on and simulator version as well as the panel model; support for one revision does not establish support for every A101.
Q&ADoes one fuel-pump button control several pumps?
A102A103A106A107
A simplified simulator panel can map a single control to several pump commands, depending on its configuration. This does not describe every Rowsfire overhead or the real aircraft overhead layout. Check the exact panel layout and aircraft profile before assuming how many pump controls are available or which pumps a button operates.
Q&ADoes A107 come with the flat lever handles like the original A101?
Check the packing list and loose-parts bag for the exact A107 revision and order option. If a handle appears to be missing, send support the order number, panel photo and switch close-up so the matching part and fitting method can be confirmed.
Q&AWhich A-series panel has a battery voltage display?
Check the current product layout and specifications for the exact panel revision. Display availability and the values shown can depend on both hardware and the supported aircraft profile. Ask support to confirm the battery-voltage function for your intended setup before ordering.
Q&AWhy does the A107 Pro overhead have no full hydraulic section?
The controls available on an A107 Pro depend on its physical layout and supported aircraft mapping. Compare the product photos and control list with the functions you need. Contact support if a particular hydraulic control is essential; do not assume a future panel or firmware update will add it.
Q&AB107: are the switches solenoid (magnetic) switches?
B107
No.
Q&ADoes B101 (EFIS) work with PMDG 777 and behave like the real one?
Confirm the exact B101 hardware revision, PMDG aircraft version and supplied software profile with support. A legacy/custom MobiFlight profile does not establish support for every aircraft or every real-aircraft EFIS function. Specify the controls you need so their mapping and physical behaviour can be checked.
Q&AD105 G1000: how does it connect? Does it work with MobiFlight and P3D?
Follow the D105-specific guide for video, power and control connections. A visible image does not confirm the input configuration or aircraft mapping. A simple HDMI splitter mirrors a source; an independent instrument desktop needs an appropriate separate display output. Confirm the simulator, aircraft and software workflow with support, including any P3D or custom MobiFlight requirement.
Q&AWhat makes the D105 G1000 different from other G1000 panels?
D103D104D105
Compare the current specifications for the exact D103, D104 or D105 variant. Screen layout, control functions, backlighting and supported aircraft/software can differ. To check suitability, identify which instrument display and controls you need, then confirm the product’s connections and matching configuration. A feature listed for one G1000 variant should not be assumed for every unit.
Q&AA108: which software shows the instruments on the screen?
Use the current Rowsfire App page and the A108 instructions for supported instrument-display modes. Earlier installations may use a separate pop-out workflow. Verify the exact simulator and aircraft, especially default Asobo variants; do not infer support from a generic A320 label. If the instruments do not appear, send the App version, aircraft name and layout screenshot to support.
Q&A3658660 screen: is it compatible with other hardware and FSLabs?
Confirm the current product name and revision for SKU 3658660 with support. Compatibility depends on the exact display connections, instrument pop-out or software workflow, simulator and aircraft add-on. An HDMI connection alone does not confirm FSLabs or another aircraft is supported.
Q&AThe manual mentions FSUIPC and MobiFlight. Do I still need them?
For combinations supported by Rowsfire App, follow the current installation guide rather than an older MobiFlight manual. MobiFlight/FSUIPC requirements belong to their own legacy or custom workflow. Check the exact model and revision first. No manual-release date is promised here.
FixMobiFlight files: what are .mfmc, .mcc and .mfproj?
A .mfmc file is a MobiFlight module configuration, not firmware. A .mcc file is a configuration file; .mfproj is a project format and is not restricted to X-Plane. Check the exact hardware and aircraft that a supplied file was built for. Importing a configuration and uploading firmware are different operations. See the official MobiFlight file-type documentation for details. MobiFlight file types →
FixControls send inputs while nobody touches the panel
Capture a short local input log with the panel untouched. Note which controls generate events, the backlight position and whether the entire USB device reconnects. Test one panel through its correct connection guide. Unexpected events, a simulator bridge reconnecting and USB power loss are different observations. Send the log, label and software versions to support; do not assume a new hub, sensitivity setting or firmware will fix every case.
FixB107: USB problems start when fitting a mount
Disconnect the panel and stop installation if tightening a bracket screw triggers USB faults, unusual heat or suspected contact with the circuit board. Do not reproduce the fault while powered or use an arbitrary longer screw. Send support the hardware label, bracket/hole photos and screw measurements. The approved mounting specification must match the exact revision.
FixThe display shows Windows desktop but no instruments
Seeing the desktop confirms an image signal is reaching the display at that moment; it does not confirm the instrument window or panel controls are configured. Check your selected display mode, exact aircraft and the approved pop-out/App layout guide. If no instruments appear, send Windows display settings, the layout screenshot, hardware label and simulator/software versions. Do not flash the input controller to fix a missing instrument window.
FixUSB/COM detection and display detection are different
A display can receive video while its controls are not detected, or the controls can respond while the image is missing. In Windows, record the monitor/display entry separately from USB/input/COM entries. A Bluetooth SPP COM port being skipped does not by itself mean the panel USB chip is broken. Provide before/after connection screenshots if support needs to identify the device.
FixD-series and YOKE: choose the model-specific setup
Choose the exact model before following a setup guide. Historical D102 instructions use easyjoy, while YOKE records use FFBMaster; display/control units and the D107 motorised throttle have different connections and dependencies. Confirm the current model-specific instructions with the Resource Hub or support. Do not assume the whole D-series uses the same App, firmware or power supply.
FixD107: separate input, motor and configuration symptoms
Record whether USB input is detected, whether the symptom concerns the motor/reverse/trim, and the exact aircraft/configuration. Include hardware and power-supply labels plus a wiring photo. The presence of a configuration file does not prove every motor or trim function is supported. Use the current D107-specific procedure; do not apply a different panel power or firmware guide.
FixWhat to include when contacting product support
Include the order number if available, product/hardware-label photo, wiring and supply-label photos, simulator and exact aircraft, software/firmware versions, full error, a short reproduction video and the steps already tried. Keep local input, output and simulator results separate. You can copy the guided-check summary from this page. If you cannot identify the revision, send a label photo instead of guessing.
02 · First-time setup & downloads

Choose the workflow for your panel.

For supported combinations

Rowsfire App

Current download, release notes, Debug tools and the version-specific compatibility matrix.

Open App & compatibility →Legacy / custom workflow

MobiFlight

Use the configuration for your exact panel and aircraft. Confirm the panel revision and aircraft before using a legacy configuration.

Open legacy guide →Model-specific resources

Resource Hub

Find the supplied guides and files. Contact support if your revision or configuration is not listed.

Open resources →
View App installation tutorials by panel →
Detailed guides & videos

Keep the full tutorial close.

Quick answers above help narrow the issue. These original blog guides keep their videos, images and existing links. Older screenshots may differ from your App; match the hardware revision and current compatibility list first.

Original blog guide

App installation tutorials

Choose a panel and open its original video or image guide.

Read full guide →Original blog guide

B107 setup video

Open the detailed B737 overhead installation walkthrough.

Read full guide →Original blog guide

A108 display setup

Open the display-mode, bridge and instrument-layout guide.

Read full guide →
Browse all product support articles →Browse news & product updates →

The quick-answer library and the blog archive are separate collections. New blog posts appear in the archive; they are not automatically added to quick-answer search.

03 · Orders & after-sales

Help beyond setup.

Track an order

Check shipment progress and tracking details.

Track shipment →

Shipping & delivery

Parcel and oversized-frame services have different coverage and transit times.

Read shipping policy →

Returns & warranty

Read the current policy before arranging a return.

Read return policy →

Damage or missing parts

Prepare your order number and photos of the part, panel and packaging.

Contact support →
06 · Human help

Still stuck? Send your setup and checks.

Tell us what happens and what you have tried. If a version or order number is unknown, say so; you can still ask for help. Nothing is sent until you press Send support request.

Your product setup

For product or damaged-part questions, enter the model or Unknown. Other version fields are optional.

This form accepts text and links. For attachments, use the contact options on our contact page. Share only files relevant to this issue. Service hours and contact channels are listed there.

Other contact options →