by the way, have you ever connected ignition to S7-1500. I am having problems addressing %MD4220 real data type, I cannot find the right way to address it. MD is real.
Thanks
Try [DeviceName]MREAL4220
1 Like
I've tried the way you suggested, I found my issues, it was not addressing issue. I actually changed attribute of all OBs and FBs De-selected "Optimized block access" for all of them.
I thought It was addressing issue. It was driving me crazy.
Thank you for reply.
Just a quick note, I wanted to Emulate a project that was commissioned with an L72. I converted to Emulate and Ignition recognized the connection and I could browse all tags, but all tags were BAD quality. The CIP connection size under device connection was set to 4000. Emulate doesn't appear to like this. I set back to the default of 500 and the tags started reading. Posting in case this will be helpful for someone else.
8 Likes
Not sure if you know about this trick, but you can export an L8x controller project to L5K format, open the file in a text editor, and replace the controller section with the corresponding controller information from an L7x L5K export. This allows you to use it with Emulate and bypass the forced Echo upgrade
5 Likes
Echo is so much nicer than Emulate though. I just wish it was part of the toolkit, but I think RA knows the majority of the users will be integrators and they'd make virtually no money on it if they included it in the toolkit.
Yeah id love to use it if they included it with the toolkit, but its just not worth paying extra for at this point
The problem with Echo is it will not support older Logix versions
I don't see that as a problem. If you need an older firmware you use Emulator, newer you use Echo. Maybe I'm just fortunate enough working with new projects that are always using new hardware so never have to deal with older hardware besides replacing it.
1 Like