Linear_Guy

I've been tasked with developing teach pendant screens/functionality on a GT14 "Handy GOT".  What I'm attempting to do is alter the object's appearance based on selecting it via script.  There are several "drawing" based commands available when using the script editing window, but I'm struggling with getting my object to resize. Here's something I've tried: if ([b:X0A2] ==ON) {clear_object(); [w:GD200] = my.width; [w:GD200] = my.height; redraw_object();} I have attempted to write a value of '100' into GD200 in both the object script window, and within the Project Script window.  My thought was the GD200 device was empty so the script wasn't functioning. I've tried many variations of the above and wish I could write hard values into 'my.width' etc, so I know for a fact the new values are present for the script to resize the object. Any help would be appreciated, as I've spent waaay to much time on this already...lol.  ...and if there's a manual resource that explains specifically how these my.width/my.height commands are meant to be used, I can find it. Thanks in advance

 

Speaking as an electrician that spent the vast majority of his career troubleshooting with simple ladder on multiple platforms, I can say that structured programming is simply the write way to develop code, IMHO. I made a career move a couple of years ago and shifted into the world of controls.  The dept. I'm now in develops our projects in roughly 90% structured text with the remainder in ladder.  The small portion of ladder that is produced, is what we deem to be client level troubleshooting code, so it's done in a format that's more comfortable for them. It took me a short while to grow accustomed to the structured method, but it is far superior.  Pages of ladder can be condensed into a few paragraphs if done efficiently. Give it some time.  You'll grow to love it.  I don't think I'd ever go back to simple ladder again.  Unless of course a client demanded it. As far as the benefits are concerned: -cross platform usage: Other than altering syntax. a cut/paste of code across unrelated platforms is an massive perk. -The 'FOR' loop:  Read up on it.  Massive time saver there.  By simply increasing the loop count you can perform what would be countless similar tasks. -CASE sequences: Although completely doable in ladder.  CASE sequences in structured text are far easier to develop, augment, and troubleshoot. that's just to list a few

Just a follow up to my previous follow up.... Apparently the version 1.105 of MT Developer2 software does support the functionality that Gambit posted.  However it's only available through the advanced synchronous control methodology, and not in virtual switching.  I find it odd that you only have access to an auxiliary clutch in ASC, but it is what it is.  For anyone else who may be new to the editor and spinning their wheels, here's the process to follow. -set up your project in "Advanced Synchronous Control".  Expand the 'Synchronous Control Parameter' tree on the right hand side.  From that expand 'Axis 1 to Axis 8 Synchronous Parameter' tree.  Then double click on 'axis 1'. Enjoy

Just as a follow up.... Looks like the Q172DSCPU is the motion controller spec'd for this project, so I'm stuck without the auxiliary clutch functionality. Thank you for the help Gambit.

Aha.... The project is being developed with a "Q172DSCPU" using an older version of Developer2 (ver1.105) When I start the project I have the option of using one of two operational methods, either "Virtual Mode Switching" or "Advanced Synchronous Control".  "Virtual mode" allows access to mechanical system functionality but apparently no option of an auxiliary clutch.  The Advanced Sync option doesn't have mechanical system functionality at all.  ...Or at least no regular method of opening it. I'll have to dig into the CPU options available for the project and update our Developer version.

Thank you for the reply Gambit... The mechanical layout you posted is a dead ringer for the example used in the revised manual dated December 2015.  Since my first post I found that revised manual.  It still doesn't provide details on how to generate the auxiliary devices though.  I'm beginning to believe my version of the software doesn't support the feature set.   In fact I can't reproduce the screen shot you added above.  At best I can assemble everything other than the auxiliary devices (horizontal clutch and speed change gear).  However, the "Synchronous control Image" window on the right hand side of your post doesn't exist.  Is that a result of a complied (checked) mechanical layout...?  I cannot reproduce a window that allows access to all the individual device settings at once.  I can only highlight one at a time, and when doing so with a clutch device there is no option to toggle it to a "auxiliary" function. 56e80ec0a4599_screenshot.bmp May I ask what version of MT Developer2 you are using...?   screen shot.bmp

Hello All... First let me say that I can't express how thankful I am that I found this forum.  I've been beating my head against a brick wall for a couple of days, and hopefully the membership here can save me a few dollars on pain killers. My issue, as the title says, is with the Mechanical System layout found in MT Developer2, (ver: 1.105).  Hopefully I can describe what I'm hoping to accomplish clearly enough. I've been tasked with attempting to create a system that is switchable between a virtual reference and a real one.  I quickly found an example layout within the "SV22 advanced synchronous control" manual (pg23, section 1.2) that illustrates the use of multiple inputs that switch in and out of the system with clutches.  My difficulty is reproducing the horizontal devices ("auxiliary shaft clutch", "speed change gear").  Section 3 breaks down the example and even provides details on the horizontal (auxiliary) devices but still does not shed any light on how to create them to begin with. I've ran through the help files, google searches, and obviously the programming manuals but have yet to find the method used for creating these devices. I have no doubt that this is simply an oversight on my part, but none the less I'm struggling at this point.  Any help anyone could provide would be greatly appreciated. Thank you in advance. L_G