protiusmime

MrPLC Member
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About protiusmime

  • Rank
    Newbie

Contact Methods

  • Website URL http://

Profile Information

  • Country United States
  1. Milltronics Belt Scale application in AB PLC5

    Thank you very much, Paul, for your reply. This Milltronics scale and tail spool encoder are already installed, but have not been used for quite some time. At this time wood chips are not selling for a very good margin so we are using them for fuel to a biogen power plant. We are needing to primarily know how much product we are sending to the fuel storage area... thus, the belt scale and encoder. I have one analog channel available on an A/B 1771-IFE in the remote I/O rack that is located within 500 feet of the Compu-M. Accordingly, the 4-20 output will be sent to the PLC5 to allow us to trend/log data to a file (MS Excel or RSView or ??) The Milltronics product/programmer lit really does not go into much detail about the composition (dimensioned data) in its output. We are most interested in product flowrate. So, I am thinking that the output can be sent directly to the A/B 1771-IFE and from there we can do whatever calcs we want for the unknowns?? I am not sure how the Milltronics performs the integration of load, speed, and total flow, but if the flowrate is in fact output on a 0-15mA or 4-20mA scaling, all I probably need to do is simply program the Params on the Compu-M and send the output to the PLC, do some ladder logic for data arrays and be done with it. I appreciate your input and suggestions.
  2. I am interested to know if anyone has any experience using a Milltronics Compu-M belt scale (dual load cells) to input analog 4-20mA to a PLC5? According to the Milltronics specs, the 4-20mA output is proportional to the "flowrate". Since the Compu-M is an integrator for load, speed, flowrate, and total flow, I am wondering if the analog output can provide more than just flowrate? According to Siemens, belt scale LOAD is equal to Flowrate over Speed (of the belt). One would think that once analog data is input to the PLC it could be used at least to calculate the other quantities.?. This system is using a MD-36 speed sensor for belt speed (36 ppr). Anyone have a bit of exerience using a belt scale input to a PLC5 (or any other PLC analog input) to trend and/or manipulate data? Thanks for any information.
  3. RSLogix 5000

    Well this post was interesting. It makes me want to punch my Mngmt Bobo doll. Sorry... I had to say it.
  4. Am attempting to use RSLinx Professional version 2.43.01 to get data from RSLogix5000 and into MS Excel. I keep getting an error that states "remote data is not accessible" and a RSLinx component needs to start. Our RSLinx Pro is running as a service and has no problems with other processors. Does anyone know if RSLinx Pro is correct for this comms? If so, what is the MS Excel formula bar syntax for using a RSLogix5000 control tag? Thanks.
  5. Lighting Control

    In the CTX family, you could use your GSV and a 7element DINT (date[0-6]) to store the year, month, day, hour, minute, and seconds. Using these elements a simple logical EQU string on a rung could condition each On/OFF time for your controls. e.g.: date[0] = year date[1] = month date[2] = day date[3] = hour date[4] = minute date[5] = second Such that if date[2] = 1, and date[3] = 10, and date[4] = 30, then turn on OTEx. OTE is true on Monday at 10:30. You would use military time so to avoid the 12-hour conflicts. You would want to increment your day counter by using the same idea to ADD 1 to a seperate tag addy (e.g. DAY_OF_WEEK) and when becomes >7, you would MOV a 1 back into the address to start over on Monday (1). EQU(date[5],59)EQU(date[4],50)EQU(date[3],5)ONS(ONS_LIGHT1_ON)OTE(LIGHT_ON); GRT(DAY_OF_WEEK,7)MOV(1,DAY_OF_WEEK); MOV(DAY_OF_WEEK,TODAY[0]); And the same for your OFF time, with comparators above set for your day,hour,minute off time. = OTE(LIGHT_OFF) Check it out and see if this makes sense.
  6. RSLogix 5000 Wall Clock

    Excellent approach by Ron, et. al. One additional use that we are doing is to update all PLCs on the highway, comms by the following: at say 23:50hrs (military standard), MOV the dint array to a tag base range, then MSG date/time tag base to each PLC upon change.. first to an integer array in each, then to the S files. MSG.DN triggers the next MSG send, etc. etc. We also use a day increment counter that is reset >7, so you could use that rollover to update the PLC system clocks. We are using a CTX for the master in this fashion to keep all others in "sync" for production tallies and a bunch of other calc timings.