Questions for the brain trust:
1. Can the same 232 port receive from one device and transmit to another device, both having the same communication protocol?
2. Do I have a sick GDL39 (and/or 795)?
Two, first. The GDL39 manual (Para 4.2.1) says it should boot in Bluetooth pairing mode when powered remotely. It does not. Believing it would, I buried the GDL on the subpanel since once paired with a 795 it would re-connect each time avionics are powered up. Not so. It appears (Para 4.1.1 and 4.1.2) that the 795 must be powered and bluetoothing before powering the GDL and manually entering pairing mode by pressing the power button 5+ seconds. But, that's a non-starter since both are powered simultaneously from an avionics bus, and I can't reach the GDL without ducking under the panel. To top it all off, having initially paired the 795 and GDL, the 795 can't find the GDL anymore though it's a listed Bluetooth device. One or both seem to be sick. That notwithstanding, if I have to go through the rigmarole of re-pairing every time I want to fly...I won't have it.
As to hard wiring, it seems I'm out of 232 ports. Besides the GDL, there's a GTN650 and a Trio Pro Pilot involved. On the 795, Tx2 feeds the Trio, and Rx1 listens to the GTN (for a much larger map display). With both ports utilized and without Bluetooth, I can't get wx and traffic from the GDL into the 795.
IF, IF, Rx2 on the 795 can receive the GTN and still talk to the Trio on Tx2 (both seemly use the same "Aviation In/NMEA Out" configuration), that frees up the 795's Tx1/Rx1 to interface with the GDL's TxB/RxB.
So the question: can the same 232 port listen to and talk to two different devices?
To be really piggy about this, the GDL's TxA/RxA, so far unused, could be tied to the GDU's port 1.
I'm beginning to long for the good ol' days of testing a sack of vacuum tubes at the local drug store.
Answers greatly appreciated.
John Siebold
1. Can the same 232 port receive from one device and transmit to another device, both having the same communication protocol?
2. Do I have a sick GDL39 (and/or 795)?
Two, first. The GDL39 manual (Para 4.2.1) says it should boot in Bluetooth pairing mode when powered remotely. It does not. Believing it would, I buried the GDL on the subpanel since once paired with a 795 it would re-connect each time avionics are powered up. Not so. It appears (Para 4.1.1 and 4.1.2) that the 795 must be powered and bluetoothing before powering the GDL and manually entering pairing mode by pressing the power button 5+ seconds. But, that's a non-starter since both are powered simultaneously from an avionics bus, and I can't reach the GDL without ducking under the panel. To top it all off, having initially paired the 795 and GDL, the 795 can't find the GDL anymore though it's a listed Bluetooth device. One or both seem to be sick. That notwithstanding, if I have to go through the rigmarole of re-pairing every time I want to fly...I won't have it.
As to hard wiring, it seems I'm out of 232 ports. Besides the GDL, there's a GTN650 and a Trio Pro Pilot involved. On the 795, Tx2 feeds the Trio, and Rx1 listens to the GTN (for a much larger map display). With both ports utilized and without Bluetooth, I can't get wx and traffic from the GDL into the 795.
IF, IF, Rx2 on the 795 can receive the GTN and still talk to the Trio on Tx2 (both seemly use the same "Aviation In/NMEA Out" configuration), that frees up the 795's Tx1/Rx1 to interface with the GDL's TxB/RxB.
So the question: can the same 232 port listen to and talk to two different devices?
To be really piggy about this, the GDL's TxA/RxA, so far unused, could be tied to the GDU's port 1.
I'm beginning to long for the good ol' days of testing a sack of vacuum tubes at the local drug store.
Answers greatly appreciated.
John Siebold