logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Mini 1080p wifi camera from Aliexpress, how to use without app (FtyCamPro)?

Wuppiduppi 61176 202
Best answers

How can I use this AliExpress mini Wi‑Fi camera without the FtyCamPro app?

Open the case, identify the chip, and replace the vendor firmware with an open build; for TXW817-810 cameras the thread settled on OpenTXW81X, flashed with a C-SKY/CK-Link style programmer via an STM32F103 “blue pill,” after first making a backup of the original flash. [#20946151] [#20946175] [#20946214] After flashing, the camera creates its own AP (typically 192.168.4.1); connect to it in the browser, set your Wi‑Fi settings, and start the stream with `startdriver TXWCAM`. [#21645812] [#21645938] The live feed is then available as RTSP at `rtsp://{ip}:7070/webcam`, and at least one user confirmed the camera sensor worked with the open firmware. [#21695014] [#21645946] If your board turns out to be the BK7252UQN48 variant instead, there is a separate open firmware project for that chip. [#20946175] [#20946214]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #91 21647937
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14389
    Help: 650
    Rate: 12308
    I'm not sure about BL602 platform, I will search for my board, but I can easily check on BK7238 and BK7231N to see if nothing's broken, when I get back home.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #93 21648063
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14389
    Help: 650
    Rate: 12308
    So the current main tree release binaries for C5 are invalid?
    Helpful post? Buy me a coffee.
  • #94 21648069
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    >>21648063
    Factory binaries are, ota binaries are ok.
  • ADVERTISEMENT
  • #95 21648397
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    >>21647854

    Aug 29 2025 11:43:01 version txw81x_7ee69b254c4f

    without TXWCAM running GPIOs are not controllable - LED/Btn anyway

    Added after 14 [minutes]:

    insmod wrote:
    Well, it was not needed in pure SDK, it's not needed now.

    would it be needed if WPA3 was ever desired?

    A table snippet showing TXW81X, manufacturer Taixin, and columns with a red X and a yellow question mark.

    seems to only be defined in customer ID 1 and 10 currently

    Screenshot of source code with highlighted comment WPA3宏定义.
  • ADVERTISEMENT
  • #96 21648413
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14389
    Help: 650
    Rate: 12308
    So something that enables GPIO is called inside camera driver?
    Helpful post? Buy me a coffee.
  • #97 21648414
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    For me, camera is started after mqtt is connected (mqttstate 1)
    Wifi led (PA07) works without camera for me.
  • #98 21648419
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    txw81x_7ee69b254c4f
    weird OK. I have nothing but IOs configured currently (no autoexec/startup commands). I'll wipe and start again to be sure.
  • #99 21648424
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    I think that some gpio pins are initialized by default, some are not.
    I probably just lucked out that my pins were already initialized.
    New commit should fix that issue.
  • #100 21648436
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    OpenTXW81X_1779_merge_75263930a2ec

    negative. toggled LEDs on but only as txwcam starts do they come on.

    Also, I know you have loglevel 6 in startup, but "All" is default for me after fresh flash
  • #102 21649806
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    Just remembered that i forgot to mention a strange quirk in wifi code.
    Currently WIFI_STA_CONNECTED will trigger on both wifi connected and received dhcp ip.
    So, expect some mqtt/ntp errors in log until dhcp address is received.
    The thing is, for me dhcp WIFI_STA_CONNECTED event would only trigger if i visited some page, or log update in web app, or received state update on main page, or pinged ip.
  • #103 21649989
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    ok.

    do you have thoughts on what could be done next with TXW81X if anything?
  • #104 21650070
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    >>21649989
    ADC and deep sleep, since a9 cameras comes with a battery. (I won't do it, and i soldered out the battery on my device)
    OTA? Binary is generated in merge.bat, but there is no real_code.BinScript that is required.
  • #105 21651179
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    insmod wrote:
    real_code.BinScript that is required.

    not sure I understand that last bit. is the end result that an OTA image is generated?
  • #106 21651183
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    >>21651179
    It would be, if the aforementioned binscript was there.
  • #107 21651192
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    I see yes, no sign but there is real_code string in:
    Search results for files containing real_code in the TXW81x_FPV firmware folder, showing loader_compress.bin and merge.bat files.

    if you extract script.7z to project\script
    Screenshot of the script folder in the project directory, showing executables and DLL files.

    it'll then do the OTA I think

    Code: Text
    Log in, to see the code


    my build is just finishing. doing more than it did without script folder

    Screenshot of Windows command prompt showing commands processing firmware for the txw81xcam project.

    Added after 3 [minutes]:

    taking ages. main app was done 7 minutes ago
  • #108 21651224
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    >>21651192
    I know, and it has frozen because there is no required binscript.
  • ADVERTISEMENT
  • #109 21651228
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    ah OK OK :)

    Added after 19 [minutes]:

    Software window showing search results for files named real_code.BinScript in the E:\TXW_WORKINGDIR folder.
    Attachments:
    • real_code.zip (510 Bytes) You must be logged in to download this attachment.
  • #110 21651265
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    building with it now. it's just

    Code: Text
    Log in, to see the code


    Added after 7 [minutes]:

    Screenshot showing two BIN files with technical names, date and time modified, and file sizes.
  • #111 21651273
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    But is upgrade working?
  • #112 21651290
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    Hmm dunno. Need to look into the mechanism to initiate ota first.
  • #113 21651394
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    OTA does nothing for me.
    I get "[73116]fwinfo_check_customer_id:Not encrypt firmware", which i assume is not an error.
    Then it goes, until everything is sent, but nothing happens afterwards. After dumping the flash - OTA wasn't written.
    (my camera sensor that arrived with this a9 is apparently sp0718, and mic doesn't work even if AUDIO_EN and AUDIO_DAC_EN is set to 1)
  • #114 21651447
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    Doubtful, since pins are set up in project_config.h
  • #115 21651443
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    insmod wrote:
    my camera sensor that arrived with this a9 is apparently sp0718, and mic doesn't work even if AUDIO_EN and AUDIO_DAC_EN is set to 1)


    boo. assume an IO variation from the Taixin template for mic or you thinking something else? Are cam pin variations likely too?

    If there are going to be x number of variations for audio/mic/whatever else, is assigning those roles within OBK an option?

    Added after 53 [seconds]:

    I guess variation extent could be somewhat gauged by me flashing other cams I have

    Added after 3 [minutes]:

    insmod wrote:
    [73116]fwinfo_check_customer_id:Not encrypt firmware


    did you play with
    Code: Text
    Log in, to see the code
    in project/makecode.ini at all?

    Added after 1 [minutes]:

    how are you OTAing anyway?
  • #116 21651483
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    New version uploaded.
    Non-working OTA code is there, but i disabled compressed image upload.
    Enabled audio.

    (Oh, and i ordered 4 different cameras. One A0, one that looks like X5, one that i hope is with BK7252N and one unknown)
  • #117 21651546
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    curious, my mic doesn't seem to work with 1779_merge_4eeb0abb6749. I think I enabled one or more of these 3 before to get audio

    https://github.com/NonPIayerCharacter/OpenTXW81X/blob/main/project/project_config.h#L1055

    Added after 30 [seconds]:

    insmod wrote:
    (Oh, and i ordered 4 different cameras. One A0, one that looks like X5, one that i hope is with BK7252N and one unknown)

    good stuff. here's hoping for a decent variety

    Added after 1 [minutes]:

    https://github.com/NonPIayerCharacter/OpenTXW81X/blob/rtsp_poc/project/project_config.h#L104
  • #118 21651548
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    I once tried with AUDIO_DAC_EN, but didn't get anything.
    Though, DAC is from digital to analog, and mic we have is analog to digital - ADC. And that one is enabled via AUDIO_EN.
    And i don't see where RTP_SOUND is used.

    Added after 4 [minutes]:

    Here's a build with those enabled: https://github.com/NonPIayerCharacter/OpenBK7231T_App/actions/runs/17411142533

    Added after 11 [minutes]:

    I found out what the problem was.
    audio_adc_init wasn't called.
    https://github.com/NonPIayerCharacter/OpenBK7231T_App/actions/runs/17411478703
  • #119 21651566
    divadiow
    Level 38  
    Posts: 4833
    Help: 420
    Rate: 851
    insmod wrote:
    Here's a build with those enabled: https://github.com/NonPIayerCharacter/OpenBK7231T_App/actions/runs/17411142533

    nope.

    playing with original project again. can't quite recall how. annoying

    Added after 37 [seconds]:

    insmod wrote:
    I found out what the problem was.
    audio_adc_init wasn't called.

    ah ok ok

    it may have been with ID 9 I had audio. no matter now

    Added after 18 [minutes]:

    txwtest_6e2915e3d439 - mic works ✅
Reply | New topic
Report a violation of the law

Topic summary

✨ A mini 1080p WiFi camera from Aliexpress priced under 3€ uses a Beken BK7252UQN48 AU3437XB chip and requires the proprietary "FtyCamPro" app for operation. The device creates its own WiFi network and assigns an IPv4 address but shows no open ports on scanning. Opening the case reveals the Beken chip, and firmware resources for this chip are available on GitHub (beken7252-opencam), enabling potential firmware backup and custom flashing after identifying the flashing pins. Some similar cameras use the Taixin TXW817 chipset, which has a different ecosystem including SDKs and programming tools like TXProgrammer and CK-Link debuggers. Attempts to access internal flash memory via QSPI/SPI have been made, but require delicate soldering and specialized hardware. The Taixin TXW81x IoT SDK and C-SKY Development Kit (CDK) support firmware development and compilation. TXProgrammer can be configured to English for easier use. A 2MB flash dump from a TXW817-810 based camera has been obtained, and a demo application runs on this hardware using hgSDK. Overall, the discussion covers hardware identification, firmware extraction, SDK availability, and programming tool usage to bypass the official app and enable local control of these low-cost WiFi cameras.
Generated by the language model.
Today's popular
ADVERTISEMENT