• The Studio is not connecting over the network with the Target, what should I do?
  
  
• In Studio, where do I setup the Domain?
  
  
• In Studio, how do I configure my network radios to communicate on the DIS network?
  
  
• In Studio, when I attempt to add a Radio Bus, World Position Bus, or Power Bus the following message appears, “Unable to set value. Data Viewer is closed.” What is my next step?
  
  
• In Studio, there are no variables or data displaying in the Component ACE Data Viewer, is there something wrong?
  
  
• In Studio, sometimes the icons are yellow question marks instead of their correct icon.
  
  
• In RMS, what do the question marks or the red 'X' displayed on the RMS Health pages mean?
  
  
• In RMS, how do I extract detailed log files to send to ASTi?
  
  
• In Studio, I'm experiencing slow responsiveness and the Studio is not able to find Targets over the network, what should I do?
  
  
• RMS reports "none" for the current project, Studio reports "Install Ok" what should I do?

Q: The Studio is not connecting over the network with the Target, what should I do?

A: This problem is solved by:

1. Ensuring that the Targets' eth ports (ETH0, ETH1, ETH2) are not in the same network class. For example, you can't have ETH0 and ETH1 set to 192.42.172.100 and 192.42.172.101, respectively.
2. Ensuring that the ACENet approved Ethernet switch supports Gigabyte connection speed.
   Note: ACENet does not support the use of routers or hubs.
3. Look on the switch and ensure the LED is lit for Gig and not 10/100... this could mean you need to change your network cable.

Q: In Studio, where do I setup the Domain?

A: The Domain is setup in two (2) locations. Global Domains for the entire project are setup in the Project Manager in the Domain Editor and the other location is in the Transceiver component in the model. A global Domain is not required for ACE radios to communicate over ASTiNet, but it is required for DIS and HLA communications. If you choose to not use the global Domain, all the ACE Transceiver components must share the same Domain to communicate.

Q: In Studio, how do I configure my network radios to communicate on the DIS network?

A: There are several steps required in Studio to configure DIS and radio parameters.
Note: These steps are assuming that you've setup the Comm Plan and RCU components correctly.

1. Domain Editor - In the DIS tab, add a DIS file and setup your default site and App IDs. If you leave them blank (not zeros) the radio environment will add in a default of the last two (2) octets of the Target's IP address. In the Domain tab, add a Domain, select the DIS file and assign an exercise ID.
2. DIS Gateway - In the Servers folder, right-click and add a DIS Gateway. Assign a network interface, port and main broadcast/multicast address.
3. Telestra Editor - Select the Sim Server tab then select your DIS Gateway.
4. In each Transceiver component in your model you must set the following values:
   a. RadioName - For example, UHF_Radio or Pilot-Radio
   b. DomainName - must match global Domain in Domain Editor.
   c. ProtocolID - This is a string of the format 'DIS:Site:App:Radio' or 'DIS:Entity:Radio' or 'DIS:Radio', where site, app, entity, and radio are positive integers. If you exclude site and app, the radio environment will assign the default site and app from the DIS file in the Domain Editor to the radio. If you exclude entity, the radio environment will assign a random unique number for the entity ID of the radio. For example, 'DIS:3.4' will use 3 as the radio's entity and 4 as the radio ID. The site and app will populate from the defaults in the Domain.

Q: In Studio, when I attempt to add a Radio Bus, World Position Bus, or Power Bus the following message appears, “Unable to set value. Data Viewer is closed.” What is my next step?

A: Restart your Studio and Target systems. If that does not fix the problem, close the ACE Studio application. Open a terminal and run ACE Studio from a terminal window by typing the following command 'ace-studio -d'. Perform the same function that reproduced the error and look at the terminal window to see if there was an error when you tried to assign the bus. It will most likely begin with the line “Traceback:.” ASTi developers rely on these detailed logs to diagnose and fix the problem.

Q: In Studio, there are no variables or data displaying in the Component ACE Data Viewer, is there something wrong?

A: This is caused when the ACE Publisher daemon or the realtime framework is not running or malfunctioning. Follow the steps below to solve this.

1. Reload the model. This is done by clicking on the icon between the stop button and the words 'Zoom Out' in the Load Viewer top tool bar.
2. Re-install the project.
3. Reboot the Target.

If that does not fix it, you'll need to extract more detailed logs from the Target system so ASTi can diagnose and find the root of the problem. Refer to the question, “How do I extract detailed log files to send to ASTi?”.

Q: In Studio, sometimes the icons are yellow question marks instead of their correct icon.

A: There is an easy work-around for software versions with this issue.

1. Close ACE Studio application.
2. Open a terminal window.
3. Type the following: rm -rf /tmp/studio_cache
   For some software versions this may produce an error, if an error is produced type the following: rm -rf /tmp/studio_cache_aceuser
4. Open ACE Studio application.
5. Re-install the Project.

Note there is a space between -rf and /tmp.

Q: In RMS, what do the question marks or the red 'X' displayed on the RMS Health pages mean?

A: Question marks in the RMS Health system are warnings. A red 'X' indicates an error. The Health system could potentially be warning us of one or more hundreds of status flags. So it is important to understand how the Health system works.

The RMS Health system consists of a tree-like structure. Each section has sub-sections and those sub-sections have sub-sections and so on. For example, if you see a yellow question mark next to 'ACE Realtime' it is telling you that one or more of ACE Realtime's sub-sections has a warning. You must click on 'ACE Realtime' to expand it and reveal it's sub-sections in order to identify the root of the warning. By far the most common occurrence is a yellow question mark next to 'ACE Realtime.' If you expand it you'll see a red 'X' by Model. This is simply telling us that the model is not running. If you click on 'Show Detail' on the right of the page you can see that it says 'Stopped' next to model. If you believe you've dug down as far as you can go and see a question mark or red 'X' next to an item, reboot the system. If the warning or error does not go away refer to the question, "How do I extract detailed log files to send to ASTi?"

Q: In RMS, how do I extract detailed log files to send to ASTi?

A: In RMS, navigate to System > Logs. Select the 'download log file' button. Use the “Save Page As…” feature on your web browser to save the log as a text file and email it to sales@asti-usa.com. To help ASTi diagnose your problem, please include steps and instructions on how to reproduce the problem, or explain what you were doing in ACE Studio when the problem occurred.

Q: In Studio, I'm experiencing slow responsiveness and the Studio is not able to find Targets over the network, what should I do?

A: There are a few possible problems including an incorrect gateway IP, invalid domain, or invalid DNS. Here are some possible solutions:

1. You may have an invalid gateway IP set in the Studio's network settings. Correct the address. If no gateway exists, use the Studio's own IP address for the gateway field.
2. You may have an invalid Domain or Domain Name System (DNS). Verify that these are set correctly. Contact your network administrator to see if the network is configured to use DNS.
   If you do not have a DNS server or gateway on the network between the Studio and Target platforms, make sure that there is nothing specified in the DNS or gateway field of the Target. This is available in the RMS Configuration > Networking page. Also make sure that the same is true on the Studio. This is available in the System > Administrator > Network.
   
3. Next, there is a daemon that maintains communications between the Studio and Target. Restarting the daemon may resolve the issues. The syntax for this is:
   
   On the Studio:

   /etc/init.d/anzac_client restart
   

   On the Target:

   /etc/initd/anzac_server restart
   

   These must run as root.
4. You may need to delete the Studio cache.
5. If none of the above resolves the issue, reboot both Studio and Target platforms.

Q: RMS reports "none" for the current project, Studio reports "Install Ok" what should I do?

A: In addition to the project not loading and the Studio report, there are a few other debug issues to check.

• Does the RMS Log file messages report any errors?
• Does RMS report an abnormally high 'non-realtime' CPU load (>85%)?
• And most importantly, does running the 'top -b -n 60 -d 1.0 > a.out' command on the Target command-line report that the "ace-modeld" process was running with non-realtimepriority? It should report RTin the Top 'PR' column. If the "ace-modeld" process reports a numeric priority, then there is a problem.

The system may be running in 'single-CPU' mode which is most likely due to misconfiguration of the BIOS. Refer to the Target Cold Start Procedure (DOC-02-TEL4-TCS-1) and follow the steps to set the system's BIOS settings.