Sharing Device Cores Across Different Blue Pills
For some workflows it may be necessary to have a package running on a one Blue Pill and use it on another.
Example 1: You are controlling and Atem, and are on a different continent, the latency would probably not work well over the distance with Atem's own protocol, so you use the Blue Pill, then the Blue Pill to Blue Pill communication does handle latency better.
Example 2: When using a Blue Pill connected to a camera with a USB cable, you have to run the cores locally as they need serial access, but you probably want a central instance of reactor controlling all of them.
Process:
To connect two Blue Pill devices when a device core/package is running on one but not the other:
- Install DeviceCore-Connector package on the BP running the needed package locally.
- AccessMode= default-allow
- On the BP not running the package locally, select Add Device on the Home Page
-
Search for shared core, selecting the specific core on the panel that you are looking to connect to.Please note, the shared core will not come up if searching by the Device Core name, only by the Device Name which is Shared Core. Selecting the specific shared core will bring in all individual devices connected to by that core on the remote Blue Pill device.
-
After adding the desired remote core it should show in the Device Core name the IP address it is connecting to the core from.
-
If it is not possible to autodiscover the shared core, it can be added manually by adding the device to be controlled.
-
Setting the proper device details for the device.
-
Click into the Device Core Details for the device.
-
Enter the IP address of the remote Blue Pill that will be hosting the device core locally.
No Comments