I see many different integrations for Nevion equipment - historically the current "Virtuoso" modular chassis has evolved from multiple hardware devices into a new unit that is preserving most of the TNS4200 or NX4600 API structures: how can I determine which DM protocol is most suitable for the functions on my device?
Would any of the NEVION Virtuoso integrations support DVEs in the near future?
All the drivers which are available can be searched on https://catalog.dataminer.services/ .
When selecting a specific driver there, you will find more information about that specific driver. In many cases the firmware will also be listed there.
If this information would not be sufficient to determine the driver you need, then you can always contact somebody here at Skyline. We can then check the device you have at hand, and see which driver can be used. In case we do not have one available of the shelf, one can be developed.
If DVEs would be a requirement, and would be beneficial for any of your Nevion Virtuoso integrations, then this can be made available in the driver.
Thanks for this feedback – I’m interested in drivers for “VIRTUOSO FA” and “VIRTUOSO MI”, as opposed to the older products NX4600 and TNS4200.
As for NX4600, from the driver info, DVEs seem to be supported – but is this currently implemented only for encoder & decoder cards? Or would we have the option to create DVEs also when a stack of TS switches is hosted in the chassis?
Hi Alberto. At the moment we already have support for Virtuoso MI, but not for FA yet. FA can be supported upon request either in a dedicated driver or in a generic Virtuoso Platform driver that supports both.
Our Nevion NX4600 offer includes only DVEs for encoders and decoders in range 1.1.4.x.
Thanks Ricardo – this clarifies
Marking this as solved – a general approach for these appliances has been defined in: https://community.dataminer.services/question/same-device-different-element-types-what-to-choose/
Getting back to this old thread as it seems two different protocols are kept in parallel – was there a fork at any point between the TNS4200 and the the NX4600 protocol?
I’ve found some “seamless switch” implementation in the TNS4200 protocol v.2.0.0.7 (originally, the probe device), yet most of the features for switching control have been improved in the NX4600 protocol (input selection based on labels rather than on numeric input IDs).
Also, what’s the current limitation on implementing the DVE option also for switch modules? This is not available yet in any of the integrations.