DOCSLIB.ORG

SIMPL ™ Windows

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SIMPL ™ Windows Crestron SIMPL™ Windows® Software Installation & Operations Guide This document was prepared and written by the Technical Documentation department at: Crestron Electronics, Inc. 15 Volvo Drive Rockleigh, NJ 07647 1-888-CRESTRON All brand names, product names and trademarks are the property of their respective owners. ©2002 Crestron Electronics, Inc. Crestron SIMPL™ Windows Software Contents Introduction 1 The Intent of this SIMPL™ Windowsâ Manual ...................................................1 SIMPL Windows New Features ..........................................................................1 SIMPL™ Windowsâ Review and Programming Preparation..............................3 SIMPL™ Windowsâ ...............................................................................3 System Design & Programming Process...............................................3 Crestron’s Programming Design Kit ......................................................4 VisionTools™ Pro-e ...............................................................................4 Programming Process ...........................................................................4 Contact Crestron Electronics, Inc. ......................................................................6 Trademark Information........................................................................................6 Installing SIMPL™ Windows® 7 System Requirements.........................................................................................7 Crestron Database Requirements ......................................................................7 Installing from the Crestron Web Site .................................................................7 Installing from the Crestron ControlCD...............................................................8 Uninstall SIMPL™ Windows®.............................................................................8 DOS Workshop 11 Migration to SIMPL Windows............................................................................11 Changes from Workshop ..................................................................................11 Symbol CrossReference......................................................................11 SpeedKey.............................................................................................12 KeyCombo Shortcut Table...................................................................12 Feature Comparison .........................................................................................14 Importing Workshop Programs .........................................................................15 SIMPL™ Windows®– Getting Started 17 SIMPL Windows Applications ...........................................................................17 Opening SIMPL Windows .................................................................................18 Set Directory Paths ...........................................................................................18 Create A New Program.....................................................................................19 Program Header ..................................................................................19 Configuration Manager 21 Accessing Configuration Manager....................................................................21 Configuration Manager Navigation ...................................................................22 Installation & Operations Guide – DOC. 5728C Crestron SIMPL Windows • i Software Crestron SIMPL™ Windows Device Library ......................................................................................22 Network System View ..........................................................................24 Detail System View ..............................................................................24 System Device Tree.............................................................................24 Configuration Manager Button Bar ...................................................................25 Configuring the System.....................................................................................26 Selecting Hardware..............................................................................26 Replacing Devices ...............................................................................28 Configure System Control Devices......................................................28 Configure User Devices .......................................................................34 Deleting Devices ..................................................................................39 Automatically Configure Devices .........................................................39 Importing VisionTools™ for Windowsâ and VisionTools™ Pro-e Projects.......40 Default Logic from Crestron Database .............................................................42 Program Manager 43 Accessing Program Manager............................................................................43 Screen Navigation.............................................................................................44 Symbol Library .....................................................................................44 Program View.......................................................................................45 Detail View ...........................................................................................47 Bookmark.............................................................................................47 World View...........................................................................................48 Signal Tray...........................................................................................49 Program Manager Button Bar...........................................................................50 Programming in SIMPL Windows .....................................................................51 Symbols & Signals ............................................................................................52 Symbol Properties................................................................................52 Symbol Categories...............................................................................54 Symbol Title Bar...................................................................................54 Programming a System ....................................................................................55 Define Signals from User Interface......................................................55 Using Logic Symbols ...........................................................................57 Naming Signals....................................................................................59 Subsystems..........................................................................................60 Programming with User Interfaces....................................................................61 Feedback .............................................................................................61 Indirect Text .........................................................................................63 Imported UI Projects ............................................................................63 Using Macros ....................................................................................................64 Crestron Macros ..................................................................................65 User Macros.........................................................................................66 Device Programming Information 71 Serial Driver Programming Information ............................................................71 [TX$].....................................................................................................71 [RX$] ....................................................................................................71 [BREAK]...............................................................................................71 [RTS] ....................................................................................................72 [CTS] ....................................................................................................72 Other Lines...........................................................................................72 [enable] ................................................................................................72 ii • Crestron SIMPL Windows Installation & Operations Guide – DOC. 5728C Crestron SIMPL™ Windows Software Programming Features 73 Signal Colors.....................................................................................................73 Signal Operations .............................................................................................74 Navigating Symbol Inputs and Outputs ...............................................74 Create New Signals .............................................................................74 Selecting Signals .................................................................................75 Edit Signal Name .................................................................................75 Rename Signal Globally ......................................................................76 Disconnect a Signal .............................................................................76 Replacing a Signal ...............................................................................77 Connect Signals...................................................................................77
Load more

Recommended publications
  • Distributed Programming I (Socket - Nov'09)
    Distributed programming I (socket - nov'09) Warning for programmers network programming is dangerously close to O.S. Network programming: sockets kernel, and therefore: It can easily hang the O.S. verify the results of every operation, without assuming anything as granted Antonio Lioy < [email protected] > APIs can vary in details that are minimal but important consider every possible situation to create english version created and modified by “portable” programs Marco D. Aime < [email protected] > we will try to use Posix 1.g Politecnico di Torino Dip. Automatica e Informatica ISO/OSI, TCP/IP, network programming Exercise – copying data copy the content of file F1 (first parameter on the application command line) into file F2 (second parameter on the 7. application details application command line) user 6. presentation (l6: XDR/XML/... process l5: RPC/SOAP/...) 5. session network programming 4. transport TCP UDP SCTP interface 3. network IPv4, IPv6 kernel communication 2. data link device driver details 1. physical and hardware OSI model IP suite ref. UNP Intro copyfile.c Error messages Error functions must contain at least: best to define standard error reporting functions [ PROG ] program name which accept: [ LEVEL ] error level (info, warning, error, bug) a format string for the error [ TEXT ] error signalling, the most specific as possible a list of parameters to be printed (e.g. input file name and line where the problem has UNP, appendix D.4 (D.3 in 3rd edition) occurred) errno? termination? log level [ ERRNO ] system error number and/or name (if applicable) err_msg no no LOG_INFO err_quit no exit(1) LOG_ERR suggested format: err_ret yes no LOG_INFO err_sys yes exit(1) LOG_ERR ( PROG ) LEVEL - TEXT : ERRNO err_dump yes abort( ) LOG_ERR errlib.h errlib.c © A.Lioy - Politecnico di Torino (2009) B-1 Distributed programming I (socket - nov'09) stdarg.h stdarg.h usage example variable list of arguments (ANSI C) create a function named my_printf declared with an ellipsis (.
    [Show full text]
  • Beej's Guide to Unix IPC
    Beej's Guide to Unix IPC Brian “Beej Jorgensen” Hall [email protected] Version 1.1.3 December 1, 2015 Copyright © 2015 Brian “Beej Jorgensen” Hall This guide is written in XML using the vim editor on a Slackware Linux box loaded with GNU tools. The cover “art” and diagrams are produced with Inkscape. The XML is converted into HTML and XSL-FO by custom Python scripts. The XSL-FO output is then munged by Apache FOP to produce PDF documents, using Liberation fonts. The toolchain is composed of 100% Free and Open Source Software. Unless otherwise mutually agreed by the parties in writing, the author offers the work as-is and makes no representations or warranties of any kind concerning the work, express, implied, statutory or otherwise, including, without limitation, warranties of title, merchantibility, fitness for a particular purpose, noninfringement, or the absence of latent or other defects, accuracy, or the presence of absence of errors, whether or not discoverable. Except to the extent required by applicable law, in no event will the author be liable to you on any legal theory for any special, incidental, consequential, punitive or exemplary damages arising out of the use of the work, even if the author has been advised of the possibility of such damages. This document is freely distributable under the terms of the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License. See the Copyright and Distribution section for details. Copyright © 2015 Brian “Beej Jorgensen” Hall Contents 1. Intro................................................................................................................................................................1 1.1. Audience 1 1.2. Platform and Compiler 1 1.3.
    [Show full text]
  • DI PROTECT™ Release Notes 16 December 2019
    Release Notes Version 3.0 DI PROTECT™ Release Notes 16 December 2019 © 2019 COPYRIGHT DIGITAL IMMUNITY www.digitalimmunity.com COPYRIGHTS & TRADEMARKS The contents of this document are the ProPerty of Digital Immunity, Inc and are confidential and coPyrighted. Use of the Digital Immunity materials is governed by the license agreement accomPanying the DI Software. Your right to coPy the Digital Immunity Materials and related documentation is limited by coPyright law. Making coPies, adaptations, or comPilation works (excePt coPies for archival PurPoses or as an essential steP in the utilization of the Program in conjunction with the equiPment) without Prior written authorization from Digital Immunity, Inc is Prohibited by law. No distribution of these materials is allowed unless with the exPlicit written consent of Digital Immunity. U.S. Government Restricted Rights (Applicable to U.S. Users Only) Digital Immunity software and documentation is Provided with RESTRICTED RIGHTS. The use, duPlication, or disclosure by the government is subject to restrictions as set forth in Paragraph (c)(l)(ii) of the Rights in Technical Data ComPuter Software clause at DFARS 252.227-7013. The manufacturer of this Software is Digital Immunity, Inc, 60 Mall Road, Suite 309, Burlington, MA 01803. Protected by multiPle Patents. Other Patents Pending. DIGITAL IMMUNITY™ is a registered trademark Protected by trademark laws under U.S. and international law. All other Intellectual brand and Product names are trademarks or registered trademarks of their resPective owners. Product Release: 3.0 Last UPdated: 16 December 2019 © Copyright 2019 by Digital Immunity, Inc. All Rights Reserved DI PROTECT™ Release Notes v3.0 | © 2019 Digital Immunity 1 TABLE OF CONTENTS 1 Introduction ......................................................................................................................
    [Show full text]
  • POSIX Signals
    CSE 410: Systems Programming POSIX Signals Ethan Blanton Department of Computer Science and Engineering University at Buffalo Introduction Signals Blocking Concurrency Sending Signals Summary References POSIX Signals POSIX signals are another form of interprocess communication. They are also a way to create concurrency in programs. For these two reasons, they are rather complicated and subtle! Signals provide a simple message passing mechanism. © 2018 Ethan Blanton / CSE 410: Systems Programming Introduction Signals Blocking Concurrency Sending Signals Summary References Signals as Messages POSIX signals are asynchronous messages. Asynchronous means that their reception can occur at any time.1 The message is the reception of the signal itself. Each signal has a number, which is a small integer. POSIX signals carry no other data. 1Almost. We’ll see how to control it later. © 2018 Ethan Blanton / CSE 410: Systems Programming Introduction Signals Blocking Concurrency Sending Signals Summary References Signal Types There are two basic types of POSIX signals: Reliable signals Real-time signals Real-time signals are much more complicated. In particular, they can carry data. We will discuss only reliable signals in this lecture. © 2018 Ethan Blanton / CSE 410: Systems Programming Introduction Signals Blocking Concurrency Sending Signals Summary References Asynchronous Reception From the point of view of the application: Signals can be blocked or ignored Enabled signals may be received between any two processor instructions A received signal can run a user-defined function called a signal handler This means that enabled signals and program code must very carefully manipulate shared or global data! © 2018 Ethan Blanton / CSE 410: Systems Programming Introduction Signals Blocking Concurrency Sending Signals Summary References Signals POSIX defines a number of signals by name and number.
    [Show full text]
  • Program Details
    Home Program Hotel Be an Exhibitor Be a Sponsor Review Committee Press Room Past Events Contact Us Program Details Monday, November 3, 2014 08:30-10:00 MORNING TUTORIALS Track 1: An Introduction to Writing Systems & Unicode Presenter: This tutorial will provide you with a good understanding of the many unique characteristics of non-Latin Richard Ishida writing systems, and illustrate the problems involved in implementing such scripts in products. It does not Internationalization provide detailed coding advice, but does provide the essential background information you need to Activity Lead, W3C understand the fundamental issues related to Unicode deployment, across a wide range of scripts. It has proved to be an excellent orientation for newcomers to the conference, providing the background needed to assist understanding of the other talks! The tutorial goes beyond encoding issues to discuss characteristics related to input of ideographs, combining characters, context-dependent shape variation, text direction, vowel signs, ligatures, punctuation, wrapping and editing, font issues, sorting and indexing, keyboards, and more. The concepts are introduced through the use of examples from Chinese, Japanese, Korean, Arabic, Hebrew, Thai, Hindi/Tamil, Russian and Greek. While the tutorial is perfectly accessible to beginners, it has also attracted very good reviews from people at an intermediate and advanced level, due to the breadth of scripts discussed. No prior knowledge is needed. Presenters: Track 2: Localization Workshop Daniel Goldschmidt Two highly experienced industry experts will illuminate the basics of localization for session participants Sr. International over the course of three one-hour blocks. This instruction is particularly oriented to participants who are Program Manager, new to localization.
    [Show full text]
  • Programming with POSIX Threads II
    Programming with POSIX Threads II CS 167 IV–1 Copyright © 2008 Thomas W. Doeppner. All rights reserved. Global Variables int IOfunc( ) { extern int errno; ... if (write(fd, buffer, size) == –1) { if (errno == EIO) fprintf(stderr, "IO problems ...\n"); ... return(0); } ... } CS 167 IV–2 Copyright © 2008 Thomas W. Doeppner. All rights reserved. Unix was not designed with multithreaded programming in mind. A good example of the implications of this is the manner in which error codes for failed system calls are made available to a program: if a system call fails, it returns –1 and the error code is stored in the global variable errno. Though this is not all that bad for single-threaded programs, it is plain wrong for multithreaded programs. Coping • Fix Unix’s C/system-call interface • Make errno refer to a different location in each thread – e.g. #define errno __errno(thread_ID) CS 167 IV–3 Copyright © 2008 Thomas W. Doeppner. All rights reserved. The ideal way to solve the “errno problem” would be to redesign the C/system-call interface: system calls should return only an error code. Anything else to be returned should be returned via result parameters. (This is how things are done in Windows NT.) Unfortunately, this is not possible (it would break pretty much every Unix program in existence). So we are stuck with errno. What can we do to make errno coexist with multithreaded programming? What would help would be to arrange, somehow, that each thread has its own private copy of errno. I.e., whenever a thread refers to errno, it refers to a different location from any other thread when it refers to errno.
    [Show full text]
  • UNIT: 4 DISTRIBUTED COMPUTING Introduction to Distributed Programming
    UNIT: 4 DISTRIBUTED COMPUTING Introduction To Distributed Programming: • Distributed computing is a model in which components of a software system are shared among multiple computers. Even though the components are spread out across multiple computers, they are run as one system. This is done in order to improve efficiency and performance. • Distributed computing allows different users or computers to share information. Distributed computing can allow an application on one machine to leverage processing power, memory, or storage on another machine. Some applications, such as word processing, might not benefit from distribution at all. • In parallel computing, all processors may have access to a shared memory to exchange information between processors. In distributed computing, each processor has its own private memory (distributed memory). Information is exchanged by passing messages between the processors. • Distributed computing systems are omnipresent in today’s world. The rapid progress in the semiconductor and networking infrastructures have blurred the differentiation between parallel and distributed computing systems and made distributed computing a workable alternative to high- performance parallel architectures. • However attractive distributed computing may be, developing software for such systems is hardly a trivial task. Many different models and technologies have been proposed by academia and industry for developing robust distributed software systems. • Despite a large number of such systems, one fact is clear that the software
    [Show full text]
  • Introduction to POSIX Signals
    Introduction to POSIX Signals Michael Jantz Prasad Kulkarni Douglas Niehaus Introduction ● This lab is an introduction to signals in Unix systems. – In it, you will learn about some common uses for signals. – You will also construct a small program that uses signals. ● Unpack the starter code, then make and tag it: – bash> tar zxvf eecs678-signals-lab.tar.gz – cd signals/; make; ctags -R EECS 678 Signals Lab 2 Signals ● A signal is a short message that may be sent to a process or a group of processes. ● The only information given to a process is usually the number identifying the signal; there is no room in standard signals for arguments, a message or other accompanying information. ● Signals serve two main purposes: – To make a process aware that a specific event has occurred. – To cause a process to execute a signal handler function included in its code. EECS 678 Signals Lab 3 Interrupts vs. Signals ● Signals and interrupts are very similar in their behavior ● Important difference: interrupts are sent to the operating system by the hardware, signals are sent to the process by the operating system, or other processes through the OS ● Important similarity: both signals and interrupts associate handlers with asynchronous events which interrupt current processing, thus inserting the handler into current code path ● Signals can thus be thought of as an interrupt in software: – However, note that signals have nothing to do with Soft-IRQs. The name seems related, but these are a method for deferring much of the processing associated with a hardware-interrupt into a less restrictive execution context inside the OS.
    [Show full text]
  • POSIX Signal Handling in Java
    Technical Document Series POSIX Signal Handling in Java POSIX Signal Handling In Java Introduction POSIX signals inform a running process of external events, such as the user wishing to kill the process, or the operating system signaling an impending shutdown, or the process being suspended or reinstated; or the process may have violated a resource constraint, such as excessive CPU usage or attempts to access areas outside its permitted memory space, and is asked to shutdown. In short, POSIX signals serve many different purposes. Some are even up to interpretation, such as the HUP (HangUP) signal, which is commonly used to inform a process that something about its environment has changed and the process should adjust accordingly. Some programs may interpret this to mean that the configuration has changed and needs to be reloaded; or the log file has been moved for archiving purposes and a new one should be started. The use of signals is widespread, especially on Unix-based operating systems, but Java provides no standard interface for a Java application to hear and react to them. This document shows you how to get around this limitation. The Good, the Bad, and the Ugly The good news is that there is a way to intercept POSIX signals and react to them in Java. This would allow your Java program to avoid being killable with ^C (SIGINT), for example, even ignore termination requests from the operating system (SIGTERM). Neither of these is necessarily a good idea, of course, unless you know exactly why you would want to catch these signals and either handle them yourself or ignore them altogether.
    [Show full text]
  • Lecture 14: Paging
    Lecture 14: Paging Fall 2018 Jason Tang Slides based upon Operating System Concept slides, http://codex.cs.yale.edu/avi/os-book/OS9/slide-dir/index.html Copyright Silberschatz, Galvin, and Gagne, 2013 "1 Topics • Memory Mappings! • Page Table! • Translation Lookaside Bu$ers! • Page Protection "2 Memory Mapped • Logical address translated not to memory but some other location! • Memory-mapped I/O (MMIO): hardware redirects read/write of certain addresses to physical device! • For example, on x86, address 0x3F8 usually mapped to first serial port! • Memory-mapped file (mmap): OS redirects read/write of mapped memory region to file on disk! • Every call to read() / write() involves a system call! • Writing to a pointer faster, and OS can translate in the background (also see upcoming lecture) "3 Memory-Mapped File • In Linux, typical pattern is to:! • Open file, using open() function! • Optional: preallocate file size, using ftruncate()! • Create memory mapping, using mmap() function! • Do work, and then release mapping using munmap() function! • Kernel might not write data to disk until munmap() "4 mmap() function void *mmap(void *addr, size_t length, int prot, int flags, int fd, off_t offset) • addr is target address of mapping, or NULL to let kernel decide! • length is number of bytes to map! • prot defines what mapping protection (read-only or read/write)! • flags sets other options! • fd is file descriptor that was returned by open()! • offset is o$set into file specified by fd "5 mmap() example part 1 • See man page for each of these functions
    [Show full text]
  • Interprocess Communication 1 Processes • Basic Concept to Build
    Interprocess Communication 1 Processes • Basic concept to build the OS, from old IBM mainframe OS to the most modern Windows • Used to express the requirements to be met by an OS – Interleave the execution of multiple processes, to maximize CPU utilization while providing good response time – Allocate resources to processes using a policy while avoiding deadlocks – Support interprocess communications and user creation of processes to help structuring applications • Background – Computer platform * Collection of hardware resources – CPU, memory, I/O modules, timers, storage devices – Computer applications * Developed to perform some task * Input, processing, output – Efficient to write applications for a given CPU * Common routines to access computer resources across platforms * CPU provides only limited support for multiprogramming; software manages sharing of CPU and other re- sources by multiple applications concurrently * Data and resources for multiple concurrent applications must be protected from other applications • Process – Abstraction of a running program – Unit of work in the system – Split into two abstractions in modern OS * Resource ownership (traditional process view) * Stream of instruction execution (thread) – Pseudoparallelism, or interleaved instructions – A process is traced by listing the sequence of instructions that execute for that process • Modeling sequential process/task – Program during execution – Program code – Current activity – Process stack * Function parameters * Return addresses * Temporary variables –
    [Show full text]
  • To: Anthonys Darrylr Cc: Cameronm Tonyw Subject: Re: OLE Date: Wed Apt 29 16:48:08 PDT 1992
    2. Maples is really interested in having the Mac presented in a positive light at the conference ( as are we all I think). Can we see a copy of the agenda. I don’t think this warrants specific Mac sessions or anything as detailed as that, just some extension of what we discussed today regarding as proposed time frame foF implementation. Maples was interested in distributing 9ome sort of document that would "commit" us to doing this on the Mac. Do either of you have an opinion on that? If we can’t produce something that is solid in this short ti~e frame, I am in favor of not distributing anything. Random info is clearly not what we need floating around at this point. Please advise on this issue. Thanks, Lisa From greqw Fri Nov 30 10:59:44 1990 To: anthonys darrylr Cc: cameronm tonyw Subject: Re: OLE Date: Wed Apt 29 16:48:08 PDT 1992 Date: Fri Nov 30 11:42:20 1990 I will talk with Tony again. The bottomline was that we were not completely convinced that the API changes would he sufficient and would not require changes later after the initial release of the libraries. Therefore, we did not change the existing APIS. If TonyW did not let PhilipL k~1ow when we made the decision to stay with the existing APIs’, then we screwed up. I am willing to jerk the ISVs around if we can convince ourselves that the link management design will be effective. We do not have much time.
    [Show full text]