CPN Tools automatically syntax checks your nets as you create them or when you load in a net. You can see by color indications how far the check has gotten. The color indications are shown in the index, underlining the name of the page where the color belongs. If the page is open in a binder, the color is also shown in the page tab at the top of the page, and on the CPN element where the color belongs.
The orange aura indicates that an element is not currently checked.
When you load a net, the syntax check takes a couple of minutes to complete. During this phase, the elements will change aura from orange to yellow to no aura (or red, if there is an error).
If the orange aura stays, it is probably because either there is something missing or there is an error on a related net element. The following explains when net elements will be checked:
If your elements keep the orange glow, and you can see no obvious reason (e.g., errors on connected elements or missing inscriptions), the simulator process might be “stuck”. Try changing an inscription on the elements - this should provoke a new syntax check. If this doesn't work, try saving the net, closing it and re-opening. The whole net should now be re-checked.
If nothing happens, it is probably because the simulator process could not be started. Check if you have a process called
Declarations are checked starting from the top. If a declaration depends on a later declaration, it will get an error saying the other declaration is not defined.
Declarations with errors are rechecked when a change is made in any declaration.
Monitors are checked starting from the top. If a monitor depends on a later monitor, an error message will be added to the monitor.
A red aura means the element has been checked but had an error. A speech bubble should appear with the exact error message. Elements connected to the element with the error, e.g. transitions connected to a place with errors, are not checked until the error is fixed.
For more information about different kinds of errors see:
If your elements have no aura, it is because they are checked and found ok. If one or more transitions should be enabled but are not, try using the Rewind tool in the Simulation tools to initialize the simulation.
A blue aura shows dependencies between declarations, inscriptions and other elements.
If you move the cursor over a declaration in the index, all nodes and other elements using that declaration will get a dark blue aura, also shown in the index and page tabs.
If you move the cursor over a monitor name in the index, all nodes that are associated with the monitor will get a dark blue aura, also shown in the index and page tabs.
If you move the cursor over an inscription on a page, the element it belongs to will get an aqua aura (only shown on the element).
If you move the cursor over a place or transition on a page, a dark blue aura is added to all of the declarations that the node depends on, and all of the monitors that are associated with the node.
If you move the cursor over a hierarchy tag, different relationships will be highlighted. For more information see Hierarchy tags.