วีดีโอ

I restored the file, looks like it was accidently deleted. Just in case here is the link: www.mediafire.com/file_premium/i2bgerwzq6nnurs/11x17_Green_Dolphin_Coffee_Titleblock.pptx/file

Don't know, but the Optix help file states FactoryTalk® Optix is compliant with MQTT version 5.0, with client supporting publisher/subscriber functionality. There is also an example of the payload structure - search for MQTT under the help center. MQTT section is under Creating Projects/Database section.

Looks like that is not part of the filter in the v1.5 release. I do see the group name appears in the "Name" field of the alarm summary, and you can sort on that column.

Currently FT Optix supports IP Address Swapping only for ControlLogix redundancy. There is an expected 7 second bump with Optix during switchover. Reference Chapter 7 of the ControlLogix redundancy manual for more info on IP Address Swapping - literature.rockwellautomation.com/idc/groups/literature/documents/um/1756-um015_-en-p.pdf

Thanks - glad these videos have been helpful... you want to use a single trend pop-up window that would pass a different tag into the trend each time?

@@wawelk Pretty much. What I currently do in View SE is use VBA to load pens into the trend display. This was done to avoid making 700+ trend displays. I'm attempting to do something similar in Optix by loading the Model dynamically, but I haven't had much luck doing so.

Sorry for the slow response - I think this should be possible by creating a panel with the trend object. Then add an alias to that panel. The catch is that you may need to create a "model" with variables and assign those variables to the controller variables you want to trend (if your data it not in a UDT (type) already).

After trying some things out, I see that it is fairly easy to use the Alias to pass in values to a Dialog Box with a Trend Object on it - problem is that this seems to work only for real time data, I have not been able to pass the historical data into a popup with an Alias, it will always grab the real time data.

Hi, I don't know if it's still relevant but the "modal" dialog window property controls this. If you want to be able to move the dialog box then also set "move target" to "self"

@@emiletetrt Thanks for your help, I didn't see this setting

Sure, Blue and Blue/White stripe would be following NFPA 79... but all I had was red and black when wiring the demo.

After working in optix for a while I think that screens just have more customization options (Background color,border color, border thickness). I see no clear advantage to using one over the other most of the time and have started just making all my HMI needs with a panel inside ScaleLayout instead so it can scale if I drag the window size up or down. It seems also that a Panelloader object will eat just about any container type and not just panels, so I don't see the big difference. Reading some documentation a screen seems to just be a subtype of a panel. The documentation also states the following for each: Panel: "Simple objects container. Display the graphical objects it contains and that can be a selectable area" Screen: "Graphical container, typically used to create HMI pages"

You will need v1.4 or higher of Optix Studio, and choose the Micro Controller Driver, it supports the Micro800 and MicroLogix 1400 Ethernet communications.

@@wawelk thankyou for your support but FT unable to import the tags

Are you trying to import controller/global scope tags, or local scope tags? It will only work with controller scope tags.

You will need v1.4 or higher of Optix Studio, and choose the Micro Controller Driver, it supports the Micro800 and MicroLogix 1400 Ethernet communications.

I'll have to look into that one, as I don't know - seems like something such as auto-scaling would be needed... but this Rockwell knowledge base article seems to confirm what you are having to do: rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1140824/

This KB article on how to automatically scale graphic objects when runtime is resized may be something to try: rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1139478/

@CameronNovak-c4g - this video from Rockwell on responsive design may also be helpful when running on different devices with varying screen resolutions. th-cam.com/video/EsKS-rXvXY4/w-d-xo.htmlsi=KKdbsq8OUJKVyP5L

@@wawelk Wayne thanks for the response, looking at a few github repositories, I settled on a single panel loader. When changing the panel if the session is a web session it loads a larger version of a screen (larger fonts, UI layout changes for web, etc) and if its not a web session it loads a duplicated panel/screen that is more suited for a small 7 inch Optix panel. probably not very efficient and heavily reliant on OOP to not have to duplicate every change, but it solves my problem. the new Grid layout and scale layout with font scaling has been helpful too.

Thanks for sharing the solution you found. I'll have to test that out as well.

Thank you, I'm glad to hear they have been helpful to you.

Thanks Marcus! I appreciate the feedback.

Thanks! Glad these videos were helpful to you.

I've had that issue before, there is a Rockwell Knowledge Base article that addresses it. Basically you will need to reduce the number of cores that your CPU is using: rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1091976/

@@wawelk Thanks for your prompt reply. May I know why "Synchronize the module configuration" button is not active for my CCW application with standard version?

If the Micro800 simulator is powered on (power light is green) it will be greyed out. You need to make configuration changes before it is power on.

Hey Zachary, that comes straight from the Optix help center where it provides Logix controller support for firmware versions 32 and later: www.rockwellautomation.com/en-us/docs/factorytalk-optix/1-00/contents-ditamap/using-the-software/communication-driver/communication-drivers-overview/ra-ethernet-ip-driver.html

Thank you for sharing that. I can confirm that online tag importing with version 30 has no issues.

Thanks, that’s good to know.

Support down to version 20 will be coming soon. It may be in the 1.4 release hopefully next week. We shall wait and see.

That's good! I had not seen anything on that, but makes sense, it probably just needed to be tested and validated back to V20 by Rockwell.

I don't see why not - it let's me add multiple aliases in the dialog's properties.

It does let you add multiple aliases to the dialog. But when you create the button click event I can’t see how to address all of the aliases. It only lets me do one!

Also, thanks for the reply!

Not sure, I'll have to give it a try...

@@wawelk I figured it out. It doesn't list the NodeID's separately in the button click event. You have to click the invisible, until you hover over it, edit button and then it shows all the aliases defined on the dialog you're trying to open.

Thanks for the comment - I was able to upload a video that shows the steps to create the Studio 5000 project and the Factory I/O scene used - th-cam.com/video/N70_RcFYpuA/w-d-xo.html

You need to enable the "Show feature previews" under FactoryTalk Optix Studio Options. Also you will need to verify that the "Advanced Mode" is checked.

@@wawelk Thanks a lot!

Yes, it is easy to customize the color of the background and objects. Images can be added by just dragging the image file from your desktop to the Optix Studio screen.

Rockwell Automation offers training workstations, you will need to work with your local Rockwell authorized distributor for more information: www.rockwellautomation.com/en-us/support/workforce-development-training/workstations.html

Thank you for your reply. I contacted a distributor but he advised to contact few other integrators. May I know what was the cost for the one you displayed in your video? Thank you

@eugeniugangan7402 - With the FactoryTalk Optix V1.4 release (coming soon), Rockwell will introduce several faceplate device libraries for Optix. These will be prebuilt faceplates similar to what is available for the PanelView Plus and View SE. Rockwell will continue to build more faceplate libraries throughout the year.

Use the Text Box base control object - this lets you click on it and enter a value during runtime.

Are you using the base controls switch? And what version of Optix Studio are you using. I have V1.3.0.968 and the base controls switch does show the value of the BOOL tag when I force the tag on/off in the PLC. It also lets me change the value of that same BOOL tag in the PLC from Optix. And it is retaining the value when I switch from between panels. I know in the previous version I saw the switch not retain when switching between panels - it may have been resolved in this latest version.

@@wawelk Hi Thanks for your videos, that helps me a lot. Can you please explain how to create a drop down list based on a string array from PLC. I have array of 32 string and I need to display them when I click on drop down/button and send a index number back to PLC so the PLC know which one I selected.

@jaconais - view this video to see how to create a popup with an alias to pass parameters into it. th-cam.com/video/BKL3RLka7Wc/w-d-xo.html

I don't have a video showing the details (will have to work on that), but there is an example project available on Rockwell's GitHub. There are two examples in that project where the "motor widget" can be opened like a popup window. github.com/FactoryTalk-Optix/Training_UserInterfaceWithAlias

View this video to see how to create a popup with an alias to pass parameters into it. th-cam.com/video/BKL3RLka7Wc/w-d-xo.html

I posted this video with the details. th-cam.com/video/UKUBQ2-sX24/w-d-xo.html Basically you need V1.3 of Optix Studio and enable Feature Previews in FactoryTalk Optix settings.

Yes, you can reference extended tag properties. For the tag's description you will reference TagName.@Description. If using FactoryTalk View SIte Edition (SE) you will need to have Version 9 or higher for this to work. For FactoryTalk Optix, referencing extended tag properties is a "feature preview" or beta release in Version 1.3.

Not sure - the only mouse event that changes just a "single bit" is the variable command "toggle". The mousedown event/mouseup event seems similar to the Siemens SetBit and ResetBit.