3.7 Output Controll...
 
Notifications
Clear all

3.7 Output Controllers

50 Posts
5 Users
0 Reactions
16 K Views
Posts: 77
Topic starter
(@dononeil)
Estimable Member
Joined: 18 years ago
JCB wrote:
I can try to build it for you. May not get to it for a couple days.

That would be awesome!! I'll test it as soon as I get it from you. Thanks so much!!


Reply
Posts: 232
 JCB
(@jcb)
Reputable Member
Joined: 17 years ago

Sorry it took me so long to get these built, I have been fighting an illness. Copy these into the Vixen folder with all the other DLLs. These should work with the latest version of Vixen 3.10u1. We updated Vixen from .NET 4.X to .NET 6 last year. This required some changes to the assembly names and the loading scheme. These two changes are probably why the older versions of the controller no longer work.

Dropbox Logo Download (Module.Controller.ElexolEtherIO.dll)

Dropbox Logo Download (Module.Controller.ElexolUSBIO.dll)


Reply
Posts: 77
Topic starter
(@dononeil)
Estimable Member
Joined: 18 years ago

Thanks so much!!! I'll test it out this week and report back, I really appreciate it!


Reply
Posts: 77
Topic starter
(@dononeil)
Estimable Member
Joined: 18 years ago

I just tried to test it and it doesn't seem to be working. I've installed the latest version on Windows 10, and created a simple patch from 24 channels to the 24 outputs, and created a simple timed sequence that steps through the relays turning them on, but nothing happens. Vixen 2.1 still can control the board, so I know it's not the issue.


Reply
Posts: 77
Topic starter
(@dononeil)
Estimable Member
Joined: 18 years ago

I also confirmed that v3.4 still works with the same simple patch and timed sequence, so something must be amiss with the new build.


Reply
Posts: 77
Topic starter
(@dononeil)
Estimable Member
Joined: 18 years ago
JCB wrote:
Sorry it took me so long to get these built, I have been fighting an illness. Copy these into the Vixen folder with all the other DLLs. These should work with the latest version of Vixen 3.10u1. We updated Vixen from .NET 4.X to .NET 6 last year. This required some changes to the assembly names and the loading scheme. These two changes are probably why the older versions of the controller no longer work.

Dropbox Logo Download (Module.Controller.ElexolEtherIO.dll)

Dropbox Logo Download (Module.Controller.ElexolUSBIO.dll)

I just tried to test it and it doesn't seem to be working. I've installed the latest version on Windows 10, and created a simple patch from 24 channels to the 24 outputs, and created a simple timed sequence that steps through the relays turning them on, but nothing happens. Vixen 2.1 still can control the board, so I know it's not the issue. I also confirmed that v3.4 still works with the same simple patch and timed sequence, so something must be amiss with the new build.


Reply
Posts: 77
Topic starter
(@dononeil)
Estimable Member
Joined: 18 years ago
dononeil wrote:
I just tried to test it and it doesn't seem to be working. I've installed the latest version on Windows 10, and created a simple patch from 24 channels to the 24 outputs, and created a simple timed sequence that steps through the relays turning them on, but nothing happens. Vixen 2.1 still can control the board, so I know it's not the issue. I also confirmed that v3.4 still works with the same simple patch and timed sequence, so something must be amiss with the new build.
JCB wrote:
Sorry it took me so long to get these built, I have been fighting an illness. Copy these into the Vixen folder with all the other DLLs. These should work with the latest version of Vixen 3.10u1. We updated Vixen from .NET 4.X to .NET 6 last year. This required some changes to the assembly names and the loading scheme. These two changes are probably why the older versions of the controller no longer work.

Dropbox Logo Download (Module.Controller.ElexolEtherIO.dll)

Dropbox Logo Download (Module.Controller.ElexolUSBIO.dll)

Some follow up info.... I ran a pcap on Vixen 3.4/3.7u4 vs 3.10u1....
As expected, once set up in the controller mapping, 3.4 & 3.7u4 continually talk to the device but 3.10u1 only talks when you press the test button. And when you do, the test message is quite strange with a 'connection successful', but the big red X. Pcap's attached.

connection message

Reply
Posts: 232
 JCB
(@jcb)
Reputable Member
Joined: 17 years ago

Anything of interest in your Vixen logs? Should be located at: \Documents\Vixen 3\logs


Reply
Posts: 77
Topic starter
(@dononeil)
Estimable Member
Joined: 18 years ago

Here's the clean output from the Application.Error.log from just a quick test run of 3.10:

06/02/2024 21:05:29.489 [Vixen.IO.Xml.Serializer.XmlModuleDataModelSerializer] Error when serializing data model of type ElexolEtherIOData System.Runtime.Serialization.InvalidDataContractException: Type 'System.Net.IPAddress' cannot be serialized. Consider marking it with the DataContractAttribute attribute, and marking all of its members you want serialized with the DataMemberAttribute attribute. Alternatively, you can ensure that the type is public and has a parameterless constructor - all public members of the type will then be serialized, and no attributes will be required.
at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.ThrowInvalidDataContractException(String message, Type type)
at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.CreateDataContract(Type type)
at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.CreateDataContract(Int32 id, RuntimeTypeHandle typeHandle, Type type)
at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.GetDataContractSkipValidation(Int32 id, RuntimeTypeHandle typeHandle, Type type)
at System.Runtime.Serialization.XmlObjectSerializerContext.GetDataContract(Int32 id, RuntimeTypeHandle typeHandle)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
at WriteElexolEtherIODataToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , ClassDataContract )
at System.Runtime.Serialization.ClassDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.WriteDataContractValue(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithoutXsiType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
at System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.DataContractSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.WriteObject(XmlDictionaryWriter writer, Object graph)
at System.Runtime.Serialization.XmlObjectSerializer.WriteObject(Stream stream, Object graph)
at Vixen.IO.Xml.Serializer.XmlModuleDataModelSerializer._SerializeDataModel(IModuleDataModel value) in D:\a\Vixen\Vixen\src\Vixen.Core\IO\Xml\Serializer\XmlModuleDataModelSerializer.cs:line 31 at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.ThrowInvalidDataContractException(String message, Type type)
at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.CreateDataContract(Type type)
at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.CreateDataContract(Int32 id, RuntimeTypeHandle typeHandle, Type type)
at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.GetDataContractSkipValidation(Int32 id, RuntimeTypeHandle typeHandle, Type type)
at System.Runtime.Serialization.XmlObjectSerializerContext.GetDataContract(Int32 id, RuntimeTypeHandle typeHandle)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
at WriteElexolEtherIODataToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , ClassDataContract )
at System.Runtime.Serialization.ClassDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.WriteDataContractValue(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithoutXsiType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
at System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.DataContractSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.WriteObject(XmlDictionaryWriter writer, Object graph)
at System.Runtime.Serialization.XmlObjectSerializer.WriteObject(Stream stream, Object graph)
at Vixen.IO.Xml.Serializer.XmlModuleDataModelSerializer._SerializeDataModel(IModuleDataModel value) in D:\a\Vixen\Vixen\src\Vixen.Core\IO\Xml\Serializer\XmlModuleDataModelSerializer.cs:line 31


Reply
Posts: 232
 JCB
(@jcb)
Reputable Member
Joined: 17 years ago

I made a couple of changes. Can you try this assembly?

Dropbox Logo Download (Module.Controller.ElexolEtherIO.dll)


Reply
Page 2 / 5
Share: