Recent Posts

Pages: [1] 2 3 ... 5
1
I'm not familiar with LIWbut you can check the disk you build to see if it has the following top level directory structure. The newer versions of the EMS NG Viewer look for this structure on all of the local disks and will display an IETM in the list when found.

  • For IETMs built with the EMS NG Publisher 2.1.9 or later, the viewer will look for an IETM_Content directory at the top level of a disk. 
  • For IETMs built with EMS NG Publisher 2.1.8 or earlier the top level of the disk will have the following directories:
    • 2361C.war
    • Output
    • ROOT.war

There are some other files in the top level of the install disk, but those are the directories the viewer looks for. I believe there are instructions in the one of the documents for the EMS NG Software suite that describe which directories you can move over to a network disk when sharing IETMs.
2
General Discussion / Downloading IETM from LIW and running from disc in EMS NG
« Last post by mitchroy41 on January 18, 2017, 08:45:49 PM »
Has anyone had success in downloading IETMs from LIW, creating them on disk, then running them from disk in EMS NG? Can't seem to get the disk content to be recognized.
3
In this case, dynamic troubleshooting refers to the inclusion of the tags <statemanipulation> tag as part of the initialization of the track or as part of the <testwithstate> blocks in order to record information used within the knowledge model of EMS NG. The tool makes the checks listed below:

  • wpno matches file name - Checks to see if the value in the wpno for the file matches the first part of the file name
  • internal links for <testwithstate> blocks - A check is done on internal links to verify that a <testwithstate> with a matching ID exists and to identify <testwithstate> blocks that don't have a link to them.
  • check of variables - When a variable is used within an <interaction> block, it is searched for in an <evaluate> block within that <testwithstate> block
  • report of ADM values - when a <diagnostic_group> block is used, the software pulls out the data that is used to start the test within the ADM. There is currently no check of the data, it is only reported in order to provide one place to check for data during a QA cycle.

There is additional functionality that could be added, but I have not had a project or time in order to complete that work. Implementing the above functionality provided us a large gain in reducing common errors in a short amount of time when we needed it. I hope my long explanation answers your question.  :)
4
By "Dynamic Troubleshooting" do you mean Test With State as opposed to Test Without State?

Thank you

Jorge Guerrero
5
EMS NG Authoring / Re: Resolve Error Message For line 203
« Last post by Tamara Harpster on September 16, 2016, 06:47:25 PM »
You can try to  find out more information about the error in the logs that the EMS NG Publisher stores. The first set of logs is located on the server in the downloads directory. There are two files generated with each publish, an Excel document and a text document. The Excel document lists the warnings and errors from the publish. The text file stores the processing that occurs during the publish. By checking the end of the text log file, you can see what file the publish stopped on. You may also want to check a few files that were published before the one causing the errors. Sometimes another file can have an error and it won't cause a problem until later on in the publish. I had a problem like that several years ago and it turned out that a file with a table in it was incorrectly formatted but it was not reported as causing the problem.
6
EMS NG Authoring / Re: RPSTL with kititem tags
« Last post by Tamara Harpster on September 16, 2016, 06:43:24 PM »
Yes, I have worked with an IETM that uses the kititem tags and clicking on the link works in bring up the other items. The IETM was built with publisher version 1.8. Here is a sample of the tagging for an item

Code: [Select]
<pi.item id="AKGA" indent="0">
<callout numref="cKIT1" assocfig="figKITS"/>
<uoc>5A5</uoc>
<qty>0001</qty>
<smr service="army" sourcecode="PA" maintcode="FZ" recovercode="Z"/>
<nsn>
<fsc>2930</fsc>
<niin>01-524-4724</niin>
</nsn>
<partno>1033-09339-01</partno>
<cageno>75418</cageno>
<name></name>
<desc>PARTS KIT,ENGINE,FA</desc>
<qty_per_end_item>00001</qty_per_end_item>
<ui um="EA">EA</ui>
<kititem>
<name>NUT,SELF-LOCKING,HE</name>
<qty> </qty>
<callout numref="c3" assocfig="fig53"/>
</kititem>
<kititem>
<name>HUB,FAN CLUTCH</name>
<qty> </qty>
<callout numref="c4" assocfig="fig53"/>
</kititem>
7
EMS NG Authoring / RPSTL with kititem tags
« Last post by vansyckel on September 15, 2016, 03:50:52 PM »
Has anyone gotten the kititem tags to work?  When I use it I get links in the kit figure description column.  When any of these links is clicked a popup opens and states no information found, which is not very useful.  I was expecting a list on the kit's items.
8
EMS NG Authoring / Re: Resolve Error Message For line 203
« Last post by RWHOWARD on September 13, 2016, 12:43:38 PM »
Completeness check shows No Error. Even when performing a mini publish the error message is showing.
9
EMS NG Authoring / Re: Resolve Error Message For line 203
« Last post by Tamara Harpster on September 12, 2016, 07:30:32 PM »
Child nodes are the XML components of a work package. For example, in a MaintWP, the parent node is maintwp and child nodes are wp.metadata, wpidinfo, wpinfo and maintsk. Within maintsk, it can then have child nodes like install, remove or other.maintsk and followon.maintsk.

I would guess that the error message is associated with an XML file that is not completely valid. Non-standard tables, like the MAC chart, can be tricky to setup and the publisher may have had problems. There are also times that the Publisher is unable to handle a non-valid file, especially when creating a PDF from the XML.

If you using Arbortext Editor, you can do a completeness check of your files to make sure that all of the required tags are included. This option is shown on the Tools menu, it can be set to display by selecting Tools->Preferences, then Selecting the Window option at the bottom of the list on the left. On the right side, underneath the Show label, check the Full Menus box, then click on OK. The Completeness Check will show in the Tools menu and can be used to check your XML. If there are problems, the errors will be displayed.

If you are using another XML editing tool, then you need to look for the Validate XML option. The editor can then do a check of the XML against the DTD to make sure it is complete.
10
EMS NG Authoring / Resolve Error Message For line 203
« Last post by RWHOWARD on September 12, 2016, 04:45:51 PM »
Who has an answer for the following error message and explanation for "childNodes":

Publish Failed Can't call method "childNodes" on an undefined value at C:/emsng_publisher/sage//lib/Publisher/Steps/ArchiveStatic/FileSystem.pm line 203.
Pages: [1] 2 3 ... 5