Advice and thoughts of the communitity would be welcome. The view of anybody who has used both would be appreciated.
I have personally only used the VIM2.
With the advent of the EIOC device from version 13.3.1, is it still advisable to specify new projects with the VIM2 card.
Or should we be specifying the EIOC device?What is the Emerson recommendation?In particular:
Thanks,
Neil.
Here's a suggested process to follow for using EIOC vs VIM2
Thanks Petroban and Matt I had performed a trial config of EIOC and I did like the ability to configure signals as per the profibus signal approach. I also like the single DV Explorer configuration of EIOC vs the dual VIMNET explorer and DV Explorer configuation required with VIM2 and serial card emulation (that is quite clunky, but appreciate the reason before Mynah were brought under Emerson ownership). Will the need for that ever be replaced with native DV Explorer config for VIM2? I’m thinking system lifecycle savings over 15 years, vs the double cost of EIOC (£4-5k more than VIM2) Unless I’m mistaken, the quoted UK cost is nearer SQ controller cost not SX which is approx 2 x SQ here in UK at the moment. Still a few other questions I posed not answered, longevity of VIM2 and can EIOC/VIM2 only do one Ethernet protocol per application? Thanks. Neil
In reply to Matt Stoner:
In reply to Chelsea Sanborn:
Good question Chelsea. It does say this in the datasheet, But I don’t see why. The EIOC seems to be in the IO Network, does this therefore mean that it’s DSTs can be used in the same way as CIOC but other controllers (limit of 4 controllers per CIOC) If this were the case why not for EMs Batch and SFCs if the DST are referenced by modules in the controllers executing the EMs Batch SFCs. I realise VIM2 is close coupled to one controller as it emulates serial IO signals of that controller. If my assumption about EIOC DSTs being accessible to any controller as per CIOC the EIOC is a solution with much more flexibility even in the EMs SFC and Batch environment .
Hi Matt, I should have read the datasheet Petroban posted From that “Batch components such as SFCs and PLMs are not supported in the EIOC. Extensive external referencing to the EIOC for applications such as VFD control and Batch control is not advised. See the PDS for the VIM2 which supports those applications.” But how is CIOC comms any different to this. Are you saying that EIOC DSTs cannot be read/written directly from other controllers on the network.(Perhaps this is the key point). But obviously you could put intermediate mapping modules into the EIOC and take the external reference hit (perhaps not a good idea) Perhaps I’m beginning to realise that Controller to CIOC comms has a higher quality of service (QoS) than external reference comms?
In reply to petroban:
In reply to IntuitiveNeil:
Andre Dicaire
In reply to Andre Dicaire:
In reply to gamella: