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
Print