MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

8 Neutral

1 Follower

About Luke.S

  • Rank

Profile Information

  • Country Japan
  1. E700 Drive

    Are you talking about an unwinder tension control? Anyway with an  E700 inverter presumably you're using an induction motor. If you forcibly reverse an induction motor I would expect it to trip the drive or at least overheat pretty badly. It sounds like you should use a permanent magnet servo motor or torque motor. 
  2. String to Decimal

    If you interpret the ASCII table in decimal, the number characters start at 48 for zero. Therefore if you subtract 48 from any number character byte, you will get its unit value. To get the tens, multiply by 10. To get the 100s multiply by 100 etc. Then sum them to get the number. E.g. (57-48*100)+(52-48*10)+(53-48*1) = 945 Because Mitsubishi PLCs have maths functions which take data 2 bytes at a time, to get the single byte you could mask the byte you don't need with WAND. Then shift the byte to the right place with SHR. E.g if you have '34' in D1, the following should give you decimal 3 in D10. WAND HFF00 D1 D10 SFR D10 k8 - D10 k48 D10
  3. Open B&r 2005 Files

    Unlike some other PLC brands, you cannot upload B&R source code back into the programming tool. Compiling the project into binary data to write to the CF is a one-way process. You should speak to the OEM or whoever developed the software regarding obtaining a copy of the source code. Sometimes a copy of the source project is attached on the CF in the user partition but if you cannot find a .apj or zip file anywhere then it appears that it is not in this case.
  4. Stop positioning instruction!

    I've used the LA and LB line driver outputs before to get the position from an analogue IO drive. That was to a Q and I used the QD62 high speed counter card with no problems.  Your FX5U should support a FX3U-2HC high speed counter card (I think it also needs a bus converter module). If you're willing to fork out for this hardware, it will be a sure-fire way to receive the line driver pulses from the drive.  
  5. CVS file log not generated.

    Or even better, handshake with the HMI: 1. SET your logging trigger 2. Map the 'Logging Notification Device' to an M contact 3. When this M contact turns on or any relevant alarms occur, RESET the logging trigger This is much more robust than using a timer delay.
  6. AJ65SBT2B-64RD3 PT100 Module

    Yes, just writing H0 should disable averaging. Or H0101 would also do so I think. Are you sure you have the correct X and Ys. Check your cclink remote device map: Is the cclink definitely communicating and the RTD station not in error? If it is working properly and you follow the program example only change device addresses for your hardware config, it should work. Yes you could just enable the X1018 network with a one shot but you would have to do it after the network communication was established, not SM402. I suppose you could just wait 1 min with a timer and trigger it on the rising edge of the timer to see if it's working. But the right thing to do would be to get a program like the example working. Post a screenshot of any parts if you'd like me to explain what it's doing.
  7. FX5 PLC loses impulses from encoder

    Yes sorry, I think JRoss is right. It's different if you're using high speed counting functions. It says the specs are up to 100kHz for 2 phase input.
  8. AJ65SBT2B-64RD3 PT100 Module

    If you just delete the lines it will be in sampling mode. If you do that then I think you will need to set another hex value so than the number of samples is zero. Or there should be a hex code you can set so that averaging is off completely. But you will still have the delay from the ADC time. Please look in the users manual for the hex codes.
  9. How to calculate KWH from instantaneous KW

    Perhaps it's easier if you consider that a Watt = Joules per second, the rate of energy transfer. So a kWh = 3600000 Joules. 1kW = 1000 J/s 1 kWh = 3600000 J Now imagine you wanted to know how close you got to a city 3600000 meters away travelling at a speed of 1000m/s. You would integrate the speed over time to get distance. If you travelled for 10 minutes you would do (10*60)seconds * 1000 m/s = 600000m. 600000/3600000 = 0.166 so you are 16.6% of the way to the city. In the same way, if you integrate the instantaneous kW over 24 hours you will find how close you got to a kWh. Or how many multiples of kWhs you did. You can do this in the PLC by adding the kW PV to the on the rising edge of a one second timer. |--(NOT t0)-------------------------------------[t0 10]--| |--(t0)--↑---[+ kW_SUM kW_PV kW_SUM]--| |---------------------[/ kW_SUM 3600 kWh_PV]--| The kWh_PV will tell you how many kWh you have done in the integrating period and you could log this value and reset to zero every 24 hours. Sampling the kW PV every second may not be fast enough depending on how fast it fluctuates. So you could sample it every 100ms but you would have to devide by 10 before adding it to the sum.
  10. AJ65SBT2B-64RD3 PT100 Module

    The hex code specifies the averaging method used to reduce the effects of noise or other unwanted disturbances. Basically like a software low pass filter. These will be explained in the manual for this module and you will find the hex codes there too. The D register will be copied to the buffer memory on the PT100 module for the averaging settings. They've only set up CH1 and 2. Probably CH3 and 4 will be in D1002, D1003 but you might need to change the FROM/TO functions too. If your temperature signals are not stable or too sensitive to things like doors opening etc., you might consider using averaging. Although it does delay the feedback to the controller, it shouldn't be a big deal in a temperature control application. If you just delete those two rungs, I'm pretty sure all channels will just be on sampling mode anyway (they will just be 16#0).
  11. Indirect addressing FX3U

    You may find this post helpful:
  12. FX5 PLC loses impulses from encoder

    To the OP, you said the input response settings are "no setting" or 10ms. This means you are sampling the encoder at 100hz. But you should be sampling at at least double the maximum frequency of the encoder. This explains why it's ok at 41.5 rpm but only catches pulses intermittently at higher rpms. You can lower the input response for the high speed X inputs to 0.6ms minimum giving you around 1.6kHz sampling or 800 pulses per second at the encoder MAX. If you expect in the application that the encoder can give you over 800pps at higher speeds, you should use a high speed counter card instead.  
  13. PT100 on Q50UDEH

    RTD = Resistance Temperature Detector There are various standard RTD types and PT100 is one of them ( 100 being 100Ω I believe) . You can take the readings remotely over CCL with this device station: Then you would have to use function blocks or code PID in the PLC to calculate commands to output to PWM or whatever method you are using to control your heater. OR You could just use a temperature controller which interfaces with the PLC over CCL. It handles the PID loop locally and will have an auto tuning function greatly reducing your development and tuning costs. Commands such as temp. SV and monitor data such as temp. PV can be sent over CCL. If your project is simple ladder (no variables) and you can't use function blocks then you are looking at a quite involved and risky software development if you do the PID on the PLC. I'm assuming you are using CCL v1.1 or 2 with a Q here.
  14. Q series PID control

    What do you want to control with the PID? There are PID function blocks available in Mitsubishi which are probably best suited to temperature control.  For harder realtime applications I have PID programmed in simple ladder but I would have to make a generic example to share it.
  15. Coverting Q-A series program

    It's relatively easy to do so. In Gx works 2 in the file menu there is an option to open a Gx Developer project. The project will be converted to Gx Works and can be downloaded to a Q without a lot of modification but you need to watch out for: 1. Special relays and registers. E.g these are M8000 onwards etc. in A but need to be changed to SM400 etc. in Q 2. Analogue scaling calculations might need to be reviewed because the resolution of Q hardware is generally higher than A (16000 vs 4000). Although some Q modules let you choose 4000 resolution mode instead of 16000. 3. You will probably need to carefully check X and Y assignments and FROM/TO command unit numbers.