User avatar
AllonisDave
Founder
Founder
Posts: 11395
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Octava Device Driver

Thu Sep 20, 2012 4:56 pm

A driver that supports the full line of Octava switches has been released. It is a member of the Switching family and Command Builder will have the command set.

We do not have any way of testing this driver so if you have one give it a go and let us know how it works. Currently the driver will not produce any status variables because the protocol documents do not describe what gets sent back from the switches. Any response from the switch should get logged and all I will need to see the Octava driver event log so I can translate the responses to meaningful variables.

freak69
Senior Member
Senior Member
Posts: 111
Joined: Sun Mar 25, 2007 4:00 pm
Contact: Send private message

Re: Octava Device Driver

Tue Oct 02, 2012 4:18 pm

Hi,

Been away for a while, just logged on again and I see you have been busy - great news on the octava and also the currentcost, that's really going to help.

I cant test this Octava at the weekend when I get it hooked up via serial.
I'll test the currentcost too.

Paul

freak69
Senior Member
Senior Member
Posts: 111
Joined: Sun Mar 25, 2007 4:00 pm
Contact: Send private message

Re: Octava Device Driver

Sat Oct 06, 2012 1:17 pm

HI,

Not working too well I'm afraid. On the surface, it doesnt appear to do anything, however portmon reveals a different side. Commands are being sent, but don't appear to be doing anything.

I also have the Octava windows gui running and that works fine when connected. The reply to all commands seems to be a status message (long hex string) - the same as the status request itself.

I enclose the output from portmon in the hope that its useful. the octava.log file is with their working gui. I systematically did set output 1,2,3,4 to input 1'

In octata-ml.log, this is the output from when ML starts and I did a switch~input2~output2 command (nothing happened).

Let me know if you need any more information
Paul
Attachments
octava-ml.log
Octave driver
(52.31 KiB) Downloaded 30 times
octava.log
Octava GUI only
(3.56 KiB) Downloaded 28 times

User avatar
AllonisDave
Founder
Founder
Posts: 11395
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: Octava Device Driver

Sat Oct 06, 2012 2:01 pm

Yes do the same test using the same commands. Just switch input 2 to output 2 using both programs. Then it is a lot easier to compare what the two programs sent and received.

freak69
Senior Member
Senior Member
Posts: 111
Joined: Sun Mar 25, 2007 4:00 pm
Contact: Send private message

Re: Octava Device Driver

Wed Oct 10, 2012 3:56 pm

HI,

Dont remember seeing this the other day, but it seems that the status command is issuing the correct command and gettng the response indicated in the logs. The swctch command is not hoswver sending the right output. Whatever switch command I do, always sends the same incorrect message to the octava - 02 32 00 00 03. The octava doesnt do anything as this is an incorrect msg. It just replys with a status output.

10/10/2012 20:20:58 ProcessCommand Cmd=[1~Status] Client=[]
10/10/2012 20:20:58 SendCommand TX: SWITCHING1| 02 30 30 31 03
10/10/2012 20:21:57 ProcessCommand Cmd=[1~Switch~Input1~Output2] Client=[MyClient1]
10/10/2012 20:21:57 SendCommand TX: SWITCHING1| 02 32 00 00 03
10/10/2012 20:44:00 ProcessCommand Cmd=[1~Switch~Input2~Output2] Client=[MyClient1]
10/10/2012 20:44:00 SendCommand TX: SWITCHING1| 02 32 00 00 03
10/10/2012 20:44:13 ProcessCommand Cmd=[1~Switch~Input1~Output1] Client=[MyClient1]
10/10/2012 20:44:13 SendCommand TX: SWITCHING1| 02 32 00 00 03
10/10/2012 20:45:22 ProcessCommand Cmd=[1~Switch~Input2~Output2] Client=[MyClient1]
10/10/2012 20:45:22 SendCommand TX: SWITCHING1| 02 32 00 00 03
10/10/2012 20:45:26 ProcessCommand Cmd=[1~Switch~Input2~Output1] Client=[MyClient1]
10/10/2012 20:45:26 SendCommand TX: SWITCHING1| 02 32 00 00 03
10/10/2012 20:45:35 ProcessCommand Cmd=[1~Switch~Input2~Output3] Client=[MyClient1]
10/10/2012 20:45:35 SendCommand TX: SWITCHING1| 02 32 00 00 03
10/10/2012 20:45:40 ProcessCommand Cmd=[1~Switch~Input2~Output4] Client=[MyClient1]
10/10/2012 20:45:40 SendCommand TX: SWITCHING1| 02 32 00 00 03
10/10/2012 20:45:49 ProcessCommand Cmd=[1~Status] Client=[MyClient1]
10/10/2012 20:45:49 SendCommand TX: SWITCHING1| 02 30 30 31 03
10/10/2012 20:46:10 ProcessCommand Cmd=[1~Switch~Input1~Output1] Client=[MyClient1]
10/10/2012 20:46:10 SendCommand TX: SWITCHING1| 02 32 00 00 03

I also enclose 2 more log files. I started the relevant app (which did a status msg first) and then did the equivilant of Switching|1~Switch~Input1~Output2

Paul
Attachments
octava-ml.log
(52.23 KiB) Downloaded 22 times
octava.log
(1.74 KiB) Downloaded 23 times

User avatar
AllonisDave
Founder
Founder
Posts: 11395
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: Octava Device Driver

Wed Oct 10, 2012 6:32 pm

I think you need to lose the input and output words. The switching command should be

Switching|1~Switch~1~1

not

Switching|1~Switch~Input1~Output1

freak69
Senior Member
Senior Member
Posts: 111
Joined: Sun Mar 25, 2007 4:00 pm
Contact: Send private message

Re: Octava Device Driver

Fri Oct 19, 2012 4:36 pm

OK, I dont know how I got that one wrong (twice!) I shoud know better by now.
Anyway, I can report the basic switching works fine and I'm currently speaking to Octava with regards to the status code, although Ive managed to reverse engineer a bit of it. I have a hunch that the status code is slightly different depending on your firmware and model number, but I'm hoping they can confirm.

freak69
Senior Member
Senior Member
Posts: 111
Joined: Sun Mar 25, 2007 4:00 pm
Contact: Send private message

Re: Octava Device Driver

Sun Nov 04, 2012 12:52 pm

Hi,

As an update, I've been speaking to Octava support with regards to the feedback message. I did get a reply back from them with regards to my unit, which is an older model (at least 18 months old). It seems the feedback code for older units like mine is not consistent, there is however a software update that I'm trying to get hold of that uses their new standard.

"The feedback code- on previous versions, we had not anticipated that users would be using the feedback. We were using the feedback strictly for our internal development of a windows program ( to control the matrix) https://octavainc.com/faq.htm#RS232control I am thinking, that if you are indeed going to write feedback code for drivers, then it makes sense to use the New code.

I have attached the latest documentation they have sent me which includes details of the feedback code. I am now trying to get a software update for my system so I can use this code.

Paul

freak69
Senior Member
Senior Member
Posts: 111
Joined: Sun Mar 25, 2007 4:00 pm
Contact: Send private message

Re: Octava Device Driver

Sun Nov 04, 2012 12:55 pm

Didn't seem to like the xlsx file. Converted to xls and trying again.
Attachments
Octava RS232 Command.xls
(84 KiB) Downloaded 30 times

freak69
Senior Member
Senior Member
Posts: 111
Joined: Sun Mar 25, 2007 4:00 pm
Contact: Send private message

Re: Octava Device Driver

Sat Nov 10, 2012 9:15 am

HI,

I have now updated my (slightly older) matrix with the latest firmware that has the standard feedback messages and I can confirm it is as per the new spreadsheet.

For example, after switch on, I issued a status command
Switching|1~Status
which sent

02 30 30 31 03

and received

02 31 31 31 31 4E 4E 4E 4E 31 31 30 30 31 4E 31 4E 4E 02 0A 0D
which equates to STX 1111NNNN11991N1NN ETX
(STX/ETX = 0x02)

Which matches perfectly with the supplied feedback. Would it be possible to provide this feedback into standard ML variables ?

Thanks
Paul

User avatar
AllonisDave
Founder
Founder
Posts: 11395
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: Octava Device Driver

Sat Nov 10, 2012 1:27 pm

Yes, I have plans to add that feedback into the driver. It should happen within the next few days.

waszaa
Newbie
Newbie
Posts: 24
Joined: Wed Oct 12, 2005 6:32 am
Location: Manchester UK
Contact: Send private message

Re: Octava Device Driver

Fri Dec 28, 2012 3:30 pm

Hi just testing out this driver on a new HDMXA71 and wondered if the feedback to ML variables had been implemented yet as i don't seem to be getting any?

Also getting an error every 2 hours in the driver Log- TimerResponse - Error at TimerResponse_Tick at line #719 - Queue empty.
thanks

Mike

User avatar
AllonisDave
Founder
Founder
Posts: 11395
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: Octava Device Driver

Sun Dec 30, 2012 11:55 am

I just uploaded a version of the Octava device driver and I need someone to test it. Could you issue some commands with logging turned on and email me the event log. I need to see if it is capturing the feedback and what it is. There are no server variables being created yet.

User avatar
AllonisDave
Founder
Founder
Posts: 11395
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: Octava Device Driver

Sun Dec 30, 2012 3:12 pm

The Octava device driver has now been updated to process the feedback data. There should be a series of "Switching_" server variables being created reflecting the state of the switch.

waszaa
Newbie
Newbie
Posts: 24
Joined: Wed Oct 12, 2005 6:32 am
Location: Manchester UK
Contact: Send private message

Re: Octava Device Driver

Mon Dec 31, 2012 12:59 pm

Yep the feedback variables are working fine now!

Noted one thing though if the switch is off it sends a message every two hours saying command invalid - one letter on each variable.

Response RX: 0A 0D 02 3F 69 6E 76 61 6C 69 64 3F 63 6F 6D 6D 61 6E 64 3F 03
Attachments
OctavaVariables.pdf
(39.44 KiB) Downloaded 29 times

Return to “MLServer 4 Device Drivers”

Who is online

Users browsing this forum: No registered users and 1 guest