Hi everyone.
Greetings!
I am using fileio library to save event logs, If I create device with path C:\ where the files will be stored and can I check the allocated memory space from SDM tool?
Thanks and regards
Hi everyone.
Greetings!
I am using fileio library to save event logs, If I create device with path C:\ where the files will be stored and can I check the allocated memory space from SDM tool?
Thanks and regards
@ashamdeep.saini I wouldn’t recommend saving data to the system partition, instead use the user partition which by default should always be created.
As your file device, create USER under USER_PATH, if it doesn’t exist already.

USER_PATH is a keyword that automatically points to the user partition (F:)
You can see the user partition status in SDM
Hi Marcel,
Thanks for the valuable suggestion.
Initially The Path Was USER_PATH, but with that i was getting an error that 20700 Invalid path. Later I Enabled FTP Server then I realiszed that only C:\ Partition existed so I started using that.
Hi,
I would avoid writing logs with the FileIo if possible.
It is very likely that a lot of write accesses are necessary for the constant updating of the time stamps.
This increases the risk of a powerfail during writing (machine is switched off) and you either destroy the entire file or even the partition.
An alternative could be using library ArEventLog to write into a user logbook. There are some wrappers listed here which make using it more comfortable (Section Tracing and logging):
Add on Question, is there any documentation which can clarify that Which letter points to which partition? e.g. (C:\ points to system memory and F:\ points to user memory).
Thanks and regards
Usually C:\ determines the first partition (like on your windows-pc)
On a Safe module system it’s 3 partitions reserved (C:\ being System, leaving D:\ and E:\ for the Data). When C:, D:\ and E:\ are already in use → F:\ is the next one to be available thus being the USER partition ![]()