3/2/2022 11:08 AM | |
Joined: 4/28/2015 Last visit: 9/9/2024 Posts: 3345 Rating: (379)
|
Hi h_p_l, thanks for this very valuable feedback! This summarizes all pain points we have at the moment. I am fighting to get better usability for Industrial OS since we pre-installed it. I hope it will get better with the version 3.x. I am totally with you and understand your concerns. I will answer or try to find answers to your questions in the following.
Basically Industrial OS and the Example Image are based on Debian, so in general you can handle both images like a usual Debian . The reason for those two, slighlty different images? - I don't know to be honest and I don't understand it, as it really confuses the users and is hard to support
This is due to the missing power handling feature of the used CPU in IOT2050 Basic FS:01 and IOT2050 Advancved FS:01, FS:02, FS:03.
You mean the power consumption is about 2A after the devices have been shutdown and are only connected to power source?
I don't agree that it is useless to get a DHCP address when ssh is disabled. There is lots more use cases having an IP address than connecting via ssh.
I will write a requirement to IndOS as well as the Example Image.
The mel-setup appearing when you plug in the service stick is a different story than changing the boot order in order to boot from the service stick.
This would really blow up the first setup documents, it is on purpose that application example are seperated from those documents.
Where did you find the information that you get a Profinet license for free for the IOT2050, but need to pay for the IOT2040? That's the mess with the Industrial OS. I can't provide the Service Stick image in SIOS as it officially needs a license to use it (the IOT2050 Advanced is the "license"). Summarized I would recommend to use the Example Image:
Nevertheless I forwarded everything you wrote to the responsilbe persons (again) and hope that those things we can solve will be solved in future. Thanks and best regards! |
Last edited by: bergmanu at: 03/02/2022 11:53:28Not working for IOT2050 support anymore from March 1st, 2024. |
|
This contribution was helpful to1 thankful Users |
3/2/2022 3:34 PM | |
Joined: 4/28/2015 Last visit: 9/9/2024 Posts: 3345 Rating: (379)
|
Hi,
With an freshly unpacked device you shouldn't have dhcp enabled, as the interface are not configured from factory. When I do not configure an interface in the first setup, no interface will be active. Please correct me, if you had a look at your dhcp router and the IOT2050 appeared with an IP address without having anything configured. I haven't tried that.
This link is about Industrial OS for IPC, not for the IOT2050. Unfortunately there is no seperate SIOS entry about the IndOS for IOT2050.
On this page you can download the Profinet relevant software for the IOT2040, not for the IOT2050 (because it is not existing yet -> details see below)
This announcement is valid for the IOT2040, that's why it is in the IOT2020/2040 section, not in the IOT2050 section
This link is outdated. The content of this entry (Profinet relevant software for the IOT2040) has been moved to the second link above
The IOT2050 is the successor of the IOT2040 with a different OS (Debian instead of Yocto) and a different hardware, especially the CPU (ARM instead of x86). From a performance and usability point of view the IOT2050 defintely was the right choice!
I don't know whether it is yet decided that PNDriver will be released for the IOT2050 for free. In any case, at the moment you would need the PNDriver sources as you need to compile the PNDriver for ARM on the IOT2050. Then I guess the PN functionality works.
I will check again with the responsible persons whether we can do that. Best regards! |
Last edited by: Jen_Moderator at: 03/03/2022 07:02:07Optimized links. Not working for IOT2050 support anymore from March 1st, 2024. |
|
3/3/2022 9:17 AM | |
Joined: 4/28/2015 Last visit: 6/28/2024 Posts: 578 Rating: (43) |
The IOT2050 has no power-off circuit - it's an industrial device, and those tend to either run 24/7, or they are powered-off via shutting down their primary supply. In any case, the consumption should not increase when issuing power-down. We had a bug in the firmware that caused a kernel panic on power-down. That was fixed with https://github.com/ARM-software/arm-trusted-firmware/commit/42d9b3aaf473a1e01475a020644b504ecc3d4443 which is part of the latest firmware 1.2.1. I suspect you are using the previous release. I just measured this scenario with PG1 Basic and a 24V supply. In idle state, the input is around 350 mA, and it's about 340 mA in "power-down" here. |
3/3/2022 2:59 PM | |
Joined: 9/7/2011 Last visit: 9/19/2024 Posts: 19 Rating: (1) |
ok thanks. how can i check the Firmware Version? |
3/3/2022 4:01 PM | |
Joined: 4/28/2015 Last visit: 9/9/2024 Posts: 3345 Rating: (379)
|
Hi, the firmware version can be checked with
More info about the versions and compatibility can be found here. To say it in advance: IndOS V2.2 does not run with the new firmware. IndOS will support it from V3.x. Best regards! |
Not working for IOT2050 support anymore from March 1st, 2024. |
|
Follow us on