collinsd70

Hi Olyn. See attached a 6 Element FIFO for the REAL Data Type. Instructions 1. Import the AOI into your Project. 2. Create an Instance in either Global or Local Memory. 3. Load the AOI into your Selected Routine, Connect the Clearall Boolean and the REAL which will load to the FIFO.(the REAL is loaded when it changes value). Note the Clearall is an IO Parameter so will be passed through the AOI and reset once all buffers are emptied. 4. oFIFO_Pos will tell you the location of the most recent Variable (to be used for an Arrow on a HMI for example) I have confirmed operation on Emulate5000 and all seems to work correctly. This AOI will load and store 6 Variables only, do not attempt to change the array sizes, if you do; you may crash the PLC.     Regards   Daniel. AOI_6FIFO_REAL.L5X

Hi Joe. Have done this on the 'bay', all other items are USA-based but everytine I list automation parts like these, they never sell or get any interest. Have also tried selling some Mitsy stuff and some Siemens Failsafe Modules (all as far as im aware; heavily underpriced). Never seem to get any bites.   Regards Daniel

Hi All. Im after some guiding for pricing on a Kinetix2000 Servo Amp rack on SERCOS II. I have flashed all modules up to V1.095. I dont want overprice and not sell- and have no idea what they are worth.   Regards Daniel

Hi mshifa. Firstly welcome to the forum. My initial guess is that you have the wrong Input Address in your program? Can you double check the input address matches your physically wired input? If this is all OK maybe check your voltage supply, it may be sufficient to illuminate the LED but not necessarily enough to close the input relay. Otherwise please attach your code and maybe a photo of your wiring..   Regards Daniel

How many REALs do you wish to store in this FIFO? What version of RSLogix500/Studio5000 are you using? I will have to customise the AOI to your requirement.     Regards   Daniel

Hi Arnoldzw   It seems you are in a very difficult position. At this point in time; I would consider which is most cost effective 1. The time it will take you reengineer this code, test and debug or 2. Bite the bullet and buy a PLC with suitable step size. You will have to play around with languages to work out which translates into less steps.   Regards   Daniel

Hi Arnoldzw. Unfortunatley there is no simple way to reduce this significantly; you may be able to use different instructions/ functions to reduce your step size, however the only significant way to reduce this is to use a different language such as simple/ structured ladder etc. Normally with a Mitsubishi system; the code would be designed and coded before buying the necessary hardware- this way you can approximate the number of steps so that you can then choose an appropriate CPU. You also should ensure you have a spare number of steps to accommodate the online change facility if this is something you wish to do during your comissioning stages. Ultimatley; your most cost effective measure will probably be to buy a bigger CPU.   Regards Daniel

Hi Olyn Firstly welcome to the forum. It sounds like you want to pass a REAL Data Type into a FIFO (First in First out) does this sound correct? So the newest value is always at the top but old values are kept below. Take a look at the standard RSLogix5000 Function for FIFO (Load and Unload). Otherwise I can send you my custom Add-On-Instructions that can hold 5.10 or 20 Values in the REAL data type. See my attachment that demonstrates operation with the INT data type. If you want a copy of my encapsulated code- just let me know.   Regards Daniel

Hi Future. Normally the connection is made under your network properties. You will need to select module type; then slot number aswell as your master/ slave transfer areas (W and B Addresses).   Regards Daniel

See here for a FB I already made at the request of another poster previously, just import the ASCII to your project. The only difference is it only takes in the lowest 8 bits but you can easily expand this yourself if you need to examine for a value over 255 decimal.     Regards Daniel

Hi Ojay. Im assuming you mean you want to display the numerical value onto a HMI? You will need to find out where the numericla display is written from then copy the device address to your graphic display   Regards Daniel

@Ron_S See attached files above   Regards Daniel  

Glad I could help Simmo, feel free to modify to suit your application.   Regards Daniel

Ron. I have made the following FB for you, it will convert any floating point to 2 seperate integers. I have bench tested on my Q-Series and seems perfectly adequate for what you need. Attached is the ASCII Import file you need plus a bitmap of an Instance working......   The logic is driven purely from the Real input value, if it changes, the calculations are completed over one whole scan and passed to the output parameters.  The code takes advantage of the REAL_to_INT_E and reverse functions for generating rounded numbers in which the differences can calculate the signifjcant digits. Hope it comes in handy. iREAL (REAL); your HMI input value oWholeNumber (INT); the whole value from the REAL oSignificant (INT); the significant value (3 decimal places). oSign (BOOL); the sign (I have an absolute in there at the moment as I assume you always want positive). I would recommend you test that it works in the ranges required as ive only tested it to 500ish I think.   Regards Daniel FB_MrPLC.bmp FB_Real_MrPLC_V1.asc

Here is a screenshot of the logic and also the encapsulated AOI (Source unprotected). Note the Tag "oHighest_Pressure" is only updated when the Start signal is high, on the falling edge of Start; the Highest Pressure tag will default back to 0.   Regards Daniel AOI_Capture_High.L5X

Hi simmo1973. Firstly welcome to the forum. Of course you can, in ladder logic this is quite simple. So on first scan or the bit you use to request monitoring, one shot the current pressure to a holding register, then in parallel if the current value is less than the new value, move the new value into the holding register. Once the conditions for your reset are fuffiled then move a 0 into the holding register. If you doing this on many machines or routines, it may be worth making this into an AOI. Does that make sense or?   Regards Daniel

Then why not just have 2 16-bit fields on your HMI, 1 for the whole number then another for the decimal point? Of convert from REAL to DINT/ INT and take your significant number off there?     Regards Daniel  

Sorry, your version of PLC does not support this for some reason. I just tried myself with your PLC type and the selection is no longer there.     Regards Daniel

Glad to hear you have a new one on the way. Make sure you come back to us if your facing the same issue.     Regards Daniel

Hi PLC369. Firstly, welcome to the forum. So the term 'POU' comes from the IEC 61131 standard and means 'Program Organization Unit' and thus all programs and resources are kept in here, whether this is routines/tasks or resources such as Function Blocks and Functions. An AOI can be called in as many instances as you want; so yes I guess they can be compared to be similar. Im not sure why Rockwell have never followed the IEC naming conventions (coming from a Mitsubishi backround I know they certainly have).   Regards Daniel

Hi IkBenNietHier. Firstly welcome to the forum. There is a setting in GX Developer onwards that allows you to drive the internal Run/Stop from a phyiscal PLC contact. To find this, its under 'PLC system' in the CPU Properties. If your just want to stop execution of main logic, you could drive all your subroutines from a common marker.   Regards   Daniel

Hi Luka. My first guess would be to use some sort of OPC Server. I believe "MX-Component or MX-Sheet" might be of use to you for this sort of thing. Just having a quick google of the above confirms this is most likely the best way to go about this. What sort of data are you populating in this array (INT, DINT, REALs?), depending on the OPC Server you may have to create a structure in your Globals and assign Mitsubishi Addresses Regards Daniel

Okay, basically if you have an alarm already (on your HMI etc) then chances are the the PLC bit is being monitored and you may need a power cycle. The bits you will need to examine are: - M8005- This is the battery low signal (taken from the PLC firmware), this should be a true reflection of the PLC state. M8007- This is the PLC Battery Low Latch- ie this will stay high after changing battery, to clear this you may be able to toggle this, otherwise it will need a PLC reset. So after a battery change...both bits should ideally be low. Regardless of how you plan on doing this; make sure you take a backup of device memory (if you are in GX Developer then just upload "Device Memory", if your in IEC Developer you will need to use the "Device Edit"). Any latched memory not written to on startup means potentially you will lose all of this data in the event of a battery failure (things like HMI setpoints etc).   Regards Daniel

Hi PLCMentor. With the Q-Series it is 3 Minutes but I guess a lot of it depends on the size of the Capacitors and Demand. Officially; Mitsubishi have always stated to power the PLC off before replacing the battery, however I have changed the Q-Series ones for years powered on without an issue. Just a slight note; If your code is monitoring the battery low latch, the PLC will have to be reset afterwards to clear this, if your PLC is monitoring the standard low battery voltage register, then it will clear automatically once the voltage reaches the minimum threshold.   Regards Daniel

Okay. Could it be that the selector switch is broken? (I have seen before). I seem to recall on 1500 series there is a software selection also made possible through the CPU Screen? With or without any Blocks in the User Memory, it is normally possible to still select Run Mode. Edit: Glad to hear you haven't tried to format the MMC in Windows  Regards Daniel