Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

MTP1500 unable to eject storage medium

Created by: WouterKUL at: 7/10/2023 10:58 AM (10 Replies)

Rating (1)

Thanks 1

Result pages:: |; 1 | 2; |

11 Entries

Entries per page: 10 | all

7/10/2023 10:58 AM	Rate (0)
WouterKUL Regular Member Joined: 1/16/2015 Last visit: 5/3/2024 Posts: 10 Rating: (0)	Hi all, I have an MTP1500 unified comfort panel. To retrieve the data of the logging to user has to insert a USB stick and press a button to export all the logging data to the USB. However, I'm unable to eject (unmount) the storage medium using the standard siemens scripts: await HMIRuntime.Device.SysFct.EjectStorageMedium("USB-X63") does not work. The stick remains mounted. Also when trying to dismount from the file browser I get the error: "umount: /media/simatic/X62: must be superuser to unmount". This sometimes results in a corrupt file when ejecting the USB without properly unmounting is. I"m logged in with a user which has the drive administrator / hmi adinistrator and NET administrator role.... Anyone experiencing the same issue / thoughts on how to resolve this? Thanks. Wouter

Suggestion To thank Quote Answer

7/10/2023 11:35 AM	Rate (0)
Cocolino Silver Member Joined: 4/8/2021 Last visit: 9/19/2024 Posts: 638 Rating: (105)	Hi Wouter, Which version is your MTP? Did you wait 15-20 seconds after you export the file to the USB before ejecting it? Maybe the writing process of the file takes more time than expected. Br, Cocolino
	Best regards, Cocolino Don't forget to use the Rate Function if you find my answer useful :) THX :)
Suggestion To thank Quote Answer

7/10/2023 3:17 PM	Rate (0)
WouterKUL Regular Member Joined: 1/16/2015 Last visit: 5/3/2024 Posts: 10 Rating: (0)	Hi, version is 18.0.0.1 (newest). Waiting after writing (1 min after writing 10kb) does not solve the problem. To me it looks like a user rights error? Wouter

Suggestion To thank Quote Answer

7/12/2023 2:11 PM	Rate (0)
Cocolino Silver Member Joined: 4/8/2021 Last visit: 9/19/2024 Posts: 638 Rating: (105)	Hi WouterKUL, I guess you already double check that the path you put wihtin the system function is actually the parth were the UBS is mounted right? I see that you use X63 but seems that the error complains about X62. Br, Cocolino
	Best regards, Cocolino Don't forget to use the Rate Function if you find my answer useful :) THX :)
Suggestion To thank Quote Answer

7/12/2023 2:59 PM	Rate (0)
WouterKUL Regular Member Joined: 1/16/2015 Last visit: 5/3/2024 Posts: 10 Rating: (0)	Correct, I tried unmounting the X62 and X63. The path is each time adapted to the actual physical medium where I inserted the USB. Can someone else maybe try to eject a USB on a MTP panel (via script or even via the File browser)?This way I would know if it is a Siemens error or a configuration error... I already opened a ticket with Siemens, but I'm not hearing anything from them. Wouter

Suggestion To thank Quote Answer

7/13/2023 12:01 PM	Rate (0)
Cocolino Silver Member Joined: 4/8/2021 Last visit: 9/19/2024 Posts: 638 Rating: (105)	Hi WounterKUL, I think I can try this but unfortunately I think it will not be until the next 2 weeks. I guess you will receive a replay from Siemens by then. Nevertheless I will post here my findings also. Br, Cocolino
	Best regards, Cocolino Don't forget to use the Rate Function if you find my answer useful :) THX :)
Suggestion To thank Quote Answer

7/13/2023 6:26 PM	Rate (1)
Stefan Arcularius Platinum Expert Joined: 1/21/2013 Last visit: 9/19/2024 Posts: 3119 Rating: (487)	Hi all, If you use EjectStorageMedium, you should read the note in the documentation. The system function only works correctly in runtime if you use the storage medium in question for logging. I know there is a good working solution using the sync command. Unfortunately, I do not know the details, but technical support should. Kind regards Stefan

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users WouterKUL

7/14/2023 8:29 AM	Rate (0)
WouterKUL Regular Member Joined: 1/16/2015 Last visit: 5/3/2024 Posts: 10 Rating: (0)	Hi, thanks, I did not see the note about the fact that the function only works for a medium which is storing the logs. After contact with Siemens support I received the following: From siemens support Use this code , to be sure that the file is written on your USB. Workaround that waits until everything is written. Similar to Curl Script: const filePath2="/media/simatic/X63/3000.tsv"; const tmp='/home/industrial/'; const date=Date.now(); const outfile='${tmp}out_${date}.txt'; HMIRuntime.FileSystem.WriteFile(tmp+'script.sh','#!/bin/bash sync -f ${filePath2} echo foo > ${outfile}','utf-8').then()=>{ HMIRuntime.Device.SysFct.StartProgram("chmod","777"+tmp+"script.sh",0,true,undefined).then()=>{ HMIRuntime.ParameterSetTypes.SysFct.ExportParameterSets(2,0,filePath2,1,true,undefined,false).then()=>{ HMIRuntime.Device.SysFct.StartProgram('script.sh',"",0,true,undefined).then(content)=>{ HMIRuntime.Trace("Sync finished successfully: "+content); }).catch((reason)=>{ HMIRuntime.Trace("Sync failed. Reason: "+HMIRuntime.GetDetailedErrorDescription(reason)); }); }); }); }); The provided script from siemens support has syntax errors (against arrow function expression) and is not documented at all. Now, I already have an export script which writes all the logged data to the inserted USB. I just want to be able to unmount it correctly afterwards. So I modified the provided scipt it as such: const tmp='/home/industrial/'; HMIRuntime.FileSystem.WriteFile(tmp+'script.sh','#!/bin/bash sync','utf-8').then( ()=>{ HMIRuntime.Device.SysFct.StartProgram("chmod","777 "+tmp+"script.sh",0,true,undefined).then( ()=>{ HMIRuntime.Device.SysFct.StartProgram('script.sh',"",0,true,undefined).then( (content)=>{ HMIRuntime.Trace("Sync finished successfully: "+content); }).catch((reason)=>{ HMIRuntime.Trace("Sync failed. Reason: "+HMIRuntime.GetDetailedErrorDescription(reason)); }); }); }); Basically I create a script.sh file in the home folder, give it all rights and afterwards run the 'sync' command. Not sure why the '-f ${filePath2} echo foo > ${outfile}' was in the bash script before. I assume this is an example script, so I removed it as I already have another script writing the logs to the USB. Also I removed the ExportParameterSets as I do not use any receipes. 3 questions: Do I understand it correctly that the sync bash function just gives the command to drectly write all the cache to the actuals drives? So basically the scipt makes sure all the data is written anyway, so when ejecting the usb without properly unmounting it gives no errors? Are my modifications / assumptions correct? How do I know it works ? So all the data is always written to the USB and ejecting will never result in a loss of data? Typically for now I advise the user to wait for a long time before ejecting the USB; but this is not really a professional way ... Thanks Wouter

Suggestion To thank Quote Answer

7/20/2023 9:45 AM	Rate (0)
CornfieldEng Regular Member Joined: 1/20/2011 Last visit: 7/18/2024 Posts: 10 Rating: (0)	Just wondering if you have managed to evaluate your solutions fully yet. We have a similar problem and have implemented the sync solution but still have reliability problems, it seems better than without sync but not 100% reliable.

Suggestion To thank Quote Answer

7/24/2023 7:20 AM	Rate (0)
WouterKUL Regular Member Joined: 1/16/2015 Last visit: 5/3/2024 Posts: 10 Rating: (0)	Hi, no, for the moment I still advice the users to keep the USB in for a long time. Otherwise sometimes the data is lost. Siemens should really solve this issue. Wouter

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on