In the password file, I see several same username, such as:
<user>
<name>test</name>
<password encoding="SHA256">iXhH.</password>
<full_name>test me</full_name>
<last_logout>Tue Apr 14 14:12:44 2009</last_logout>
<last_activity>Wed May 19 09:39:32 2010</last_activity>
<email>maqm@ihep.ac.cn</email>
<email_notify/>
</user>
<user>
<name>test</name>
<password encoding="SHA256">iXhH.</password>
<full_name>test me</full_name>
<last_logout>0</last_logout>
<last_activity>0</last_activity>
<inactive>0</inactive>
<email>maqm@ihep.ac.cn</email>
<email_notify/>
</user>
<user>
<name>test</name>
<password encoding="SHA256">iXhH.</password>
<full_name>test me</full_name>
<last_logout>0</last_logout>
<last_activity>0</last_activity>
<inactive>0</inactive>
<email>maqm@ihep.ac.cn</email>
<email_notify/>
</user>
I don't know the reason why eLog can have the same username.
And what should I do to prevent these things happen?
Thanks!
|
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
|
-
|
Power-On Ixxxx
|
|
|
|
-
|
Test communications with ...
|
|
|
|
-
|
Command xxxx to switch-on the value ….V DC/DC
|
|
|
|
-
|
Configure a multimeter to measure voltage
|
|
|
|
-
|
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
|
|
|
-
|
Repeat operation between pins z and q of …
|
Volts: 5. 097V ≤ ______ ≤ 5.252V
|
|
|
-
|
Command xxxx to switch-on the ..V DC/DC
|
|
|
|
-
|
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
|
|
|
-
|
Power-Off xxx
|
|
|
|
-
|
Re-connect harness to zzzz through yyyy connector
|
|
|
|
-
|
Power-On xxx
|
|
|
|
-
|
Verify ..V input voltage. Check final voltage
|
Final Volts @ ..V: x.x V ≤ __ ≤ 5y.yV
|
|
|
-
|
Verify ..V power consumption
|
Consumption @ ..V: x.x< _ < y.y W
|
|
|
-
|
|
|
|
|
Stefan Ritt wrote: |
You can just copy-and-paste an elog entry into Word. I tested it here wiht a simple table:
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
|
|
|
[global]
logbook tabs = 1
port = 8081
; on reste en anglais car les textes francais sont trop longs
;Language = french
Date format = %d/%m/%y %H:%M
Password file = passwords.txt
Login expiration = 24
Self register = 0
SMTP host = archie.gsi.synergie-inf.com
Suppress Email to users = 1
; attributs communs
Options Client = CE Astrium, Cofogar, Deco Ouest, GA, Mairie StO, RTS, Subra, Swap-Data
Extendable options = Client
[Routeurs]
Theme = default
Comment = Gestion des routeurs
Attributes = Author, Client, Equipment, Category, Summary
Preset Author = $short_name
Options Category = Modification, Update, Correction, Installation, Autre
Required Attributes = Client, Equipment, Category
Locked Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Client, Equipment, Category
[Liste Routeurs]
Theme = default
Comment = Liste des routeurs
Attributes = Client, Equipment, EqType, HostName
Required Attributes = Client, Equipment, EqType
Options EqType = FWL1, FWL2, VPN1, VPN2
Page Title = Equipement - $Equipment
Quick filter = Client, EqType
Menu commands = Back, New, Edit, Delete, Find, Help
Summary lines = 6
[Problems]
Theme = default
Comment = Problemes et Knowledgebase
Attributes = Author, PbType, PbStatus, Priority, Client, Equipment, Description
Options PbType = Event, System, Applic, Other
Options PbStatus = Reported, Confirmed, Investigating, Testing, Solved, Suspended
Options Priority = 1 Critical, 2 Urgent, 3 Normal, 4 Background, 5 Low
Required Attributes = Author, PbType, PbStatus, Priority, Description
Quick Filter = Author, PbStatus, PbType
Locked Attributes = Author
Fixed Attributes Reply = PbType
Preset Author = $short_name
Display mode = threaded
Reverse Sort = 1
Quote On Reply = 0
[ProblemsA]
Theme = default
Comment = Problemes et Knowledgebase, single entry
Attributes = Author, PbType, PbStatus, Revisions, Priority, Client, Equipment, Description
Options PbType = Event, System, Applic, Other
Options PbStatus = Reported, Confirmed, Investigating, Testing, Solved, Suspended
Options Priority = 1 Critical, 2 Urgent, 3 Normal, 4 Background, 5 Low
Required Attributes = Author, PbType, PbStatus, Priority, Description
Quick Filter = Author, PbStatus, PbType
Locked Attributes = Author, Revisions
Fixed Attributes Reply = PbType
Preset Author = $short_name
Menu commands = Back, New, Edit, Delete, Find, Help
Reverse Sort = 1
Subst on Edit Revisions = $Revisions $date par $short_name
|