Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 541 of 808  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  69678   Wed Jul 26 14:43:48 2023 Reply Stefan Rittstefan.ritt@psi.chInfoLinux | Windows | Mac OSX | All | Other3.1.4Re: export the entries from ELOG to ECSS Word document (Manifacturing Report)

You can export logbook entries into a CSV file, then load it into Excel.

Stefan

Manuela Rigano wrote:

Thanks a lot Stefan,

I asked if it is possible, in general, to create a connection and automatically fill in the tables of a report, or export the data into excell tables to then be connected to the report, having in our case about 24 process tables to be filled in with data or validation, for each report. If the compilation is not automatic, after having compiled the elog in each phase of the processing, the manifacturing report will then have to be compiled manually.

We use elog, having already used it in MEG We must then compulsorily also make manufacturing  and test reports. The expected space-type documentation format for these documents is in word.

Below is a small example of a test table, with just a few steps.

Thanks again

Manuela

POWER INTERFACE VERIFICATION TEST

STEP

Description

Expected Value

Measured value

Remarks

  1.  

Power-On Ixxxx

 

 

 

  1.  

Test communications with ...

 

 

 

  1.  

Command xxxx to switch-on the  value ….V DC/DC

 

 

 

  1.  

Configure a multimeter to measure voltage

 

 

 

  1.  

Use the multimeter to check ..V interface. Connect multimeter positive prove to pin x, and negative prove to pin y of yyyy connector

Volts:  x.xV ≤ ___ ≤ y.yV

 

 

  1.  

Repeat operation between pins z and q of …

Volts:  5. 097V ≤ ______ ≤ 5.252V

 

 

  1.  

Command xxxx to switch-on the ..V DC/DC

 

 

 

  1.  

Use the multimeter to check ..V interface. Connect multimeter positive prove to pin xx, and negative prove to pin yy of yyyy connector

Volts:  x.x V ≤ ______ ≤ y.y V

 

 

  1.  

Power-Off xxx

 

 

 

  1.  

Re-connect harness to zzzz through yyyy connector

 

 

 

  1.  

Power-On xxx

 

 

 

  1.  

Verify ..V input voltage. Check final voltage

Final Volts @ ..V:  x.x V ≤ __ ≤ 5y.yV

 

 

  1.  

Verify ..V power consumption

Consumption @ ..V: x.x< _ < y.y W

 

 

  1.  

 

 

 

 

 

Stefan Ritt wrote:

You can just copy-and-paste an elog entry into Word. I tested it here wiht a simple table:

one two
three four

Did a copy-and-paste to Word, and got the thing below.

Best,
Stefan

 

 

Manuela Rigano wrote:

HI,

Is there a way to export the ELOG entries to a file like Microsoft Word?
For ECSS-type documents for space missions, I have to report the data that we enter in the ELOG in a Manufacturing Report, foreseen for ECSS, in word format. It's possible to do it?
The data has to go into tables, inserted in the world file, called "as run procedure".
Is it possible to connect the elog to a report template so that it automatically generates the manufacturing report? Or link the tables placed in it so that they are automatically filled in?

Thank you so much
Manuela

 

 

 

  69681   Mon Aug 14 08:35:58 2023 Reply Stefan RittTherestefan.ritt@psi.chQuestionLinux3.1.5-1Re: line breaks in 'Subject'

There are two locations where 'Subject' is shown, the list display and the individual message display. I guess you mean the first one. 

In that case, you can modify the CSS styel sheet 'elog.css' and add following statement to the classes list2 and list2h:

.list2 {
   ...
   white-space: nowrap;
}  

.list2h {
   ...
   white-space: nowrap;
}  

 

Evinrude Motor wrote:

Certain characters contained in the 'Subject' will cause the text to split into multiple lines .

For example if  I enter "My Subject" in the 'Subject' field it is displayed as

My

Subject

If I enter "My_Subject" it is displayed as 

My_Subject

Is there any way to change this so no line breaks are created ?

 

  69682   Mon Aug 14 13:15:38 2023 Reply Evinrude Motorminsonj2016@gmail.comQuestionLinux3.1.5-1Re: line breaks in 'Subject'

Thanks for that bit of info . I had looked at that file but the answer was not obvious to me . Now I have to have an ELOG entry about , well , ELOG :}

Stefan Ritt wrote:

There are two locations where 'Subject' is shown, the list display and the individual message display. I guess you mean the first one. 

In that case, you can modify the CSS styel sheet 'elog.css' and add following statement to the classes list2 and list2h:

.list2 {
   ...
   white-space: nowrap;
}  

.list2h {
   ...
   white-space: nowrap;
}  

 

Evinrude Motor wrote:

Certain characters contained in the 'Subject' will cause the text to split into multiple lines .

For example if  I enter "My Subject" in the 'Subject' field it is displayed as

My

Subject

If I enter "My_Subject" it is displayed as 

My_Subject

Is there any way to change this so no line breaks are created ?

 

 

  69687   Thu Aug 24 16:43:41 2023 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.5-1Re: File/App associations for attachments

Below are the MIME types hard-coded into elogd. As you can see there is neither .ods nor .eml. If you give me the MIME type, I can add that easily. I wonder however why both work differently for you. I believe this is a browser setting.

Stefan

 

struct FILETYPE {
   char ext[32];
   char type[80];
} filetype[] = {
        {".AI",   "application/postscript"},
        {".ASC",  "text/plain"},
        {".BZ2",  "application/x-bzip2"},
        {".CFG",  "text/plain"},
        {".CHRT", "application/x-kchart"},
        {".CONF", "text/plain"},
        {".CSH",  "application/x-csh"},
        {".CSS",  "text/css"},
        {".DOC",  "application/msword"},
        {".DVI",  "application/x-dvi"},
        {".EPS",  "application/postscript"},
        {".GIF",  "image/gif"},
        {".GZ",   "application/x-gzip"},
        {".HTM",  "text/html"},
        {".HTML", "text/html"},
        {".ICO",  "image/x-icon"},
        {".JPEG", "image/jpeg"},
        {".JPG",  "image/jpeg"},
        {".JS",   "application/x-javascript"},
        {".KPR",  "application/x-kpresenter"},
        {".KSP",  "application/x-kspread"},
        {".KWD",  "application/x-kword"},
        {".MP3",  "audio/mpeg"},
        {".OGG",  "application/x-ogg"},
        {".PDF",  "application/pdf"},
        {".PNG",  "image/png"},
        {".PS",   "application/postscript"},
        {".RAM",  "audio/x-pn-realaudio"},
        {".RM",   "audio/x-pn-realaudio"},
        {".RM",   "audio/x-pn-realaudio"},
        {".RM",   "audio/x-pn-realaudio"},
        {".RPM",  "application/x-rpm"},
        {".RTF",  "application/rtf"},
        {".SH",   "application/x-sh"},
        {".SVG",  "image/svg+xml"},
        {".TAR",  "application/x-tar"},
        {".TCL",  "application/x-tcl"},
        {".TEX",  "application/x-tex"},
        {".TGZ",  "application/x-gzip"},
        {".TIF",  "image/tiff"},
        {".TIFF", "image/tiff"},
        {".TXT",  "text/plain"},
        {".WAV",  "audio/x-wav"},
        {".XLS",  "application/x-msexcel"},
        {".XML",  "text/xml"},
        {".XSL",  "text/xml"},
        {".ZIP",  "application/x-zip-compressed"},
        /* Open XML file types */
        {".DOCM", "application/vnd.ms-word.document.macroEnabled.12"},
        {".DOCX", "application/vnd.openxmlformats-officedocument.wordprocessingml.document"},
        {".DOTM", "application/vnd.ms-word.template.macroEnabled.12"},
        {".DOTX", "application/vnd.openxmlformats-officedocument.wordprocessingml.template"},
        {".PPSM", "application/vnd.ms-powerpoint.slideshow.macroEnabled.12"},
        {".PPSX", "application/vnd.openxmlformats-officedocument.presentationml.slideshow"},
        {".PPTM", "application/vnd.ms-powerpoint.presentation.macroEnabled.12"},
        {".PPTX", "application/vnd.openxmlformats-officedocument.presentationml.presentation"},
        {".XLSB", "application/vnd.ms-excel.sheet.binary.macroEnabled.12"},
        {".XLSM", "application/vnd.ms-excel.sheet.macroEnabled.12"},
        {".XLSX", "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet"},
        {".XPS",  "application/vnd.ms-xpsdocument"},
        {"",      ""},
};
  69691   Thu Aug 24 19:48:06 2023 Reply Evinrude Motorminsonj2016@gmail.comQuestionLinux3.1.5-1Re: File/App associations for attachments

You were correct  . This is 100% a browser issue , Thanks for your assistance.

Stefan Ritt wrote:

Below are the MIME types hard-coded into elogd. As you can see there is neither .ods nor .eml. If you give me the MIME type, I can add that easily. I wonder however why both work differently for you. I believe this is a browser setting.

Stefan

 

struct FILETYPE {
   char ext[32];
   char type[80];
} filetype[] = {
        {".AI",   "application/postscript"},
        {".ASC",  "text/plain"},
        {".BZ2",  "application/x-bzip2"},
        {".CFG",  "text/plain"},
        {".CHRT", "application/x-kchart"},
        {".CONF", "text/plain"},
        {".CSH",  "application/x-csh"},
        {".CSS",  "text/css"},
        {".DOC",  "application/msword"},
        {".DVI",  "application/x-dvi"},
        {".EPS",  "application/postscript"},
        {".GIF",  "image/gif"},
        {".GZ",   "application/x-gzip"},
        {".HTM",  "text/html"},
        {".HTML", "text/html"},
        {".ICO",  "image/x-icon"},
        {".JPEG", "image/jpeg"},
        {".JPG",  "image/jpeg"},
        {".JS",   "application/x-javascript"},
        {".KPR",  "application/x-kpresenter"},
        {".KSP",  "application/x-kspread"},
        {".KWD",  "application/x-kword"},
        {".MP3",  "audio/mpeg"},
        {".OGG",  "application/x-ogg"},
        {".PDF",  "application/pdf"},
        {".PNG",  "image/png"},
        {".PS",   "application/postscript"},
        {".RAM",  "audio/x-pn-realaudio"},
        {".RM",   "audio/x-pn-realaudio"},
        {".RM",   "audio/x-pn-realaudio"},
        {".RM",   "audio/x-pn-realaudio"},
        {".RPM",  "application/x-rpm"},
        {".RTF",  "application/rtf"},
        {".SH",   "application/x-sh"},
        {".SVG",  "image/svg+xml"},
        {".TAR",  "application/x-tar"},
        {".TCL",  "application/x-tcl"},
        {".TEX",  "application/x-tex"},
        {".TGZ",  "application/x-gzip"},
        {".TIF",  "image/tiff"},
        {".TIFF", "image/tiff"},
        {".TXT",  "text/plain"},
        {".WAV",  "audio/x-wav"},
        {".XLS",  "application/x-msexcel"},
        {".XML",  "text/xml"},
        {".XSL",  "text/xml"},
        {".ZIP",  "application/x-zip-compressed"},
        /* Open XML file types */
        {".DOCM", "application/vnd.ms-word.document.macroEnabled.12"},
        {".DOCX", "application/vnd.openxmlformats-officedocument.wordprocessingml.document"},
        {".DOTM", "application/vnd.ms-word.template.macroEnabled.12"},
        {".DOTX", "application/vnd.openxmlformats-officedocument.wordprocessingml.template"},
        {".PPSM", "application/vnd.ms-powerpoint.slideshow.macroEnabled.12"},
        {".PPSX", "application/vnd.openxmlformats-officedocument.presentationml.slideshow"},
        {".PPTM", "application/vnd.ms-powerpoint.presentation.macroEnabled.12"},
        {".PPTX", "application/vnd.openxmlformats-officedocument.presentationml.presentation"},
        {".XLSB", "application/vnd.ms-excel.sheet.binary.macroEnabled.12"},
        {".XLSM", "application/vnd.ms-excel.sheet.macroEnabled.12"},
        {".XLSX", "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet"},
        {".XPS",  "application/vnd.ms-xpsdocument"},
        {"",      ""},
};

 

  69696   Mon Sep 18 14:38:30 2023 Reply Stefan Rittstefan.ritt@psi.chBug reportOtherlatestRe: update elog downloads page
Thanks for the reminder, I updated the download instructions.
  69697   Tue Sep 19 10:58:14 2023 Reply Heinz Junkesjunkes@fhi-berlin.mpg.deBug reportLinuxelogd 3.1.4Re: elog server crashed due to cookies send by client

The server is crached because the author field was accidentally filled with a long string due to an automated (remote) script:


Author: The ion getter pump has successfully recovered and appears to be operating steadily once more. Consequently, I proceeded with sputtering to obtain an XPS survey scan of the Au sample.  Initially, the stability of the X-ray function was compromised, leading to multiple interruptions. Subsequently, an unexplained issue arose regarding the collection of counts on the channeltron detector. Additionally, the emission current exhibited fluctuations. Fortunately, it seems that we have addressed and resolved the previous issues.  In the image below, two XPS survey spectra are presented. The spectrum highlighted with a red line corresponds to the AlKa source, which was selected using the AlKa button. Conversely, the spectrum with a black line represents the MgKa source. In both cases, the energy configuration was set to 1486.7 eV. It's worth noting that the 1050 eV peak in both spectra corresponds to the Au4f state, with an energy displacement of 961.7 eV due to X-ray ghost lines caused by O contamination (84+961.7). It has come to my attention that the Mg source appears to have oxidized, a phenomenon we've observed before.  Moreover, it's important to highlight that the difference between the peaks in the low binding energy region is approximately 100 eV, not the expected 233 eV (considering the energy difference between magnesium and aluminum). This observation holds true for both cases where the same energy setting was used. Additionally, the energy of the Au4f peakSotirios Tsatso

Instead of just "Sotirios Tsatso". 

So it had nothing to do with the cookies etc.. But when the item created in this way was called up, the system crashed:

[248459.853246] elogd_misc[8407]: segfault at 561725164a4e ip 00007f8210c02854 sp 00007ffdcb92b338 error 4 in libc-2.31.so[7f8210a99000+178000]
[248459.853251] Code: 7f 07 c5 fe 7f 4f 20 c5 fe 7f 54 17 e0 c5 fe 7f 5c 17 c0 c5 f8 77 c3 48 39 f7 0f 87 ab 00 00 00 0f 84 e5 fe ff ff c5 fe 6f 26 <c5> fe 6f 6c 16 e0 c5 fe 6f 74 16 c0 c5 fe 6f 7c 16 a0 c5 7e 6f 44

 

Heinz Junkes wrote:

Our elog instance (elogd 3.1.4 built Jan 13 2021, 20:44:20 revision ce2a48e9) has been running for years without any problems.

We have a new user who consistently crashes the elog:

GET /Omicron-STM-XPS/?rsort=Record%20date HTTP/1.1
Host: elog.fhi-berlin.mpg.de:4821
Cache-Control: max-age=0
DNT: 1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
sec-gpc: 1
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: navigate
Sec-Fetch-User: ?1
Sec-Fetch-Dest: document
sec-ch-ua: "Google Chrome";v="117", "Not;A=Brand";v="8", "Chromium";v="117"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Linux"
Referer: https://elog.fhi-berlin.mpg.de/elog/isc/Omicron-STM-XPS/
Accept-Encoding: gzip, deflate, br
Accept-Language: el-GR,el;q=0.9,en;q=0.8
Cookie: ufnm=Sotirios Tsatsos; urem=1; elmode=full; elattach=1; sid=CD2B04E2C3F02EA4; googtrans=/en/en; amp_6e403e=aWS6RQd5UjGctj5Ym_cDzA.c2Fsdm9fc290b2thaXRlbkB5YWhvby5jb20=..1hajnscc0.1hajnscc0.0.ac.ac
X-Forwarded-For: 141.14.151.26
X-Forwarded-Host: elog.fhi-berlin.mpg.de
X-Forwarded-Server: elog.fhi-berlin.mpg.de
Connection: Keep-Alive


Received unknown cookie "googtrans"
Received unknown cookie "amp_6e403e"
*** buffer overflow detected ***: terminated
Abort (core dumped)

 

  69700   Mon Oct 9 12:30:44 2023 Reply Stefan RittI guesstefan.ritt@psi.chQuestionWindowsELOG V3.1.3-793Re: link to attachment within html editor

You can always insert the full link to the attachment like this one: https://elog.psi.ch/elogs/Forum/231009_104933/SCR14.PNG

But you can also use elog:69699/1 as shown here. Unfortunately you can do that only after the entry has been submitted, so you know the ID number of that entry. Once you have it, edit the entry and put it in.

Stefan

 

Celeste Torkzaban wrote:

Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the html editor (without the space) and submit (even with an attachment present), it weirdly gets changed and shows up as 61/1 in the submitted elog, without any hyperlink. As far as I know we're using the standard elog code and only modified css parameters. Is there another syntax to link to attachments in html?
Testing it out here: 69699/1  (elog :/1 without the space turned into 69699/1)

 

ELOG V3.1.5-3fb85fa6