Unable to figure out Edge Insights for Fleets

[ikinyarel]

Hello guys,

I've been trying to leverage edge insights for fleets on my machine but have been unable to do so. I have installed and setup the edge software, but my main issue comes from trying to leverage the system within my codebase. I have tried bringing up the reference applications and gotten some insights, but some things still aren't clear to me, mainly how do I get data from the EIF system? I looked through some reference apps that weren't completely coupled as the edgesoftware and they use stuff like opencv, grafana etc to get data, but I couldn't find any place where the underlying edgesoftware installed was being used. On the architecture diagram here (How it Works), I noticed the use of the message bus to transmit data. Do we set this up? Is there a specific container we can make calls to? Or have I completely missed the mark with how I'm going about this?

Please, I'm pretty new to this stuff so pardon me if the question is too basic

Thanks for the help

[Peh_Intel]

Thanks for reaching out to us.

I'm working on getting you an answer and get back to you.

Regards,

Peh

[ikinyarel]

Kindly noted

[Peh_Intel]

Hi ikinyarel,

Thanks for your patience.

After checking, we are sorry to inform you that the Edge Insights for Fleet software package has not been updated and the reference implementations within the package are no longer available.

Please review the Edge Software Catalog for a list of software packages that are available today. 

Regards,

Peh

[ikinyarel]

Hi Peh,

Thanks for the response. I have been able to leverage the EIF software to build some custom modules. I am facing issues trying to compile the edge software (along with custom modules) for reinstallation in another node/machine. Do you have any documentation on how to proceed with this? using the "./edgesoftware export" command zips everything up, but it doesnt add my custom modules but when I try to manually add it to the configuration xml file, I get a 404 Not found error for that module upon installation. Any feedback would be much appreciated.

Thank you

[Peh_Intel]

Hi ikinyarel,

Here is the documentation:

https://www.intel.com/content/www/us/en/docs/edge-insights-industrial/get-started-guide/3-0-1/introduction-to-the-edge-software-cli.html

Please try to list the package modules to ensure that your custom modules are in the list.

./edgesoftware list

Regards,

Peh

[Peh_Intel]

Hi ikinyarel,

Did your custom modules shown in the list after you run the command?

./edgesoftware list

Have you updated the package modules also?

./edgesoftware update <MODULE_ID>

Regards,

Peh

[ikinyarel]

Hello, 

Sorry for the late response, and thank you for the feedback

The custom modules did not show up.  Here are the steps I've currently gone through, please help inform on where I've possible missed it:

Step 1: Installation

I started by downloading the Edge Insights for Fleets sample application. Once I had the files, I unzipped the package, updated the necessary permissions, and ran the installation command to pull all the required applications onto the machine. The installation followed the commands outlined in the documentation.

Step 2: Bringing Everything Up (Build & Run)

With the installation complete, I moved on to the setup process. I curated the docker-compose file, by running the build python script, that contained the configurations needed to build and launch all the necessary applications. After running it, the system was up and running with no additional modifications—just the default setup (video analytics & ingestion)

(Side Note: According to the documentation, there were no remote images involved. Instead, all the application source files were downloaded, unzipped, and then built locally using the docker-compose setup. So, I had to follow the same approach.)

Step 3: Customization & Updates

Since the default setup didn’t fully match what I needed, I had to customize and integrate additional services. This involved modifying the existing system, incorporating new components, and ensuring they were properly connected to the message bus. After making these changes, I ran multiple tests to confirm everything was working correctly.

Step 4: Exporting for Deployment

The final step was preparing the application for deployment on other machines or fleet devices. This required exporting all the services, including the custom ones I had integrated. However, this is where I ran into a roadblock.

The main issue revolved around the edgesoftware_configuration.xml file, which defines module configurations. Intel’s documentation suggests that this file pulls modules from an online repository based on specific IDs and isn’t meant to be manually edited. I tried using the provided export and update commands, but they only worked for existing modules, not the new ones I added.

I also reviewed several reference applications that had custom modules and service definitions, but none included instructions on how to add new modules. That’s the main challenge I’m currently working through.

[Peh_Intel]

Hi ikinyarel,

Thanks for the detailed description in exporting the custom modules. I am checking with the development team and get back to you at the earliest.

Regards,

Peh

[Peh_Intel]

Hi ikinyarel,

Below are the steps to install a reference implementation from the Edge Software Catalog, modify or add code, export the package, and restore it to a new system.

We tested these steps using the pallet defect detection reference implementation, but they should be applicable to any package. Please be aware that the export command has not been used or tested for a long time and may be deprecated in the future.

1.     Install the Reference Implementation: Follow the standard installation procedure provided by the Edge Software Catalog.

2.     Modify Code and Prepare for Export:

• Make your desired changes to the code.
• Create a zip file of the modified implementation, ensuring it retains the same module UUID. Refer to edgesoftware_configuration.xml to identify the UUID.
• Replace the original downloaded zip file with your updated zip file.

3.     Export the Modified Package: Use the export functionality to create a zipped package of the modified implementation.

4.     Transfer to New System: Copy the zipped package to the new system using your preferred file transfer method.

5.     Install the Updated Package: On the new system, install the package by referencing edgesoftware_configuration.yaml to ensure proper configuration.

Commands:

1.     ./edgesoftware install

2.     

a.     cd ~/ pallet-defect-detection/Pallet_Defect_Detection_Reference_Implementation_1.0.0/pallet_defect_detection

b.     zip -r ../66c32c1901ec42ec84dafbff.zip *

3.     ./edgesoftware export

4.     scp user@192.168.1.3:~/pallet-defect-detection/Pallet_Defect_Detection_Reference_Implementation.zip

5.     

a.     unzip Pallet_Defect_Detection_Reference_Implementation.zip

b.     cd Pallet_Defect_Detection_Reference_Implementation/

c.     ./edgesoftware install -f edgesoftware_configuration.yaml

Regards,

Peh

[Peh_Intel]

Hi ikinyarel,

This thread will no longer be monitored since we have provided a solution. If you need any additional information from Intel, please submit a new question. 

Regards,

Peh

[AbhiwanTechnology]

This is a helpful discussion on Edge Insights for Fleet. Just like setting up EIF requires technical expertise, working with a professional mobile game development company ensures smooth development and deployment of gaming apps. Leveraging expert support in both fields can truly enhance performance and user experience. Thanks for sharing!