User Tools
software:knowledge-base:brand-knowledge-base:crestron
Differences
This shows you the differences between two versions of the page.
|
software:knowledge-base:brand-knowledge-base:crestron [2012/09/11 03:42] jarrod |
software:knowledge-base:brand-knowledge-base:crestron [2015/09/24 22:40] (current) jarrod [CrestronMobile Module] |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| CommandFusion iViewer can communicate with Crestron processors in a variety of ways: | CommandFusion iViewer can communicate with Crestron processors in a variety of ways: | ||
| + | * Using the SIMPL CrestronMobile symbol and the [[https://github.com/CommandFusion/CrestronMobile|iViewer CrestronMobile module]] ([[https://github.com/CommandFusion/CrestronMobile/wiki|documentation]]). | ||
| + | * Using the SIMPL XPanel symbol and the [[https://github.com/CommandFusion/CIP|iViewer CIP module]] ([[https://github.com/CommandFusion/CIP/wiki|documentation]]). | ||
| * [[https://github.com/CommandFusion/CrestronModule|iViewer Server SIMPL+ module]], using the [[http://cmdf.us/controlprotocol|Control System protocol]] built into iViewer. | * [[https://github.com/CommandFusion/CrestronModule|iViewer Server SIMPL+ module]], using the [[http://cmdf.us/controlprotocol|Control System protocol]] built into iViewer. | ||
| - | * Using the SIMPL CrestronMobile symbol and the [[https://github.com/CommandFusion/CrestronMobile|iViewer CrestronMobile module]]. | ||
| - | * Using the SIMPL XPanel symbol and the [[https://github.com/CommandFusion/CIP|iViewer CIP module]]. | ||
| Documentation for each method is available on their respective GitHub repositories. | Documentation for each method is available on their respective GitHub repositories. | ||
| - | |||
| ===== Comparison of Methods ===== | ===== Comparison of Methods ===== | ||
| - | Each method has pros and cons, which have been discussed quite frequently on the [[https://groups.google.com/forum/?fromgroups#!forum/commandfusion|CommandFusion Software Google Group]].\\ | + | Each method has pros and cons, which have been discussed quite frequently on the [[https://groups.google.com/forum/?fromgroups#!forum/commandfusion|CommandFusion Software Google Group]]. |
| In Summary: | In Summary: | ||
| - | |||
| - | ==== iViewer SIMPL+ Module ==== | ||
| - | * **Pros** | ||
| - | * Communication protocol natively built into iViewer, less overhead (No JavaScript required). | ||
| - | * Very easy to integrate in guiDesigner - just define the connection properties in project properties and join changes propagate automatically. | ||
| - | * **Cons** | ||
| - | * Relies on the TCP Server functionality in SIMPL+, which has been found to not be as reliable as the lower level access that native Crestron symbols provide. | ||
| - | * Less flexibility in communications - Can only talk to a single processor at once, all joins will propagate (no way to limit join ranges). | ||
| - | * All join types are cluttered into the SIMPL+ module, and you must edit the SIMPL+ code to increase/decrease the number of joins that can be used. | ||
| ==== CrestronMobile Module ==== | ==== CrestronMobile Module ==== | ||
| + | <WRAP center round info 80%> | ||
| + | **For first time integration with Crestron, we recommend this approach.** | ||
| + | </WRAP> | ||
| + | |||
| * **Pros** | * **Pros** | ||
| * Uses the native CrestronMobile SIMPL symbol - familiar symbol to connect to your SIMPL programs. | * Uses the native CrestronMobile SIMPL symbol - familiar symbol to connect to your SIMPL programs. | ||
| * Allows for flexible communication routing (filtering join ranges, multiple processors) | * Allows for flexible communication routing (filtering join ranges, multiple processors) | ||
| + | * Supports the use of different text encodings via system properties for language character sets such as cyrillic via UTF-8 encoding. | ||
| * **Cons** | * **Cons** | ||
| * Relies in the CrestronMobile symbol protocol - if this was ever changed by Crestron, the module may stop working until it is updated to support any changes. | * Relies in the CrestronMobile symbol protocol - if this was ever changed by Crestron, the module may stop working until it is updated to support any changes. | ||
| Line 37: | Line 33: | ||
| * More complicated to setup | * More complicated to setup | ||
| + | ==== iViewer SIMPL+ Module ==== | ||
| + | <WRAP center round important 80%> | ||
| + | Not recommended for 3 series products. Choose the Crestron Mobile method above if you are using 3 series processors. | ||
| + | </WRAP> | ||
| + | * **Pros** | ||
| + | * Communication protocol natively built into iViewer, less overhead (No JavaScript required). | ||
| + | * Very easy to integrate in guiDesigner - just define the connection properties in project properties and join changes propagate automatically. | ||
| + | * **Cons** | ||
| + | * Relies on the TCP Server functionality in SIMPL+, which has been found to not be as reliable as the lower level access that native Crestron symbols provide. | ||
| + | * Less flexibility in communications - Can only talk to a single processor at once, all joins will propagate (no way to limit join ranges). | ||
| + | * All join types are cluttered into the SIMPL+ module, and you must edit the SIMPL+ code to increase/decrease the number of joins that can be used. | ||
| + | * No text encoding support | ||
| + | ===== Common Problems ===== | ||
| + | ==== iViewer wont connect to my Crestron system ==== | ||
| + | Firstly, make sure you are using the latest version of iViewer 4 (not CF iViewer). If the problem persists - contact us via one of the options on our [[http://www.commandfusion.com/support|support page.]] | ||
software/knowledge-base/brand-knowledge-base/crestron.txt · Last modified: 2015/09/24 22:40 by jarrod
