Error building source distribution of a project containing real-time utility VIs

I'm using Labview 8.0.
When building the source distribution of a project I get the following message:
An error occurred while building the following file:
C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\real-time\rtutility.llb\FPC pad/strip string to size.vi
I'm using "RT reboot controller.vi" and "RT ping controllers.vi" in the project.
Anyone can tell me how to solve the problem?
Is it correct that the filename of a VI contains the character "/"? (FPC pad/strip string to size.vi)

Hi!
You fall in a LabView library error..sorry.
As you have imagined the problem is the slash in the filename and to solve you have to remove it. Go to ..\National Instruments\LabVIEW 8.0\vi.lib\real-time\rtutility.llb and rename the file.
Let me know if this solve.
Ciao
Clara
AE Manager
NI Italy

Similar Messages

Error Building Source Distribution

Hello group,
I'm trying to build a Source Distribution in LV8.6.
The application is used to drive a LV USB NI-8451 SPI adapter (among other things), so I have installed the SPI drivers in the default folder "C:\Progran Files\National Instruments\Labview 8.6\resource\objmgr\"
The source files for the project are located on our company's network drive, mapped as "S:\Machine_Plant-Eng\".
But when I try to build the source distribution, it is looking for the files to drive the SPI at "S:\Machine_Plant-Eng\ Progran Files\National Instruments\Labview 8.6\resource\objmgr\"
I don't know how to repoint the Project so it finds the correct files in the correct places.
Thanks,
Mike

check the "installer source location" under "additional Installers" in the "installer properites" and browse to cate the "S:\" drive (the complete path)
Regards
Guru (CLA)

Error 7 occurred while building source distribution in labview 8

I can build exe file and installer for my project. But while trying to build source distribution i got an error. Error description is as follows:
Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File.vi -> SDBEP_Invoke_Build_Engine.vi -> SDBUIP_Build_Invoke.vi -> SDBUIP_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux.

Hi Andy,
FYI, initially part of this project was developed in LabVIEW 7.1 and now I have
converted all the project files to LabVIEW 8.0. This was done by mass compiling and
saving all the VIs.
It is possible for me to build source distribution for some other programs. But I got the error while building source distribution for my current project. Same error was generated even while previewing the source distribution. This project contains some dynamic VIs. I had included them under the dynamic VIs and support files while creating EXE file. While building source distribution, i got an error message saying that :
"Unable to generate preview. An included VI or one of its dependencies does not exist. Open all Startup/Exported/Dynamically called VIs, recompile them (Ctrl-Shift Click the run arrow), and save them to update their dependencies.
\\Source code\Controls\Tests\Battery Current Calibration\Battery Current Calibration1.ctl
<Call Chain>Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File.vi -> SDBEP_Invoke_Build_Engine_Preview.vi -> SDBUIP_Build_Rule_Editor.vi -> SDBUIP_Item_OnDoProperties.vi -> SDBUIP_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux."
For this error I rename the control, relink it in the code, and save the VI. Now I got an error message indicating different control. I was totally confused by this behaviour. What is the problem? Why the problem occured? What procedure to follow to avoid these kind of errors in future? I would be thankful, if I can get answers for my questions.
Thanks in advance.
Ramasamy.

Getting error in building source distribution

While building source distribution, I am getting an error
Error copying files.
Source: ..\Program Files\National Instruments\LabVIEW 8.6\resource\visarc
Destination: D:\Chirag\builds\Arduino LLB\Arduino LLB\data\data\visarc
Librarian Path Location.vi
Error 1 occurred at AB_Destination.lvclass:Copy_File.vi -> AB_Source.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
can someone please help me with this ??

Do you have multiple job servers in your environment? Did all the Job servers configured SMTP settings?

Error 1 occurred while building source distribution in labview 8.2.1

I can build exe file and installer for my project. But while trying to build source distribution on RT i got an error. Error description is as follows:
Error -1 occurred at Invoke Node in SDBUIP_Build_Invoke.vi->SDBUIP_Build_Rule_Editor.vi->SDBUIP_CreateNewWizard_Invoke.vi->SDBUIP_CreateNewWizard_Invoke.vi.ProxyCaller
When i click generate preview, i got an error.
Unable to generate preview. Invoke Node in ABAPI Dist read linkages.vi->ABAPI Dist Cmp Settings to Disk Hier.vi->ABAPI Get Settings From File2.vi->SDBEP_Invoke_Build_Engine_Preview.vi->SDBUIP_Build_Rule_Editor.vi->SDBUIP_Item_OnDoProperties.vi->SDBUIP_Item_OnDoProperties.vi.ProxyCaller
Thanks in advance.
Poolsak T.
Attachments:
rt_deploy2.zip ‏34 KB

Hi,
I would first try mass compiling the vi's within your project to ensure there aren't any unresolved conflicts. Moreover, it's intersting that you can create an application without problems but upon building a distribution, things go awry.
Do the vi's run on the RT target without error? Does the application run on the target without error? Or do they run on your host just fine and its when you attempt to deploy on to your RT target that this error occurs?
Let's see where this gets us.
Cheers,
Emilie K | National Instruments

Error building source distribution

I get an error when building source distribution saying:
"LabVIEW cannot find a file that is a dependency of a Startup, Exported, or Always Included VI.
File Not Found: The file at 'C:\Program Files (x86)\National Instruments\LabVIEW 2011\vi.lib\utf\common\conversion\utf_string_to_tag.vi' was expected to have the qualified name 'NI_UnitTestFramework.lvlib:utf_string_to_tag.vi', but has the qualified name 'utf_string_to_tag.vi'.
The missing file might be referenced by one of the libraries included in the build or by the file - OpenData.vi. To fix this issue:
- Open all Startup, Exported, or Always Included VIs, recompile them (CTRL+SHIFT Click the Run arrow) and save them to update their dependencies.
- Open all libraries included in the build and verify the existence and locations of referenced files. Also, try building with the additional exclusion option, "Remove unused members of project libraries", checked."
Any ideas why this happens?
Solved!
Go to Solution.

Obvious question, but have your tried the recommendations?
Reese, (former CLAD, future CLD)
Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home

How to get last Build date of a dll in the real time target

Info On My Project
I am working on LabWindows CVI 12.0 for development . This project is a real time application for hardware, which is having Phar Lap ETS as RTOS...
I am facing some problems while checking Build date of my Application file( .dll)
I have tried to use GetFileDate API. But it is not supporting for realtime Target..
So i have tried __DATE__ macro.. That also having some problems..
How to get last Build date of a dll from the real time target ??
Please Help to solve this....
Thanks
Vaishakh A K

Please reply if any one have suggestion...

Hi Experts! Clarififcation regardng the phases of project in real time

Hi ,
Can any body please explain the phases of project and thier details like wht all will be done at each stage in the real time since i am very new to tht kind of phases ..
Please donot kindly send me any links for reference rather plz describe it in detail..
Regards,
Eshwant....

Hi,
Implementation processes:
Project preparation
The project preparation phase, depicted below, focuses at two main activities, i.e. to make a setup for the TSO and to define a solution vision. These activities allow an organization to put in on the right track towards implementation.
Design and initially staff the SAP TSO
TSO chart exampleThe first major step of the project preparation phase is to design and initially staff an SAP technical support organization (TSO), which is the organization that is charged with addressing, designing, implementing and supporting the SAP solution. This can be programmers, project management, database administrators, test teams, etc. At this point, the focus should be at staffing the key positions of the TSO, e.g. the high-level project team and SAP professionals like the senior database administrator and the solution architect. Next to that, this is the time to make decisions about choosing for internal staff members or external consultants.
The image at the right shows a typical TSO chart.
Craft solution vision
The second project preparation job is to define a so-called solution vision, i.e. a vision of the future-state of the SAP solution, where it is important to address both business and financial requirements (budgets). The main focus within the vision should be on the companys core business and how the SAP solution will better enable that core business to be successful. Next to that, the shortcomings of the current systems should be described and short but clear requirements should be provided regarding availability (uptime), security, manageability and scalability of the SAP system.
Sizing and blueprinting
The next phase is often referred to as the sizing and blueprinting phase and forms the main chunk of the implementation process
Perform cost of ownership analysis
Figure 5: Solution stack delta analysisThis phase starts with performing a total cost of ownership analysis (TCO analysis) to determine how to get the best business solution at the lowest costs. This means to compare SAP solution stack options and alternatives and then determine what costs each part of the stack will bring and when these costs will be incurred. Parts of the stack are for example the hardware, operating system and database, which form the acquisition costs. Next to that, there should be taken a look at recurring costs like maintenance costs and downtime costs. Instead of performing a complete TCO analysis for various solution stack alternatives that would like to compare, it can be wise just to do a so-called delta analysis, where only the differences between solutions (stacks) are identified and analyzed. The image at the right depicts the essence of a delta analysis.
Identify high availability and disaster recovery requirements
The next step is identifying the high availability requirements and the more serious disaster recovery requirements. This is to plan what to do with later downtime of the SAP system, caused by e.g. hardware failures, application failures or power outages. It should be noted that it is very important to calculate the cost of downtime, so that an organization has a good idea of its actual availability requirements.
Engage SAP solution stack vendors
Figure 6: Simplified SAP solution stackA true sizing process is to engage the SAP solution stack vendors, which is the next step. This means selecting the best SAP hardware and software technology partners for all layers and components of the solution stack, based on a side-by-side sizing comparison. The most important factors that are of influence here are the estimated numbers of (concurrent) users and batch sizes. A wise thing to do is to involve SAP AG itself to let them create a sizing proposal stating the advised solution stack, before moving to SAPs technology partners/SAP vendors, like HP, Sun Microsystems and IBM. A simplified solution stack is depicted at the right, showing the many layers for which software and hardware has to be acquired. Note the overlap with the OSI model.
Staff TSO
The TSO is the most important resource for an organization that is implementing SAP, so staffing the TSO is a vital job which can consume a lot of time. In a previous phase, the organization should already have staffed the most vital positions. At this point the organization should staff the bulk of the TSO, i.e. fill the positions that directly support the near-term objectives of the implementation, which are to develop and begin the installation/implementation of the SAP data center. Examples are: data center experts, network infrastructure experts, security specialists and database administration experts.
There are many ways to find the right people within or outside the organization for all of the TSO positions and it depends on the organization how much time it wants to spend on staffing.
Training
One of the most vital stages of the implementation process is training. Very few people within an organization are SAP experts or even have worked with SAP software. It is therefore very important to train the end users but especially the SAP TSO: the people who design and implement the solution. Many people within the TSO need all kinds of training. Some examples of these positions:
SAP Network Specialists
SAP Database Administrators
SAP Security specialists
Documentation specialists
Et cetera
All of these people need to acquire the required SAP knowledge and skills or even SAP certifications through training. Moreover, people need to learn to do business in a totally new way. To define how much SAP training every person needs, a company can make use of a skillset matrix. With this matrix, a manager can identify who possesses what knowledge, to manage and plan training, by defining the height of expertise with a number between e.g. 1 and 4 for each skill for each employee.
Setup SAP data center
The next step is to set up the SAP data center. This means either building a new data center facility or transforming the current data center into a foundation capable of supporting the SAP solution stack, i.e. all of the technology layers and components (SAP software products) in a productive SAP installation. The most important factor when designing the data center is availability. The high availability and disaster recovery requirements which should have been defined earlier, give a good idea of the required data center requirements to host the SAP software. Data center requirements can be a:
Physical requirement like power requirements
Rack requirement
Network infrastructure requirement or
Requirement to the network server.
Perform installations
The following step is to install the required SAP software parts which are called components and technological foundations like a web application server or enterprise portals, to a state ready for business process configuration. The most vital sub steps are to prepare your OS, prepare the database server and then start installing SAP software. Here it is very important to use installation guides, which are published for each SAP component or technology solution by SAP AG. Examples of SAP components are:
R/3 Enterprise Transaction Processing
mySAP BI Business Information Warehouse
mySAP CRM Customer Relationship Management
mySAP KW Knowledge Warehouse
mySAP PLM Product Lifecycle Management
mySAP SCM Supply Chain Management
mySAP SEM Strategic Enterprise Management
mySAP SRM Supplier Relationship Management
Round out support for SAP
Before moving into the functional development phase, the organization should identify and staff the remaining TSO roles, e.g. roles that relate to helpdesk work and other such support providing work.
[edit] Functional development
The next phase is the functional development phase, where it is all about change management and testing. This phase is depicted below.
Figure 7: Functional development phase
Address change management
The next challenge for an organization is all about change management / change control, which means to develop a planned approach to the changes the organization faces. The objective here is to maximize the collective efforts of all people involved in the change and to minimize the risk of failure of implementing the changes related to the SAP implementation.
The implementation of SAP software will most surely come with many changes and an organization can expect many natural reactions, i.e. denial, to these changes. To fight this, it is most important to create a solid project team dedicated to change management and to communicate the solution vision and goals of this team. This team should be prepared to handle the many change issues that come from various sources like:
End-user requests
Operations
Data center team
DBA group
Systems management
SAP systems and operations management
Next thing is to create a foundation for the SAP systems management and SAP computer operations, by creating a SAP operations manual and by evaluating SAP management applications. The manual is a collection of current state system documentation, day-to-day and other regularly scheduled operations tasks, various installation and operations checklists and how-to process documents.
Functional, integration and regression testing
Testing is very important before going live with any system. Before going live with a SAP system, it is vital to do many different kinds of testing, since there is often a large, complex infrastructure of hardware and software involved. Both requirements as well as quality parameters are to be tested. Important types of testing are:
Functional testing: to test using functional use cases, i.e. a set of conditions or variables under which a tester will determine if a certain business process works
Integration testing
Regression testing
All tests should be preceded by creating solid test plans.
[edit] Final preparation
The last phase before going live can be referred to as the final preparation phase and is depicted below.
Figure 8: Final preparation phase
Systems and stress testing
Another vital preparation activity before going live with SAP is systems and stress testing. This means planning, scripting, executing and monitoring system and stress tests, to see if the expectations of the end users, defined in service level agreements, will be met. This can be done with SAPs standard application benchmarks, to benchmark the organizations configurations against configurations that have been tested by SAPs hardware technology partners. Again, a test plan should be created at first.
Prepare for cutover
The final phase before going live with SAP is often referred to as the cutover phase, which is the process of transitioning from one system to a new one. The organization needs to plan, prepare and execute the cutover, by creating a cutover plan that describes all cutover tasks that have to be performed before the actual go-live. Examples of cutover tasks are:
Review and update all systems-related operations procedures like backup policies and system monitoring
Assign ownership of SAPs functional processes to individuals
Let SAP AG do a GoingLive check, to get their blessing to go live with the system
Lock down the system, i.e. do not make any more changes to the SAP system
[edit] Go Live
All of the previously described phases all lead towards this final moment: the go-live. Go-live means to turn on the SAP system for the end-users and to obtain feedback on the solution and to monitor the solution. It is also the moment where product software adoption comes into play. More information on this topic:
Product Software Adoption: Big Bang Adoption
Product Software Adoption: Parallel Adoption
Product Software Adoption: Phased Adoption
HTH
Regards,
Dhruv Shah

Configuring FCP to preview project in real-time on TV via Camcorder

Hey,
Somebody that I've worked with explained to me that it was possible to hook up my camcorder (GL2) by firewire to my iMac and also connect the camcorder with RCA cables to a regular TV so that the camcorder bridges the image of my project to my television so I can preview my project on a TV in real time.
He explained to me that I only had to hook up the camcorder and configure Final Cut Pro HD in the "Audio/Video settings" so that the video feed is streamed to the television.
Obviously, it doesn't work for me since I'm posting here, so I was wondering if somebody knew the settings I had to put in "Audio/Video Settings" to insure that I can see the video that I'm working on in real-time.
Thanks for your time!!
20" iMac G5 2GhZ 1gig RAM Mac OS X (10.4)

its a simple thing once you do it the first time:
assuming you have connected it all up,
go to FCP's View menu and choose "Refresh A/V Devices" (Opt-F12)
then View > Video Playback > Apple Firewire NTSC
then View > Audio Playback > "Audio Follows Video" (or Firewire DV)
then View > External Video > All Frames (Cmd-F12)

Error while creating Ear File for project Containing (WAR+MAR) in jdev

hi,
I am trying to deploy my adf application containing MDS customization.While creating EAR from application properties--->deploy--->deploye to EAR i am getting following error.
Wrote MAR file to C:\JDeveloper\mywork\MDSApp\deploy\AutoGeneratedMar.mar
[04:40:07 PM] Wrote Web Application Module to C:\JDeveloper\mywork\MDSApp\ViewController\deploy\MDSApp_ViewController_webapp1.war
*[04:40:07 PM] Warning: Some of the customization documents under '/' are packaged as part of WAR. This metadata cannot be accessed from WAR using MDS.*
*[04:40:07 PM] Info: Namespace '/xliffbundles' is mapped to deploy-target metadata-store-usage 'MAR_TargetRepos' in adf-config.xml but no metadata from the namespace is included in the MAR*.
[04:40:07 PM] Wrote Enterprise Application Module to C:\JDeveloper\mywork\MDSApp\deploy\MDSApp_application1.ear
[04:40:07 PM] Elapsed time for deployment: 4 seconds
[04:40:07 PM] ---- Deployment finished. ----
my adf-config.xml is as below
<?xml version="1.0" encoding="windows-1252" ?>
<adf-config xmlns="http://xmlns.oracle.com/adf/config"
xmlns:adf="http://xmlns.oracle.com/adf/config/properties"
xmlns:sec="http://xmlns.oracle.com/adf/security/config">
<adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
<adf-property name="adfAppUID" value="MDSApp-3718"/>
</adf:adf-properties-child>
<sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
<CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
<sec:JaasSecurityContext initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
authorizationEnforce="true"
authenticationRequire="true"/>
</sec:adf-security-child>
<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
<mds-config xmlns="http://xmlns.oracle.com/mds/config" version="11.1.1.000">
<cust-config>
<match path="/">
<customization-class name="oracle.model.mycompany.SiteCC"/>
<customization-class name="oracle.adf.share.config.UserCC"/>
</match>
</cust-config>
<persistence-config>
<metadata-namespaces>
<namespace path="/xliffbundles" metadata-store-usage="MAR_TargetRepos"/>
</metadata-namespaces>
<metadata-store-usages >
<metadata-store-usage id="MAR_TargetRepos" deploy-target="true">
<metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
<property name="jndi-datasource" value="jdbc/mds/DEV_MDS"/>
<property name="partition-name" value="part1"/>
</metadata-store>
</metadata-store-usage>
</metadata-store-usages>
</persistence-config>
</mds-config>
</adf-mds-config>
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">
<taglib-config>
<taglib uri="http://xmlns.oracle.com/adf/faces/rich">
<tag name="column">
<attribute name="displayIndex">
<persist-changes>true</persist-changes>
</attribute>
<attribute name="frozen">
<persist-changes>true</persist-changes>
</attribute>
<attribute name="noWrap">
<persist-changes>true</persist-changes>
</attribute>
<attribute name="selected">
<persist-changes>true</persist-changes>
</attribute>
<attribute name="visible">
<persist-changes>true</persist-changes>
</attribute>
<attribute name="width">
<persist-changes>true</persist-changes>
</attribute>
</tag>
<tag name="showDetailHeader">
<attribute name="disclosed">
<persist-changes>true</persist-changes>
</attribute>
</tag>
<tag name="panelSplitter">
<attribute name="collapsed">
<persist-changes>true</persist-changes>
</attribute>
<attribute name="splitterPosition">
<persist-changes>true</persist-changes>
</attribute>
</tag>
</taglib>
</taglib-config>
<persistent-change-manager>
<persistent-change-manager-class>oracle.adf.view.rich.change.MDSDocumentChangeManager</persistent-change-manager-class>
</persistent-change-manager>
</adf-faces-config>
</adf-config>

hi frank,
If you have any idea plz reply...We r stucked with metadat-namespace path attribute.

Error while deploying project to Real Time Decision Server

Hi,
I followed the link : Creating an Inline Service - 11g Release 1 (11.1.1) to create an inline service.
I was able to develop this, but, while deployment through eclipse; I am facing the following error.
[2013-11-13T16:12:48.935+05:30] [bi_server1] [NOTIFICATION] [] [oracle.wsm.security.policy.scenario.util.ScenarioUtils] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 7863b382e4716382:-f0e14fc:14251056623:-8000-000000000000156d,0] [APP: OracleRTD#11.1.1] [J2EE_APP.name: OracleRTD_11.1.1] [J2EE_MODULE.name: ws] [WEBSERVICE.name: WorkbenchEndPointService] [WEBSERVICE_PORT.name: WorkbenchEndPointPort] [WSM_POLICY_NAME: oracle/wss_username_token_service_policy] Configuration property reference.priority value is null
[2013-11-13T16:12:48.935+05:30] [bi_server1] [NOTIFICATION] [] [oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 7863b382e4716382:-f0e14fc:14251056623:-8000-000000000000156d,0] [APP: OracleRTD#11.1.1] [J2EE_APP.name: OracleRTD_11.1.1] [J2EE_MODULE.name: ws] [WEBSERVICE.name: WorkbenchEndPointService] [WEBSERVICE_PORT.name: WorkbenchEndPointPort] [WSM_POLICY_NAME: oracle/wss_username_token_service_policy] Recipient Alias property not configured in the policy. Defaulting to encrypting with signers certificate.
[2013-11-13T16:13:09.410+05:30] [bi_server1] [ERROR] [RTD-10307] [oracle.rtd.logger] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 7863b382e4716382:-f0e14fc:14251056623:-8000-0000000000001571,0] [APP: OracleRTD#11.1.1] [J2EE_APP.name: OracleRTD_11.1.1] [J2EE_MODULE.name: ws] [WEBSERVICE.name: WorkbenchEndPointService] [WEBSERVICE_PORT.name: WorkbenchEndPointPort] Management Service error[[
java.lang.ExceptionInInitializerError
at com.sigmadynamics.sdo.access.impl.ObjectFactoryImpl.createSDApplicationType(ObjectFactoryImpl.java:1463)
at com.sigmadynamics.sdo.access.impl.ObjectFactoryImpl.create(ObjectFactoryImpl.java:140)
at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.createObject(XMLHelperImpl.java:739)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFactory(XMLHandler.java:1386)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectByType(XMLHandler.java:754)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createTopObject(XMLHandler.java:779)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:462)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:449)
at org.eclipse.emf.ecore.xmi.impl.SAXWrapper.startElement(SAXWrapper.java:73)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:767)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1363)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDriver.scanRootElementHook(XMLDocumentScannerImpl.java:1315)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3104)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:921)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:133)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:173)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:140)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:169)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:988)
at com.sigmadynamics.sdo.loading.Metadata.createSDOFrom(Metadata.java:249)
at com.sigmadynamics.sdo.loading.Metadata.createSDORoot(Metadata.java:159)
at com.sigmadynamics.sdo.loading.Metadata.getSDTypes(Metadata.java:322)
at com.sigmadynamics.sdo.loading.SDA.getAppName(SDA.java:417)
at com.sigmadynamics.workbench.commands.DeployAppCommand.internalExecute(DeployAppCommand.java:99)
at com.sigmadynamics.workbench.commands.DeployAppCommand.execute(DeployAppCommand.java:80)
at com.sigmadynamics.workbench.commands.WorkbenchExecutionContext.execute(WorkbenchExecutionContext.java:53)
at com.sigmadynamics.ws.workbench.server.WorkbenchEndPoint$DeploymentExecutionContext.execute(WorkbenchEndPoint.java:149)
at com.sigmadynamics.workbench.access.impl.WSParamImpl.doExecute(WSParamImpl.java:171)
at com.sigmadynamics.ws.workbench.server.WorkbenchEndPoint.deploy(WorkbenchEndPoint.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:370)
at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:202)
at oracle.j2ee.ws.server.jaxws.JAXWSRuntimeDelegate.processMessage(JAXWSRuntimeDelegate.java:477)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1187)
at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:1131)
at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:1129)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:74)
at oracle.security.jps.internal.jaas.AbstractSubjectSecurity$ActionExecutorWrapper.execute(AbstractSubjectSecurity.java:242)
at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:83)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:51)
at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:56)
at oracle.security.jps.internal.jaas.AbstractSubjectSecurity$ActionExecutorWrapper.execute(AbstractSubjectSecurity.java:242)
at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:458)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1149)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:581)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:235)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:195)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:487)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.lang.NullPointerException
at java.io.File.<init>(File.java:222)
at java.lang.Package$1.run(Package.java:527)
at java.lang.Package.defineSystemPackage(Package.java:520)
at java.lang.Package.getSystemPackages(Package.java:511)
at java.lang.ClassLoader.getPackages(ClassLoader.java:1513)
at java.lang.ClassLoader.getPackages(ClassLoader.java:1511)
at java.lang.ClassLoader.getPackages(ClassLoader.java:1511)
at java.lang.ClassLoader.getPackages(ClassLoader.java:1511)
at java.lang.ClassLoader.getPackages(ClassLoader.java:1511)
at java.lang.Package.getPackages(Package.java:281)
at com.sigmadynamics.sdo.access.impl.SDApplicationTypeImpl.<clinit>(SDApplicationTypeImpl.java:1029)
at com.sigmadynamics.sdo.access.impl.ObjectFactoryImpl.createSDApplicationType(ObjectFactoryImpl.java:1463)
at com.sigmadynamics.sdo.access.impl.ObjectFactoryImpl.create(ObjectFactoryImpl.java:140)
at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.createObject(XMLHelperImpl.java:739)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFactory(XMLHandler.java:1386)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectByType(XMLHandler.java:754)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createTopObject(XMLHandler.java:780)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:462)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:450)
at org.eclipse.emf.ecore.xmi.impl.SAXWrapper.startElement(SAXWrapper.java:74)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:767)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1363)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDriver.scanRootElementHook(XMLDocumentScannerImpl.java:1315)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3104)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:921)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:121)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:523)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:134)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:173)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:396)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:140)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:169)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:988)
at com.sigmadynamics.sdo.loading.Metadata.createSDOFrom(Metadata.java:249)
at com.sigmadynamics.sdo.loading.Metadata.createSDORoot(Metadata.java:159)
at com.sigmadynamics.sdo.loading.Metadata.getSDTypes(Metadata.java:322)
at com.sigmadynamics.sdo.loading.SDA.getAppName(SDA.java:417)
at com.sigmadynamics.workbench.commands.DeployAppCommand.internalExecute(DeployAppCommand.java:99)
at com.sigmadynamics.workbench.commands.DeployAppCommand.execute(DeployAppCommand.java:80)
at com.sigmadynamics.workbench.commands.WorkbenchExecutionContext.execute(WorkbenchExecutionContext.java:53)
at com.sigmadynamics.ws.workbench.server.WorkbenchEndPoint$DeploymentExecutionContext.execute(WorkbenchEndPoint.java:149)
at com.sigmadynamics.workbench.access.impl.WSParamImpl.doExecute(WSParamImpl.java:171)
at com.sigmadynamics.ws.workbench.server.WorkbenchEndPoint.deploy(WorkbenchEndPoint.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:370)
at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:202)
at oracle.j2ee.ws.server.jaxws.JAXWSRuntimeDelegate.processMessage(JAXWSRuntimeDelegate.java:477)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1187)
at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:1131)
at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:1129)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:74)
at oracle.security.jps.internal.jaas.AbstractSubjectSecurity$ActionExecutorWrapper.execute(AbstractSubjectSecurity.java:242)
at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:83)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:51)
at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:56)
at oracle.security.jps.internal.jaas.AbstractSubjectSecurity$ActionExecutorWrapper.execute(AbstractSubjectSecurity.java:242)
at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:458)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1149)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:581)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:235)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:196)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:487)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
... 9 more
It would be great if any pointers can be provided to solve the same.
Thanks and Regards,
Vijay Inani

Also, this error is coming in Eclipse logs
javax.xml.ws.soap.SOAPFaultException: java.lang.ExceptionInInitializerError
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:171)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:240)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
at $Proxy32.deploy(Unknown Source)
at com.sigmadynamics.ws.workbench.client.WorkbenchServerClient.deploy(WorkbenchServerClient.java:50)
at com.sigmadynamics.studio.util.ServerConnectionData.deploy(ServerConnectionData.java:356)
at com.sigmadynamics.studio.util.DeployAction$DeployJob.run(DeployAction.java:187)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

Building a PC for faster rendering and real time workflow

Hi guys - need help if possible since I'm not into hardware all that much...
I have a few problems when using Premiere Pro CS6 which resulted in thinking of buying a new computer:
1) Exporting a one hour full HD video takes about 23 hours (no effects except color correction)
2) When making a color correction it is impossible to preview it on timeline even in 1/4 resolution - video starts to jitter so I have to export it to realize that some scenes are too dark, too light, too something, etc. And, as said, it takes around 23 hours... So this makes it 46 hours...
3) Using a multicam view is extremely jerky and so - pretty useless
All in all - I need a computer with a lot more muscle. So, I went through many forum discussions, read on the Internet, blah, blah.. and decided to build a PC rather than MAC since I get more "bang for the buck" when considering the same budget (around 3000$). Speaking of this, please consider that I live in Croatia and 3K$ here are not the same as in USA or many parts of Europe - it's a little more pricey here...
So, here's the setup so review it if you're into hardware and CS6 compatibility/optimization and please comment/advise, having in mind the problems I have previously stated out.
Just one thing - please, please, please don't get too complicated because I really don't know that much about hardwareing and I'm pretty fed up with exploring hundreds and hundreds of posts, opinions, forums, etc....
Make it simple - is it a good choice or not for CS6 workflow and which component should I potentially change for a better one (but staying in budget).
I use Premiere for editing full HD videos (sometimes I get nearly 500GB of raw material) and I frequently use After Effects for various animations.
Thanks a lot!
Intel core i7 3930K (3.2 GHz, hex, 1.5 MB, 12 MB, Socket 2011, box)
MSI x79-GD65-8D
Asus GTX 690 - 4GB
Kingmax SSD 60BG (for windows and cs6)
Seagate HDD Desktop Barracuda 7200 (3TB, 64MB, Sata III-600)
Corsair 32GB, DDR3, 1600 MHz
Spire 750W Black Eagle

Intel core i7 3930K (3.2 GHz, hex, 1.5 MB, 12 MB, Socket 2011, box), good choice
MSI x79-GD65-8D, consider Asus
Asus GTX 690 - 4GB, wrong choice. a 670 is more than enough
Kingmax SSD 60BG (for windows and cs6), consider a Corsair PP 128 GB
Seagate HDD Desktop Barracuda 7200 (3TB, 64MB, Sata III-600), make that 3 or 4 disks
Corsair 32GB, DDR3, 1600 MHz, as long as they are max 1.5V and 8 GB sticks
Spire 750W Black Eagle, better look at Seasonic or Corsair Gold+ rated PSU's and maybe increase W to 850.
Look here for other approaches: http://ppbm7.com/index.php/intro-part-1

LabVIEW 2013: Source distribution, destination path for post build VI changed?

Hi,
In a source distribution for an embedded target (Real-Time for instance) you specify both "Local destination directory" and "Target destination directory". Let's say the local directory is "C:\MyProject\MyModules\", and the target directory is "C:\" for instance. Then on my build machine my source distribution will end up in "C:\MyProject\MyModules\c\<source distrib files>", and I can then FTP everything from <source distrib files> to the root of my target's c-drive (or in some cases I can just deploy directly after the build, and LabVIEW will move the files to the target for me).
You can also specify a Post Build VI that can do stuff to your source distribution after the build has completed. Such a Post Build VI has an input named "Destination Path" for use inside your Post Build VI, so you can find your files to operate on :-)
In LabVIEW versions prior to 2013 this destination path would be "C:\MyProject\MyModules\c\", but in LabVIEW 2013 the destination path is only "C:\MyProject\MyModules\" thus missing the target destination directory part. Now my Post Build VI can no longer find my source distribution files, unless I inside that VI hardcode the target destination directory - and that isn't a good solution.
Is this changed by design in LabVIEW 2013, or is it a bug?
Cheers,
Steen
CLA, CTA, CLED & LabVIEW Champion

I don't do a lot of (actually any) source distributions of embedded files, but I can tell you that there was a bug in earlier versions where during an application build, the destination path was reported incorrectly. Perhaps this is related.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Real-Time Application doesn't run; source code works fine

The short version is I'm programming a cRIO and apparently the RT code isn't running after being deployed and I can't figure out why. This is further complicated that I'm doing all this remotely and I don't have direct access to the unit since I'm 500 miles away. I'm working through a couple of other guys who know some LabVIEW, but neither works at the site so they have to explicitely travel out there every time I have a bright idea.
I was out there a few weeks ago. During this time I created a simple cRIO code, since I'm new to cRIO, that allowed the user to move a control and change a graph. It worked fine, but I should note it did not have an FPGA component. After that I worked on the real code, which reads some sensors, displays the results on a UI and logs the results. This did have FPGA. I used it in the LabVIEW environment and it worked fine, but I ran out of time before I could complete a release version and deploy the RT as a compiled application. I sent them the release version later, my contact deployed it but got network stream errors when running the UI.
After hours of looking at network problems and sending over debug versions, I tried creating a log on the RT level so I could see what was going on. The log doesn't even open, even if it's the first command in the code. I pored through the forums and found http://forums.ni.com/t5/LabVIEW/cRIO-Troubleshooting-creation-and-deployment-of-startup/td-p/1956475... which took me in a new direction.
I had my contact use the RT debug console and when he pulls up the RT front panel, it shows a broken run arrow. He clicks it and nothing happens -- no running, no bug list. If he pulls up the bug list manually, it's empty. Again the RT works fine if you run it through LabVIEW and not as a compiled real-time application. He also noticed that the Open FPGA VI was grayed out on the block diagram. No other icons are.
So the problem appears to be that the compiled RT application is getting some kind of error but not telling me what it is, and it seems to be related to opening the FPGA. I've recompiled the FPGA and RT. I've had him recompile the RT himself, but not the FPGA because it would take hours. He's downloading everything correctly to the cRIO. The RT is set to run automatically. He's rebooting the cRIO every time he deploys the RT. They have LabVIEW on a computer there but it doesn't have the right drivers to run the code from the LV environment. I'm resisting having them install the dirvers because downloading big files is complicated there due to security restrictions and a lousy network connection at a remote site. Besides that doesn't solve the problem of the RT executable not running the same as the source code, which according to the thread above appears to be a thing.
The latest thing I'm trying is that I sent him instructions for how to build a source distribution from the project I sent and try deploying that to the cRIO. Even if that works I'm not sure that's an acceptable solution because I assume running the VI rather than the EXE is slower, and they need speed on this project.
I simply have no idea where to go from here. I probably need to get direct acess to the cRIO and I might be able to convince them to ship it to me so I can figure this out, but I'm not sure where I'd even start other than the standard voodoo debugging of "try stuff at random until something works". I'm open to suggestions if anyone has managed to solve this before.
Code snippet of the first part of the project is attached, though I'm not sure how much good it will do. I'm really stumped and the client is getting frustrated with how much of the budget is going to fix this.
Solved!
Go to Solution.
Attachments:
RTMainSnippet.png ‏623 KB

Have you checked the cRIO error log? Usually I'd access it through the LabVIEW project (right-click on the target, don't remember the exact menu options and I don't have the RT toolkit installed on this machine to check), but it must be stored somewhere on the cRIO as well, although I don't know if it's in a human-readable format.
Which cRIO are you using? What exactly do you mean by "debug console"? (This may be related to the cRIO - the newer ones have video out, although I don't know if that's what you're referring to.) With a broken run arrow, you won't get an error list unless you're running in the development environment.
Have you confirmed that the software installed on the cRIO matches the version you're using for development, including patch level? Get someone to connect to the cRIO with Measurement and Automation Explorer, and get a list of the software installed on the cRIO.
Sounds like the ability to connect with a remote debugger would be helpful here, if you can get the right drivers installed on the machine with LabVIEW that's connected to the cRIO. Make sure all driver versions match what you're using. Any chance you could then do a remote desktop connection from your work site to the remote LabVIEW machine?

Error 6 during Build Specification of My Source Distribution in Project explorer

While trying to convert a LV 8.0 application into a project file I get an Error 6. Message as Follows:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 6 occurred at ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> SDBEP_Invoke_Build_Engine.vi -> SDBUIP_Build_Invoke.vi -> SDBUIP_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Generic file I/O error.
NI-488: I/O operation aborted.
The error referenced a vi from a third-party labview driver for Iotech hardware.
Could the path be too long?

JT1958,
These types of errors are a bit tricky to diagnose. I would try the following, in order of easiness:
1) Mass compile your project by doing a <Ctrl-Shift-Run> on your top level VI to make sure your project is linked correctly. Sometimes if there is a bad VI reference somewhere you can have these types of problems.
2) The path being to long most likely isn't the issue, but if you suspect the IOTech driver, you may try taking it out of your code and see if that allows you to build a source distribution. If that works, try creating a simple project that contains VIs from the driver and see if you can get it to build. The point is to narrow down what specifically is causing the build to fail.
3) You can try to build this in LabVIEW 8.2 as some improvements to the source distribution builder were made.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

Error building source distribution of a project containing real-time utility VIs

Similar Messages

Maybe you are looking for