Scribd
Upload
3 views1 page

ModbusGUIPython_1

The document discusses the implementation of a WINSTAR SLAVE display using MODBUS for construction speed, detailing the communication between a display (slave 1) and an inverter motor (slave 2). It raises questions about the logic for reading and writing MODBUS registers, suggesting the use of a minimalmodbus Python script for real-time GUI control. Additionally, it inquires about the necessity of continuous polling for both slaves and references examples of writing values to MODBUS registers.

Uploaded by

torikulislamnishad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views1 page

ModbusGUIPython_1

The document discusses the implementation of a WINSTAR SLAVE display using MODBUS for construction speed, detailing the communication between a display (slave 1) and an inverter motor (slave 2). It raises questions about the logic for reading and writing MODBUS registers, suggesting the use of a minimalmodbus Python script for real-time GUI control. Additionally, it inquires about the necessity of continuous polling for both slaves and references examples of writing values to MODBUS registers.

Uploaded by

torikulislamnishad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

In the end for speed of construction I chose the new WINSTAR SLAVE display, it is a powerful

slave that communicates in MODBUS, any graphic widget (it is simply imported with drag and
drop) is associated with a 16-bit modbus register ID, when the gauge cursor the GUI BUILDER
tells you ID, value, MODBUS data frame
https://first-components.com/en/smartdisplay-rs485-introduction-control-methods-for-cross-platfo
rm-concept

so the simple logic now is to read the dynamic value of the MODBUS register on Slave 1
(WINSTAR DISPLAY) and apply the writing call to the dynamic registers of slave 2 (INVERTER
BLDC MOTOR).
The logic is not clear to me, however, create many IF, ELIF, create a single python program,
create 2 separate python programs, one that reads slave1 (display), another that writes to slave2
(INVERTER), continuous polling?

We can use this MODBUS BLDC driver to create the minimalmodbus communication script
between the 2 slaves, on page 9 you can find the mapping MODBUS register Driver . I can
anticipate the cost of the driver. The display (slave1) you can simulate the reading calls with your
slave:
https://www.omc-stepperonline.com/it/driver-motore-cc-digitale-senza-spazzole-110-220v-ca-max
-7-0a-750w-bld-ac750s

Let me know if you can quickly create the minimalmodbus python script for GUI control multi
slave real time READ / WRITE (slave1=DISPLAY, slave2=DRIVER INVERTER MOTOR BLDC)
ID LOGGING REGISTER in real time (widget element) - GUI BUILDER Winstar Display
https://www.winstar.com.tw/video/play/100.html

Is continuous polling necessary on slave1 and 2? here is a very powerful example of sending
writing values ​to modbus registers to PLC servo drive, but only terminal WITHOUT GUI.

Very powerful, each write command register calls its function, If possible use this structure write
multi function: https://qiita.com/kotai2003/items/400e7c34d50928395e28

You might also like