Compatibility with RTL8812BU

[Vishalelectro]

I recently bought a runcam wifilink based on openipc. They recommended to use fpv4win to setup the ground station. Unfortunately the wifi adapters I bought have chipsets 8812BU and 8811AU and i am unable to work with it. Is there any possibility that any of these chipsets is comaptible with fpv4win in current or future circumstances. I believe this change Will be helpful for others as well, to get into openipc.

[TalusL]

I recently bought a runcam wifilink based on openipc. They recommended to use fpv4win to setup the ground station. Unfortunately the wifi adapters I bought have chipsets 8812BU and 8811AU and i am unable to work with it. Is there any possibility that any of these chipsets is comaptible with fpv4win in current or future circumstances. I believe this change Will be helpful for others as well, to get into openipc.

I'm sorry to inform you that the current Wi - Fi driver is a user - space driver ported for RTL8812AU based on libusb. It may be difficult to achieve compatibility with other chip adaptations on Windows. If new chips are adapted upstream, I will follow up in a timely manner. https://github.com/buldo/WiFiDriver

[Vishalelectro]

Sir, Thank you for the reply. Last time i tried again and found that the fpv4win is showing "listening air" in its wifi driver message box. But no video output is there. I think my rtl8811au is working, can you please help me for sorting this out.

…

On Wed, Oct 23, 2024, 7:24 AM Talus ***@***.***> wrote: I recently bought a runcam wifilink based on openipc. They recommended to use fpv4win to setup the ground station. Unfortunately the wifi adapters I bought have chipsets 8812BU and 8811AU and i am unable to work with it. Is there any possibility that any of these chipsets is comaptible with fpv4win in current or future circumstances. I believe this change Will be helpful for others as well, to get into openipc. I'm sorry to inform you that the current Wi - Fi driver is a user - space driver ported for RTL8812AU based on libusb. It may be difficult to achieve compatibility with other chip adaptations on Windows. If new chips are adapted upstream, I will follow up in a timely manner. https://github.com/buldo/WiFiDriver — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVXXYJM56BVPPSI7WJPLWQTZ436TXAVCNFSM6AAAAABQMOUVUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZQGYZTMNZYGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[TalusL]

Sir,

Thank you for the reply. Last time i tried again and found that the fpv4win

is showing "listening air" in its wifi driver message box. But no video

output is there. I think my rtl8811au is working, can you please help me

for sorting this out.

On Wed, Oct 23, 2024, 7:24 AM Talus @.***> wrote:

I recently bought a runcam wifilink based on openipc. They recommended to

use fpv4win to setup the ground station. Unfortunately the wifi adapters I

bought have chipsets 8812BU and 8811AU and i am unable to work with it. Is

there any possibility that any of these chipsets is comaptible with fpv4win

in current or future circumstances. I believe this change Will be helpful

for others as well, to get into openipc.

I'm sorry to inform you that the current Wi - Fi driver is a user - space

driver ported for RTL8812AU based on libusb. It may be difficult to achieve

compatibility with other chip adaptations on Windows. If new chips are

adapted upstream, I will follow up in a timely manner.

https://github.com/buldo/WiFiDriver

—

Reply to this email directly, view it on GitHub

#4 (comment), or

unsubscribe

https://github.com/notifications/unsubscribe-auth/AVXXYJM56BVPPSI7WJPLWQTZ436TXAVCNFSM6AAAAABQMOUVUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZQGYZTMNZYGY

.

You are receiving this because you authored the thread.Message ID:

@.***>

Initial troubleshooting can be done as follows:

1. There is no "Listening air....." in the log. The network card is not working. Refer to the documentation of fpv4win and follow the steps to handle it. https://github.com/OpenIPC/fpv4win

2. 802.11 counts the WIFI packets captured from the network card. If the amount of data is too small, it indicates that the sky end is not normal or the channel is incorrect.

3. WFB is selected from 802.11 and is a packet that conforms to the WFB format. If the amount of data is small, it indicates that the sky end is not working properly or the channel is incorrect.

4. RTP is the original video packet obtained after decrypting the WFB packet with the key. If the amount of WFB data is large but the amount of RTP data is small, it indicates that the key is incorrect.

[Vishalelectro]

Sir i am getting this output in my driver log

…

On Wed, 23 Oct 2024 at 07:50, Talus ***@***.***> wrote: Sir, Thank you for the reply. Last time i tried again and found that the fpv4win is showing "listening air" in its wifi driver message box. But no video output is there. I think my rtl8811au is working, can you please help me for sorting this out. On Wed, Oct 23, 2024, 7:24 AM Talus *@*.***> wrote: I recently bought a runcam wifilink based on openipc. They recommended to use fpv4win to setup the ground station. Unfortunately the wifi adapters I bought have chipsets 8812BU and 8811AU and i am unable to work with it. Is there any possibility that any of these chipsets is comaptible with fpv4win in current or future circumstances. I believe this change Will be helpful for others as well, to get into openipc. I'm sorry to inform you that the current Wi - Fi driver is a user - space driver ported for RTL8812AU based on libusb. It may be difficult to achieve compatibility with other chip adaptations on Windows. If new chips are adapted upstream, I will follow up in a timely manner. https://github.com/buldo/WiFiDriver — Reply to this email directly, view it on GitHub #4 (comment) <#4 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVXXYJM56BVPPSI7WJPLWQTZ436TXAVCNFSM6AAAAABQMOUVUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZQGYZTMNZYGY . You are receiving this because you authored the thread.Message ID: *@*.***> Initial troubleshooting can be done as follows: 1. There is no "Listening air....." in the log. The network card is not working. Refer to the documentation of fpv4win and follow the steps to handle it. https://github.com/OpenIPC/fpv4win 2. 802.11 counts the WIFI packets captured from the network card. If the amount of data is too small, it indicates that the sky end is not normal or the channel is incorrect. 3. WFB is selected from 802.11 and is a packet that conforms to the WFB format. If the amount of data is small, it indicates that the sky end is not working properly or the channel is incorrect. 4. RTP is the original video packet obtained after decrypting the WFB packet with the key. If the amount of WFB data is large but the amount of RTP data is small, it indicates that the key is incorrect. — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVXXYJOXU5X4X25X5J5B55TZ44BYRAVCNFSM6AAAAABQMOUVUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZQGY4DMNBTHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>