Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

INAV wont load after flash on RXSR-FC (OMNIBUS F4 Fireworks V2) #4239

Closed
TIMO88D opened this issue Jan 21, 2019 · 8 comments

Comments

@TIMO88D
Copy link

commented Jan 21, 2019

Current Behavior

RXSR-FC (OMNIBUS F4 Fireworks V2) will not open in inav

Steps to Reproduce

have a RXSR-FC (OMNIBUS F4 Fireworks V2)

  1. enter boot mode on FC by holding button
  2. Connect to windows 10 pc via usb (ensure correct driver is elected through Zadig (winusb for stem32))
  3. use Inav configurator to flash FireworksV2 Firmware succefully
  4. reboot fc
  5. attempt to connect through correct com Chanel (3 for me)
  6. "Serial port successfully opened ID:1"
  7. "no configuration received within 10 seconds, communication falied"
  8. give up, re flash betaflight, open bug issue.

Expected behavior

Flash will work, but Inav configurator will not be able to open a serial connection

Suggested solution(s)

Unknown

Additional context


not possible

  • FC Board name and vendor:
    RXSR-FC (OMNIBUS F4 Fireworks V2)

  • INAV version string:
    Inav configurator 2.1.0, FrieworksV2 firmware 2.0.1

@a1axx

This comment has been minimized.

Copy link

commented Jan 27, 2019

Same behaviour with omniNXT f7

@bchristal

This comment has been minimized.

Copy link

commented Feb 2, 2019

Same issue with Matek F22 and Omnibus F4. The Omnibus F4 connects fine with Betaflight.

Windows 10
CP210x USB to UART Bridge Virtual COM Port Windows 10 Universal (v10.1.4) - Installed

image

Device Manager:
image

@stale

This comment has been minimized.

Copy link

commented Apr 3, 2019

This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help.
This issue / pull request will be closed if no further activity occurs within two weeks.

@stale stale bot added the Inactive label Apr 3, 2019
@PHMT

This comment has been minimized.

Copy link

commented Apr 14, 2019

Same behavior (and error) as the OP. Trying to use 2.1 on the Kakute F7 (non-AIO version) using INAV configurator 2.1.4. Re-flashing Betaflight 4.0 works just fine.

Edit: Never mind. My issue looks like it was a driver problem. I went back and re-flashed iNav and now iNav connected just fine after the flash. I spent hours yesterday and iNav would not connect. Now it did. What changed was in between, I had given up on iNav and flashed Arducopter and had downloaded Mission Planner. When Mission Planner installed, I noticed that it installed/re-installed some drivers and one of them was a STM driver. What ever drivers I had previously worked just fine for Betaflight, but apparently not iNav. I suspect that at least one of the drivers installed by Mission Planner was also what iNav needed. So now it works.

@stale stale bot removed the Inactive label Apr 14, 2019
@stale

This comment has been minimized.

Copy link

commented Jun 14, 2019

This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help.
This issue / pull request will be closed if no further activity occurs within two weeks.

@stale stale bot added the Inactive label Jun 14, 2019
@stale

This comment has been minimized.

Copy link

commented Jun 28, 2019

Automatically closing as inactive.

@stale stale bot closed this Jun 28, 2019
@Mougs

This comment has been minimized.

Copy link

commented Sep 13, 2019

Current Behavior

RXSR-FC (OMNIBUS F4 Fireworks V2) will not open in inav

Steps to Reproduce

have a RXSR-FC (OMNIBUS F4 Fireworks V2)

  1. enter boot mode on FC by holding button
  2. Connect to windows 10 pc via usb (ensure correct driver is elected through Zadig (winusb for stem32))
  3. use Inav configurator to flash FireworksV2 Firmware succefully
  4. reboot fc
  5. attempt to connect through correct com Chanel (3 for me)
  6. "Serial port successfully opened ID:1"
  7. "no configuration received within 10 seconds, communication falied"
  8. give up, re flash betaflight, open bug issue.

Expected behavior

Flash will work, but Inav configurator will not be able to open a serial connection

Suggested solution(s)

Unknown

Additional context

not possible

  • FC Board name and vendor:
    RXSR-FC (OMNIBUS F4 Fireworks V2)
  • INAV version string:
    Inav configurator 2.1.0, FrieworksV2 firmware 2.0.1

Same problem with Inav configurator 2.2.1

@Mougs

This comment has been minimized.

Copy link

commented Oct 4, 2019

Hello,
Nobody have a solution for this communication problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.