Difference between revisions of "ROS2 Suite eFlow"
From ESS-WIKI
Eric.liang (talk | contribs) (→Peripheral Porting) |
Eric.liang (talk | contribs) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
= ROS2 Suite Service = | = ROS2 Suite Service = | ||
| − | *Standard Porting | + | *<span style="font-size:larger;">Standard R</span><span style="font-size:larger;">OS2 Suite Porting </span> |
| − | *Peripheral | + | *<span style="font-size:larger;">ROS2 Peripheral Porting</span> |
| − | *Custom Developing | + | *<span style="font-size:larger;">ROS2 Custom Developing</span> |
| − | |||
| − | |||
== Standard Porting == | == Standard Porting == | ||
| Line 58: | Line 56: | ||
| style="width: 211px;" | <span style="font-size:medium;"> x 1</span> | | style="width: 211px;" | <span style="font-size:medium;"> x 1</span> | ||
|} | |} | ||
| − | |||
| − | |||
| | ||
| Line 83: | Line 79: | ||
** - CPU, RAM, HDD, OS, SUSI | ** - CPU, RAM, HDD, OS, SUSI | ||
| + | | ||
| + | | ||
| − | == Peripheral Porting == | + | == ROS2 Peripheral Porting == |
<span style="font-size:large;">Pre-requisite</span> | <span style="font-size:large;">Pre-requisite</span> | ||
| Line 91: | Line 89: | ||
#<span style="font-size:large;">The target platform supports ROS2 suite.</span> | #<span style="font-size:large;">The target platform supports ROS2 suite.</span> | ||
#<font size="4">The target platform supports peripheral's interface ( eg. USB, LAN, CANBus ... )</font> | #<font size="4">The target platform supports peripheral's interface ( eg. USB, LAN, CANBus ... )</font> | ||
| − | #<font size="4"> | + | #<font size="4">A target platform x1</font> |
#<font size="4">Peripheral x 1</font> | #<font size="4">Peripheral x 1</font> | ||
<span style="font-size:large;">Application</span> | <span style="font-size:large;">Application</span> | ||
| − | If you have confirm your device is meet above pre-requisite. You can apply an eFlow for porting the peripheral in | + | If you have confirm your device is meet above pre-requisite. You can apply an eFlow for porting the peripheral in ROS2 suite compatible sensor. |
[[File:ROS2 Suite eFlow-peripheral-porting.jpg|800x500px|ROS2 Suite eFlow-peripheral-porting.jpg]] | [[File:ROS2 Suite eFlow-peripheral-porting.jpg|800x500px|ROS2 Suite eFlow-peripheral-porting.jpg]] | ||
| Line 104: | Line 102: | ||
*MODEL NAME: Target Platform Name | *MODEL NAME: Target Platform Name | ||
*Description: List detail information of peripheral | *Description: List detail information of peripheral | ||
| − | ** - Type, Brand, Model, Inteface, Related links of Techical docs | + | ** - Type, Brand, Model, Inteface, Related links of Techical docs |
| − | == Custom Developing == | + | == ROS2 Custom Developing == |
<span style="font-size: large;">Pre-requisite</span> | <span style="font-size: large;">Pre-requisite</span> | ||
| − | #<span style="font-size:large"> | + | #<span style="font-size:large">The target platform supports ROS2 suite.</span> |
| − | #<font size="4">Purpose: | + | #<span style="font-size:large">Detailed description of your requirements.</span> |
| + | #<font size="4">Purpose: Demo or Customer's needs</font> | ||
#<font size="4">Releated peripherals</font> | #<font size="4">Releated peripherals</font> | ||
#<font size="4">Target platform x 1</font> | #<font size="4">Target platform x 1</font> | ||
| Line 118: | Line 117: | ||
<span style="font-size:large;">[[File:ROS2 Suite eFlow-custom-developing.jpg|800x500px|ROS2 Suite eFlow-custom-developing.jpg]]</span> | <span style="font-size:large;">[[File:ROS2 Suite eFlow-custom-developing.jpg|800x500px|ROS2 Suite eFlow-custom-developing.jpg]]</span> | ||
| − | |||
| − | |||
Latest revision as of 03:45, 1 June 2023
Contents
ROS2 Suite Service
- Standard ROS2 Suite Porting
- ROS2 Peripheral Porting
- ROS2 Custom Developing
Standard Porting
Pre-requisite
To confirm your platform complies with the following ROS 2 Suite standard porting requirements. If NOT complies and You can contact with PM Nathan.Wang for further evaluation.
| Intel | AMD | NVIDIA Jetson | NXP | |
| CPU | 11th ( TigerLake ) | Ryzen Embedded V2000 | Jetson Serial | iMX 8 Serial |
| Storage | 64 GB or More | 64 GB or More | 16 GB or More | 16 GB or More |
| RAM | 8 GB or More | 8 GB or More | 8 GB or More | 6 GB or More |
| OS | Ubuntu 20.04 ( ready ) | Ubuntu 20.04 ( ready ) | Ubuntu 20.04 ( ready ) | Ubuntu 20.04 ( ready ) |
| Driver | SUSI ( ready ) | SUSI ( ready ) | SUSI ( ready ) | SUSI ( ready ) |
| Platform | x 1 | x 1 | x 1 | x 1 |
Application
If you have confirm your device is meet above pre-requisite. You can apply an eFlow for porting standard ROS 2 Suite as follow.
1. eFlow/R&D Services/Software Request
2. To select issue type and fill information
- ISSUE TYPE: Std ROS Porting
- OS TYPE: [x86] Linux or [RISC] Linux
- MODEL NAME: Target Platform Name
- Description: List detail information of platform
- - CPU, RAM, HDD, OS, SUSI
ROS2 Peripheral Porting
Pre-requisite
- The target platform supports ROS2 suite.
- The target platform supports peripheral's interface ( eg. USB, LAN, CANBus ... )
- A target platform x1
- Peripheral x 1
Application
If you have confirm your device is meet above pre-requisite. You can apply an eFlow for porting the peripheral in ROS2 suite compatible sensor.
- ISSUE TYPE: Peripheral Porting
- OS TYPE: [x86] Linux or [RISC] Linux
- MODEL NAME: Target Platform Name
- Description: List detail information of peripheral
- - Type, Brand, Model, Inteface, Related links of Techical docs
ROS2 Custom Developing
Pre-requisite
- The target platform supports ROS2 suite.
- Detailed description of your requirements.
- Purpose: Demo or Customer's needs
- Releated peripherals
- Target platform x 1
Application
