Convert legacy YIPI5/WOWE project to Core Studio

Core Studio is the latest dev tool for the Reax Series controllers. If you want to re-purpose an older project that was ceated in YIPI5 and WOWE, you can follow the below steps to convert/import to the new Core Studio format.

Import WOWE (.wmod) into Core Studio:

To import an existing Wowe project in Core-studio, you need to:

• Navigate to the Wowe project location using File Explorer in Windows.
• Drag the .wmod file you want to import from the File Explorer to the Core-studio window and drop it over the core-studio project.
• Repeat that (3) for the related .wir and .wsm files (dnd from file explorer to the corresponding folder in the Core-Studio project)
• Change the extension of the .wmod file to .cc. At this point you should be able to double click and open the .cc file in Core-studio.

Note: If you only have .wem, use WOWE to convert to .wmod.)

Import YIPI5 (.Y5P) into Core Studio:

• Unzip the .y5p file in new folder. For that you might need to change the extension to .zip
• Drag all the files contained in the .y5p archive from the File Explorer to the Core-studio window and drop it over the core-studio project.
• Change the extension of the .ycp file to .ci. At this point you should be able to double click and open the .ci file in Core-studio.
• Link the panel (.ci) to the proper .cc file: in the Settings view / Linked Code file section, browse to the .cc file related to the panel.

Important Notes:

• EXPRESSIONS Expressions in the .wmod actions and events may not be fully compatible with Core-Studio. Most of them will need manual review and possibly rework.
• USE TELNET ENCODING Legacy projects may have been working with this checked, but it will break Telnet control on most all devices in CS
• HTTP POST ACTIONS Unlike legacy projects, CS requires the HTTP POST/GET IP (output to) to include an 'http://' or 'https://'
• RPC COMMANDS FROM EXTERNAL DEVICES If you are using an external software or another controller to send RPC commands to the ReAX controller, you now need to make sure you define the HTTP port '8888'. Example: 192.168.1.10:8888/rpc
  For legacy QX and NX devices, you must declare port 80 and the /rpc path. Example:
  192.168.1.10:80/rpc
• REMOTE HOST
  RX Series:
  ReAX devices only need the IP address to function with Remote Host. The other info (http://, :8888/rpc) will be added automatically when the command is sent.
  Note: The "Relay Toggle" RPC is not currently implemented.
  LXC, DXB-8i, and legacy (QX, NX, WACI POD, WACI Nugget, WACI, etc.):
  These legacy devices rely on port 80 to function with Remote Host. Enter 'ip_address:80'. The other info (http://, /rpc) will be added automatically when the command is sent.
• TELNET EVENTS PORT IS 2323 When the connect box is checked, it will act as a client (origin should be 'ip:port'). When unchecked, it will act as a server (origin should be 'ip').
  More info on Telnet/TCP here: https://support.auroramultimedia.com/kb/faq.php?id=3
• CHANGE INCOMING DATA TRIGGER Change \g to _g. Also, _g now requires expression box checked.