Open Source Python Building Automation Software for Mac

Wire Factory Simulator (WFS) is a free software to simulate the control of a factory, mainly controlled by IEC 61499 applications. You can build your own factory and controller. The controller can be implemented on any programming language. WFS was originally built to simulate the action of an IEC 614999 application. So, the devices in the factory are easily connected to IEC 61499 applications. The WFS were mainly tested with FBDK (http://www.holobloc.com/). Wire Factory has been implemented to help to test more complex automation systems during a doctorate course under guidance of: Supervisor: Prof. Dr. Roberto Silvio Ubertino Rosso Jr. Co-Supervisor: Prof. Dr. André Bittencourt Leal at Santa Catarina University State (UDESC) located in Joinville/Brazil. CONTACT INFO ------------ Leandro Israel Pinto leandroip.com leandro.israel.p@gmail.com

remove the temporary files using Temp manager, and automate the operation (remove the files every 5 seconds). Built with python. Interface : Tkinter.

Under the hood, Helium forwards each call to Selenium. The difference is that Helium's API is much more high-level. In Selenium, you need to use HTML IDs, XPaths and CSS selectors to identify web page elements. Helium on the other hand lets you refer to elements by user-visible labels. As a result, Helium scripts are typically 30-50% shorter than similar Selenium scripts. What's more, they are easier to read and more stable with respect to changes in the underlying web page. Selenium-python is great for web automation. Helium makes it easier to use. Helium ships with its own copies of ChromeDriver and geckodriver so you don't need to download and put them on your PATH. Unlike Selenium, Helium lets you interact with elements inside nested iFrames, without having to first "switch to" the iFrame. Helium notices when popups open or close and focuses / defocuses them like a user would. You can also easily switch to a window by (parts of) its title.

Implements a stepped state machine, i.e. a state machine which executes a single state transition at a time. Because of this, no data, e.g. state data, can be stored between executions. Instead, any such data must be stored in persistent storage between executions. This permits operation of the state machine as a CGI program in a web server. A WSGI or fastCGI or other such web server is not required. Received symbols may be received from sources outside the state machine, or may be generated internally by the state functions.