Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

SmartSDR TCP/IP interface

Barry Comer
Barry Comer Member
edited May 2020 in SmartSDR API
I am looking for docs describing the TCP/IP interface.

My development will be done using Java.

Answers

  • Sergey R5AU
    Sergey R5AU Member ✭✭
    edited April 2017
    Barry, this is not help you:  http://www.flexradio.com/downloads/flexlib_api-zip/   ?
  • Barry Comer
    Barry Comer Member
    edited May 2015
    Thanks but this is of no use since it is .Net based and I am developing in Java.
    There must be a development document or specification available.
  • Richard G7EIX
    Richard G7EIX Member ✭✭
    edited March 2015

    If you want to use the TCPIP API then the source code contained in that zip will be of use to you.  You will also do well to get access to the Dev Wiki which contains a lot of information on the TCPIP API too.

    http://wiki.flexradio.com

    You may need to request access to this.   

    I am not using the FlexLib, but have created my own library in C# for use on Windows Phone.

    There is also the objective-c source from Stu K6TU /N5AC here...

    https://github.com/n5ac/smartsdr-objective-c

    It's a case of piecing it all together - as there are no detailed manuals specific to any language.

  • Barry Comer
    Barry Comer Member
    edited May 2020
    As a senior software developer, I expect a public document detailing the TCP/IP interface since there is so much built on top of it. In order to promote the development of third party applications the information has to be readily available. Digging through source code in an effort to try and understand it is a major shortcoming.
  • Richard G7EIX
    Richard G7EIX Member ✭✭
    edited March 2015

    I am sure the docs you yearn for will be available at some point in the distant future - right now though, anyone who wants to develop for this relatively young product has to dig in and piece it together - it was not hard - took a day at the most to build an interface and then its a case of gleaning information from the code available and WireShark captures while playing with SmartSDR.   

    I think once we have a SmartSDR with all the initial promised features in place - then the Devs will have time to build a solid usable documentation source for the rest of us.

    There are a good amount of Software Devs and Engineers on here - myself included.   But those that want to create something have dug in and unearthed the information they want.    Unfortunately there is no silver platter with SmartSDR API docs at this time.  Would have saved us all some time, but where would the fun in learning be?  :-)

    Good luck!

  • Barry Comer
    Barry Comer Member
    edited May 2015
    Richard, I agree with you about digging in and it is done on a daily basis at work.
    It is just nice every once and a while to have a "living" document in hand. This fosters a better experience with time actually spend developing. Discovery is an expensive process when the work is done outside of a work environment.

    No disrespect to the group or Flex intended!!
  • Richard G7EIX
    Richard G7EIX Member ✭✭
    edited March 2015
    I agree 100% with you.   I do.  But I also see it this way....

    If I am part of a small group that is willing to do the research and find the information as opposed to having a pile of docs that spell it out for me, then that also means I am in a smaller group who will get a product to market (if that was my intention) with less competition.

    Stu K6TU and a few others have already done this.... braver people than I!

    As soon as those docs arrive - spelling out every last detail, then the market gets saturated very quickly with similar projects and apps.

    It all depends on the product I suppose - is it worth the effort financially?   With SmartSDR its about the educational aspect for me - i'm learning something beyond my commercial skillset.

    I'm not creating commercial products with this though - HAM's are a tightfisted bunch - I'll stick with my commercial customers who want boring and expensive databases and web-based apps.
  • Barry Comer
    Barry Comer Member
    edited May 2015
    I agree with you and for me it is also about education. Docs available or not, there will be lots learned even developing the simplest of applications.

  • Stu Phillips - K6TU
    Stu Phillips - K6TU Member ✭✭
    edited August 2016
    My suggestion is to help provide the documentation...

    I'm in the process of adding VITA-49 support to the Objective-C interface and took the opportunity to document it as I'm going along.  I plan on giving the document(s) back to FlexRadio as I write them.

    Sure would be nice if others pitched in and helped.

    Yes, in an ideal world the documents would already be there - but FRS has constrained resources and this is an area where we can all help.

    Stu K6TU
  • Barry Comer
    Barry Comer Member
    edited May 2015
    What a great idea. On a related note, I do not mind the upgrade charge every once and a while as giving away free software is not good for the company's long term health. 
  • Eric-KE5DTO
    Eric-KE5DTO Administrator, FlexRadio Employee admin
    edited February 2017
    I think Richard nailed it.  The closest thing we have to what you want, I think, is on the wiki at http://wiki.flexradio.com.  You can create your own account there.


  • Barry Comer
    Barry Comer Member
    edited May 2015
    As a developer I am big on customer experience and code quality. I always use Microsoft as the yardstick for **** products when I need a reminder to put in the extra effort. If it is easy to use  people will spread the word. If it is hard to use people will spread the word. I really like the Flex products. End of thread.

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.