This would all be Simian. All the settings and baud rate are the same.
I've always used Simian to control the receiver, so it keeps the serial
port open. The incoming trigger also needs to be seen by Simian.
So would I just by a DB-9 "Y" to split this? Someone also suggested
splitting the send and receive on the com port. This might be "safer"
since I only need to send to the sat receiver and receive from the BT
box. Being able to see the data back from the Unity is sometimes nice
(like the RT C command) but not critical.
I did find now that by changing the serial port in Simian to Com3 it
does see the incoming triggers. So that's good...except that I still
need to control the satellite receiver somehow. It's just easiest to do
it from within Simian.
Thanks to everyone for the responses...this is all very helpful!
On 12/15/2017 11:37 AM, Terry Cowan wrote:
I'm not totally following you but here is what should work. First of
all, a serial port must be open all of the time to "receive" data from
any box. Naturally, the serial port must be open to send information
to the Unity. If you are receiving and sending from the same software
and the software is not closing the serial port after sending to the
Unity and if the baud rate is the same for both sending and receiving
it should work fine. If not all of the above conditions are met you
Is Simian both setting the time based upon a closure and sending
commands to the Unity or are you using different software for sending
On 12/15/17 05:42, Andy Larsen wrote:
I'm working on upgrading our automation system computer and running
into a couple of issues with Simian. If anybody has first-hand
experience, I'd love some input from here. We are currently running
Simian 2.2 on a 32-bit computer, with one of the older computerboards
cards and Instacal for a trigger kit. The only trigger we use is the
54:30 clock sync. I use Simian directly to send serial strings to the
Unity 4000 receiver for switching. We still record several feeds, do
live news, and air Jimmy DeYoung live on Saturdays.
I purchased the BT GPI-16 (from BSI) to use for the triggers, since
the new computer doesn't have the PCI slot for the antique card.
BSI's site indicates it can be connected via serial or USB, but I
can't get it to recognize triggers when connected via USB. Tech
support now tells me it's a serial based device, and directed me to
set it up via serial. Is anyone using this through USB, or is their
web site incorrect?
I don't believe I can configure Simian to use two different serial
ports, because I'd need one for the GPI-16, and a second for
controlling the Unity 4000. I seem to remember people using a box to
turn relay closures into serial strings. This might be an option if I
upgraded to the other trigger kit, which includes relay outputs as
well. Another possibility would be to use a stand-alone program
running on another machine to switch the satellite receiver. Possibly
on our Amb-OS computer? Are any of those still supported?
Since we only use the clock sync, I may be able to do away with the
trigger kit. I believe I've read about people using GPS for clock
sync. I assume this requires both hardware and
software...recommendations if I go this route?
Finally...anyone using Simian 2.2 on a 64-bit machine? My computer
guy called and talked to BSI before building this computer, and was
led to believe that 2.2 would work on a 64-bit system. I've installed
it and it seems to be fine, though I'm still working on configuring
this and only have the 60-minute demo period. The email from tech
support also noted that if using Win7 64-bit, we would need to
upgrade to Simian 2.3.
I've sent email back to tech support (I don't pay for a tech support
plan) but I'd love some input from BSI users here as well.
For CRTech resources visit http://CRTech.org/
To unsubscribe, e-mail: email@example.com
List problems?� E-mail: TechStaff@CRTech.org
WHWL * WEUL * WHWG
Gospel Opportunities, Inc.
130 Carmen Drive
Marquette, MI 49855
This email has been checked for viruses by Avast antivirus software.