collinsd70

MrPLC Member
  • Content count

    264
  • Joined

  • Last visited

Posts posted by collinsd70


  1. Okay. So you have the final revision of IEC Developer.

    I normally prefer working in IEC Developer but in this case it might be worthwhile to upgrade to GXWorks2, you wouldnt need to 'rewrite' your code, simply just convert between the 2. 

    If you want me to take a look at this- send me a PM- otherwise I see no alternative unfortunatley.


  2. Normally on a machine commisoning; the customer would be asked to specify machine firmware revision requirements- the reason is normally to avoid the exact problems you are facing.

    As newer revisions are released- the software and hardware functionality also expands giving you better ways to look and analyse different conditions, the risk of downgrading firmware revisions at this stage potentially means some of your code will need to be rewritten and function tested.


  3. Again- you are facing the same situation you have before.

    Lets say your CPU is running firmware revision '25', you will need Studio5000 version 25 in order to open the file. 

    Once you have the file open then you are free to upgrade/ downgrade as you wish depending on the installed software versions on your computer.

    My main virtual machine for example runs RSLogix5000 v10 all the way to 19- then Studio 5000 20-31. So I have the luxury of being able to open pretty much any program. 


  4. Yes that is correct, the only way to convert your application is to open in a compatible version then roll backwards or forwards as you wish.

    The problem with rolling back a version is you may find lack of certain functions- leaving you with an uncompiled program, if its just for 'viewing' purposes then thats fine. If you are planning to load it in a machine you will need to be aware of whatever changes are needed in your code and you could expect slightly different functionality.


  5. Okay, in this case I would create a new Project in RSLogix5000. You need to match your project revision to the firmware revision on the CPU (lets say for example 15.1). This info will be on the CPU itself or check via the RSLinx window

    Once the project is built- download to the controller, whilst online go to your controller properties and go to Internet Protocol, here it will give you the option to manually set an IP Address and a Subnet Mask, once complete apply via 'Set' and your good to go...

    The other option is to click your ethernet module properties in the RSLinx tree and apply the same setting there- but Enivitabiy you will have to create a project at some point regardless. 

     

    1 person likes this

  6. Hello Anthony.

    Firstly welcome to the forum.

    There isnt a straight forward-answer to this i'm afraid but you do have several options.

    1. If you have the correct serial cable you could connect intially via RSLinx then set a new IP Address using RSLogix5000. The cable you need would be a 1756-CP3.

    2. If you know the subnet range in the PLC- if you make sure your PC is on the same and connect via ethernet- RSLinx may be able to check this way. Otherwise the BOOTP Utility could be used if the hardware address (MAC Address) is known.

    3. If you have the original machine program that this PLC was removed from- the intial IP Address will be stored in here (assuming  the memory card is sill intact). By all means you can send me the program (if you have it available) and I can check for you.

     

     

    Regards

    Daniel


  7. 40. You are trying to run a MSO or MAH instruction when the drive is locally disabled.

    Could it be that the axis was inhibited at the time? 

    This also could co-incide with the point I made previously regarding the hardwired enable to the drive missing..

    In your MSO command...are you checking the contact x.DriveEnableStatus where x is your axis name? 


  8. Hi Bendanator.

    So if you 'monitor' your MSO Error Instruction in the Controller Tags- there is an INT inside the structure that will contain the last generated motion instruction error.

    As long as you havent cleared the PLC Memory- this error code should still be stored in the controllers memory.

    Please post the error number and I will feedback with further information. Where 'x' is the symbolic name of your MSO instruction- find 'x.ERR'.

    Otherwise save a copy of your .ACD file and post here and I will check for you.

     

    Regards

     

    Daniel


  9. Hi Cushera.

    OK, then that is not the problem. Why can you not examine for 'GT or EQ'? If you are examing for an exact value; depending on the mechanical movement- you may not see this value on a scan of the PLC.


  10. Hi Cuschera

    You are making a comparison to a Value stored in Data Register D886- but as a standard Signed 16-Bit Integer will only reach a positive value of 32,767.

    This might explain why your never setting 'M1'? 


  11. Paolo.

    The station number for the QJ71E71-100 on the PLC side should be 1...

    Change the Station Number on the PC side to 10 then test your connection.

    The open settings are regardless for this connection.

     

    Regards

     

    Daniel.


  12. Hi dFx

    The problem is...I dont have a compatible user program for this firmware version. Lets say I generate a new user program and load into the CPU with the above mentioned firmware version- it will not boot into runtime because the RETAIN base address in the user program is wrong.

    This error is generated by the firmware NOT the user program- therefore the necessary requirements for memory addressing are stipulated in the firmware revision and not the uer program.


  13. Hi abdoon89.

    You will probably need the Melsoft MR-Configurator2 software, I am not 100% sure if the most recent version support the J2's as these are not quite old now.

    From memory- I changed one of these drives out and re-entered the parameters using 2 push buttons somewhere near the display.

    1 person likes this

  14. Hi panic_mode.

    This is a bespoke KEBA system and certainly not one of your 'normal' PLC's. The machine is built on MIPS Architecture. 

    This is about all the information I can provide really- I know this RETAIN address will be coded in the firmware file somewhere but other than opening in a Hex-editor; I have no idea how I could find this..

    The only other alternative is to recompile the user program using different RETAIN addresses then reload until successful- but this could obviously take a few days.


  15. Hi All.

    Bit of an odd question- but wondered if anyone had any ideas on how I could figure this out.

    I am using a CPU that compromises of 2 levels of software- 1. The firmware (this is written by the hardware manufacturer and I have no access to the source code, only the compiled files) 2. The 'User application' this is built of many object, include and headers and is compiled using a linker application into 1 executable that is placed in the CPU's disk drive.

    Upon compiling the user program- 2 memory addresses have to be configured.

    1.ST Base Address- this is the start of the user appication memory

    2. RETAIN Base Address- this is the start of the retentive user memory.

    When I compile my program- I leave these as default, however when I boot in the CPU with firmware 3.25 (for example), I am informed that the RETAIN base address is wrong. I cannot upgrade/ downgrade the firmware until I can boot the application....

    I have examined the .bin firmware file in a Hex Editor bit can only recognise version number.

    Does anyone have any idea how I might be able to find this RETAIN address? 

    I no longer have any connection with this company- and due to NDA it wouldnt be possible to ask them. This is all for training purposes only.