SEW MOVITRAC modbus control
% start synopsis % start main
This is a simple controller for SEW MOVITRAC motor controllers.
% end synopsis % end main
Instructions
Read section 10 of the controller's documentation (that's the "installation" chapter).
Configure the controller. Minimum initial configuration:
-
P1-10: nominal motor speed in r/min.
-
P1-01: max motor speed
-
P1-02: min motor speed
-
P1-07: motor voltage (V)
-
P1-08: motor current (1/10 A)
-
P1-09: motor AC frequency (50Hz)
-
P4-01: control mode. See the documentation. You probably want 2.
-
P1-12: 7 (Modbus)
-
P1-15: 201 (extended control)
-
P5-03: 0-4 (Baud rate, 9600 … 115200)
-
P5-04: 0-3 (parity: no/no2/odd/even)
-
P5-06: timeout in 1/10 sec, zero to disable (this is NOT recommended!)
-
P5-09: 1 (speed as percentage of max)
Check that the motor can turn freely without injuring somebody or breaking something. Check again.
Now connect the emergency switch. See section 6.3.2 in the documentation. DO NOT proceed if this switch is not installed correctly.
The controller should now auto-tune its motor parameters. This process takes up to two minutes and may engage the motor. You can also trigger this process manually by setting P4-02 to 1.
Write a config file along these lines::
link:
root: !P moat.com.example
dev:
sew:
power: !P moat.sew.power
state: !P moat.sew.state
mqtt:
will:
topic: !P moat.sew.state
message: null
modbus:
port: "/dev/ttyUSB0"
serial:
rate: 19200
parity: N
unit: 1
Run "moat -c CONFIG dev sew run".
You now can operate the motor. Send a percentage to the topic moat.sew.power.
You probably should use QOS=1.
MoaT-Link messages are sent as CBOR-encoded data, under the topic
configured in link.root. If you need them as ASCII or JSON, set up
a MoaT-Link MQTT gateway.
TODO
- Add more control.
Metadata
Release files for moat-dev-sew 0.1.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| moat_dev_sew-0.1.8.tar.gz | 7.5 kB | Without provenance | Details for moat_dev_sew-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| moat_dev_sew-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for moat_dev_sew-0.1.8-py3-none-any.whl |
Total release size: 14.5 kB
Release files / moat_dev_sew-0.1.8.tar.gz
| Download URL | moat_dev_sew-0.1.8.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
23803b992617cdab9d7d0a16719ad1bff49728d712db6b5370d8a3c102b24ecb
|
|
BLAKE2b-256 checksum How to use checksums |
1f17224da5a7c17b694356ab7cff73f73b1e333c4260b827c1b2d91c26fd4133
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / moat_dev_sew-0.1.8-py3-none-any.whl
| Download URL | moat_dev_sew-0.1.8-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
06457874ed39543342002f64a6e32d859e5cce5fd49c501b2a585b0a310ee0ba
|
|
BLAKE2b-256 checksum How to use checksums |
abacec4b0514f903b7fe764cf238de9652bd0ead09b29da473e54428aa5211a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for moat-dev-sew 0.1.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.