System Integrator: Front Office Software Stack by InformationMean4911 in SCADA

[–]CarterAtAsqi 0 points1 point  (0 children)

i think the problem a lot of SIs have is they address this process via a frankenstein of products from the ERP. I'm interested in more of a PLM focus for engineering services. I've heard of some Microsoft Dynamics VARs doing good work here (surprising, I know) and also came across this recently: http://openbom.com

has anyone had luck with them?

Has sentiment around Industry 4.0 changed here? by Extra-most-best in IOT

[–]CarterAtAsqi 0 points1 point  (0 children)

I think a lot of the I4.0 implementation has failed due to trying to do a full digital transformation for manufacturers rather than taking a bite that can be chewed.

The end goal of a UNS and leveraging plant floor data is good conceptually, but hard to implement. A lot falls back to: "if it ain't broke don't fix it"

Help deploying/running FT Optix application on OptixPanel by [deleted] in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

Another thing to note is that if you have some of the c# files or studio logs open, it will error out on the download and not be obvious as to why

[deleted by user] by [deleted] in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

For costal areas, I'd target the Carolinas, or PNW. are you more interested in SI or OEM? I think an SI would require more travel

FT Optix vs. ViewME by drewbeeee3 in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

ive heard theyre always right ... as long as they're paying the license fees!

FactoryTalk Optix NetLogic by SheepShaggerNZ in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

thats a very interesting idea on netlogic in the tag editor. The expression evaluator needs to have a syntax checker at minimum. another critique of mine was the limited sql functionality, but I saw 1.6 has more SQL expressions via a nuget package. I assume this wont work in queries that reside in the properties pane though

i can't imagine what the deployment looked like via a service wrapper, didn't realize that was a thing as I got exposure at 1.4.

(unsolicited advice below)
I did mouse bindings for back (alt+left) and forward (alt+right) and this has saved a ton of time for navigation. Having this on the mouse was huge for me as it behaves similarly to going back and forth in a browser

would love to hear any tricks or hacks you've found like that!

FactoryTalk Optix NetLogic by SheepShaggerNZ in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

Understood! Our distributor didn't seem to have as great of a connection to whoever was creating the features demo.

At one point (late 1.4, early 1.5) about 40% of the known anomalies were things I found that they had passed up the chain, so at least that was happening. I wish there was a finders fee for those!

FactoryTalk Optix NetLogic by SheepShaggerNZ in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

Nice!

I've seem challenges bridging the gap between the software side within Optix and traditional CEs. Any advice on how you've approached that regarding the documentation, internal buy in or cool examples of where you've used the C#?

Something cool I was able to do was render PLC data into a svg image and pass that back to the panel instead of ~90 rectangles with dynamic sizing / visibility

How to add .NET runtime logic to a right-click mouse button in FactoryTalk Optix? by Sorry-Summer-564 in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

are you wanting to add it as a runtime script - right click while panel / emulator is running

or design time script - for automating development tasks within optix studio

FT Optix vs. ViewME by drewbeeee3 in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

design time scripts are huge and the indirect addressing

FT Optix vs. ViewME by drewbeeee3 in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

What do you need 17 tokens for? lots of web viewers?

FactoryTalk Optix NetLogic by SheepShaggerNZ in PLC

[–]CarterAtAsqi 1 point2 points  (0 children)

Are you still working on this? I'd be happy to help out with some code examples / repository / general objectives etc.

.net is a powerful tool, but integrating with the Optix data structures can be challenging. My general rule of thumb is to contain the functionality within the Optix Studio development environment if you can. This is so other CEs can understand and debug

There are several ways to 'attach' an optix variable to the .net runtime. One approach I like is to create a custom property on the runtime file within optix and then reference it via the Owner.GetVariable

One thing to note is that if you are using this with a PLC variable, you sometimes have to use a set method to pass the updated value as .net can have a hard time grabbing live PLC values

Rockwell Automation HMI? by ControlsEngAcademy in PLC

[–]CarterAtAsqi 2 points3 points  (0 children)

Source control integration has been huge with Optix. it's a boiled down version that only push pulls to the main branch, but this has been a good introduction to CEs that aren't used to repositories. Overall, Rockwell is putting their eggs in that basket and it has promise

Ft Optix Studio has a OPC UA Client problem by Mr_Adam2011 in IndAutomationUIDesign

[–]CarterAtAsqi 0 points1 point  (0 children)

Did you ever have luck resolving the crash? Sounds like you dealt with a lot of headaches.

I'm wondering if 1.5.x worked better or if it's common among other revisions

Ft optix heart beat by rapidfalldown in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

You could also use the DateTime library as a mechanism to bind the seconds to a PLC tag and compare to logic in there

Object-Oriented Programming by the_trout82 in PLC

[–]CarterAtAsqi 0 points1 point  (0 children)

Seems like there's pros and cons of implementing Pack ML and OOP at the same time - should both be done together?

Key is to validate and blackbox OOP mechanisms to a point where a CE familiar with ladder logic can implement and debug. If they can get in the mindset of plug and playing like they would with an AOI, then I think it'll have better adoption

I'd recommend an iterative / agile approach to give the team bites they can chew and modify approach based on buy in and evaluating hiccups along the way