MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About strantor_

  • Rank

Profile Information

  • Country United States
  1. cp1l-e and HBM rs485 load cells

    I hope the HBM load cell does not use very deep ASCII commands. I just finished an ASCII project with a different device, and it was originally specified for CP1H, which does not support STRING data type (neither does CP1L/E). Here's an example of the message exchanges required to get a measurement value from the device: Because of this, especially that long string "D/KS....." which needed to be examined and values parsed out, the project quickly became very complicated and difficult without STRING data type. I had to change the PLC spec to CJ2M in order to meet the deadline.  If your load cell is just sending you a number it should be easy enough, but if requires a whole conversation to coerce a value out, or it's sending something like above, consider doing something else.
  2. When will I use CIO and Work bits?

    Work bits are non-retentive memory. Use them for almost everything, except that which needs to be retained. D20.00, if ON before power-off, will be ON when power comes back. W20.00 if ON before power-off, will not come back to the ON state when power comes back.

    You bet!
  4. Custom Data type question

    I found A solution. Not sure if it's the best solution. Open to new ideas. I just changed the WORD in my datatype to a BOOL and new the BOOL is named. When I type the WORD address into the TIMLX instruction it inherits the symbol name from the datatype but shows no ".xxx" - good enough for me.
  5. Custom Data type question

    I am getting ready to migrate a bunch of TIMX to TIMLX. For this I want to create a custom data type for the new timers' parameters. I want to give a name to a BOOL within a WORD that is also named. Because for some reason TIML/TIMLX makes you specify an entire word for the completion flag, when all you need is one bit of the word. Maybe it will be more clear if I demonstrate:         Is there a way that  I can name the bits within my CompletionWord?    Thank you  

    I've uploaded one of my projects that contains the whole shebang of networking with the DRM21. CX-Integrator file and CX-Programmer file (all logic & FBs deleted - CIO tags still intact) . You set up your remote I/O memory locations in CX-Integrator and then add CIO addresses in your CX-Programmer program that correspond to what you  put in CX-Integrator.       DRM21
  7. Here's an anomaly for ya! (I finally got a break ) I received the CJ2M today and hooked up. I was in the middle of performing my multi-stage process when I looked over and saw that the HMI was just talking to the CJ2M right out of the box. Amazing! It's looking for a CP series, instead found a CJ series, and for whatever reason, it's totally cool with that.
  8. I just received a box of Omron parts from my supplier and they had dust/lint on them. That caught my eye so I looked harder and realized there are no stickers over the vents that I'm used to seeing. The ones to keep debris out during installation and say "remove after installation."  These were purchased as NEW parts and they were inside their proper boxes sealed with Omron tamper tape intact. The boxes do not look like they have been opened. The PLC and I/O cards have MFG dates <6mos old.  I am used to Omron components coming with the debris sticker, and had they not been covered in dust I probably wouldn't have missed them. I don't know what to think. Now I doubt my memory of the stickers; I know for a fact I've seen them on Omron PLCs and I/O cards, but on ALL of them? I'm just not sure. And now I can't remember when was the last time i specifically opened CJ1W I/O. So I Google Image searched my specific cards and found several images of them with the stickers. I know that, at some point, these stickers would have been on my cards. Has Omron ceased the practice of installing these stickers? Or did I buy not-so-cleverly disguised used cards?
  9. Alarm history in NB Designer

    Yes I agree. I devoted a lot of time in the manufacturing plant where I cut my teeth, pondering to what extent cultural differences affect our logic and what we find intuitive. Most of the machines in that plant were from the '60s, and were a mixture of German, Austrian, American, and French machines. As a noob I picked up ladder diagrams very easily with no real training, but the old European physical relay logic prints were something that took me a while to grasp. I kept telling myself "think like a German." Siemens is another example. Maybe for a German it's totally intuitive. For me, the time I would have to invest into learning where they've hidden everything probably wouldn't pay off, unless I was to groom myself into a "Siemens Specialist" and do only Siemens for a living, so I stay away. I think my American upbringing naturally led me to find Allen Bradley and Ladder Logic more intuitive than Siemens and IEC drawings - in some way that I don't fully understand. I can't put my finger on it, but there's definitely something to this. 
  10. Alarm history in NB Designer

    Excellent! You saved the day again, Michael! Thank you! I thought I had tried everything. "Event?" = [Alarm History] Really? That's wasn't even on my list of things to try. I'm starting think maybe I should have attended some vendor training before diving into NB. Other Omron stuff was more intuitive.  
  11. I would like to have an "Alarm History" page showing historical alarms with timestamps for time generated/acknowledged/cleared. Like this (ex from web, not my work):  This is a fairly common feature but I do not see an out-of-the-box solution in NB designer. I have played around with the "Event History," "Alarm Display," and "Event Display" and none seem to fit. I feel like I'm supposed to make "Event History" work for my purposes, but it's pretty confusing for me. The manual could be better. Any example of, or guidance for implementing an alarm history in NB,  even if not exactly like I want, will be greatly appreciated! Thank you!
  12. omron CP1E-E30
  13. PLC TO HMI

    Ah ok. Thanks for the explanation. I accidentally deleted my question while you were answering it. I was trying to edit it to show the quote.
  14. Ok I wasn't able to add the CP Series and transfer directly from CJ to CP. For your (and everyone's) reference, here's how I had to do it, using the general concept that you provided. Starting point. CJ/CS/NJ with all my addresses in it Step 1: add a CP series (or any PLC with serial port I guess). This is just an intermediate container for information. Add a serial link between them Step 2: Perform the memory address transfer as described in the document provided by Michael Walsh in post #3 Step 3: Delete the CS/CJ/NJ, and accept the scary confirmation message.  Add a CP series where it used to be. Configure the IP address according to the document Step 4: Double click the HMI , Go into the communication settings, note that the HMI protocol is different than the only PLC in the program. Change it to CP series ethernet. Step 5: Perform the Same find/replace operation to migrate the addresses out of the temporary CP1H (PLC1 in my case) to the new CS/CJ/NJ (PLC0 in my case) Step 6: delete the temporary CP1H and serial connector Done!   Thanks Michael!