• Join/Login
  • Business Software
  • Open Source Software
  • For Vendors
  • Blog
  • About
  • More
    • Articles
    • Create
    • SourceForge Podcast
    • Site Documentation
    • Subscribe to our Newsletter
    • Support Request
SourceForge logo
For Vendors Help Create Join Login
SourceForge logo
Business Software
Open Source Software
SourceForge Podcast
Resources
  • Articles
  • Case Studies
  • Blog
Menu
  • Help
  • Create
  • Join
  • Login
  • Home
  • Browse
  • SvxLink
  • Mailing Lists

Re: [Svxlink-devel] Data Communication Protocol

Brought to you by: sm0svx
  • Summary
  • Files
  • Reviews
  • Support
  • Mailing Lists
  • Tickets ▾
    • Feature Requests
    • Bugs
  • News
Menu ▾ ▴
  • svxlink-announce
  • svxlink-commits
  • svxlink-devel

Re: [Svxlink-devel] Data Communication Protocol

Re: [Svxlink-devel] Data Communication Protocol
From: Norbert S. <nse...@ds...> - 2008-10-06 16:52:31
Aleks,
your comments are very much appreciated. Must have overlooked the JP2 
and its function
but I was pretty close with my theory. The RX ID will wind up in my 
Firmware and can be set by
RS232 using a terminal program and write it into EEPROM when done.
Great idea to signal the end of DTMF via a bit. Saves some hardware for 
muting.
I'll hook up my prototype interface and see how SVXLINK is acting with 
my firmware.
The hardware design can route audio both ways i.e. act as input or as 
output via mode
jumper. COR and PTT are automatically switched to the proper logic.
Also, I think it will work fine with host detection SVXLINK or Echo-Link 
though I haven't tested it yet.

Thanks again!
Regards,
Norbert, KJ6ZD

Aleksander S. wrote:
> On Sat, 4 Oct 2008 at 20:57:51, Norbert Seibert wrote:
>
>   
>> I haven't seen anything on Aleks interface that could distinguish between RX0
>> and RX1 unless SVXLINK can do something with this bit.
>>     
>
> The "RX address" of the particular interface is set by JP2.
>
>   
>> The three function bits, I guess that f2 and f1 is actually for future use.
>>
>> f0 is telling SVXLINK that a DTMF char comes along according to the decoded
>> nibble.
>>
>> Since the interface is sending the "event" only if there was an event, I
>> don't understand what 
>> f0 = 0 does. Unless it is for future purpose and implemented now I don't see
>> its purpose yet.
>>     
>
> f0 = 0 signals the end of DTMF tone detection. This is important for SVXlink 
> to handle DTMF muting properly.
>
>
>   
>> So I assume that SVXLINK does not ask for anything, besides I have seen on
>> Aleks interface that there is only the TXD available. So, SVXLINK couldn't
>> send anything to the Interface, even if it wanted to.  
>>     
>
> Currently SVXlink transmits to the interface nothing. Therefore the second "RX 
> section" of the interface's RS-232/UART converter (MAX232) is used to drive a 
> LED.
>
> 73 de Aleks
>
>
>
> ____________________
> http://www.email.si/
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Svxlink-devel mailing list
> Svx...@li...
> https://lists.sourceforge.net/lists/listinfo/svxlink-devel
>
>   



View entire thread

SourceForge
  • Create a Project
  • Open Source Software
  • Business Software
  • Top Downloaded Projects
Company
  • About
  • Team
  • SourceForge Headquarters
    1320 Columbia Street Suite 310
    San Diego, CA 92101
    +1 (858) 422-6466
Resources
  • Support
  • Site Documentation
  • Site Status
  • SourceForge Reviews
SourceForge logo
© 2026 Slashdot Media. All Rights Reserved.
Terms Privacy Opt Out Advertise