MartinMotycka

  • Sep 12, 2024
  • Joined Mar 5, 2024
  • 0 best answers
  • Hi @DiproChakraborty .

    I suppose that you downloaded the source code of the app and tried to start it locally? Right?

    It does not work this way with Luxonis Hub (LH). Those applications are working inside the LH only.

    So you need a device (it can be anything running supported OS - like RasPi 4 or 5) with connected OAK camera. Then you can maintain the device and it's apps from your Mac via web browser.

    1. Create your account on LH and log in.
    2. Connect your device and follow the instructions. It will install the agent to the device. Its a service that provides a communication between the device and the LH.

    Please note, you need direct SSH access to the device for setup.

    Access the device list in the left-hand panel. Locate your newly configured device and open its details page. Navigate to the "App" tab, where you can install the apps from the list.

  • Hello @gregflurry .

    It is not possibile to develop app that has been installed in the run mode. In develop mode the app runs completely on the device and you need direct access to the device via local network.

    To run the local frontend, go to devices -> select your device from the list and go to Apps tab:

    And there you find the local frontned:

    If you install the app in develop mode, on the same place is the code editor.

    • Hello gregflurry

      To run Code Editor the app has to be installed in the develop mode.

      Go to apps --> create new app. You can install it in the develop mode from the app overview. Second possibility is to go to "install app" and the install it from there in the develop mode. When installed go to device --> app --> app detail and there you will find the Code Editor

      Note: We do not recommend to use the legacy front end. It might not work as expected.

      • Hello @greffeb

        At first, please always use the "new" Hub frontend, the legacy front end may not work as expected. New front end you will wind at hub.luxonis.com

        1) Car App - Please go to the app detail and there you will find the local front end button. You can control the RAE there.

        2) "ghcr.io/luxonis/rae-ros:v0.2.2-humble" -> This is a link where you can download the image, current latest version is v0.4

        3) robothub.toml and writing python script - Both can be done via Code Editor that can be found at the app detail. Code editor is available for app installed in the develop mode.

        • go to Apps tab - > create new app -> select "RAE starter" (it's a simple streaming app)
        • open the new app and select and then under development select choose device and select your RAE
        • When installed, open the app detail and there is a Code Editor
      • Hello community.

        We have released a new version (2.28.0) of DepthAI library.

        To help improve the reliability and performance of the library, DepthAI will now collect anonymous usage data. Rest assured, no personally identifiable information will be gathered. If you prefer to opt out, you can disable this feature by setting the appropriate environment variable, as detailed below.

        Features

        • Changed the automatic crashdump collection to always on unless DEPTHAI_DISABLE_CRASHDUMP_COLLECTION is set.
        • Added DEPTHAI_ENABLE_ANALYTICS_COLLECTION environment variable - when set, analytic data (pipeline schema only) is sent to Luxonis which will be used to further improve the library.
        • Undistort both outputs of ToF by default.
        • Improved 3A syncing on OAK-D-LR.
        • Added support for YoloV10.

        Bug Fixes

        • Fix Camera node to correctly allocate resources for undistortion.
        • Fix StereoDepth node when decimation filter and depth alignment are used.
        • Fix host timestamps on OAK-T to be synced correctly.

        Misc

        • Updated XLink to support clangd and shared libraries on Windows.
        • Removed a custom assert to always produce a crash dump to improve the UX with the automatic crashdump collection.
        • Increased watchdog priority on device side to improve stability during high load.
      • Hi FredWerner

        Yes, the reflections from the cover glass directly back to the Time-of-Flight (ToF) sensor could be problematic.

      • Awab_Younas

        Hello.
        Enabling GPIO pins is a task related to specific HW platform. Since our main effort is focused to new generation of products, this task has a low priority.

        About adding a video feed. Our main goal for video streaming is to stream into the browser. Streaming video into a different app via API is not possible at this moment. But you can implement this feature directly in your app.

      • Hello FredWerner

        The first produce batch from August 2024 has only IP65. Later units will have IP67.

        The specification for IP67 is 1 meter of depth during 30 minutes. So if the device is deeper or it is submersed longer than 30 minutes, it is not covered by this IP rating.

      • Hi KenMax

        No. Installed apps can not be switched to develop mode since in this mode is everything running locally on the device, where agent is installed.

        So what you have to do is to create your own app. You can start with the "template" app (that also live and detect app). Go to the apps from the left panel a and create new "video stream". Then you should see it in the develop menu when installing new app.

        You can also download the source code for our apps. Links are in the docs (https://docs.luxonis.com/cloud/perception-apps/examples/). When a new app is created you can upload source code as single zip file (zip the content of the folder, not the folder itself). Delete the existing source and uplodad the zip archive. The you can install it in develop mode.

        When you are finished with developing, you can publish the app from the VS code. It will build the app and it can be installed in "run" mode.

      • Hello @KenMax
        When you logged into the Hub, go to devices list - from the left panel or from the widget on the main page.

        Select your device and the go to apps tab. Or if it is your first app you should see the widget for installing first app.

        Hope this will help.

      • Hello community.

        We have released a minor update to the DepthAI library. The changelog is available here:

        Features

        • Automatic crash dump collection when DEPTHAI_ENABLE_FEEDBACK_CRASHDUMP is set.

        Bug Fixes

        • Fix PointCloud generation when depth comes out of the ImageAlign node
        • Fix IMX214 (OAK Lite series) potential crash on init with more complex pipelines
        • Fix a rare bug on a crash if a camera stream is closed after 1 second while AF is running

        Python Only

        • Add support for NumPy 2
      • Hi @Davidr99

        The Hub studio runs on the host where is the Hub agent installed. What host and OS do you use? Are you sure, that this is not a connectivity issue? Is there anything suspicious in the browser console when this freeze happens?

        Thanks, M.

      • Hi @gby, it looks like there is a problem with the user rights to the team, where are you try to connect the new device.

        Please try to log into the Hub first, select the team where you want to add the device and then use Add device button on the dashboard. This ensure that the device will be connected to this team.

        • gby replied to this.
        • Hello, community members!

          We released a new version of the DepthAI library. The latest release (v2.26.0) includes several new features and improvements:

          Features

          • ImageAlign Node

            • Aligns depth to any other sensor on the device, including ToF.
            • Aligns two sensors with a static depth (default at infinity), useful for thermal-RGB alignment.
          • Cast Node

            • Casts NNData message to ImgFrame.
            • Useful for using NeuralNetwork node outputs with nodes that only accept ImgFrame.
          • Full ToF Support

            • Live running at 30 FPS.
            • Measuring range of 20cm to 6m.
            • Less than 1% error across the range.
          • Support for ToF in spatial nodes.

          • An option to limit bandwidth over XLink setXLinkRateLimit(int maxRateBytesPerSecond, int burstSize, int delayUs)

          Stability Improvements and Bug Fixes

          • Improved PoE stability on reboots - eliminate a case where powercycle of the device was sometimes needed- Improved runtime stability for heavy pipelines by prioritizing cameras in the NoC.
          • Improved runtime stability of heavy pipelines by increasing priority of the cameras in the NoC
          • Improved ImageManip stability
          • Fix a bug where stereo rectification was inaccurate when the calibration data didn't contain direct link between the two inputs
            • Relevant for custom setups on FFC devices

          Misc

          • Improve numerical stability of the rectification algorithm
            • Improves stereo quality on wide FOV sensors

          Python Only

          • Add docstrings to stubs - docs are shown in vscode by default now
          • Fix stubs/autocomplete to correctly work with with dai.Device() as device
          • Fix stubs/autocomplete to return the correct type in getCvFrame function.

          Please note that if you are using a PoE device, you will receive a notification if an older version of the bootloader is in use.

          [2024-05-24 20:46:14.962] [depthai] [warning] [1944301041AA751300] [10.12.103.140] Flashed bootloader version 0.0.21, less than 0.0.28 is susceptible to bootup/restart failure. Upgrading is advised, flashing main/factory (not user) bootloader. Available: 0.0.28

          Guidelines to update you will find on the release notes page.

        • Hello, we've identified the issue and are actively working on a solution. Thank you for your patience.

        • gregflurry

          Hi.

          Firstly, we would like to express our gratitude for your comprehensive feedback. It holds immense value for us and we truly appreciate it. We acknowledge that the user experience with RAE has room for improvement, and we want to assure you that the development of RAE is an ongoing process. As Luxonis-Vlad mentioned, there are significant enhancements planned for the future.

          I will attempt to clarify some questions from your document and previous post.

          • I need a lot more help with the USB-C cable stuff
            Apologies for any confusion. Only the firmware can be updated via USB-C. Hub applications, on the other hand, can only be installed through the Hub.
          • my RAE only has 0.4 GB of "disk" available
            The Hub interface currently displays the system partition. We are aware of this issue and it will be addressed in a future firmware update. If you want to check free space it should be possible via SSH - df command should work.
          • App size
            The current display shows the size of the Python script. However, when the application is downloaded, it includes much more data - the entire runtime environment. We acknowledge that this can be confusing and may lead to a poor user experience. Rest assured, this issue will be addressed in a future firmware update.
          • Apps development
            App development in Hub involves two steps. Initially, you create an app and deploy it to the robot/device in development mode. This mode requires working on your local network, necessitating direct access to the device. All development can be done in the Robothub Studio through the web interface.


            Once you've completed your work, you can publish the app to the Robothub cloud. Upon publishing, the app is built and will appear in the "Run" menu during installation. You can modify the app's name and description in the "robothub.toml" file within the Studio. It's recommended to change the name to distinguish between the development app and the launchable app.


            This two-step approach offers a significant advantage when you have a fleet of devices. After you've finished development and published the app, anyone on your team can easily download and use the app. This makes deploying apps to the devices very easy. The same applies when you need to update the app. You make your changes in the code, publish a new version to the Hub, and anyone can then download the updated version.

          • Updating Agent
            I honestly don't know why this is happen. In RAE is agent part of the firmware and it should updates only with firmware. I have to try to reproduce this behavior.
          • Default app
            Version 1.2 requires firmware version 1.13 or earlier. Version 2.0 requires firmware version 1.14. This information should be in the installation dialog. Version 2.0 is much more bigger. So it took some time to download and install. When I have some free unit at hand, i will test how long it takes in mine environment.

          Regards, M.

        • Hi @RyanLee

          If you’re using a static IP address, it’s stored in the bootloader flash. This means that if you connect the camera to a different network or subnet (provided it’s the same one where you’re operating the Device Manager), you should still be able to locate the camera.

          Regards, Martin