Common Problems In Studio

This article was written for version 2.0.9 of Core. Click here for the most recent version of the help center.

Find solutions to common problems reported through Studio’s system state module.

1. Missing manager error

Missing manager error

This is fixed by starting the manager, which can be done from the command line:

$ polysync-core-manager
2033-01-05 10:28:46 DEBUG [20749:src/polysync_core.c:884] manager_daemon : created daemon process

Studio will automatically detect when the manager starts, and system state will update to look similar to this:

Missing manager error recovery

In standby, hardware and replay contexts, it’s required that the PolySync manager is running on each host defined in the SDF .

2. Missing nodes error

Missing nodes error

Hardware

  1. Toggle nodes into standby mode
  2. Toggle nodes back into hardware mode

The nodes will reinitialize their connection with the hardware devices and sensors. If one or more nodes are still in an error state, close Studio and use the manager to stop all other nodes and clean the environment.

$ polysync-core-manager -f 

Now the system is in a clean state. Restart the manager and start Studio to replay a logfile session:

$ polysync-core-manager
$ polysync-core-studio

Replay

  1. Toggle nodes into standby mode
  2. Reselect the logfile session from the playlist
  3. Playback will begin and nodes show up in system state with the blue replay status

Missing nodes error recovery

If one or modes remain in an error state, close Studio and use the manager to stop all other nodes and clean the environment.

$ polysync-core-manager -f 

Now the system is in a clean state. Restart the manager and start Studio to replay a logfile sesion:

$ polysync-core-manager
$ polysync-core-studio