bnordgren / rpi-wd-packet-interface Goto Github PK

Add a USB hub chip and "adequate" output ports. Expected connectivity:

• "Upstream" USB to the controller (WiFi router's USB port/Arduino/Pi/Odroid/phone/laptop/tower computer)
• USB to optional external GPS
• USB to onboard soundcard chip
• USB to onboard Ethernet controller to local network or WiFi router/access point (#3)
• USB to CAT control interface?

Add Anderson Powerpoles for DC input power, and provide power to one or more USB ports. Use this to power the Pi.

Replace the analog inputs with a USB interface and a soundcard chip.

See jaymzx#2

• Powerpoles #2
• USB hub #4

Provide ~12W PoE ([email protected]) to ethernet device (e.g., Ubiquiti WiFi access points). This will likely require a DC-DC converter

10/100 USB Ethernet controller and RJ45

Allow the following methods for triggering PTT:

• Audio sense (existing)
• Direwolf and fldigi will allow you to use a gpio pin to trigger ptt.
• fldigi sends a 1600hz cw key signal to the right channel (https://docs.google.com/document/d/1jt7npAl58t1uaKVCCdDD9g3tHAhxzD0bXas1b565kJI/edit)
• fldigi uses the left channel for afcw (connected to mic input)
• fldigi can send a 1000 hz tone to right channel for PTT (http://www.w1hkj.com/FldigiHelp/rig_config_page.html)

fldigi can also use hamlib, rigcat, RTS/DTS pins of a serial line, or a pin on a parallel port.

Looks like we want the existing detector circuit on the left channel, an additional detector circuit on the right channel, and a means of selecting which PTT to use. (but sound to radio always goes to left channel--happily, channel 0 for direwolf). PTT options are: GPIO input, left detection, right detection.

Should put a special CW/PTT out connector to wire to a CW key.