Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Improved G110/G120 Tracing script

Created by: Graeme at: 5/14/2012 12:03 AM (7 Replies)

Rating (11)

Thanks 12

8 Entries

5/14/2012 12:03 AM	Rate (8)
Graeme Platinum Member Joined: 6/4/2008 Last visit: 9/30/2024 Posts: 1497 Rating: (324)	Hi All, In the attachment, I have modified the original trace script file which is still downloaded from here: http://support.automation.siemens.com/WW/view/en/55652880 I have added a few little extras, the most significant being a rudimentary trigger. The script monitors r947 for a state change (i.e. anything other than 0) Limitations are of course that the text file will keep growing until either the "Cancel" button is pushed OR a fault is encountered. Also, I struggled to try and make the trigger BIT operated (i.e. r968.3) which meant that any variable/binnector could be used as a trigger, but I failed If anyone out there knows of a way, please post and we can develop the script further. There is also a Trigger Low and Trigger High, and this ONLY relates to the GRAPH, basically, to try and mimic Drivemonitors vertical trigger line, the value of the trigger channel is 0 until the trigger even after which the value changes to 100 (so basically, you see a line where the trigger happened) As a hint, if you are monitoring currents and torque values around 20 & 30, then it makes sense to make the Trigger Low = 20, and the Trigger High = 30, then you can see all the detail of the currents and torques. I guess you need to play with it to see what I mean. I have attached a graph of my drive accelerating and then decelerating after which I then triggered an EXTERNAL fault. Note the current (Yellow, you can hardly see it, as I was tracing DC Link voltage which is up at around 350V) So it would make sense to leave out the DC link volts if I wanted to closely monitor current for example. The script now has 4 parameters which can be traced, so be sensible with the connection speed, at 9600 baud, you will see NOTHING valuable. Set the interface as FAST AS POSSIBLE. If you don't want to monitor 4 parameters, you have a choice, you can either remove the parameters you don't want from the script file, or just monitor 1 parameter twice. The script also writes the headings for the graph which makes it a little more readable. The simple exchange of the Timestamp from the right hand side to the left hand side of the data series means one less step when importing into Excels Graph function. Please be aware, that the original limitations ofthe script are still in force (i.e. "This FAQ only applies to SINAMICS G110, SIMATIC ET200S FC and, due to differences in the parameter structure, MICROMASTER 4 and SINAMICS CU240x with Firmware < V4.0") As always, you take full resposibility for using this trace function - I have tested this on MM4 series and G120 (CU240s) - I have not tested this on G110, so please let me know if it works ok. And finally, ALL credit is really for the original author of the script file - I just modified their good work. Regards, Graeme Attachment Trace.zip (467 Downloads)

Suggestion To thank Quote Answer
This contribution was helpful to 6 thankful Users UMENCHO Gary.Hare Vithani 0_Einstein RobboC a_diaz123

5/14/2012 4:21 AM	Rate (0)
Vithani Platinum Member Joined: 7/8/2009 Last visit: 8/5/2024 Posts: 1976 Rating: (477)	Good Work Graeme Cant give you stars because I am out of dailyLimit But Thanks for sharing. Keep posting such good posts Regards Devesh Vithani
	Last edited by: Vithani at: 5/14/2012 4:21 AM I dont Like people driving Fast, thats the reason I overtake them ;)
Suggestion To thank Quote Answer

5/14/2012 1:23 PM	Rate (0)
RobboC Posts: 15 Rating: (2)	Nice, I hope this works, I am sick of standing around resetting/waiting for the original script to capture a fault. I will try it out and let you know if G110 works Thanks, C
RobboC Posts: 15 Rating: (2)
Suggestion To thank Quote Answer

5/14/2012 9:42 PM	Rate (1)
0_Einstein Diamond Member Joined: 7/7/2010 Last visit: 10/3/2024 Posts: 15261 Rating: (2421)	Right in the middle of a couple of loops, I see "Script.Exit" Is that debug code left in the script or does it serve a special purpose? I know nothing about starter scripting but have many years of working with vbscripts.
	science guy
Suggestion To thank Quote Answer

5/14/2012 9:52 PM	Rate (0)
Graeme Platinum Member Joined: 6/4/2008 Last visit: 9/30/2024 Posts: 1497 Rating: (324)	Ha ha, nicely spotted, I found if that is missing, the script just reports endless errors, due to a "non recognised state" i.e. Fault even though I had a "resume on error". If you have any suggestions for making the trigger Bit based, I would be glad to hear/see them. The form of the Parameter call seems to be (Parameter.Index) but I would like to make the fault/or anything of interest trigger on a bit for example r968.3 for a Micromaster, or r2139.3 on the Sinamics G120. Regards, Graeme
	Last edited by: Graeme at: 5/14/2012 10:18 PM Resume on Error, not exit
Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users UMENCHO Vithani king_1985

5/14/2012 11:54 PM	Rate (2)
0_Einstein Diamond Member Joined: 7/7/2010 Last visit: 10/3/2024 Posts: 15261 Rating: (2421)	Graeme Ha ha, nicely spotted, I found if that is missing, the script just reports endless errors, due to a "non recognised state" i.e. Fault even though I had a "resume on error". If you have any suggestions for making the trigger Bit based, I would be glad to hear/see them. The form of the Parameter call seems to be (Parameter.Index) but I would like to make the fault/or anything of interest trigger on a bit for example r968.3 for a Micromaster, or r2139.3 on the Sinamics G120. How about making trigger a float/real? 947.3 is 947 +3rd binary digitright? 947.3 means-> ( (Parameters( 947, 0)&& 4) == 0 ) The bit comes from taking the MOD 10 of the trigger: triggerbit = triggerMOD 10 ' but this might get round-off errors Instead, convert to string, then take right most digit (and verify it is a number) strTrigger = CStr(trigger) str_n = right(strTrigger,1) if isNumber( str_n ) then index = 2^(INT( str_n ) - 1) else index = 255 end if --- I have not tested this, but it should give a possible idea --- So maybe it is : While (Parameters(trigger, 0)&& 2^^(index-1))== 0) ... Wend ---- Ok, maybe that's a little too round-about way to grab the bit from the right index = ROUND( trigger MOD 10 ) if (index < 0) \|\| (index > 7) then index = 255 else index = 2^(index - 1) end if
	Last edited by: huggy_d1 at: 5/15/2012 12:00 AM science guy
Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users UMENCHO Graeme Vithani

5/15/2012 9:26 PM	Rate (0)
Graeme Platinum Member Joined: 6/4/2008 Last visit: 9/30/2024 Posts: 1497 Rating: (324)	Nice one, I will try some of these next time I can connect to a MM4 or G120 Regards, Graeme

Suggestion To thank Quote Answer

4/16/2020 11:11 PM	Rate (0)
a_diaz123 Posts: 36 Rating: (3)	Hello everyone, I've been successfully using the script Graeme made for us, even modified it to create a version with eight parameters for some specific uses. Now I would like to take a trace of two units (two G120 with a CU250S-2 each) at the same time but this seems to be impossible. The script has to be embedded on the unit we want to take the trace, otherwise it won't work (i.e. if you place it on the default Scripts folder that Starter provides). My idea was to insert the script on the Project folder and run it so it could capture both motors but it does not record any data. I know a trace of two motors is possible in S120 with the two power units under the same CU... Any ideas? Thanks in advance. Regards,
a_diaz123 Posts: 36 Rating: (3)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

Follow us on