Bug IN GC-100 Plugin

Circe640 · Post by **Circe640** » Sun Oct 10, 2004 4:38 pm

I beleive I have found a problem in the GC-100 plugin. I am using Xantech double unit mini-mouse emitters. I started off by testing 1 double cable directly from the GC-100. Works perfectly! Then I started setting up with 5 double emitter cables through a Xantech 791-44 connecting block using the GC-CGX adapter cable. Again everything is working so far. During testing I then found that my Pioneer 563 DVD/DVD-A/SACD player uses the same remote codes as my Pioneer DVL-909 LD/DVD Combi player. Whoops!! Okay no problem, move the emitter cable for the 909 off the Xantech block and directly onto port 2 of the GC-100. Went and changed the IR codes for the 909 to IR port 2 on the GC-100. No go!!! Same thing for port 3. It looks like although you can configure port 2 or port 3 in the IR codes with the GC-100, the plugin does not do anything with that info to route to the 2nd or 3rd IR ports! HEELLPPP!

Post by **ScottBot** » Sun Oct 10, 2004 5:26 pm

It looks like although you can configure port 2 or port 3 in the IR codes with the GC-100, the plugin does not do anything with that info to route to the 2nd or 3rd IR ports! HEELLPPP!

I just retested this with my GC-100, and I was able to change the port and module configuration of the IR code to selectively send it to any of the six outputs.

I would double-check your GC-100 configuration (via web configuration) to make sure that your other IR Connectors (ports) are configured as "IR Out".

Circe640 · Post by **Circe640** » Sun Oct 10, 2004 7:51 pm

All connectors are configured as IR Out

Circe640 · Post by **Circe640** » Sun Oct 10, 2004 7:51 pm

Does Sensor notifications have to be enabled?

Post by **ScottBot** » Sun Oct 10, 2004 8:11 pm

Yes it does.

Circe640 · Post by **Circe640** » Mon Oct 11, 2004 1:58 am

OK I will try that tonight(Mon) -- I am confused though, according to the GC-100 documentation 'Sensor Notifications is used to automatically signal changes in sensor state. Any connector configured as an input will send notification unless this feature is disabled' I don't understand why when all the ports are used as outputs this has to be on and why port 1 works but 2&3 don't. This function was disabled by factory default.

Circe640 · Post by **Circe640** » Tue Oct 12, 2004 12:53 am

Yep That worked!! Does make any sense, but I am not going to bother to try and understand why!!

Thanks Scott!!

Post by **ScottBot** » Tue Oct 12, 2004 3:32 pm

I don't know either. It doesn't really state it in their documentation. When you asked, I simply tested it both ways and found it was required.