|
Serial I/O & KeyspanHi I have just got a keyspan usb/serial adapter that I am trying to set up to control an extron matrix switcher. I have set the device correctly and the plugin fires up correctly and opens the port but it then closes the port and I cant seem to get any data to it. Any advice. Cheers Steve
|
Can you provide any console logs? (Console.app) Or, try using a slightly older version of the plugin, and see if that generates different messages or functionality.
Worst case, please e-mail me personally (info@kineme.net) and we'll discuss this to see what we can work out -- serial has been a chore, and I've not had many devices to test with/get the bugs worked out.
Sorry I pasted the console log into the log section but it doesn't seem to have appeared here it is.
01/06/2008 15:24:02 Quartz Composer[586] KinemeSerialO: openDevice: opening /dev/cu.USA19H1d1P1.1 01/06/2008 15:24:02 Quartz Composer[586] KinemeSerialIO: openDevice: Configuring device 01/06/2008 15:24:02 Quartz Composer[586] KinemeSerialIO: 9600 baud rate configured 01/06/2008 15:24:02 Quartz Composer[586] KinemeSerialIO: Current Configuration: 01/06/2008 15:24:02 Quartz Composer[586] * Parity: No 01/06/2008 15:24:02 Quartz Composer[586] * Type: Even 01/06/2008 15:24:02 Quartz Composer[586] * Data Bits: 8 bit 01/06/2008 15:24:02 Quartz Composer[586] * Stop Bits: 1 01/06/2008 15:24:02 Quartz Composer[586] KinemeSerialIO: configDevice: Disabling Parity 01/06/2008 15:24:02 Quartz Composer[586] KinemeSerialIO: configDevice: Enabling 8 Data Bits 01/06/2008 15:24:02 Quartz Composer[586] KinemeSerialIO: openDevice: Configured. Adding to dictionary. 01/06/2008 15:24:02 Quartz Composer[586] KinemeSerialIO: openDevice: all finished up! 01/06/2008 15:24:04 Quartz Composer[586] KinemeSerialIO: closeDevice: Last user of 12 closed. Cleaning up 01/06/2008 15:24:04 Quartz Composer[586] KinemeSerialIO: closeDevice: All devices closed. Cleaning up.
Thanks for the reply I realise the serial patch is a pain but it could open lots of doors which would be great. I will download some previous versions and see if anything works differently. Cheers Steve
Cheers for the help.
thanks for the log -- nothing interesting there. Can you try receiving/sending some data before closing it again? (it was only open for 2 seconds in that log dump... nothing interesting). -- old versions will log when they send and receive, and how much, and if an error occurs; this is what I was looking for.
As for opening doors, I completely agree. Unfortunately, RS232 has had an unspeakably low Return-On-Investment, time-wise, so I typically choose to spend my time on other patches that cover more ground without all these peculiar bugs.