Arlen Jacobs

MrPLC Member
  • Content count

    49
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Arlen Jacobs

  • Rank
    Sparky

Profile Information

  • Gender Male
  • Location Kelowna, BC
  • Country Canada
  1. ME Data Store Logging Data

    1) Yes, there is a flag (one shot) when the file write is done; use the handshake connection. 2) Yes, you can manually log data to the file; use the trigger connection. 3) The handshake connection tells you when the file write has completed. It is an odd way for it to work, but when you use the handshake the system will set that connection to 1 and then clear to 0 after the file write is complete. It will also clear the "trigger" connection to 0. I think you can get it to work the way you want; log a string comment one time. - have a push button to manually trigger the data store write; after a comment is typed in. - assign a global macro to clear the comments string; use the same tag assigned to the handshake connection to also trigger the global macro. Give it a shot and post back on how you got it working.  
  2. FTview 8 Recipe Plus: Current Recipe Display?

    You can use one ingredient as a string and store the name there.
  3. FactiryTalk View Macros

    Macros let you change tag values, based on an event. It is a simple version of scripting. You create the macro files from the explorer window, then you assign them to an event somewhere else. These events can be assigned a macro: user login or logout display open or close based on an expression, when it changes from zero to non-zero (Remote macro in global connections) a user pushes a Macro push button on a graphicAssign a tag on the left side of a macro line and then assign a math expression on the right side. tag <---- math expression Whatever the right side evaluates to will be sent to the tag on the left side. You can use/assign strings and a few other items, but that is quite limited. Things to note The lines within a macro are not guaranteed to execute in order (ex. not always line 1, then 2, then 3...etc.). As an example, you may have line 23 complete before line 15 does. Macro files will be completed in order. So, if you trigger macro 1 it will execute before macro 2 starts. Macro lines within the same file are executed in blocks of 50. The first 50 lines are executed and completed before the next block of 50 lines are executed (should you actually have a macro with that many lines).
  4. Copy HMI Tag value to parameter

    Can you use: #100 = [PLC] and #100 = [PLC]Program:ComponentX.
  5. WHICH PLC TO CHOOSE?

    Given those two choices I'd go with Omron. I like where they are going for machine builders; at least what they are saying and put into the software. It pulls together motion, PLC, drives, safety and HMI. Sysmac Studio looks promising, but new (bugs? or lack of features?). You can get a trial copy and take a look. You should do that for Keyence as well. Definitely, look at tech support and local support (distributor, field services). You already gave Omron a +1 so that seems like your standard to beat.
  6. Custom navigation button / Macro to change display

    Have you tried the security expression CurrentUserHasCode()? You can use that with visibility animation to hide buttons that you want secured (ex. change value, GoTo screen). Put your login GoTo button behind the "secured" button. Users hate it when buttons disappear. If you do hide buttons, make sure that you put another "unsecured" button immediately behind it. That way if the user does not have security access, there is always something there.
  7. PackML

    From an end-user perspective (or systems integrator), I love the "idea". As an OEM, I have mixed opinions. What I like is that it gives some common ground between different machines on a line. If they say "the whole line was built with PackML" right away it gives me a picture of what to expect. Basically, it saves time trying to learn how the machine works through its states. I don't remember seeing an end-user with 100% of their machines from the same vendor; which means each spaghetti coded machine is a different invention to figure out. For OEMs, I've seen it help where they had: to create ANY standard of programming for the first time (small # of engineers)no chance of agreeing on their own standard (large # of engineers)to sell their machines as better than competitors' (ex. this helps you end-user)But it doesn't mean that PackML is the best for that particular OEM. So they still change, add, delete guidelines as it suites them. I have seen very few machines using/claiming PackML (out of 1,000's). Unless more end-users demand PackML it will stay in limited use with machine builders. It's an end-user benefit, from my experience. Maybe others have seen different in the field?
  8. Factory Talk View Studio Alarm Ack Bit

    Not easily, no. Each alarm trigger has an "optional trigger connection" that can write back to the controller. You would want to use the ACK connection. Whenever that alarm trigger is acknowledged (at that particular PanelView) the PanelView will send a non-zero value to the controller. Ex. writes 1 to the controller. You would need to setup the ACK for each of your alarm triggers, then have the controller do the logic if all of the alarms have been acknowledged. Those tag connections in the Alarm List that you found are read only; they are only used to change the display of the Alarm List. So, those will not help you in this case. Try it out just using memory tags in the PanelView and you'll figure out how it works.
  9. FactortyTalk Trend Issue

    (1) Make sure you have the {Stretcher}Pressure_Transducer tag added to the data log model (Connections tab of the trend) (2) Enable & select the Pressure_Trend model in the Startup settings of your project. In FTView Studio, the Startup settings are in the project explorer tree. (3) assign the data log to the trend, on the pens tab; as you have already done. It doesn't make sense, but you need to do all three to get the data log working.
  10. HMI PanelView Plus vs PanelView Plus 6

    PanelView Plus is the older hardware and supports up to version 5.x of the software. It is discontinued and no longer available for new sales. PanelView Plus 6 is newer and supports the latest version 8 of the software. PanelView Plus 7 just released this year and it also supports the latest version 8 of the software. The big difference in the PanelView Plus 6 is the extra memory and speed. If you had large projects, then you will notice screen changes are faster.
  11. PanelView Web Link

    You would have to experiment with the ME Program Launcher activeX control. Set that up to open your web browser (IE, Chrome, Firefox, ?) and use the command parameter for the web address. The exact syntax for the command parameter is what you'll have to figure out by testing it. Use a momentary push button to trigger the Program Launcher to open your web browser.
  12. FTView SE Client Display Changeover

    I would start with (2) first; change to widescreen displays. Then work on (1) as time goes on; update the screens per High Performance HMI Handbook. The FTView screen do not scale well. It is best to manually resize them in FTView Studio for the widescreen display. Going from a standard display (4:3 ratio) to a widescreen (16:9 ratio) always has problems for any HMI. Either you stretch out the graphics or you have blank spots on the ends (like your t.v. does for "old" movies and shows).
  13. Extreme Environment HMI

    Jeremy, what did you find out? Is there a good way to install an HMI into C1D2, outdoor and freezing temps?
  14. Multi language PV, selected language to PLC?

    np. Post back if you find any tips or gotchas.
  15. Multi language PV, selected language to PLC?

    There is an expression that will give you the name of the current language (string data type) CurrentLanguage( )Use a macro to copy that expression value to a string tag in the controller, process it there. How you trigger that macro could be done a few ways. Using the global connection "Remote Macro" is probably the easiest. Ex. when the current language is different than the last language run Macro1.