Colin Carpenter

MrPLC Member
  • Content count

    449
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Colin Carpenter

  • Rank
    Sparky

Contact Methods

  • Website URL http://www.dairystandardising.co.uk
  • ICQ 0

Profile Information

  • Gender Male
  • Location Trowbridge, England
  • Country England

Recent Profile Visitors

3034 profile views
  1. IEC Developer Online Change rules

    Thanks .... we are using GX Works 2 so will have a detailed look. Still puzzled by the Q02 and IEC Developer though ......
  2. IEC Developer Online Change rules

    Thanks, When you say MBOC, is that an checkbox option when you format the CPU memory to completely erase everything and re-format? Have never fully understood the benefits or usage of a memory card in the PLC and have always just relied on the battery backed memory options until now. Would you say that the benefits of a memory card are worth having as we are just installing a Q04 CPU and now would be a good time to add one if there are real benefits for future online changes etc.  
  3. IEC Developer Online Change rules

    Came across an issue yesterday that made me (once again) realise that I have no real idea about the rules regarding online changes when using IEC Developer 7.04. We had to modify some code on a Q02 CPU that could not be stopped without a lot of grief, and it seemed simple enough, but proved a head scratcher. Essentially we had one POU that contained numerous lines that allowed an operator to press an HMI GO button and, whatever he had selected from a drop down menu would set a bit on in the PLC. Essentially, the raw code of that particular "rung" of the POU ended with  LD  " go button"   AND "op1 requested"   PLS  "system bit" and it was quite happy with that. We wanted to use the system bit to SET a bit on, so the online change amounted to installing 2 extra lines, namely: LD "system bit" SET "op1 flag" Strangely, the online change of adding these two lines wasn't allowed as it said that it would need 530 lines to do the change???? I've found in the past that IEC seems to let you do large changes in POUs that are near the bottom of the "compiler table" but can struggle if the POU is high up, which I assume is related to the amount of lines of code beneath the change that have to be shifted down, but this is the first time I've seen such a tiny change cause issues. We have set the "online changes to 2000 lines" in the options and know that his been downloaded in the past to the parameters,  but the CPU still seems to work to a 512 limit? The work around was easy enough to do, but just left me realising that I still have no idea regarding the rules of online changes. Any advice gratefully received ....    
  4. GX Works 2 Global Label Export Detail Setting

    I'm afraid that's a new one on me ..... must admit to never having realised that "structured data types" actually existed.
  5. GX Works 2 Global Variable Update

    Thanks for that, and it is probably the best way to do it, but it does involve a lot of typing or copying and pasting to do fifty or so global variables ....... It's really annoying as GX Works 2 should be an improvement on the "no longer in development" IEC Developer, and it seems obvious that they built in the mechanism to to do it, but a bug seems to stop it happening. The UK distributor says that he has raised it with Mitsubishi and hopefully there might one day be a fix that allows it to work correctly. Cheers
  6. GX Works 2 Global Variable Update

    Got a reply from the UK distributor and it turns out that everybody gets this problem when they try to do this. Short of exporting the variables, changing them in a spreadsheet and re-importing, there doesn't seem to be a work around, though there's a video on Youtube showing that GX Works 3 can do it ....... doh!!!!  
  7. GX Works 2 Global Variable Update

    I've recently started using GX Works 2 ( the latest version V1.580E) having been a long time user of IEC Developer 7.04 and some things I like, and some things I'm not so keen on, but there is one thing that is really puzzling me. In IEC, if I change the name of global variable and click on the "check" button, then all instances of that global variable are updated automatically in the POUs in which that variable is used. Life is sweet. In GX Works 2, if I change the name of a global variable, then I'm told that I have to click on the "Reservation to System Variable" button and then click on the "Reflect to System Variable Database" button to allow all the POU instances of that variable to update, but when I do this, I get the message as shown in the attached png. It's a bit of a pain having to go through and change each instance in the POUs by hand, and am wondering if anyone can tell me what I'm doing wrong? Thanks, Colin
  8. IEC Developer and the AS-i interface

    As an update on this, we found that Mitsubishi seem to have missed a trick by not keeping up to date with the As-i standards. We installed the Mitsubishi As-i master (V2.11) to our Q01 test mule and then connected a V3.0 slave to it. Initially things looked good as we could address the slave and see the the inputs correctly coming back from the slave. So far, so good, but it all fell apart when we tried to actuate the three solenoid valves on the slave, and found that by activating the 4 bits in the 16 combinations possible, we could get solenoids 2 and 3 to go on or off but in a totally random / no sense order and solenoid 1 refused to actuate at all. Further reading reveals that the V3.0 "slave profile" of the slave is important, and this does not tally with any slave profile supported in V2.11, so we got nowhere. Bent Mitsubishi's ear about keeping up to date with things, but was told that as there was little take up on the card, they lost interest in it and stopped any future development. UK distributors have been very good, so now we're just about to try a CC Link card with a Pepperl and Fuchs gateway, which is pretty much guaranteed by the distributors to work, to the extent that they have promised to get Pepperl and Fuchs on site if it doesn't. Time will tell ...... 
  9. IEC Developer and the AS-i interface

    The project has now been approved, we have a Mitsubishi AS-i card to play with and a test bench PLC ready to install it on, and in the next week or so, we should have a couple of  Thinktops complete with As-i interface capability to play with, as well as the power supplies, cable fittings etc. Total count of AS-i valves will be in the order of 72, so we'll be looking at two AS-i cards at least. HMI will be the IX Developer range from Beijers and we've already got a fair bit of experience on those, having converted code from older 1000 series HMIs to run on the newer screens, so comms and set up is not a problem now. I'm pretty clued up now about the buffer memories and how they hold the data "to and from" the AS-i slaves, but would appreciate some pointers in terms of "good practice" and spotting issues / errors on the loops to aid in future maintenance etc. Thanks Colin
  10. IEC Developer and the AS-i interface

    As an update, I now have an AS-i master card and am looking into the programming of it using the manual, which, as usual is a massive amount of information, but little in the way of "good practice" advice. I've given up on the "configurator" package as it seems expensive and totally related to GX Developer and not to IEC Developer, so have had a good, in depth look at the single page of code in the manual that shows how the 16 bit buffer memory words are converted to individual bits and what those bits actually mean, and it's all starting to make sense. I would like to create a page on the HMI and some code in the PLC that shows dignostics for the AS-i loops (what is out there by comparison with what should be out there etc.) and wonder if anyone has been through this learning curve and could offer some advice. This seems to be one of those Mitsubishi cards that is really short on meaningful manuals, but I'm sure that once it's working it will be fine, and I have a few months to figure it all out. Thanks
  11. IEC Developer and the AS-i interface

    Thanks again for the info. The project is looking like it will involve around 100 "stainless steel process valves" as used in the food industry. The valve type varies, some being simple butterfly valves, some "3 port" divert valves and some "4 port" mixproof valves. The valves will almost certainly be fitted with Alfa Laval "Thinktop" heads, each one of which can be fitted with "from 1 to 3" solenoids and each one having two feedback sensors to indicate if the valve shaft has reached the end of it's travel. All are operated by compressed air, with springs to return the valve to the default position. In the past, we've done things the simple way, by having a dedicated PLC output for each solenoid and two dedicated inputs for the "energised" and "de-energised" feedback sensors, with the PLC code flagging up a valve alarm if the the positions of the feedback sensors are wrong for whatever reason. However, to do this job would mean say 120 outputs and say 200 inputs, so the attraction of the As-i interface is much reduced wiring and a much reduced PLC cost, so I can see the benefits. Looking at the manual for the thinktops, AS-I is one of the standard interfaces on those units (Device Net being the other one) and I've heard good things about how well it works and how easy it is to install.  As you rightly say, the AS-i version in the thinktops is V3.0 while the Mitsubishi module still runs at V2.xx, so hopefully this is OK. Reading the manuals of both the AS-i module and the thinktop seems to make perfect sense as all the IO will be binary (on or off) and we're not planning to use it for any analogues (still like the reliability of a 4-20mA signal). I think we'll order up the Mitsubishi AS-i module and have a play on the test rack, but I'm still confused by the constant references to GX Configurator in all the manuals??? Colin 
  12. IEC Developer and the AS-i interface

    Thanks for the replies. At the moment the project is still in the "loose stage" in that the only thing that has been defined is that the PLC will be a Q series and that it will communicate with an older Q2AS by ethernet ( which I got working a while ago). I have downloaded the manual for the AS-i card and it does seem fairly straighforward in the way it uses buffer memories to send outputs and receive inputs, but the frequent mentions of "configurator software" confuses me as well as I've never used anything other than IEC Developer ....... must look into it. What is an AS-i gateway .... is that a standalone box that enable comms to Mitsubishi ethernet? Colin
  13. IEC Developer and the AS-i interface

    Hi, I'm currently looking at a job involving the installation of lots of process valves, and the intelligent actuators on the valves are capable of communicating using the AS-i interface, and as the  Q PLC has an AS-i card available (QJ71AS92), was wondering if anyone has used this card, and if so, can it be installed and run with IEC Developer, our preferred software? All feedback gratefully received, Thanks, Colin 
  14. IEC Developer Ethernet Peer to Peer Comms

    Just as an update, I used the Write_done[0] and Read_done[0] bits to pulse a local variable bit and used the relevant pulsed bit to initiate the read or write instead of the 100ms timer bit and it all works perfectly.  Cheers
  15. IEC Developer Ethernet Peer to Peer Comms

    I'll give it a try next week and see which one of those "done" bits will do the business and report back when I find out which one it is. Thanks for your help, Colin