bitfocus / companion-module-generic-swp08

Bitfocus Companion Module for Probel SW P 08 General Remote Control Protocol
https://wwwapps.grassvalley.com/docs/Manuals/sam/Protocols%20and%20MIBs/Router%20Control%20Protocols%20SW-P-88%20Iss
MIT License
6 stars 3 forks source link

Conflict with SWP08 Lawo VSM #16

Closed CharlesSicard closed 1 year ago

CharlesSicard commented 1 year ago

Hi,

I've been trying to implement a connectivity between Companion and VSM. It works fine thru the Ember connection, but I would like to also use SW-P 08 protocol. This seems to be the same problem as issue #13. I'm setting up a SW P-08 Connection in Companion, a Inbound TCP SWP08 in Lawo VSM, defined has a controller for a virtual matrix, everything is in the green, and marked as conneted. However I cannont manage to make a crosspoint. When I send one, i have the following in my logs in Companion :

23.03.20 17:48:11 instance(SW-P-08 VSM A): 8,1,247 23.03.20 17:48:11 instance(SW-P-08 VSM A): Unknown response code 8 23.03.20 17:48:11 instance(SW-P-08 VSM A): 8,1,247,8,1,248 23.03.20 17:48:11 instance(SW-P-08 VSM A): Unknown response code 8 23.03.20 17:48:10 instance(SW-P-08 VSM A): Unable to verify list of implemented commands 23.03.20 17:48:10 instance(SW-P-08 VSM A): Crosspoint 1>1 level 1 23.03.20 17:48:00 instance(SW-P-08 VSM A): 8,1,247 23.03.20 17:48:00 instance(SW-P-08 VSM A): Unknown response code 8 23.03.20 17:48:00 instance(SW-P-08 VSM A): 8,1,247,8,1,248

Seems like the two devices don't speak the same language.

On the VSM side, I get Detected possible communication problem... From time to time

Any idea ? As anyone had the same issue ? I have also tried to emulate a SWP08 device using vsmGadgetServer, with the same result.

Thanks in advance

daniep01 commented 1 year ago

Have you tried turning off 'Request supported commands on connection' in the module settings? Unfortunately I don't have any Lavo equipment to test with.

CharlesSicard commented 1 year ago

Hi Daniep01, thanks for the quick reply. You are right, it works fine now. I feel very stupid not reading the comment "Try disabling this feature if you encounter problems"

I'm closing this thread