I am not on a Kalypso all that often, but I am pretty sure you can go in and rename the triggers to be Play, recue..etc..instead of 1,2 etc. This I would assume is on a device address by device address level..since one PBUS address can have one set of commands, where another could have a different one. It all depends on what you are talking to. It sounds like maybe your trigger types got renamed DDR1 and DDR 2 To use Bob's example from above of having 4 separate PBUS addresses ( 1 for each channel of Thunder)...you would I think need 4 different "device rows" in the PBUS menu on the Kalypso. This way you would have control of each of the channels individually. If you are only going to trigger 1, then maybe you only need the one... We have each channel of THunder as a different address. ( 11-14).. Devices 1-4 are already in use. You will have to go in the Thunder ( file...> Preferences> Protocol Setup I believe)...and assign a different device # to the second channel of Thunder you are going to trigger ( assuming you are going to recall/play etc these channels separately. ) Glad it is working. The good news is that your cabling is working..>Now it is all software related. Curt

Thanks Curt, you just cleared everything up for me. I couldn't figure out why only DDR1 was firing. What I now realize is that it was set up incorrectly, as I have only 1 device listed as Thunder, then instead of trigger "0" and "1", they are now renamed DDR1 and DDR2. Just talked to engineering and they're going to assign another "Device" row and give it the appropriate ip address to trigger DDR2. Right now DDR1 is firing the triggers you explained (though like I said, rather than "1" it's been renamed to "DDR2" but it's the same play function.) Thanks for clearing that up!

Hello, Here are the PBUS triggers for Thunder 1 Play 2 Pause 3 Recue So firing the above trigger will result in the action on the right. I would test the connection first...by recalling on the Thunder itself 4 clips...then try playing each PBUS address ( one for each channel)...If you can't play...most likly you aren't connected. If you open up one of the windows that are minimized in the task bar , you will see "data" come in when you test fire from the switcher. Not data , I assume would mean no connection. If you want to send me an email through this site, we can arrange a time when you can call. I am not on a Kalypso , but I do use Thunder with PBUS and a Sony 8000. I could walk you through the menus on the Thunder. Curt

I believe that the Pbus on thunder recalls whatever clip you have loaded when you learn your emem. You will have to look in the thunder menu...I think there is a setting to enable the learn function. You will also have to have the right triggers to play / recue / so on.

So engineering has made the connection, and in my PBus menu I can see "Thunder" listed as a device, and "DDR1" and "DDR2" labeled in place of trigger 0 and 1... really I only need control of channel 1 and 2 anyway since these are the channels with audio, 3 and 4 are used for OTS and plasma graphics which change on a daily basis, which are run from the thunder shotbox. But now how do I get the kalypso to fire the appropriate clip, from playing around in Thunder it looks like it's in the protocol set up menu, but everything I'm trying isn't working (which is all guess work anyway). Any assistance? Thanks in advance!

[quote="TekD"]Yeah I've been working with our engineer to get this going, it's new to him as well, so you guys have been a help to both of us... I'm gonna try running the 422 cable then play around with the menus and see what comes up. As far as odetics or louth the engineer told me we don't have either, so we'll see what comes about with just the direct cable. Thanks again for your help![/quote] Odetics and louth is nothing to 'have' The thunder runs this as part of standard protocols. In a menu to select and restart (see other post). Thunder does a bunch of protocols. Kalypso standard machine control does odetics through serial connection, as well as louth I believe. AMP is an option on Kalypso machine control, which thunder doesn't do anyway. Check out ENG/Devices menu, add new device pretty straight forward.

Yeah I've been working with our engineer to get this going, it's new to him as well, so you guys have been a help to both of us... I'm gonna try running the 422 cable then play around with the menus and see what comes up. As far as odetics or louth the engineer told me we don't have either, so we'll see what comes about with just the direct cable. Thanks again for your help!

[quote="TekD"]Question, so how do we "pick" or find the correct ip address? And it's basically just the cable from an open serial port to an open com port on Thunder? If so we have more than 4 available, would running one to each port for each channel, or maybe just 1 or 2 channels make sense to do or does it not work that way for PBus? Thank you by the way, you're providing major insight! :)[/quote] There should not be a need for an IP address for P-bus. You only need one cable to Thunder. Thunder lets you gang the communciation to the other channels via the menus. This does not gang the channels for recall, you can and should have seperate P-bus address for each channel as Bob mentioned. If you have 4 ports open. I would still run one, and try running the control through odetics or louth. As I mentioned in the Kalypso you will set this up as a device that the switcher can control like machine control. If this test works and still allows the Thunder to work with the keyboard and mouse (think it should), and does all the looping as setup in thunder then this would be my preferred way of hooking it up. Engineering should run you a cable do some testing between shows, and see what happens.

[quote="TekD"]Question, so how do we "pick" or find the correct ip address? And it's basically just the cable from an open serial port to an open com port on Thunder? If so we have more than 4 available, would running one to each port for each channel, or maybe just 1 or 2 channels make sense to do or does it not work that way for PBus?[/quote] If you're doing IP addresses, you're only limited by the SubNet Mask. If the SubNet Mask is set at 255.255.255.0 (which is fairly standard on most systems) then your 1st 3 octets need to exactly match the network's address [192.168.0.---]. You'd find an open address for the last octet; one that isn't already being used by another device on the network - the numbers range from 0 to 255. I usually pick something in the 100's, but a simple device sniffer program can tell you what's already being used. For PBus you can choose any address from 0 through 23. Again, as long as there isn't another device with the same number, the choice is yours & the number doesn't really matter. If you want to put 2 devices at the same PBus number, that's OK as long as you keep it straight in your head to have both devices ready to go (both fill & key) when you initiate your Learn command, and as long as it's OK that your 1 switcher command will affect multiple devices. In the past, I've given each of 4 devices their own unique PBus address & then use the DNF or LANCE box to gang channels under 1 PBus address when necessary...I have found that this approach is very flexible.

Question, so how do we "pick" or find the correct ip address? And it's basically just the cable from an open serial port to an open com port on Thunder? If so we have more than 4 available, would running one to each port for each channel, or maybe just 1 or 2 channels make sense to do or does it not work that way for PBus? Thank you by the way, you're providing major insight! :)

Kalypso to Thunder, use any open serial port, wire a 422 cable to any open Thunder serial port On Kalypso you need to go setup the P-bus, different address for each thunder channel, maybe someone if front of a Kalypso can help you with the menus. On thunder go into one of the menu's again not in front of it, under file, protocol setup maybe? Go to channel 1, select com port, select P-bus, select address (your choice). Go to the other channels, and under port I think you select link to channel 1. Basically this allows you to control all 4 channels with seperate address's with one cable. This will allow you through a macro or emem, recall P-bus for any channel to call up a clip or still. Then run it when you want to play, transition, etc. As you mentioned Thunder is slowwww, it is still slow with P-bus. One other option if you want to try, and not sure you may need 4 serial cables between kalypso and thunder is to use odetics or louth (I think Kalypso does louth). Anyway this is direct machine control. Works a lot better and easier to use then P-bus, it actually downloads the clip list into the switcher. You pick your clip and insert a keyframe, etc. Not sure how well this will work with Thunder never tried it, worth a try with one channel first. ENG menu, add a device, pick odetics, serial port #, etc. Then go into device menu and you should see thunder in there (if you named it in ENG menu). Build your timeline through misc that you assigned that device to, works really nice, if it works with Thunder. Oh one other thing in Thunder before closing that menu, hit restart all, on the windows tab on the bottom you should see tabs for each channel's protocol, these need to be on all the time. Also each show can have it's own P-bus file to save and load, this allows different operators to use the same emem to call up different clips As far as digitcart read the other posts see what model you have and see whether it will do P-bus or GPI, call 360 (I think they make digicart) and ask if not sure. Also the Thunder stuff is actually documented in the thunder manual. Hope that helps

Though it's an old topic, looks like we're finally getting around to getting our GPI's connected... So let's see if this is straight, first we are on a Kalypso Classic. On the back of hte panel there is a DB37 port... But also the pbus ports, if all I'm looking to do is connect my Thunder and Digicart what are the pros and cons of using a PBus and/or GPI? Sorry but I'm completely green to the switcher controlling external devices. I'm also curious how it would work once it's talking to Thunder, right now we use a shotbox and create a sequence with about 30 or so clips, for bumpers, toss boxes, animated over the shoulders, full screen gfx, etc. The main reason I want to get Thunder and Kalypso to start talking is so that we can start using more animated wipes, currently we only have a handful that are in the internal SS, but we only have 1 min. of memory, so we're limited in that way. If we do get these devices talking, when I build an effect, will the clip cue up then run when I need it to? Or am i only able to recall the clip and play it immediately, which I hope isn't the case as Thunder takes a few seconds to cue up. Thanks!!!

I tried everything I could think of to trigger a DigiCart E via PBuss over at the E! and G4 studios. After a day of attempts, the engineers dug up an old DNF PBIB PBuss interface. Works great. FWIW, at my primary studio, I also tried to PBuss a 360 Systems Image Server 2000. No luck there, either. I guess 360 Systems' implementation of PBuss, even though advertised and described in the manual, simply isn't there.

Steve, I have yet to have enough time to try to get either a Sony or Kalypso to trigger an "E" series. This is where the DD35's concept of having panel GPI's would work real well. On Comcast's HD truck the tub is at the opposite end of the truck from audio but the panel is maybe a 10 foot cable away from the Digicarts.

@Mike - have you gotten the internal PBuss to work with the DigiCart E? I haven't had any success @TekD - the GPI connector on the back of the Kalypso (it's a DB37, I believe) has pins for all 16 GPIs. Check out the Kalypso installation manual (available on the Grass Valley FTP site) for pinout. If you can't find it, let me know - I'll dig it up for you. The Kalypso sends a normally open relay closure to fire the GPI circuit. Mike's suggestion of using Cat5 adapted to DB-9 is excellent for anything requiring RS-422 (serial) control. For the GPIs, since it's nothing more than a contact closure, you can even use regular telephone "jake" cable. All you need is one pair of wires for a GPI.

Depending on what series DigiCart you have you might be able to trigger it via PBus, the Digicart E series, most recent series, has PBus control built in. Then you would need a RS422 cable run to it. The above mentioned Belden cable is around $180/1000', in many cases you cane also use Cat5 cable with RJ45 connectors and then a 9pin to RJ45 adapter on it. Cat5 goes for around $130-150/1000'.

Yeah it didn't make any sense to me, I mean I'm on the bottom of the totem pole at my station for TD's, but I want to do more than they used to... So if they tell me something and the other Director's don't question it supposedly it's true, but this one just didn't seem right to me... crosspoints router etc. didn't make sense. I was looking around for the port that I would connect to and found one marked GPI, course that's in the room down the hall, so I'll probably still need engineering to run the cable through the wall... But basically you're saying all I need is to run the cable with adapters from that port to say the digicart and I'm set?

I agree what station, that is some good bullshit. It will take them longer to run the cable then to hook it up. For Thunder you only need one 422 cable for P-bus from the switcher.

I took pictures of my GPI/O setup, but I think that I can only link to pictures, not actually host them on this site. I use several products from asi-ez.com Check Out ? I use these interface modules for 2 Chyrons, 2 Servers, a Kayak, a Zeus (Telex I/com relay control), tally distribution, etc.

Sounds like someone does not want to work. Why would you need another router?? To connect the GPI's you just need some cat5 cable, heck even some spare Belden 8451 audio cable if you are going to wire one device. You need some $2 connectors and you are done. What does identifying cross points have to do with wiring peripherals? BTW, as pointed out in another thread EVERY single piece of cable in the building should be documented. What station is this? Who owns this place?