huangyizhe
/
XinJe_PLC_Skill
1
1
Forka 0
Codice Problemi 0 Pull Requests 0 Rilasci 1 Wiki Attività
信捷PLCSkill
Non puoi selezionare più di 25 argomenti Gli argomenti devono iniziare con una lettera o un numero, possono includere trattini ('-') e possono essere lunghi fino a 35 caratteri.
5 Commit
1 Ramo (Branch)
204 MiB
 
 
 
 
Albero (Tree): 7bb23acbd4
Rami (Branch) Tag
${ item.name }
Crea branch ${ searchTerm }
da '7bb23acbd4'
${ noResults }
XinJe_PLC_Skill/references/touchwin-overview.md

2.0 KiB
Originale Blame Cronologia

TouchWin Overview

This is a v0.1 overview distilled from the TouchWin editing software manual outline. Use it for high-level HMI workflow answers until detailed TouchWin references are added.

Covered Manual Areas

  • TouchWin editing software installation and uninstallation.
  • Simple project creation.
  • Screen editing.
  • Offline simulation.
  • Online simulation.
  • Project download.
  • Project upload.
  • Software structure, project area, menu bar, tools, and views.
  • HMI communication, alarms, recipes, macros, variables, and registers appear in the manual and need detailed extraction in future iterations.

Basic HMI Workflow

  1. Confirm the HMI model and target PLC model.
  2. Create or open the TouchWin project.
  3. Set project communication to match the PLC protocol and connection method.
  4. Create screens by operating purpose: main status, manual operation, parameter setting, alarms, recipe, maintenance/debug.
  5. Bind buttons, lamps, numeric displays, and numeric inputs to PLC soft elements or registers.
  6. Configure alarm objects and reset/acknowledge behavior.
  7. Configure recipe objects if the machine has product parameters or batch settings.
  8. Use offline simulation for screen behavior where possible.
  9. Use online simulation or download for PLC communication testing.
  10. Verify PLC/HMI address consistency against the soft-element table.

Questions To Ask

  • HMI model and screen resolution:
  • PLC model and communication port:
  • Protocol: XNET, Modbus RTU, Modbus TCP, or other:
  • Screen list and operator workflow:
  • Variables/registers needed by each screen:
  • Alarm list and reset rules:
  • Recipe parameters and storage behavior:
  • Whether download/upload is allowed on the current machine:

Output Expectations

For TouchWin answers, produce:

  • Screen structure.
  • HMI variable list.
  • Alarm table.
  • Recipe table if needed.
  • Communication setup assumptions.
  • Test procedure: offline simulation, online simulation, download, communication verification, alarm/reset, recipe read/write.