Download
1 / 11
110 likes | 206 Vues
Explore the advanced capability of capturing debug data for detailed analysis between PLC and Matroller, using Winsock connection tools. Enables users to view commands, history data, and troubleshoot overlap feeds. Detailed steps for enabling and capturing data provided. Includes exercises and key insights into material feed analysis.
E N D
MUST HAVE SHOULD HAVE COULD HAVE Module # 160
Advanced Bonus Topics Debug Data Capturing Feed History data Overlapping Feed Exercise
Debug Data • Commands that Qi receives can be monitored externally • This data gives us more information on what is happening between the PLC and the Matroller. • Every Command that the Qi receives will be re-broadcast out the Ethernet port (1749) • Trace Debug O/P must be enabled in the Qi ! • Enabling “Trace Debug” • Via Web Pages goto >> Communications > Network > Ethernet • Check “Enable Trace Data” • Any S/W that supports a Winsock connection can be used to capture the data such as Hyper Terminal • (hyperterminal is supplied with Windows) • During commissioning this is an important tool that allows us to view what commands the PLC is sending. • Note: Once you are finished using this feature be sure to disable it. This feature adds an extra load on the CPU
Capturing this Data • Run “HyperTerminal” • Select using: TCP/IP • Host Address: Your QiMPACT’s IP address • Port number: 1749 • Make sure that Connected is displayed on lower left • Test connection by viewing PAC Cross Reference Table • Data should appear on the HyperTerminal screen • Run a few more feeds • What do you see on your HyperTerminal screen? • Tip: Text should appear on your screen
Analysis of the data • The Trace Debug O/P must be enabled in the Qi. • Typical Start Feed Command: • 4199114mp=13,ch=3,cm=1,sq=45,tg=1024.00,gp=0,ng=0,st=0 Qi0.3.1_0616 Clock in ¼ second intervals Channel Material Path Command number Target Qi firmware version # Ovlp feeds Sequence number Ovlp Grp number Command Status ARN06
Data Capture – Feed History • Feed History data is also sent out of the Ethernet Port • This data is always transmitted • History data is always available, and is a string of text as follows: • (*hst* …”DATA IN HERE”….. *hst*) • This data is transmitted out of the Ethernet port and is available to any application to use • Qi365 has been designed to capture and present this data in a user friendly manner • The structure is described in two documents: • HistoryRecords.doc and TestDataHeadings.xls • The String can be copied and then pasted into the supplied spreadsheet and then parsed into the columns
Overlapping Feed Exercise • These are our Material and their Parameters: • Primary Material MP1: • FlowAve: 50 g/s DrainTime: 5 s Feed Alone Time: 8 s • Feed Alone Tolerance: 6 s Target 1000 grams • Secondary Material MP2: • FlowAve: 25 g/s DrainTime: 3 s Target 300 grams • Exercise A • Draw a graph showing the feed time and starting points of these two materials
Your calculations here – answer on next slide – no peeking !
Exercise A Answer • MP1 feed time is 1000 ÷ 50 = 20 seconds • MP1 desired Feed Alone time is: 8 + 6 = 14 s • MP2 feed time is 300 ÷ 25 + DrainTime = 12 + 3 = 15 s • The overlap time is: 20s – 14s = 6s • The Primary will therefore be delayed by 15s – 6s = 9 seconds
Graphical view Feed Time of 12 sec Drain Time of 3 sec Feed Alone Time of 14 sec MP2 - Sec MP1 - Prim Primary delayed by 9 sec Overlap of 6 sec 9s 12s 15s 29s
Review Questions • Is there Debug data always transmitted out of the Ethernet port ? • What is the Port number for this data ?
