rdrast said:I have installations of FactoryTalk SE 5.0, with a couple patches. I'm not seeing any issues with SE, or communications. There is however a problem with the VBA engine, you cannot pass parameters across display boundries, they get dropped. That seems a bug in VBA though.
Then again, we here haven't had much trouble with any installations of View SE, all the way back to Vers. 3.1.
A big problem with SE, is that is is NOT easy to just load and go. There are lots of things that need to be understood about the software itself, operating system compatability, patch levels, access rights, etc.
It's unfortunate, but there are probably more incorrect installations of RSView/FTView SE out there then correct ones.
Amazingmg said:The "tagless" system is the way to go and I love it. The only tags I had to create were for legacy PLC interfaces.
Amazingmg said:Oh, btw, the speed of the "tagless" system is one of the biggest selling points (or so they say), so if you are using tags for everything.....you are losing some of the benefit.
rdrast said:One other things I do, is generally, I try to develop at least my base screens in RSView ME, and then import them into SE. That way, I have a functional version ready to go if I toss a Panelview in somewhere (since you cannot import SE displays to ME).
rdrast said:Speed? No speed differences, the dynamic request arrays to Linx, Linx Enterprise are built much faster than either data server can actually respond, so the extra level of indirection doesn't hurt.
Also, you lose the ability to enforce limits, or do scaling (on numeric references),
...and in quite a few cases, leaving View to decide on the numeric representation doesn't work... Defining a tag lets you explicitly have a value interpreted as a LONG, or FLOAT, or INT, etc.
Re-use... I have many many screens that are common, even if used on very different overall machines. I just export the tag dictionary to Excel, do a global search and replace on "[Machine_1]" changing it to [Machine_2].
Re-import tags with update, Done.
One other things I do, is generally, I try to develop at least my base screens in RSView ME, and then import them into SE. That way, I have a functional version ready to go if I toss a Panelview in somewhere (since you cannot import SE displays to ME).