Sylk Bus Bandwidth and Proxy File Usage

Adding Sylk devices like Zio Wall Modules would consume Proxy File space in Spyder. Proxy File Space is used to store Sylk device configuration information. Addition of Sylk device also uses Sylk bus bandwidth. Each Sylk device is powered by the connected Spyder controller. Spyder has a limit on the amount of power it can deliver. Adddition of Sylk device consumes some portion of the Spyder Sylk power capacity. Spyder's Resource Usage view provides information about Spyder's Proxy File usage. When Spyder's Power capacity limit is hit, the tool cautions the user by showing appropriate message during validation process. The tool does not track the Sylk bus bandwidth.

The following tips help optimize Sylk bus bandwidth usage and Spyder Proxy File usage:

On a Sylk Bus basis
Total number of messages on the Sylk Bus per unit of time 1. Reduce the number of parameters being sent from Spyder or Sylk Device.
2. In Zios, reduce scheduling. Have one Zio show scheduling instead of all Zios. Use a 5-2 schedule scheme instead of 7 or 8 day.
Total power consumption on the Sylk Bus 1. Reduce the number of devices on the Sylk Bus.
Total of 14 Sylk devices + 1 Spyder on the Sylk bus 1. Reduce the number of devices on the Sylk Bus.
On a Spyder basis (Sylk bus specific)
Total Proxy file size 1. Reduce the configuration in one or more Sylk Devices by following the tips specific to the device.
2. Reduce the configuration in one or more Sylk bus devices by following their tips.
Number of Fail Detects The tool manages this and optimizes.
Number of Send table entries 1. Reduce the number of Value from Controller parameters.
2. Reduce the number of Network setpoint parameters.
3. In Zios, use a 5-2 schedule scheme instead of 7 or 8 day.
4. In Zios, disable scheduling.
Number of Group table entries 1. See above tips for Send table entries.
Number of Error bits 1. See tips on reducing Spyder number of Fail Detects.