|
| 1 | += Fatek / Facom |
| 2 | + |
| 3 | +This binding integrates Taiwanese brand of PLC called Fatek. |
| 4 | +Fatek is recognized and known worldwide. |
| 5 | +One of this brand uniqueness comes from its own engineering software and programming in leather. |
| 6 | + |
| 7 | +Fatek has its own protocol which description is published. |
| 8 | +This protocol is sometimes (quite rarely) named Facom. |
| 9 | +Since it is used only by this brand it remains proprietary to this firm. |
| 10 | +It is possible to interface Fatek with other systems through Modbus (supported by PLCs at no cost). |
| 11 | +There are several BUS couplers which allow to pair it with other equipment or even modems. |
| 12 | + |
| 13 | +Facom can utilize several transports - most common ones are TCP and serial. |
| 14 | +Protocol payload remains the same. |
| 15 | + |
| 16 | +.Fatek binding capability table |
| 17 | +|=== |
| 18 | +|Device discovery| Channel discovery |Read | Write | Subscribe |
| 19 | + |
| 20 | +|Yes |
| 21 | +|No |
| 22 | +|Yes |
| 23 | +|Yes |
| 24 | +|No |
| 25 | +|=== |
| 26 | + |
| 27 | +The Facom protocol does not provide a subscription operation. |
| 28 | +All states have to be polled in cyclic manner. |
| 29 | + |
| 30 | +== Device discovery |
| 31 | +Binding supports an undocumented discovery feature of the protocol. |
| 32 | +It is able to detect all compatible devices within IP network through broadcasts. |
| 33 | +Once devices are found binding attempts to scan available station ids to identify reachable endpoints. |
| 34 | + |
| 35 | +== Thing and Channel discovery |
| 36 | +Binding is able to discover _Thing_, with all necessary connection parameters, but it can not discover channels. |
| 37 | + |
| 38 | +== Supported hardware |
| 39 | +While Facom seem to be a common protocol used across different product lines this binding is confirmed to work with Fatek FBs series. |
| 40 | +Other product groups have not been tested. |
| 41 | +Most of Fatek PLCs include serial port which can be used for programming. |
| 42 | +This port can be also used for serial communication and integration with binding. |
| 43 | + |
| 44 | +In order to start reading data you need to create at least one `tcp` or `serial` connection (_Bridge_). |
| 45 | +The `tcp` connection usually rely on port 500, however it can be amended in PLC configuration. |
| 46 | + |
| 47 | +Because of protocol limitations configuration needs to be prepared manually based on known register addresses. |
| 48 | +There are several kinds of addresses defined by protocol. |
| 49 | + |
| 50 | +.Register kinds supported by Fatek binding: |
| 51 | +|=== |
| 52 | +|Register |Description |Command/State type |
| 53 | + |
| 54 | +| `X` | (DI) Digital input | `ON` and `OFF` (`OnOffType`) |
| 55 | +| `Y` | (DO) Digital output | `ON` and `OFF` (`OnOffType`) |
| 56 | +| `M` | Internal relay | `ON` and `OFF` (`OnOffType`) |
| 57 | +| `S` | Step relay | `ON` and `OFF` (`OnOffType`) |
| 58 | +| `T` | Timer contact | `ON` and `OFF` (`OnOffType`) |
| 59 | +| `C` | Counter contact | `ON` and `OFF` (`OnOffType`) |
| 60 | +|=== |
| 61 | + |
| 62 | +== Textual configuration |
| 63 | + |
| 64 | +Below is example of a text configuration which you can use as a started. |
| 65 | +Keeping configuration in a file allows to use a regular version control system to track changes over time. |
| 66 | +The same can be done via user interface. |
| 67 | + |
| 68 | +[source,indent=0,subs="verbatim,attributes",role="primary"] |
| 69 | +.dsl |
| 70 | +---- |
| 71 | +include::{examplesdir}/fatek/fatek.things[] |
| 72 | +---- |
| 73 | + |
| 74 | +[source,yaml,indent=0,subs="verbatim,attributes",role="secondary"] |
| 75 | +.yaml |
| 76 | +---- |
| 77 | +include::{examplesdir}/fatek/fatek.yaml[] |
| 78 | +---- |
0 commit comments