Hello Everybody,

I have been testing the IOT2050 Basic Version (6ES7647 - 0BA00 - 0YA2) for about two weeks now.

Last week I set it up with the example Image V1.3.1 (IOT2050_Example_Image_V1.3.1), which I downloaded from the official site. The setup via SD Card was quite easy and I followed the Instructions of this Post:How to setup the IOT2050 with Example Image - 238945 - Industry Support Siemens.

After that I did the following steps:

• Add a new User with sudo rights

• Install a desktop Environment (How to install desktop environment - 237805 - Industry Support Siemens):

Therefore I executed the following commands:

• sudo apt update
• sudo apt install lxde
  
• sudo apt install task-lxde-desktop
  
• sudo apt install xfce4-power-manager
  
• reboot

--> to this point I was still connected via SSH Client (I used PuTTy)

• After the reboot I installed xrdp so I can connect via Remote desktop

Therefore I executed the following commands:

• sudo apt install xrdp
• sudo apt install xorgxrdp
  
• sudo systemctl restart xrdp
  
• sudo systemctl start xrpd
  
• sudo systemctl enable xrdp

--> After doing so the status showed Active when I executed "sudo systemctl status xrdp" and I could connect via Windows remote desktop from my engineering station.

• While connected from Windows RDP I installed chromium and Grafana from the LXTerminal as follows:

• sudo apt install chromium
  
• sudo apt-get install -y adduser libfontconfig1 musl
  
• wget https://dl.grafana.com/enterprise/release/grafana-enterprise_11.1.4_arm64.deb
  
• sudo dpkg -i grafana-enterprise_11.1.4_arm64.deb
  

(For Installing Grafana I followed their Instructions fromDownload Grafana | Grafana Labs)

• Enable and start grafana server

In terminal:

• sudo /bin/systemctl daemon-reload
  
• sudo /bin/systemctl enable grafana-server
  
• sudo /bin/systemctl start grafana-server
  

--> after a reboot I could also access Grafana in the browser at localhost:3000

To this point I had no problems with the device and it ran without problems for a few days of testing. The other day I did some more configuration on the IOT2050 where one of them (I cannot tell which) must have caused the issues I am now facing.

I did the following changes:

• Disable the auto sleep mode

Therefore I used the Desktop Environment and went to Preferences (in the menu in the bottom left corner) --> power manager --> in the Tab Display I disabled the option "Display power management"

• Configure the device to automatically log in to a user

• In Terminal: sudo nano /etc/lightdm/lightdm.conf
• In this file under the section [Seat:*] I uncommented the following lines:
• pam-service=lightdm
  
• greeter-session=example-gtk-gnome
  
• session-wrapper=lightdm-session
  
• autologin-user-timeout=0
  
• Also I uncommented the line "autologin-user=" and added the username to it

• set up chromium so that it always starts on reboot (Source: https://raspberrypi.stackexchange.com/questions/12970/run-sh-file-after-lxde-enviroment-is-completely-loaded):

• create a file called start_chromium.sh with the following contents and place it on the desktop:

"

#!/bin/bash

chromium http://localhost:3000/dashboards --kiosk

"

• make the bash file executable: In Terminal execute "chmod +x start_chromium.sh"
• then I executed "sudo nano /home/<user>/.config/lxsession/LXDE/autostart" and added the line "@sh /start_chromium.sh" to the end of it

This ia about all the configuration I did on the device.

Now my problem is that after I did those last 3 changes the device would not boot anymore. When I tried to reboot the stat LED just stayed red.

I decided to set the device up again from the beginning as I could not get it to boot.

But since this happened, the IOT is behaving super weird. It often does not boot at all even with a whole new basis image (I tried two other new SD-Cards as well). When it recognizes the SD card and continues to boot then it is super slow (I am talking about 10 minutes for the boot process). Also new Errors occured: when I tried to install packages it often says something like

"sudo: unable to open ... Read-only file system"

So installing anything on the device really got a pain, as it also seems like the download is way slower than before even though I am using the same connection. Also unpacking the packages when trying to install something just takes ages. The problem with the read-only file system can be solved by simply rebooting, where the problem comes into play that only about every tenth reboot actually suceeds, and the device boots.

I would really appreciate any help with the device as I think I already tried out as much as I can but cannot get it to work propperly again.

Hello udae,

thanks for your reply!

I got the IOT up and running again (still very slow) and these are the Outputs/informations for you:

Check your system logs

the output of dmesg | grep -i "error" is the following:

Hello,

sadly I do not have any UART Cable at the moment. So capturing the boot process will be a little hard.

At the moment there is a desktop environment installed again but the installation of it already took very long when I startet with a new example image. I am going to try and boot it again with another SD card and fresh installed example image and we will see if there are any Errors when executing 

dmesg | grep -i "error"

journalctl -b

Thanks for your help