rmclark

I'm working with two WATCHPAX ver 1. Which want to be included on a network with other Watchout Displays and lighting control all in the 10.10.10.x domain. When I use my laptop (with parallels) I have no problem "changing" the IP to 10.10.10.x domain on each watchpax and connecting to them from the Virtual Machine Windows 7 Professional system. I have the mac side looking for DHCP (and it sees the "native" address of each of the watchpax) and on my windows side i have a static IP set at 10.10.10.x and it connects sees and connects to the newly set 10.10.10.x IP'S on each watchpax. Additionally other controls can be sent and received via Artnet and all is well. Until. I remove my computer as the production machine and place in a iMac with Bootcamp (running Windows 7 enterprise). It continues to the see the watchpax in the application (green ok when checking the IP), but when you go online to transfer content the PAX (both of them) "freeze' and claim the network connection is lost. Trying to use watchout VNC at this point usually doesn't work either (remote connection lost or some such) so you cycle the power. you open everything up again and it appears (offline) that it's all going to work. You can remote manage them through VNC until you try to go online and again and back to the paragraph above... I'm wondering if my laptop config is actually supplying a DHCP server and that is somehow allowing the win 7 static Ip to operate flawlessly. However in Bootcamp... it's having some sort of conflict between the "native IP" of the watchpax and the newly assigned IP. I set Win 7 on this macine to accept multiple networks. DHCP as primary and an alternate in the 10.10.10.x domain (and of course watchout seems happy offline..) but it still crashes when going online. Is my only choice to reset to the native IP and then ask all the other departments to do the same? Am I missing something obvious? Is there additional networking features I can add to make the Bootcamp Win 7 behave? Is it a difference of Enterprise vs Professional ( I wouldn't think so... but.) I turn to the good folks of the forum for advice and guidance. Thank you!

that's the kind of thing that would be really useful posted somewhere here.

it's strange. I get a serial 'handshake' to the camera and it locks up from external control. When i send the serial commands through watchout no camera response... (sony 990). So i know it's talking it to it, but somehow it's not receiving the commands... I was hoping i can send the moxa a serial command directly (outside of watchout, say through terminal or something...) but i haven't figured out how to do that either.... M

is there an instruction on how to setup watchout for these devices? I'm trying to use a moxa 5110 to send serial commands to a camera... I can see the moxa device on the network, but i'm not sure how to send the serial command from watchout through the moxa to the camera. Do you have any advice that you can share please?