Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vox Triggered, phone not charging. #3

Open
hallbdh opened this issue Mar 20, 2014 · 7 comments
Open

Vox Triggered, phone not charging. #3

hallbdh opened this issue Mar 20, 2014 · 7 comments

Comments

@hallbdh
Copy link

hallbdh commented Mar 20, 2014

When I enable vox on the radio it automatically opens the mic. Happens at any vox setting other than off. Happens when any program, including PocketPacket uses the speaker. Board is built as described on this site.

@johnboiles
Copy link
Owner

When you say 'uses the speaker' do you mean when the apps (including PocketPacket) make sound? It's expected that any app that makes sound will trigger the vox. This is a limitation of using the phone's audio out and vox. I recommend putting the phone on silent and not actively using other apps while transmitting APRS.

On Mar 20, 2014, at 6:17 AM, hallbdh [email protected] wrote:

When I enable vox on the radio it automatically opens the mic. Happens at any vox setting other than off. Happens when any program, including PocketPacket uses the speaker. Board is built as described on this site.


Reply to this email directly or view it on GitHub.

@hallbdh
Copy link
Author

hallbdh commented Mar 20, 2014

No. When PocketPacket is open. Even if transmit is disabled it keys the mic through vox. I have tried this with a simple voice memo and my call sign and once the recording starts it activates vox but then hangs open after recording is done. I wonder if there is something in the apps that is causing this. Could it be new to 5s or are others having success with the same combination.

@johnboiles
Copy link
Owner

Just tried with my wife's 5S and it worked ok.

When I first enabled VOX, the radio started transmitting without ceasing. I then unplugged the TRRS connector from the iPhone and plugged it back in. After that everything worked as expected. Surprisingly I didn't get the charging bug with the 5S --I was able to receive, transmit, and charge all at the same time. That doesn't seem to work on my 5.

Something's probably causing noise on the radio's microphone line and triggering VOX. Could be anything from a nearby AM transmission, something electrically in your radio or phone, or a feedback loop where your radio transmitting created noise on the mic line. Are the cables you are using shielded?

It's obviously not ideal to not connect the radio's microphone ground, but I couldn't think of a good way to connect it without triggering PTT. The real solution is probably to build a full optoisolated circuit, but that adds complexity, cost, and size. If you have any ideas for workarounds, I'd love to hear them!

On Mar 20, 2014, at 9:00 AM, hallbdh [email protected] wrote:

No. When PocketPacket is open. Even if transmit is disabled it keys the mic through vox. I have tried this with a simple voice memo and my call sign and once the recording starts it activates vox but then hangs open after recording is done. I wonder if there is something in the apps that is causing this. Could it be new to 5s or are others having success with the same combination.


Reply to this email directly or view it on GitHub.

@johnboiles
Copy link
Owner

Were you ever able to resolve this?

Are the cables you are using shielded? Depending on your RF environment, you could be picking up enough noise to trigger VOX. Then once VOX is triggered, the output from your 4-5W Baofeng is probably enough to keep VOX triggered.

@hallbdh
Copy link
Author

hallbdh commented Jul 31, 2014

John,

I cannot remember if they were shielded or not. I have not tried it anywhere but by the house so RF noise could be an issue. I am going camping this weekend and will be in a totally different environment so will give it a try there. The cable I ordered was meant for connection of the two post to single post device. All I did was cut it in half, strip back some wire and put the board in the middle. Thinking back I do not remember shielding. A ferrite bead did not help around the house.

It does work for output from radio to input to phone just not other way around. I am using it as the primary purpose was to receive from a GPS beacon located in a high power rocket.

If things change I will let you know.

Brad

On Jul 24, 2014, at 2:46 PM, John Boiles [email protected] wrote:

Were you ever able to resolve this?

Are the cables you are using shielded? Depending on your RF environment, you could be picking up enough noise to trigger VOX. Then once VOX is triggered, the output from your 4-5W Baofeng is probably enough to keep VOX triggered.


Reply to this email directly or view it on GitHub.

@wrsweeney
Copy link

Was this issue ever resolved? Have same problem with APRS PRO. Beofeng goes into transmit as soon as headphone volume is taken off mute...no matter what settings are used...tried mono left and right in 4S iPhone I am using. Shutting down app stops the PTT trigger or going back to mute. Only hiss can be heard in nearby receiver. Funny thing is that this app fine worked for a short time before this issue developed. It only shows up when app is running. Sorry for being so late to post. Please redirect me to solution if it is here. Thank you for your work

@wrsweeney
Copy link

Having same problem as others while using the BTECH APRSv01 cable, but using your suggestion above has solved the problem. Had same problem with POCKET PACKET and APRSPRO...as soon as the headphone level is taken off mute, the Beofeng goes into TX on VOX. Go back to mute and HT goes back to receive. Other apps with audio would trip VOX but not lock in on TX, only the aprs apps. I found a hardware solution, but someone needs to find a software solution but current versions don't work with 4S iPhone. May only be problem with 4S and was solved in later models and became a mute point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants