- How do you see there is a new revision available?
- How do you update that component without closing and reopening the assembly?
You’re using Teamcenter 10 and NX 9, and you have an assembly open in NX, when someone creates a new revision of one of the components in your assembly. In this situation, two questions may come to mind:
Case Study: Stöckli Swiss Sports uses Solid Edge to Optimize and Individualize any Ski in Just One Hour
Stöckli Swiss Sports AG is the last big Swiss ski manufacturer. Every year, approximately 35 employees manufacture about 50,000 pairs of skis, all hand-made. About 40 percent of these are exported, predominantly to the United States, Italy and Austria. The company also produces ski boots and poles, fitness/adventure apparel, bikes and other outdoor equipment.
Spring Srl was established in 1998 in Monteviale, Italy, near Vicenza, by business people with previous experience in product design, molds and dies, and prototyping. The company’s core business is engineering services, delivered by a team of qualified engineers who are continuously trained to use the most advanced computer-aided design, engineering, and manufacturing (CAD/CAM/CAE) tools. Over the years, Spring has expanded its service portfolio, building up a rapid prototyping line that can respond to different customer requirements.
Case Study: Offshore Oil Vessel Specialist, Inocean, Advances Agility, Innovation and Business Goals with NX and Teamcenter
Here’s a quick tip that a lot of end users don’t think about since we’re so accustomed to 3D graphics devices to manipulate the graphics display in both Solid Edge and NX.
After observing another person manipulating the display in a drafting document in Solid Edge ST7, an end user asked me how to get the mouse wheel to zoom in and out instead of the default behavior of panning the displayed drawing up and down in the Solid Edge application window. Since the default use for the mouse wheel on my Solid Edge desktop was to zoom in and out, it took me a few minutes to figure out what controls the two behaviors.
We are pleased to announce the release of Maintenance Pack 06 (MP06) for Solid Edge ST7. Just a reminder that you will need your webkey to download this maintenance pack.
Read _Me Doc
If you have any questions, please do not hesitate to contact us at firstname.lastname@example.org.
For most Siemens’ CAD/CAM end users, seeing a license error dialog appear right in the middle of the screen during NX boot up means that progress stops and someone has to be called. Even I have to see that ugly message appear and re-appear several times before I decide that it is not going to go away.
Unfortunately, having a screen shot of the error message is a good start, but it is rarely enough information to diagnose the problem. With a little bit of knowledge regarding your license installation configuration and what factors are involved, you may be able to understand what is happening and help to expedite the solution.
In what ways does Siemens license their NX software? At the end user or client level, there are basically two ways that NX functionality is licensed and controlled when you launch NX. They are commonly known as “floating” and “node locked.” Node locked licensing allows you to utilize NX functionality that is authorized for a specific work station or “node.” The number of licenses do not need to be counted because there is only one license allocation for a given piece of NX functionality that is authorized for that specific node.
On the other hand, floating licenses allows you to use NX functionality from any work station on the same network because a license server controls the number of licenses handed out for the NX functionality that you are trying to use. Floating licenses are always counted by the license server, and are best characterized as a pool of licenses.
Is it true that you cannot use a license server for node locked licensing? This is not entirely true. It is true however, that all floating licenses must be managed by a license server, so you must use a license server if you incorporate both floating and node locked licenses in the same installation. Using a license server for node locked licenses can also be considered as a convenience, since it allows you to maintain a single license file on the server that controls both counted (floating) and uncounted (node locked) licenses.
For instance, when you are using a license server with node locked licenses, and you are upgrading from NX 9 to NX 10, you only have to replace one license file on the license server machine because all of your client machines will be looking to the server for an appropriate license when it is needed.
On the other hand, if you had a group of node locked licenses in a single license file that is not managed by a license server, you would have to distribute the license file to every machine in the list, and put it in the right location at each client machine.
Where does the license server reside and who maintains it? These are license configuration options that are determined by the customer. The SPLM License Server is simply a background service that can run on any machine in a supported Windows, Mac OS, or Linux environment. It is tied to a specific machine by Composite ID which is an encrypted hexadecimal number that is derived from the MAC address of one of the network adapters of the server machine.
The customer can register up to (3) composite IDs to assure replication in case a server fails or goes off line. The SPLM License Server service can be run on the same machine as the NX software so that the same machine can be both client and server.
If a floating license is tied to a server by Composite ID, what ties a node locked license to a specific machine? In node locked licensing, each piece of NX functionality is linked to a specific machine by an unencrypted MAC address of one of the network adapters installed in the client machine.
How do I determine if the license configuration for my NX installation is controlled by a server? The easiest way to make this determination is by looking at the system environment variables on your machine. You can view the Windows system environment variables by using the “set” command at the command prompt in a cmd window.
Here is an example of typical output:
Subscribe to our Blog!