Nightfly

MrPLC Member
  • Content count

    99
  • Joined

  • Last visited

Posts posted by Nightfly


  1.  

    Think we will need more info. What PLC and what software are you referring to? There is obviously no problem converting Hex to decimal (just google it if you don't know). OxFF02 is 65282 as an unsigned 16bit Integer. I would question that is an address the program is writing to - if anything that could be data.

     Can you post any of the C code here? 

     

     

     

     


  2.  

    Well Gambit's Idea is the best solution. However, if you cannot do this for whatever reason then as you already surmised un-ticking everything except "Set terminal Clock" will just change the clock (to the current time on you PC). The unit will obviously go into transfer mode but when it reboots only the time will have changed.

     

     


  3.  

    I agree with Kaare_t.

    The WinCPU just looks like a Windows embedded PC.  If this is the case it will probably be doing the SECS/GEM protocol and using a bespoke interface to the PLC. Can you log into the PC? You may be able to see how it is communicating with the PLC. If I was doing this I would use an OPC Server on the WinCPU simply because all the time and effort I would spend creating the SECS/GEM interface to the PLC (in C or whatever) could then be reused on any PLC without having to recode it (just point the OPC server to a different PLC). If an OPC server is installed it probably also has a standalone client you can use to see all the registers in the PLC it is using.


  4.  

    You can use block move

    Example in ST...

    BMOV_M(TRUE, RecipeSteps[CurrentStep].Operation, K100, StepData.Operation);

     

    The above copies one subscript of an array of structures (DUT) called RecipeSteps, to a single structure (of the same type) called StepData.

    The variable "Operation" is the first variable declared (start address) of the structure. The K value is the length of the structure in total.

     

     

     

     

     

     

     


  5.  

    You can't piggyback the wires from the pt100's but you can of course use the double or duel output type ones. Do the standalone temperature controllers also have an output of their own (4-20mA etc)? If so you could simply program the controllers to retransmit the values (OK you would have to replace the module you have just ordered).


  6. Quote

    To use it as a condition not with MOV but like D0.1 and D0.2 -> Y1

     

    Think this is dependent upon what PLC you are using - For example I’m pretty sure you can’t do this on Fx3G’s - but you can on Fx3U’s and Q’s etc

     

     


  7.  

    You need Information Designer. E-Designer is actually identical and the conversion is trivial but E-Designer will not download to an Exter.

     

    Many send the project to Beijer for conversion but actually just open the E-Designer .mpa project file and the Information Designer .cpa project file and copy the differences from the first 6 lines or so then rename the .mpa file to cpa file. We use Beijer a lot so I have actually written an app that converts between the formats. Let me know if you want me to send it to you. Check you your email for details.

    Alternatively send me your project and I will convert it to Information Designer and export it to a .Dat file for you. You can then put the Dat file on a usb stick (or CF card) and plugging it into the HMI it will automatically load the project.

     

     

    Regards

    2 people like this

  8. When you don't want a screen to change put -1 in the register (there is no -1 screen).

    To change a screen I do the following...

    1. When I don't need to switch a screen with the PLC the screen switching register is always set to -1 .

    2. When you want the screen to change put the screen number into the switching register. Personally I pulse this value on/off with a value of -1 (so if I want to switch to screen 43 I put 43 in the register for 1 second and -1 for another second etc)

    3. When the HMI says it has changed to the correct screen I put -1 back in.

     

    Works every time.

     

     


  9. Sounds like a normal bi-stable valve.

    One output opens the valve, the other closes it. Once an output has been turned on the position of the valve is maintained even if the output is turned off. This is oposite to a "spring return" valve which only uses a single output (generally to open the valve) and when the output is turned off the valve closes using a spring inside the valve.

     


  10.  

    17 hours ago, madatix said:

    I HAVE INFORMATION DESIGNER SOFTWARE BUT THERE ARE NO .CAP OR .DAT FILES, I GUESS IT'S " ix" TYPE..i tried to upgrade the HMI system files

     

    If you have the source code you WILL NOT have a .dat file. You will need to create one.

    If you actually show us what files you have we will be better able to help you (otherwise we are just guessing).

    Can you upload the files you have for us to see? - or take a screen shot of the files you are talking about.

     


  11.  

    It sounds like you may have the actual project files (source code)

    do you have a file ending in .cpa and a folder that contains images and a driver configuration file.

    for example...

    1 x text file called - "Machine_1_V2.cpa"

    1 x folder called -    "Machine_1_V2-Files"  (same name as above but with "-Files" appended to it)

    If so you have the project files that can be loaded into Beijer information Designer (I-Designer). Once loaded you can create you own *.dat file to put

    on your flash card (or just program the HMI directly using the software).

    http://beijerinc.com/product/information-designer/

     

    Alternately if you do not have I-Designer you could post it on this forum (or just to me) me and I will create one for you.

     

    However if you have a project and one of the folders has 50+ files with the extension "DLL" inside the main folder. Then this is probably an IX project for a different HMI

     

     

     

     

     

     

     

    1 person likes this

  12. ST.

    It's not very elegant for bit logic but it has one major advantage. It can be copied and pasted between most PLC's provided you make your code as generic as possible (try to avoid using functions only built into a particular PLC). Our equipment is complex and would run to hundreds of thousands of rungs if coded in ladder (and would take several months to re-code between different PLC vendors). Keeping a single code base in ST means we can add features to the system knowing all new orders on whatever PLC the customer chooses will get all the new features and will be as far as possible tested. 

    Same with the HMI. We find companies tend to be insistent on the PLC, but far more flexible with the HMI. We use the Beijer IX series HMI's as standard (simply because our recipes run to over 30k word registers and include images). If the customer insists it has to be a particular brand we just run the IX software as a app on the customer preferred brand PPC. Apart from re-tagging the OPC variables to the new PLC there is no need to touch the HMI code.  

    Often the case against using ST is that it is not "maintenance man" friendly. This is a point I do have some sympathy for (however on a couple of jobs the original URS has specified only ladder - but the customer soon changed their mind once we update our quote to reflect the re-coding required).

     

     

     

    1 person likes this

  13. We have over a thousand FX's in the field, and have found them to be seriously built proof (apart fro a couple of outputs failing not one PLC has gone down in close to fifteen years).  Mitsubishi software is also very cheap compared to AB (and does not change revision every 20 seconds). Same with the PLC's no firmware updates etc like AB. However, If your coming from AB I would check out how you got on with GT Designer before committing yourself. Mitsubishi HMI hardware is fantastic (and seriously good IP protection) but IMHO the software for them is just dire compared to AB. Another downer for Mitsubishi is documentation  - lots of it in "chinglish". Amazes me how such huge organization cannot afford to pass its document authoring though a native English speaker.

         

     


  14. We used to use MX component but found it buggy and unreliable (version 3). We moved over to OPC about 5 years ago and would not look back. OPC servers are easy to set up and far more flexible.

    Do the systems have a HMI? you might be able to get your data out through them (they would have a serial or Ethernet port built in so you would not have to add anything to the Plc .

     

     


  15.   Most likely a false alarm. Eset and Kaspersky on my machines seem happy with it - whose AV are you running? Until it was changed a couple of weeks ago I use to get them on this site too! Best Regards    

  16.   You can actually buy the 1063 (and all the E1000 range) direct from Beijer, the company that actually always made them (they were always rebadged under the Mitsubishi name). They are actually identical to the Beijer Exter range - but the Exter range never included the driver for Mitsubishi PLC's therefore forcing you yo buy the E1000 range instead through Mitsubishi (the Exter actually now includes the Mitsubishi driver).  see... http://www.beijerelectronics.com/en/products/ix-hmi-solution/other-hmi/E1000%20operator%20panels/New%20Folder/E1063   Best regards            

  17. We have used hundred's of these screens and I must say we too have had problems with condensation compared to other HMI's we use (mainly in the food industry where they love squirting water lol) . We found installing a heater inside the cabinet worked pretty well - also putting a flip plastic cover over the front, but this was more to stop direct water jets hitting the screen.

  18. I have not use STL myself, however one problem I find with standard "step type" or "state machine" programming as I see it is that you transition to the next step by a condition. Now if you loose this condition after you have move on to the next step then the logic will just continue on regardless (Ron_S touched upon this earlier). In many situations this is undesirable. A simple example would be... You want to put a round bolt into a hole and your machine uses a sensor to detect when the hole and the bolt line up. The step logic starts moving the machine into position and waits for the input (X0) to indicate the bolt and the hole line up. It detects X0, stops the machine and then transitions to the next step. On this step we want to actual insert the bolt - so we start moving the bolt into the hole. However, for some reason the machine actually overshot the X0 sensor and the bolt and the hole are not actually lined up. Regardless of the fact the bolt and hole are not lined up the machine continues to try and insert the bolt. (because we are not looking for X0 in the logic anymore as we have moved on from that step). Step programming is common and there are lots of ways to do it. STL is just Mitsubishi's inbuilt system. Many people just roll there own using set/reset, shift registers or even switch/case statements (in structured text). Then they put extra code in where required to check for things like the above (and act accordingly, stopping the machine or jumping back to previous steps etc). As I said earlier I have not used STL before - just my thoughts on this type of programming.

  19. I would presume they are referring to STL (Step Ladder Programming) Google JY992D48301 to get the programming manual. Chapter 3 describes it in detail. And quoting the manual... "STL is really a method of sequencing a series of events" Best Regards

  20. If positioning on power up is important to you perhaps you should look at an absolute encoder (if possible on you application). Otherwise can you not just not datum the axis first (as JRoss said). Your PLC can remember the position it should be going to next and just carry on the sequence after the datum. Regards

  21. Personally I would check that all the 0V's of each PSU in each cabinet were connected to ground (earth). I have had similar problems when on of them was left floating. This is standard practice on all out panels.

  22. Ok with the backup copy of the program you have just sucked out.... 1. Go to network services and switch on "Remote access" - leave all port settings alone. 2. If you use recipes on the HMI you may also want to turn on "FTP Server" as well - this will allow you to backup all the recipes created on the HMI using windows file explorer (simple drag and drop) or an FTP Client. 3. Transfer the project back into the HMI (remember the IP address so you can put it into the VNC client to get remote access) 4. download "TightVNC" or Remote Access Viewer from the Beijer website (link below). Actually most VNC clients will work fine (we have our own PC based recipe system and have a generic VNC client embedded in the program). http://ftc.beijer.se/files/C125728B003AF839/D27215D44319B05BC1257728004244E0/RemoteAccessViewerSetup%201.5.4_iX.exe