Quantcast
Channel: FlexRadio Systems Knowledge Center
Viewing all 66 articles
Browse latest View live

PowerSDR 1.x CAT Command Set

0
0
PowerSDR 2.x CAT Command Reference Guide

System Dependencies
Minimum PowerSDR Version: 2.0.0
Applicable Hardware: N/A

Content provided by: FlexRadio Systems Engineering

This document defines the syntax for using native FlexRadio CAT commands as well as the current FlexRadio CAT command set cross-reference that groups FlexRadio CAT commands by function and control along with showing the equivalent Kenwood CAT command.


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

PowerSDR 2.x CAT Command Reference Guide


FlexRadio Systems™ Proprietary End User Software License Agreement “EULA”

0
0
FlexRadio Systems™ Proprietary End User Software License Agreement “EULA”

  System Dependencies
  Minimum PowerSDR Version:     All versions 
  Applicable Hardware:     N/A 

Content provided by: FlexRadio Systems Engineering

FlexRadio Systems™ Proprietary End User Software License Agreement “EULA”

Updated 5/25/2010

SCOPE: THIS DISTRIBUTION OF FLEXRADIO SYSTEMS PowerSDR™ INCORPORATES A "MIXED SOURCE" MODEL INCLUDING BOTH OPEN SOURCE AND CLOSED SOURCE COMPONENTS. THE OPEN SOURCE COMPONENTS ARE COVERED UNDER A SEPARATE AGREEMENT. THE CLOSED SOURCE COMPONENTS ARE PROPRIETARY TO FLEXRADIO SYSTEMS AND ITS LICESNSORS. THIS DOCUMENT COVERS YOUR RIGHTS, PRIVILEGES, AND RESPONSIBILITIES RELATING TO FLEXRADIO CLOSED SOURCE PROPRIETARY SOFTWARE. A DETAILED LISTING OF THE OPEN SOURCE AND CLOSED SOURCE COMPONENTS USED IN CONJUCTION WITH THIS DISTRIBUTION OF PowerSDR IS CONTAINED IN THE ELECTRONIC DOCUMENTATION INCLUDED WITH THIS DISTRIBUTION.

A. FlexRadio Systems PROPRIETARY Software License Agreement
B. FlexRadio Systems Trademark and Copyright Notices

A: PROPRIETARY SOFTWARE LICENSE AGREEMENT

PLEASE READ THIS PROPRIETARY SOFTWARE LICENSE AGREEMENT (“LICENSE”) CAREFULLY BEFORE CLICKING “I ACCEPT THE TERMS” OR USING FLEXRADIO SYSTEMS PROPRIETARY SOFTWARE. BY CLICKING “I ACCEPT THE TERMS” OR BY USING THIS SOFTWARE, INCLUDING SOFTWARE UPDATES AS APPLICABLE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS LICENSE. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENSE, CLICK “I DO NOT ACCEPT THE TERMS” AND DO NOT USE THIS FLEXRADIO PROPRIETARY SOFTWARE.

1. DEFINITIONS: The term “FlexRadio Proprietary Software” includes application code downloaded or read from media, embedded firmware, dynamic linked libraries (DLLs) whether created by or licensed to FlexRadio Systems, installer applications, documentation, interfaces, content, fonts, and static or software generated visual images and presentation graphics as may be updated or replaced by feature enhancements; whether stored in Read Only Memory (ROM), on any other media or in any other form, including software updates provided by FlexRadio Systems and not specifically licensed otherwise; are collectively referred to as “FlexRadio Proprietary Software”. This does NOT include any software or firmware that is separately licensed under the Free Software Foundation’s GNU General Public License (GPL), Lesser General Public License (LGPL), or any other open source, proprietary or less restrictive license. The term “FlexRadio Systems Hardware Platforms” refers to electronic hardware designed and manufactured by FlexRadio Systems, generally for use in, but not limited to receiving and transmitting radio signals, interfacing to other radio-related equipment, and other hardware control apparatus.

2. GENERAL: FlexRadio Proprietary Software including updates are licensed not sold, to you by FlexRadio Systems for use only under the terms of the License. FlexRadio Systems and it licensors retain ownership of “FlexRadio Proprietary Software” itself and reserve all rights not expressly granted to you.

3. PERMITTED LICENSE USES AND RESTRICTIONS:
(a) Subject to the terms and conditions of this license, you are granted a limited non-exclusive license to use the FlexRadio Proprietary Software in conjunction with FlexRadio Systems Hardware Platforms. Except as specifically allowed below, this license does not allow FlexRadio Proprietary Software to be used in conjunction with any non-FlexRadio Systems Hardware Platforms.
(b) Unless expressly granted by FlexRadio Systems, this License does not grant you any rights to use FlexRadio Proprietary Software in the design, development, manufacture, licensing, or distribution of non-FlexRadio Systems Hardware Platforms.
(c) Subject to the terms of this License, you are granted a limited non-exclusive license to download and execute updates to FlexRadio Proprietary Software for use in conjunction with FlexRadio Systems Hardware Platforms according to the then current terms provided by FlexRadio Systems. You may make one copy of the FlexRadio Proprietary Software stored on your computer in machine-readable form for backup purposes only, provided that the backup copy must include all copyright or other proprietary notices contained in the original.
(d) You may not and you agree not to, or to enable others to, copy (except as expressly permitted by this License), decompile, reverse engineer, disassemble, attempt to derive the source code of, decrypt, modify, or create derivative works of FlexRadio Proprietary Software, or any part thereof. Any attempt to do so is a violation of the rights of FlexRadio Systems and its licensors of FlexRadio Proprietary Software.
(e) You agree to use FlexRadio Proprietary Software in compliance with all applicable laws, including local laws of the country or region in which you reside or in which you download and use FlexRadio Proprietary Software in conjunction with FlexRadio Systems Hardware Platforms.

4. TRANSFER: you may not rent, lease, lend, sell, redistribute, or sublicense FlexRadio Proprietary Software. You may however, make a one-time permanent transfer of all your license rights to FlexRadio Proprietary Software in conjunction with the transfer of ownership of your FlexRadio Systems Hardware Platform; provided that
(a) the transfer must include your FlexRadio Systems Hardware Platform and all FlexRadio Proprietary Software, including all its component parts, original media, printed materials and this license;
(b) you do not retain any copies of FlexRadio Proprietary Software, full or partial, including copies stored on a computer or other storage device; and
(c) the party receiving the FlexRadio Systems Hardware Platform and FlexRadio Proprietary Software reads and agrees to accept the terms and conditions of this License.

5. TERMINATION: This License is effective until terminated. Your rights under this License will terminate automatically or otherwise cease to be effective without notice from FlexRadio Systems if you fail to comply with any term(s) of this License. Upon the termination of this License, you shall cease all use of FlexRadio Proprietary Software. Sections 6, 7, 8, 9, and 10 of this License shall survive any such termination.

6. DISCLAIMER OF WARRANTIES: YOU EXPRESSLY ACKNOWLEDGE AND AGREE THAT , TO THE EXTENT PERMITTED BY APPLICABLE LAW, FLEXRADIO PROPRIETARY SOFTWARE AND ITS ACCOMPANYING WRITTEN MATERIALS ARE PROVIDED “AS IS” AND “AS APPLICABLE” WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY FLEXRADIO SYSTEMS OR ITS REPRESENTATIVES, AUTHORIZED DISTRIBUTORS, OR EMPLOYEES SHALL CREATE A WARRANTY, OR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY; AND YOU MAY NOT RELY ON SUCH INFORMATION OR ADVICE. FLEXRADIO SYSTEMS AND ITS LICENSORS DO NOT GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF USE, OF FLEXRADIO PROPRIETARY SOFTWARE OR WRITTEN MATERIALS IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE, AND THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE OF THE SOFTWARE IS ASSUMED BY YOU, THE USER. IF FLEXRADIO PROPRIETARY SOFTWARE OR WRITTEN MATERIALS ARE DEFECTIVE, YOU, AND NOT FLEXRADIO SYSTEMS OR EMPLOYEES, ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION OTHER THAN EXPRESSLY DESCRIBED ABOVE.

7. LIMITATION OF LIABILITY: TO THE EXTENT NOT PROHIBITED BY APPLICABLE LAW, IN NO EVENT SHALL FLEXRADIO SYSTEMS OR THEIR AUTHORIZED AGENT(S) BE LIABLE FOR PERSONAL INJURY, OR ANY INCIDENTAL, SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, CORRUPTION OR LOSS OF DATA, FAILURE TO TRANSMIT OR RECEIVE ANY INFORMATION, BUSINESS INTERRUPTION OR ANY OTHER COMMERCIAL DAMAGES OR LOSSES, ARISING OUT OF OR RELATED TO YOUR USE OF OR INABILITY TO USE FLEXRADIO PROPRIETARY SOFTWARE, HOWEVER CAUSED, EVEN IF FLEXRADIO SYSTEMS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

8. CONTROLLING LAW AND SEVERABILITY: This License will be governed by and construed in accordance with the laws of the State of Texas, excluding its conflict of law principles. If for any reason a court of competent jurisdiction finds any provision, or portion thereof, to be unenforceable, the remainder of this License shall continue in full force and effect.

9. COMPLETE AGREEMENT: This License constitutes the entire agreement between you and FlexRadio Systems relating to FlexRadio Proprietary Software and supersedes all prior or contemporaneous understandings regarding such subject matter. No amendment to or modification of this License will be binding unless in writing and signed by FlexRadio Systems.
10. GOVERNING LANGUAGE: Any translation of this License is done for local requirements and in the event of a dispute between the English and any non-English versions, the English version of the License shall govern, to the extent not prohibited by local law in your jurisdiction.

11. THIRD PARTY ACKNOWLEDGEMENTS: Portions of FlexRadio Proprietary Software may utilize or include third party software and other copyrighted material. Acknowledgments, licensing terms and disclaimers for such material are contained in the electronic documentation for FlexRadio Proprietary Software, and your use of such material is governed by their respective terms.


B: FLEXRADIO SYSTEMS TRADEMARK AND COPYRIGHT NOTICES

The image (see below)
 


and the textual equivalent “FlexRadio Systems®” logo is a registered trademark of FlexRadio Systems.
“FlexRadio Systems PowerSDR™”, PowerSDR™ ,“Tune in Excitement!™”,”Excitement to Go™”, “Excitement Anywhere™”, SDR-1000™, FLEX-5000™, FLEX-3000™, FLEX-1500™, FlexWire™, ClickTune™, MultiRX™, PanaFall™ and PanaScope™, are all trademarks owned exclusively by FlexRadio Systems. While portions of PowerSDR software are distributed under the GPL Open Source License, the PowerSDR trademark is owned exclusively by FlexRadio Systems.

All source code, application code, machine readable code, embedded firmware, drivers, dynamic linked libraries (DLL) created by FlexRadio Systems, installer applications, documentation, interfaces, content, fonts, and static or software generated visual images, including PowerSDR Presentation Graphics (also known as “Skins”), as may be updated or replaced by feature enhancements; whether stored in Read Only Memory (ROM), downloaded or read from media, on any other media or in any other form, including software updates provided by FlexRadio Systems; relating to FlexRadio Systems Proprietary Software are © 2004-2010, FlexRadio Systems, All Rights Reserved. Except as covered by the FlexRadio Proprietary Software License in Section (A) above, any unauthorized use, duplication, or distribution of this software or images is strictly prohibited by law. No PowerSDR Skin or portion thereof, image, or similar likeness may be used without express written permission of FlexRadio Systems.

FireWire® and the FireWire logo are registered trademarks of Apple Computer Inc., under license

© 2010 - FlexRadio Systems, 13091 Pond Springs Rd. #250 Austin, TX USA 78729



This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file. You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced


FlexRadio Systems® PowerSDR™ GNU GPL Software License Agreement “EULA”

0
0
FlexRadio Systems® PowerSDR™ GNU GPL Software License Agreement “EULA”

System Dependencies
Minimum PowerSDR Version: All versions
Applicable Hardware: N/A

Content provided by: FlexRadio Systems Engineering

FlexRadio Systems® PowerSDR™ GNU GPL Software License Agreement “EULA”

Updated 5/25/2010

SCOPE: THIS DISTRIBUTION OF FLEXRADIO SYSTEMS PowerSDR™ INCORPORATES A "MIXED SOURCE" MODEL INCLUDING BOTH OPEN SOURCE AND CLOSED SOURCE COMPONENTS. THE CLOSED SOURCE COMPONENTS ARE PROPRIETARY TO FLEXRADIO SYSTEMS AND ITS LICESNSORS AND COVERED UNDER A SEPARATE AGREEMENT. THIS DOCUMENT COVERS YOUR RIGHTS, PRIVILEGES, AND RESPONSIBILITIES RELATING TO FLEXRADIO OPEN SOURCE SOFTWARE. A DETAILED LISTING OF THE OPEN SOURCE AND CLOSED SOURCE COMPONENTS USED IN CONJUNCTION WITH THIS DISTRIBUTION OF PowerSDR IS CONTAINED IN THE ELECTRONIC DOCUMENTATION INCLUDED WITH THIS DISTRIBUTION.

PLEASE READ THIS SOFTWARE LICENSE AGREEMENT (“LICENSE”) CAREFULLY BEFORE CLICKING “I ACCEPT THE TERMS” OR USING FLEXRADIO SYSTEMS SOFTWARE. BY CLICKING “I ACCEPT THE TERMS” OR BY USING THIS SOFTWARE, INCLUDING SOFTWARE UPDATES AS APPLICABLE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS LICENSE. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENSE, CLICK “I DO NOT ACCEPT THE TERMS” AND DO NOT USE THIS FLEXRADIO SOFTWARE.



GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330,
Boston, MA 02111-1307
USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give to the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow.


GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA

Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989 Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.



This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

SAM mode - Explained

0
0
SAM mode - Explained

System Dependencies
Minimum PowerSDR Version: 1.X.0
Applicable Hardware: FLEX-5000

Content provided by: Brian, WB6RQN/J79BPL

It is just a different type of AM detector. Synchronous AM detection (SAM) phase-locks the BFO to the AM carrier and then uses the BFO with product detection. It doesn't suffer from the loss of intelligibility during QSB that a normal AM envelope detector does. But you also can't see zero beat with it either since it will track the AM carrier even if you tune a little bit off-frequency.




This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced


FLEX-5000A and FLEX-5000C Transceiver Specifications

0
0
FLEX-5000A and FLEX-5000C Transceiver Specifications

System Dependencies
Minimum PowerSDR Version:
N/A
Applicable Hardware: FLEX-5000

Content provided by: FlexRadio Systems Engineering

General

Rx Frequency Range:

10 KHz - 60 MHz

(Customer provided preselector or appropriately selected low pass filters required to eliminate images when used below 1.8 MHz)

160 - 6 m (specified performance, Amateur bands only)

Transmitter Frequency Range:

160 - 6 m (Amateur bands only)

Frequency Stability:

±0.5 ppm 32 °F to 122 °F (0 °C to +50 °C)

Ambient Operating Temperature Range:

14 °F to 122 °F (–10 °C to +50 °C)

Emission Modes:

A1A (CW), A3E (AM), J3E (LSB, USB), F3E (FM),

F1B (RTTY), F1D (PACKET), F2D (PACKET)

Frequency Steps:

1Hz minimum

Antenna Impedance:

50 Ohms, unbalanced

6 - 1000 Ohms, unbalanced (With Optional Tuner ON, 160 - 10 m Amateur bands)

16 - 150 Ohms, unbalanced (With Optional Tuner ON, 6 m Amateur band)

Power Consumption:

Rx 1.5A (typ.); Tx (100 W) 25A (max.)

Supply Voltage:

DC: DC 13.8 V ± 10%

Maximum Interconnect Cable Length:

Firewire - 10 feet (3m),

No restriction on DC power cable within voltage tolerance limits under load.

Special EMI/RFI Requirements:

NOTE: Necessary to minimize RFI radiation from the cables attached to the radio

1 snap on ferrite bead on DC power cable,

2 snap on ferrite beads on FireWire® cable

1 snap on ferrite bead on FlexWire™ cable

All beads to be located adjacent to rear panel of radio.

FLEX-5000A Dimensions:

(WxHxD): 9.3” x 8.7” x 13.8” (23.5 cm x 22.1 cm x 31.5 cm)

FLEX-5000A Weight:

(approx.): 13 lbs (5.9 kg)

Transmitter

Power Output:

1 - 100 watts PEP CW and SSB (2 - 25 watts AM carrier)

28 MHz IF Power Output:

0 dBm (1.0 milliwatt)

Emission Modes Types:

A1A (CWU, CWL), J3E (USB, LSB), A3E (AM), F3E (FM), DIGITAL

Spurious and Harmonic Radiation:

Better than –55 dB (160 - 10m Amateur bands)

Better than –65 dB (6m Amateur band)

SSB Carrier Suppression:

At least 55 dB below peak output

Undesired Sideband Suppression:

At least 60 dB below peak output

Audio Response (SSB):

90 Hz @ -3dB / flat to upper limit set by software, Software EQ optional

3rd-order IMD:

Better than –33 dB below PEP @14.2 MHz 100 watts PEP

9th-order IMD:
Better than –54 dB below PEP @14.2 MHz 100 watts PEP

Image Rejection:

88 dB

Microphone Impedance:

600 Ohms (200 to 10k Ω)

Balanced Line In Impedance:

600 Ohms (200 to 10k Ω)

Receiver

Circuit Type:

Direct conversion, low IF

Intermediate Frequency:

Software selectable from DC to 20 KHz

Sensitivity (preamp off/on):

1.3/0.3 µV at 14 MHz

MDS (preamp off/on):

-123 dBm/-133 dBm in 500 Hz BW

IMD DR3 (dynamic range):

99 dB at 14 MHz with preamp off or off at 2 kHz or less tone spacing

IP3:

+30 dBm at 14 MHz with preamp off at 2 kHz or less tone spacing (S5 IM3 test method)

+39 dBm at 14 MHz with preamp off at 2 kHz or less tone spacing (ARRL test method)
IP2:
+63 dBm at 14 MHz with preamp off at 2 kHz or less tone spacing (ARRL test method)

Selectivity (–6/–60 dB):

CW 500 Hz –6/-60 dB: 500/640

SSB 2.4 kHz –6/-60 dB: 2.39/2.54

AM 6.6 kHz –6/-60 dB: 6.60/6.74

Image Rejection:

70 dB or better (160 - 6m Amateur bands)

Certifications:

CE Declaration of Conformity (25-August-2007) for the FLEX-5000A

CE Declaration of Conformity (23-August-2008) for the FLEX-5000A with RX2 (second receiver)


Specifications are subject to change without notice or obligation, and specifications are guaranteed only within the amateur radio bands.


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

FLEX-3000 Transceiver Specifications

0
0
FLEX-3000 Transceiver Specifications

System Dependencies
Minimum PowerSDR Version:
N/A
Applicable Hardware: FLEX-3000

Content provided by: FlexRadio Systems Engineering

General

Rx Frequency Range:

10 KHz - 60 MHz

(Customer provided preselector or appropriately selected low pass filters required to eliminate images when used below 1.8 MHz)

160 - 6 m (specified performance, Amateur bands only)

Transmitter Frequency Range:

160 - 6 m (Amateur bands only)

Frequency Stability:

TBD

Ambient Operating Temperature Range:

14 °F to 122 °F (–10 °C to +50 °C)

Emission Modes:

A1A (CW), A3E (AM), J3E (LSB, USB), F3E (FM),

F1B (RTTY), F1D (PACKET), F2D (PACKET)

Frequency Steps:

1Hz minimum

Antenna Impedance:

50 ohms

Power Consumption:

Rx 1.5A (typ.); Tx (100 W) 25A (max.)

Supply Voltage:

DC: DC 13.8 V ± 10%

Maximum Interconnect Cable Length:

Firewire - 10 feet (3m),

No restriction on DC power cable within voltage tolerance limits under load.

Special EMI/RFI Requirements:

NOTE: Necessary to minimize RFI radiation from the cables attached to the radio

1 snap on ferrite bead on DC power cable,

2 snap on ferrite beads on FireWire® cable

1 snap on ferrite bead on FlexWire™ cable

All beads to be located adjacent to rear panel of radio.

FLEX-3000 Dimensions:

(WxHxD): 12.25” x 1.75” x 12.25” (31.1 cm x 4.4 cm x 31.1 cm)

FLEX-3000 Weight:

(approx.): 9 lbs (4.08 kg)


Transmitter

Power Output:

1 - 100 watts PEP CW and SSB (2 - 25 watts AM carrier)

Emission Modes Types:

A1A (CWU, CWL), J3E (USB, LSB), A3E (AM), F3E (FM), DIGITAL

Spurious and Harmonic Radiation:

160-10m: -55 dB
6m: -65 dB

SSB Carrier Suppression:

Better than > 70 dB @ peak output

Undesired Sideband Suppression:

Better than 65 dB @ peak output

Audio Response (SSB):

90 Hz @ -3dB / flat to upper limit set by software, Software EQ optional

3rd-order IMD:

160-10m: -31 dB

6m: -30 dB

9th-order IMD:
160-10m: -48 dB

6m: -48 dB

Image Rejection:

TBD

Microphone Impedance:

600 Ohms (200 to 10k Ω)

Receiver

Circuit Type:

Direct conversion, low IF

Intermediate Frequency:

Software selectable from DC to 20 KHz

Sensitivity (preamp off/on):

1.3 / 0.3 µV (-123/-133 dBm in 500 Hz)

MDS (preamp off/on):

-121 dBm (14.2 MHz, preamp off)

-135 dBm (14.2 MHz, preamp-2 on)

-137 dBm (50.125 MHz, preamp on)

IMD DR3 (dynamic range):

95 dB (@ 2 KHz spacing / 14.2 MHz))

IP3:

Greater than +26 dBm (preamp off)
IP2:
+69 dBm (Preamp off)
+45 dBm (Preamp-2 on)

Selectivity (–6 to 60 dB):

CW 500/640

SSB 2.39/2.54

AM 6.6/6.74

Image Rejection:

160-10m: 96dB or better

6m: 71 dB or better


Certifications:

CE Declaration of Conformity received May 2009.



Specifications are subject to change without notice or obligation, and specifications are guaranteed only within the amateur radio bands.


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

DPCLAT - DPC Latency Checker Tool

0
0
DPCLAT - DPC Latency Checker Tool

System Dependencies
Minimum PowerSDR Version:
All Windows versions
Applicable Hardware: N/A

Content provided by: FlexRadio Systems Engineering

This KB article references the DPC Latency checker (dpclat.exe) by Thesycon that can be used to analyze you system for excessive or abnormally long DPC (differed procedure calls) that adversely effect applications that run in real time, such as PowerSDR. Below is some information from the Thesycon web site.

The DPC Latency Checker tool determines the maximum DPC latency that occurs on your Windows system and thus enables you to check the real-time capabilities of your computer. DPC Latency Checker works independent of any external hardware. Using this tool may be helpful in the following situations:
  • You experience interruptions (drop-outs) in a flow of data processed in real-time, for example an audio stream, video stream or a sequence of measuring data, and you want to find out the reason for this problem.
  • You want to verify that your Windows system is configured properly so that it is capable of handling real-time data transfer before you install the corresponding streaming application.
  • You want to check if a particular computer system is suitable for streaming applications, for example before you buy this system.
If any kernel-mode device driver in your Windows system is implemented improperly and causes excessive latencies of Deferred Procedure Calls (DPCs) then probably drop-outs will occur when you use real-time audio or video streaming applications.

Use the Related Links below to download the most recent version of the DPC Latency Tool, how to use it to determine if you have excessive latencies possible strategies to resolve the problems resulting from excessive DPCs


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

NoneReferenced

How to Adjust RF Power Output for Best IMD when Operating Digital Modes

0
0
How to Adjust RF Power Output for Best IMD when Operating Digital Modes

System Dependencies
Minimum PowerSDR Version: 2.0.x
Applicable Hardware: FLEX-5000/3000

Content provided by: Tim, W4TME& Brian, WB6RQN

When using a traditional analog transceiver to adjust the power output when running digital modes, it is customary adjust the radio's RF output until the ALC begins to register and then back it off a little bit. With a FlexRadio SDR running PowerSDR and using VAC for the digital audio transfer between PowerSDR and the sound card digital mode program, the following technique can lead to better control and cleaner signals.

In the olden days, the mic gain was how you controlled power output from your radio so to those of us who grew up with older radios, this approach seems natural. You would just advance the mic gain until just below the level where you actuated the ALC (onset of clipping) and you were all done. If you wanted less power you just turned down the PA RF gain (power).

What typically happens is that people set the AF input gain control a bit too high and then compensate by turning down the RF drive level. The result is clipping at an early stage within the radio. Most analog radios can tolerate a bit of over-driving at an early stage. The result is minor compression of the peaks and a minor increase in distortion. In fact, for SSB operation this might even provide just a bit more "punch" to the signal.

In the case of an SDR, the clipping is hard flat-topping, usually from exceeding the range of the A/D converter at the audio input. The rise in distortion is very rapid. So in order to ensure that all the stages are operating linearly, one must be sure to keep the input level below that which produces any clipping at all. Fortunately for us the FlexRadio Systems software defined radios have an indicator of AF input level at different stages in the TX audio chain. If ALC, which is at the end of the TX audio chain is indicating less than 0dB, you are not clipping the signal in the radio. With the VAC TX Gain (input signal) at 0 and the drive level set for 100, the RF output is 100 watts if using a pure tone. If you want to reduce the output and still make sure you have some headroom to prevent clipping, it is easier to turn down the VAC TX Gain (input level). Setting the VAC TX Gain in order to produce a -5dB ALC level should produce a RF output that is close to 50% of the PAs rated power.

Procedure for Adjust RF Power Output for Best IMD when Operating Digital Modes


Step 1. Set the PA Gain to 100.
Set your PA drive at 100. When you keep the audio input levels below -1dB, this will produce a signal that has the most optimal IMD figure with the maximum RF output.

Step 2. Set the TX Meter to Forward Power (FWD PWR)
You are going adjust your RF output by changing the VAC TX Gain (AF input) and not by turning down the drive on the PA. So you need the TX meter set for Forward Power rather than ALC.

Step 3. Adjust the VAC TX Gain (audio input) Until you Reach the Desired RF Power Level Out.
For PSK31 or other low wattage digital modes, adjust the VAC TX gain until you hit 35 watts output. On my setup that is about a value of -5. For other higher power digital modes, adjust the VAC TX gain up until you reach the desired RF output level that does not exceed 100 watts PEP.

Step 4. Check to See if you are Over Driving the Radio's AF Input
Now change your TX meter to ALC and you should be well below 0 dB. If you run the VAC TX gain up to 0, you should be very close to 0 db on the ALC TX meter reading and consequently putting out about 100 watts PEP. You never want to exceed 0 dB on the TX ALC meter or your signal will be distorting due to DSP clipping. Peaking at -1 dB is the recommended maximum audio input for digital mode operation.

BTW, if you are operating PSK you need to realize that PSK31 is not pure PSK but has envelope shaping in order to minimize the sidebands. This means that there is amplitude variation along with the phase shift in the carrier. It is a good idea to include some headroom so that the amplitude peaks are not clipping. Setting the VAC TX Gain to produce a ALC level output of something less than -3dB is probably safe.


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced


FLEX-3000/1500 RJ-45 Mic to W2IHY Audio Interface Configuration

0
0
FLEX-3000/1500 RJ-45 Mic to W2IHY Audio Interface Configuration

System Dependencies
Minimum PowerSDR Version: N/A
Applicable Hardware: FLEX-3000 & FLEX-1500

Content provided by: FlexRadio Systems Engineering

The following wiring diagram represents how to wire the modular FLEX-3000 & FLEX-1500 RJ-45 8-pin microphone connector to the W2IHY EQplus and the 8-Band EQ using the 5-pin DIN connector.




NOTE: Connect the GROUND (GND) to the cable shield but do not connect it to the shield of the DIN connector

FLEX-3000/1500 Microphone Pinout Configuration
Pin Number
Function
1 Not Used - Reserved for future use
2 Not Used - Reserved for future use
3 Vcc (+5 VDC)
4 Microphone Ground (mic -)
5 Microphone In (mic +)
6 PTT (PTT +)
7 PTT Ground (PTT -)
8 Not Used - Reserved for future use


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

FLEX-5000 Balanced Line-In to W2IHY Audio Interface Configuration

0
0
FLEX-5000 Balanced Line-In to W2IHY Audio Interface Configuration

System Dependencies
Minimum PowerSDR Version:   N/A
Applicable Hardware:   FLEX-5000 

Content provided by: FlexRadio Systems Engineering & W2IHY 

The following wiring diagram represents how to wire the FLEX-5000 Balanced Line-In (1/4" TRS) and PTT to the W2IHY EQplus and the 8-Band EQ using the 5-pin DIN connector.


NOTE:  Connect the GROUND (GND) to the cable shield but do not connect it to the shield of the DIN connector


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

Remote Operation of PowerSDR Using TeamViewer

0
0
Remote Operation of PowerSDR Using TeamViewer

System Dependencies
Minimum PowerSDR Version: 2.X.0
Applicable Hardware: All FlexRadio SDRs

Content provided by: Harry, W9BR

Having run a remote radio for several years over the internet, I have had many disappointments and achievements through the use of software and hardware interfaces. Surely the very best experiences have been accomplished with my FLEX-5000a. I have run in the past, Kenwood, Icom and a SDR-1000, all remotely. I have built hardware audio interfaces for the hardware radios that had plugged into the mike jacks to provide audio in and out of these radios. The audio has always been a challenge to get the very best quality and the lowest latency. This article describes how to use TeamViewer PC and iPad applications to remote your FlexRadio Systems software defined radio running PowerSDR 2.x

Getting Started with your FlexRadio Software Defined Radio

The Flex product is a PC based user interface (and also a software defined product) using the PC to control the radio and define the filters, etc of the radio. This makes it easy as using a remote desktop product would appear to be the only thing that is required. However, we still need to get the audio connected to the radio. In the past, I have used a VPN connection to my home network, Windows Remote Desktop, and a VoIP product called IPSound. I had a lot of success with it at first, but there are certain anomalies with IPSound that cannot be resolved, and I moved on. IPSound requires a fixed IP address and most people have dynamic addresses.

The greatest success I have had is with a remote desktop product called TeamViewer. TeamViewer is a free product for a non-commercial user and it can be downloaded at www.TeamViewer.com. The other GREAT thing about the TeamViewer product is that recent upgrades to their software provides a VoIP tunnel, right within the product that can be “mapped” to the audio input of the Flex. This allows you to make an audio connection and control the computer with a single product.

You however are required to purchase Virtual Audio Cables from an online store. The VAC product allows you to “patch” audio inputs and outputs from the Flex and your computer audio. It is much like using physical audio patch cables, but they are virtually done in software (thus Virtual Audio Cables). Go to http://software.muzychenko.net/eng/vac.htm purchase the software. PLEASE NOTE THAT THE TRIAL VERSION HAS TEST AUDIO THAT KEEPS REPEATING ON IT AND IT IS NOT USABLE FOR ACTUAL FLEX OPERATION. You need to buy it. I run version 4.08 with no problems. The current version is 4.10.

TeamViewer & PowerSDR Installation and Setup

Download and get TeamViewer free operating on your remote computer. Also download and get TeamViewer running on your local (ham shack) computer. When this process is completed using all of the instructions provided by TeamViewer, you should have an Icon on the bottom right hand side of your tool bar by the clock.



By clicking on the icon, you will get a screen that allows you to sign into the TeamViewer and then log on to your remote computer. Follow their instructions to do this. You can set up a permanent password to easily log in again, or log in automatically when you click one button.



When you have successfully logged in, you now see your remote computer screen, as you can see mine here. You will also see some other programs that I have running in the background that I will explain later. You now can see the PowerSDR screen that you can operate just as you do when you are sitting in front of your PC at home. The only thing you lack now is your audio connections.



Your Virtual Audio Cable program was previously installed ON THE HAM SHACK COMPUTER. Using the instructions provided with that program, create some “virtual patch cords” to patch audio with the VAC program.



I created 4 of them here. All I require to use for the TeamViewer patching is cables 1 and 2. Go to PowerSDR program and select SETUP / AUDIO / VAC…. You should see the following screen. Make sure that the driver is Windows Direct Sound and that the Input is set to Virtual Audio Cable 1 and the output is set to Virtual Audio Cable 2. You can turn on the VAC operation in this window or from the front panel of PowerSDR. Also note that you can set other VAC parameters in this setup window. One of the most important will be the TX and RX gain controls as when you are using VAC, the front panel SDR gain controls for mike audio and receive audio are ignored on VAC.



OK, now let’s get the audio working over the TeamViewer VoIP connection.

In the top window of the local computer, you will see a TeamViewer Tab in the center of the screen. Click on the Audio/Video and then click on VoIP. This produces another small window in the upper right hand side of the screen on the local computer. Now your screen looks like this.



You now need to click on the lower right hand side of this new box where you see an arrow and some script. It will then say audio settings. Click on the “audio settings” and now you have a new box that looks like this:



This new box is where you set the audio input and audio output of the LOCAL COMPUTER.

Now we have to set the audio input and output of the Ham Shack computer. To do this, click OK on the “open audio setting” window (which closes that window) and now click on the same looking audio setting box in the lower right hand side of the HAM SHACK COMPUTER. The screen now looks like this:



You are now seeing the same looking screen on the Ham Shack computer.

Do the same thing. That is SET THE AUDIO INPUT AND OUTPUT OF THE (HAM SHACK) COMPUTER. This has to match the settings in Power SDR VAC. In this case, Virtual Audio Cable 1 is set as the Speakers and Virtual Audio Cable 2 is set as the Microphone. Now last and very importantly, you must click on each one of the computer screens (Local and Ham Shack), “Transmit my Audio Now”. At this point you will hear the Flex audio in the local computer’s selected speakers (headphones) and when you click on the MOX button on the SDR front panel, you will be able to transmit the remote audio. Using a combination of the TeamViewer audio setting screens and the VAC settings in Power SDR, set a comfortable listening and transmit audio without over-driving the input. “Tweak” your audio at the remote site using the EQ settings of the Power SDR and then you should save the settings within your Power SDR favorites (database) as “Remote”. You can listen to you transmitted audio remotely by listening to it using the MON (Monitor) button. However, hearing the latency over the internet will probably produce an echo that is not pleasing for your normal operation. However, it does allow you to set a good transmit level and EQ setting. Sometimes I record a WAV file and play it back using the Flex capabilities and this allows you perfect audio settings.

Some people prefer VOX and this is also possible using the remote set up. Just select VOX and you can let the Flex transmit and receive using VOX. This usually works best for remote operation as it lets the Flex automatically transmit and receive to the transmitted word, rather than when you think you need to go back into receive. With the delay (or latency) of the internet, sometimes it can be seconds, so this way you don’t cut off words when you manually think that you are done with a sentence. Use either operation to meet your situation.

I also had some other things on my desktop that you saw before. I am a huge promoter of the Wavenode WN-2 product www.wavenode.com. In addition to using it to see my Power out, it controls other things. I use it to control the power on/off, Power Amp On/Off, FLEX-5000 on/off, antennas on/grounded, etc. The Wavenode in this screen shows my Wavenode settings and my Power IN and Out. In this example, I am only showing the exciter power in both the in and out of the amp. My FLEX-5000 has a reed relay that I installed across the power control switch of the FLEX-5000, which when operated, by the WN-2 is like pushing the front panel 5000 power switch. A feature that Al Burros of Wavenode added for the Flex users is momentary operation of the soft buttons on the Wavenode PC interface. When you momentarily click on the Flex button, it activates the reed relay in the Flex, which simulates you pressing the front panel switch of the FLEX-5000 for ON or OFF operation. You can also wire up to button “lights” if you want to see what is on or off on the User Interface as the WN-2 has logical inputs. I can see when my SGC power amp fault light has “tripped”.



In this screen shot, I have turned on the SGC amp. It is a perfect companion to the FLEX-5000 and I highly recommend it. It has all of the protection circuits that you require for remote high power operation (it is meant to run in a trunk of a car!!).The SGC-500 has a very easy on/off/reset logic input. That logic input is controlled by the Wavenode WN-2 logic out and when turned on, now can produce as much as 700 watts out, when you use the 16 volt SGC power supply. In mobile use you only get 500 watts at 13 volts. This is very clean RF power. I also run fans on the heat sinks of the SGC continuously when it is turned on.



The other utility that is a must for remote operation is DDUtil by K5FR. This is a tremendous tool to use for automating other things, like antennas, other switching utilities. Etc. Most importantly to me, it clones your FLEX-5000 RS-232 output signal to feed multiple devices, such as antenna switches and my Palstar AT-Auto.

Remoting Your FlexRadio Systems SDR from an iPad

My very latest endeavor has been to use my iPad to control my FLEX-5000. I totally love this operation. The iPad fires up fast, it is very easy to use, and has great audio. The only down side is that the TeamViewer app for iPad does not allow the VoIP tunnel. Therefore you have to use an alternate method of getting the audio to the ham shack computer. I use Skype, and have great audio reports with it!!

Getting Started with the iPad

Do everything on the ham shack computer exactly as explained above. The only difference now is that you must “map” the audio in and out from Skype using the Virtual Audio Cables to PowerSDR.

Download the TeamViewer app from the app store on your iPad. The setup is very straight forward. You will log into your home PC similar to what you do on a PC, but using your iPad. The big difference is that once you set up your preferences and TeamViewer remembers them on the iPad, it is very simple.

Download the Skype app from the app store. You will have to use a different Skype name on the iPad than your home computer. Go to Tools/options/audio settings in the Skype windows. On your home PC, Match the audio settings of the audio output of your radio to the audio input of Skype. MATCH the audio audio input of your radio to the audio output of Skype. My sequence is to go on my iPad Skype first, then call my home machine. After I hear ringing on the iPad, I go to the TeamViewer app on the iPad (do not close the Skype app) by simply hitting the left button on the iPad screen one time and touching the TeamViewer Icon on the iPad screen. Go through the sign on procedure for TeamViewer. When you see your home PC screen, you will see the Skype ringing. Click on the Skype answer button on your home screen. If your VAC is set up right, (the VAC button clicked on your 5000, etc) you should hear audio on the iPad. You can use the built in microphone on the iPad, but the audio may sound “boomy” and needs to be EQ’d.



This is my favorite operating position. It is a bar!!! I am having my beer, waiting on dinner and checking into one of my favorite nightly nets. All done while on the road at my regular job!! Note the ear buds on the bar.
Use a standard set of Apple ear buds with a mike like for an iPhone for good audio.


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

How to use the FM Repeater Mode

0
0
How to use the FM Repeater Mode

System Dependencies
Minimum PowerSDR Version: 2.1.5
Applicable Hardware: All FlexRadio Systems SDRs

Content provided by: FlexRadio Systems Engineering

With the release of PowerSDR v2.1.5, a repeater operation feature or "repeater mode" has been added that enhances the FM mode of operation. When operating FM, you now have the ability to select Simplex mode, where the RX and TX frequencies are the same, or you may select a positive (+) or negative (-) frequency offset that automatically enables the Repeater Mode. These controls are available from the main console when FM mode has been selected. See the area outlined in red in image below.


PowerSDR v2.1.3 Console in FM Mode

In the image above, you will notice in the red square the FM mode specific controls. The three buttons in a row labeled [-] [Simplex] [+] determines if the radio is operating in FM Repeater mode. The field above these controls, RPTR Offset (MHz) is where you enter the frequency offset for the particular band you are operating. In this example, the radio in in FM Repeater mode with a positive frequency offset of 0.600 MHz.

When transmitting in Repeater Mode, you will see the actual transmit frequency displayed in VFO-A, giving you a visual reference to what frequency you are transmitting on.

In this mode of operation there is no need to set SPLIT. If you do set SPLIT to ON, then PowerSDR it taken out of Repeater Mode, the Repeater Mode Offset is no longer being recognized and SPLIT is active, transmitting on the frequency shown in VFO-B.

NOTE: The Repeater Offset is not set automatically based on the receive frequency, so you must determine the whether or not the offset is positive or negative and the frequency of the offset.

For most cases, the offset band plan in the US for 2 meters follows these guidelines. Please verify that this band plan is applicable for the repeaters that you plan to work

The offset is ±600 KHz, the deviation is 5 KHz

At 145.000 through 146.999 MHz, as shown on the Panadapter while receiving,the transmit frequency is 600 KHz below the receive frequency; this is a negative offset.
At 147.000 MHz and above, as shown on the Panadapter while receiving, the transmit frequency is 600 KHz above the receive frequency; this is a positive offset.



This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

Updating the ohci1394.sys Firewire Host Controller System Driver for Windows XP

0
0
Updating the ohci1394.sys Firewire Host Controller System Driver for Windows XP

System Dependencies
Minimum PowerSDR Version: N/A
Applicable Hardware: N/A

Content provided by: FlexRadio Systems Engineering

The ohci1394.sys is the Windows XP system device driver for OHCI (open host controller interface) compliant Firewire host controllers. This driver is the software interface between your Firewire hardware and the Windows XP operating system.

Microsoft has issued several updates that can only be installed using their "hotfix" process. Below are the URLs to the Microsoft Knowledge Base articles describing the problem or condition and where to get the updates to resolve the aforementioned issues.

WARNING!! - These updates can result in an unstable or inoperable system. FlexRadio Systems makes no guarantee or takes any responsibility for these hotfixes or any problems that may result if applied.

!!! USE AT YOUR OWN RISK !!!

Performance of 1394 devices may decrease after you install Windows XP Service Pack 2:
http://support.microsoft.com/?kbid=885222 ohci1394.sys version: 5.1.2600.2549


Performance of 800 Mbit, 1394 devices may decrease after you install Windows XP Service Pack 3:
http://support.microsoft.com/?kbid=955408 ohci1394.sys version: 5.1.2600.3311
This particularly important if your device is a 800 Mbit capable device, 400 Mbit speed will default to 100 Mbit instead.



This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

Sample Rate Synchronization between VAC and Vista/Win7 Sound Devices

0
0
Sample Rate Synchronization between VAC and Vista/Win7 Sound Devices

  System Dependencies
  Minimum PowerSDR Version:     1.X.0  
  Applicable Hardware:    All FlexRadio Systems SDRs  

Content provided by: FlexRadio Systems Engineering

Explanation of the Problem
When transferring an audio stream between two software process such as PowerSDR and a digital mode application using VAC (virtual audio cables) one consideration is sampling rate conversions at different steps in the audio signal path. Ideally your source and destination sampling rates would be the same resulting in no sampling rate conversions. Unfortunately this ideal situation does not exist therefore you must take this process of sample rate conversion into consideration when setting up PowerSDR to transfer audio to a third-party application.

With the introduction of Vista and Win7, Microsoft changed the behavior of sound devices where the user has more control of the low-level parameters and the default sampling rate parameter was set for playing CD music at 44.1 KHz. In addition, the ability to control the low-level parameters from third-party programs like VAC has been limited. The end result of these changes is that Windows is forcing an un-necessary and detrimental sampling rate down-conversion in the PowerSDR<->VAC<->digital mode program signal path which results in additional system resource overhead, added latency and audio artifacts that show up as unwanted sidebands or harmonics that the digital mode sound card program's DSP filtering does not remove.

It is best to illustrate this situation with an example. When operating digital modes, you are transferring audio from PowerSDR to a digital mode program like Fldigi via VAC "cables". It is a common de facto practice to set the VAC sampling rate in PowerSDR to 48 KHz which is a natural multiple of the audio sampling rates PowerSDR operates at normally (48, 96 & 192 KHz). From a operational standpoint, it is much "cleaner" to down or up-convert sampling rates that are even multiples so that audio buffers align on natural boundaries, eliminating buffers that are only partially full of actual audio data. In the case of VAC, the 48 KHz sampling rate is equal to or an even multiple of the possible the PowerSDR audio sampling rates.

The VAC cable which is used to transfer the audio streams between PowerSDR and the third-party digital mode application is a Windows sound device and it will adjust the audio steam parameters (sampling rate, bit depth and number of channels) at each end point of the VAC cable to match the applications audio stream parameters. For example, in PowerSDR if you set the VAC sampling rate to 48 KHz and have the Mono/Stereo check box unchecked, then the audio stream parameters are 48 KHz, 16-bit depth, single channel. The other end of the VAC audio cable that connects to the third-party digital mode application also has audio steam parameters that should be the same as PowerSDR. In this case either VAC or the third-party digital mode application itself will change the characteristics of the audio stream to match the other end point of the VAC cable.

In the case of Fldigi, you can configure its "sound card" settings, which in this case are the audio steam parameters of the connected Windows sound device or VAC cable. Now it gets a little more complicated. The "modems" or the DSP software that performs the modulation/demodulation of a specific sound card digital mode operates at a different sampling rate than that of the connected "sound card. In the case of Fldigi, the modems operate at 8 KHz, which is a multiple of most legal sampling rates and therefore does not usually have problems with partially filled audio buffers. So in the aforementioned example, the following is a representation of the audio stream signal path in regards to the audio steam parameters.

[PowerSDR, VAC I/O: 48 KHz, 16-bit, 1 channel] <-> [VAC Cable-1, end point1: 48 KHz, 16-bit, 1 channel]==[VAC Cable-1, end point2: 48 KHz, 16-bit, 1 channel] <-> [Fldigi Sound card interface: 48 KHz, 16-bit, 1 channel]==[Fldig modem: 8 KHz, 16-bit, 1 channel]

As you can see, ignoring the PowerSDR audio sampling rate, there is only one sampling rate conversion that happens during this process which is "inside" Fldigi at the modem stage. This represents a sampling rate conversion scenario which is about as ideal as you can get.

With Vista and Win7, Microsoft change some of the default behaviors of their sound devices, of which VAC cables are Windows Sound devices, abet they are virtual rather than physical like a sound card.  One of these changes was to set the default audio device parameters of all sound devices to 44.1 KHz, 16-bit, 2 channel (stereo) and VAC can not over-ride the defaults.  The result is an audio stream signal path tha now looks like the following

[PowerSDR, VAC I/O: 48 KHz, 16-bit, 1 channel] <-> [VAC Cable-1, end point1: 44.1 KHz, 16-bit, 2 channel]==[VAC Cable-1, end point2: 44.1 KHz, 16-bit, 2 channel] <-> [Fldigi Sound card interface: 48 KHz, 16-bit, 1 channel]==[Fldig modem: 8 KHz, 16-bit, 1 channel]

As you now see we have three sampling rate conversions instead of one and to make things a lot worse, the conversions are not natural multiples or divisors so we have introduced inefficiencies in the transfer of data at the buffer level.  The result of this operation is the additional system resource overhead, added latencyand audio artifacts that show up as unwanted sidebands or harmonics that the DSP filtering does not remove mentioned above.  All of which is detrimental to the operation of digital modes with PowerSDR and your software defined radio.

So how do we fix this problem?  We do it by changing the default audio parameters of the Windows sound device, which in this case are the VAC cables used to transfer audio to and from PowerSDR and the third-party digital mode programs.

Changing the Default Sound Device Parameter for VAC Cables

The following procedure will describe how to change the default Windows sound device parameter from 44.1 KHz, 16-bit, 2 channels to an optimal configuration for PowerSDR using VAC for audio transfer of 48 KHz, 16-bit 1 channel.

Setting the PowerSDR VAC Parameters

1. Open the VAC setup tab in PowerSDR: Setup->Audio->VAC
2. Set the following VAC Parameters (the other parameters may need to be set specific to the sound card application you are using
a.) Sampling Rate: 48000
b.) Mono/Stereo: The Stereo check box is unchecked

Changing the Default Sampling Rate for a Windows Sound Device

Note: Make sure PowerSDR and any digital mode programs are not running

1. Click on the Windows Start button and Select the Control Panel option
2. Click on the Hardware and Sound category
3. In the Sound sub-category, select Manage Audio Devices
4. In the Playback tab, locate the first VAC cable, it should be labeled as Line 1, Virtual Audio Cable. Right click on it and select Properties from the menu.
5. Click on the Advanced tab
6. Click on the drop down box in the Default Format section.  Select "2 channel, 16 bit, 48000 Hz (DVD Quality)"


7. In the Exclusive Mode section, check both boxes; "Allow applications to take exclusive control of this device" and "Give exclusive mode applications priority".
8. Click on the OK button
9. Repeat steps 5-6 for all of the VAC cables in the Playback tab
10. Select the Recording tab.
11. In the Recording tab, locate the first VAC cable,it should be labeled as Line 1, Virtual Audio Cable. Right click on itand select Properties from the menu.
12. Click on the Advanced tab
13. Click on the drop down box in the Default Format section.  Select "2 channel, 16 bit, 48000 Hz (DVD Quality)"
14. In the Exclusive Mode section, check both boxes; "Allow applications to take exclusive control of this device" and "Give exclusive mode applications priority".
15. Click on the OK button
16. Repeat steps 5-6 for all of the VAC cables in the Recording tab






This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

Different Antenna Configuration Modes for the FLEX-5000

0
0
Different Antenna Configuration Modes for the FLEX-5000

  System Dependencies
  Minimum PowerSDR Version:     1.16.1 
  Applicable Hardware:     FLEX-5000  

Content provided by: FlexRadio Systems Engineering

The FLEX-5000 provides the greatest FLEXibility in being able to configure the RF input and output signal paths in more ways than any other amateur radio. This article will describe some of the different antenna configurations that are possible with the FLEX-5000.

Before we begin our discussion, it is important to remember that the FLEX-5000 is a full duplex software defined radio. This means that the receiver and transmitter are independent of each other and do not share the same filtering components or RF signal paths. The same is true if the second receiver (RX2) is installed in the FLEX-5000. It too is fully independent of the transmitter and receiver circuitry as well, making the FLEX-5000 a true triplex software defined radio.

The FLEX-5000 contains a RF switching matrix called the HFRIO board. The primary function of this component is to route RF signals to the appropriate device for the operation being performed, such as transmitting, receiving or both at the same time. The PowerSDR Antenna Selection form is used to configure the HRFIO switching matrix by assigning different antenna ports to the transmitter and receivers.

There are several different configurations that are available for use with the FLEX-5000. By default, the FLEX-5000 uses the same transceiver port for both transmit and receive. You can also configure the FLEX-5000 to use a RX only receiving antenna that is separate from the transmit antenna.

One unique feature of the FLEX-5000 series of transceivers is that it allows one to easily insert a receive (RX) only device into the RF signal path of the primary receiver (RX1). This capability is referred to as the "RX Loop". When the radio is transmitting, the resulting RF output is not routed through the "RX loop" whereby protecting sensitive receive only devices such as preamps from damaging RF energy. Therefore there is no need for manual switching to take the external receive preamp out of the RF signal path when transmitting.

Since the FLEX-5000 becomes a triplex software defined radio once the RX2 (second receiver) is installed, you will have an additional configuration possibilities specifically for the RX2 that are independent of the RX1/TX and RX Loop configurations shown below. There is the standard RX2 receive only configuration which allows for diversity reception and when used with the HRFIO-34 (or above) board, you can also configure the RX2 in a SO2R mode where you can transmit on the same antenna connector where the RX2 is assigned.

PowerSDR 1.x Antenna Selection Form

The examples below will show how to configure the PowerSDR Antenna Selection form for different modes of operation. In the Antenna Selection form, you can choose two Complexity levels; Simple or Expert. The difference between the two is as follows.
  • Simple - The configuration you set is configured for ALL of the bands.
  • Expert - The configuration you set is configured ONLY for the band displayed.
This setting does not effect the examples below in any way except to determine which band the configuration is applied. Please be aware of this setting when setting your antenna configuration.


Standard Transceiver Antenna Configuration

In the standard transceiver operation mode RF signals are received and transmitted through the same transceiver antenna connector. There are three (3) of these Amphenol SO-239 ports on the FLEX-5000 and they are labeled ANT 1-3. Any one of these three can be selected for transceiver operation. The HRFIO board performs the switching between the ANT 1-3 ports, the receiver and transmitter. The RF signal path is depicted below in Figure 1.

To enable this configuration, open the Antenna Selection form in PowerSDR and assign ANT-1 as the Receiver 1 antenna input and the Transmit output using the antenna selection drop down box. Make sure to check the Lock box to ensure you are transmitting and receiving using the same antenna connector. See Figure 1 for an example of how PowerSDR is configured to use the ANT-1 for both receive and transmit.
   
Figure 1 - Standard Transceiver Mode


Separate RX and TX Antenna Mode of Operation
On the back panel of the FLEX-5000 there are two Amphenol BNC connectors labeled RX1 IN and RX1 OUT. These are multi-function ports depending on how you have them configured in the Antenna Selection setup form in PowerSDR. In the default mode the RX1 IN port can be used to connect a receive only antenna to the FLEX-5000's primary receiver, such as a small receiving loop or a beverage antenna. In this configuration the RX1 OUT connector is not utilized.

You are not restricted to using just the RX1 IN port for a receive only antenna. Since you can assign separate antennas independently to the receiver and the transmitter using any transceiver (ANT 1-3) connector that is not in use by the transmitter can be assigned to either receiver (if RX2 is installed). In this configuration, RF input is routed directly to the receiver via the RX1 IN or ANT1-3 port and the RF output is routed out to one of the three transceiver ports assigned to the transmitter. Refer to the RF signal path block diagram below in Figure 2 for an example of using RX1 IN for a receive only antenna.

To enable this configuration, open the Antenna Selection form in PowerSDR and assign RX1 IN as the Receiver 1 antenna input and ANT-3 as the Transmit output using the antenna selection drop down box. Make sure to un-check the Lock box before making the changes because you are using separate transmit and receive antennas. See Figure 2 for an example of how PowerSDR is configured to use the RX1 IN for receive and the ANT-3 for transmit.
 
Figure 2 - Separate RX and TX Mode using RX1 IN


In the example below, the transceiver port ANT-2 is used exclusively for the receive only antenna and ANT-3 is being utilized for the transmit antenna.
   
Figure 2a - Separate RX and TX mode using ANT-x connectors.


RX Loop Mode of Operation
The RX Loop mode of operation can be used with either the standard transceiver or separate RX/TX mode of operation. When the RX Loop is enabled, the received signals ingress the FLEX-5000 through the antenna port assigned to the primary (RX1) receiver, such as ANT 1-3, but there is an additional RF signal path that is automatically switched in by the HRFIO board which sends the RX signal out of the RX1 OUT BNC connector and it must be fed back into the RX1 IN BCN connector before being sent to the receiver.

This allows you to connect the RX1 OUT connector to a preamp/filter INPUT and the preamp/filter OUTPUT to the RX1 IN connector for routing signals through the "loop" and then to the receiver. Refer to Figure 4 below for a representation of the RF signal path when using the RX Loop.

One additional option you will find useful when using the RX loop capabilities of the FLEX-5000 is the ability to compensate for the additional gain provided by an external preamp.  Adding additional gain to the RF input will skew the RX signal strength reading shown by the Panadapter and on the S meter.  If you know how much gain is provided by the external RX preamp you are using, you can enter it into the Gain adjustment field (box) so that you continue to have accurate signal strength readings.

To enable this configuration, open the Antenna Selection form in PowerSDR and assign ANT-3 as the Receiver 1 antenna input and the Transmit output using the antenna selection drop down box. Make sure to check the Lock box because the transmitter and receiver will be using the same antenna connector. To enable the RX Loop feature, check the box labeled Use RX1 Out to RX1 In Loop. See Figure 3 for an example of how PowerSDR is configured to use the ANT-3 for transmit/receive and the RX LOOP for routing the RX signal through an external preamp.
   
Figure 3 - RX Loop Mode of Operation Using the same Transceiver Antenna Connector

In the example below, ANT-2 is used as the receive only antenna input and ANT-3 is being utilized for the transmitter output with the RX Loop enabled. To enable this configuration, open the Antenna Selection form in PowerSDR and assign ANT-2 as the Receiver 1 antenna input and ANT-3 as the Transmit output using the antenna selection drop down box. Make sure to un-check the Lock box because transmitter and receiver will not be using the same antenna. To enable the RX Loop feature, check the box labeled Use RX1 Out to RX1 In Loop. See figure 3a for an example of how PowerSDR is configured to use the ANT-3 for transmit/receive and the RX LOOP for routing the RX signal through an external preamp.
   
Figure 3a - RX Loop Mode of Operation Using a Different Transmit and Receive Antenna Connectors

NOTE: If you enable the Use RX1 Out to RX1 In Loop option in the Antenna Selection form and there is not an active device or a coax jumper that is routing the receive RF from the RX1 OUT to the RX1 IN ports, you will not receive any signals.

NOTE: The RX1 OUT BNC connector is only active in the RX signal path when the RX Loop feature is enabled.



RX2 Standard Antenna Configuration - Single RX Antenna
The RX2 is an independent fully functional second receiver option for the FLEX-5000. There are several different ways you can assign an antenna port to the RX2.

CAUTION: When transmitting with a separate receive only antenna connected to the RX2, the RX2 is not muted or switched out of the RF signal path. Although the RX2 has a very stout front end, you must take care that you do not overload the RX2 with excessive RF energy which can damage the receiver. Decoupling the receive only antenna when transmitting is highly recommended especially in high RF environments. This condition is applicable for any of the antenna configurations that the RX2 uses, such as when using the RX2 IN and the RX1 IN + RX1 TAP configurations. The RX2 Mute software configuration option is muting only the audio output from the RX2 and not actually turning the RX2 off during transmit. The RX2 is always on no matter what settings are used.

If you do not have a separate receiving antenna for the RX2, the simplest way to utilize the RX2 is the "share" the same antenna that is assigned to RX1 by selecting the RX1 TAP antenna selection. On the HRFIO board, this is accomplished by using a splitter and a preamp or buffer amp to compensate for any induced losses. Using this configuration will allow you to listen to other frequencies on the same band that might exceed the sampling rate reception bandwidth window or to listen to other bands if your antenna is sufficiently multiple band capable. This configuration provides only limited diversity reception capabilities for AM and DSB signals. The RF signal path for this configuration is as depicted below in Figure 4.

To enable this configuration, open the Antenna Selection form in PowerSDR and assign RX1 Tap as the Receiver 1 antenna input and ANT-2 as the Receiver 1 antenna input and the Transmit output using the antenna selection drop down box. Make sure to check the Lock box to ensure you are transmitting and receiving using the same antenna connector. See Figure 4 for an example of how PowerSDR is configured to use the ANT-2 for both receive and transmit and the RX1 TAP for the RX2.
   
Figure 4 - RX2 using the RX1 TAP Antenna Assignment


RX2 Standard Antenna Configuration - Dedicated RX2 Antenna
If you do have a separate receiving antenna for the RX2, then it should be connected to the dedicated RX2 IN BNC connector and configured the same as using the RX1 TAP in the previous example except you assign RX2 IN as the Receiver 2 antenna connector.

Using this configuration will allow you to listen to other frequencies on the same band or to listen to other bands the same as if you were using the single RX antenna configuration listed above, but you have the additional capability for enhanced diversity reception. Using this configuration will allow you to experiment with different diversity reception techniques depending on your antenna configuration to enhance reception by mitigating the effects of fading and to enhance the signal-to-noise ratio.

NOTE: The RX2 antenna configurations are independent of the RX1/TX configurations listed above. You can have any of the configurations listed above as long is there is not a conflict with the association of an antenna port to an RF device (RX1/RX2 or TX).

The following configuration example is going to be a little more complex since we are going to combine using separate antennas for the primary receiver (RX1) and the transmitter, add the RX Loop feature and have a separate receive only antenna for the RX2 to allow for diversity reception. The following The RF signal path for this configuration is depicted below in Figure 4a.

In the example below, ANT-2 is used as a receive only antenna connector for RX1 and ANT-3 is being utilized for the transmit antenna connector with the RX Loop enabled. Additionally, the RX2 IN antenna connector is being assigned to the RX2 for diversity reception capabilities.

To enable this configuration, open the Antenna Selection form in PowerSDR and assign RX2 IN as the Receiver 2 antenna input, ANT-2 as the Receiver 1 antenna input and ANT-3 as the Transmit output using the antenna selection drop down box. Make sure to un-check the Lock box because transmitter and receiver will not be using the same antenna. To enable the RX Loop feature, check the box labeled Use RX1 Out to RX1 In Loop. See figure 4a for an example of how PowerSDR is configured to use the ANT-3 for transmit, ANT-2 for receive and the RX LOOP for routing the RX signal through an external preamp with a separate RX2 antenna connected to the RX2 IN antenna input.
   
Figure 4a - RX2 Diversity Reception Configuration with Separate RX1 and TX Antennas with the RX Loop Feature Enabled.


RX2 SO2R Antenna Configuration

The FLEX-5000 allows you to operate as SO2R with a single radio. This is another first in ham radio for FlexRadio Systems. In order to facilitate a SO2R configuration, you must be able to transmit on either the primary RX1 frequency or the RX2 frequency. This means that the second receiver (RX2) must be able to be assigned to a transceiver antenna port as opposed to a receive only antenna input. This capability exist in the FLEX-5000 only if the HRFIO-34 (or greater) RF switching matrix board is installed in your radio. If your FLEX-5000 has the HRFIO-34 board installed, you can assign the RX2 to ANT-1, a transceiver port. With this configuration, you have the option of transmitting on the same frequency as the RX2 on ANT-1 or transmitting on the RX1 frequency with either ANT-2 or ANT-3.

Building on the example directly above, we will modify the configuration so that the RX2 uses ANT-1 rather than the dedicated receive only RX1 IN antenna port.

In this example, ANT-2 is used as a receive only antenna connector for RX1 and ANT-3 is being utilized for the transmit antenna connector with the RX Loop enabled. Additionally, the ANT-1 transceiver antenna connector is being assigned to the RX2 for SO2R and/or diversity reception capabilities.

To enable this configuration, open the Antenna Selection form in PowerSDR and assign ANT-1 as the Receiver 2 antenna input, ANT-2 as the Receiver 1 antenna input and ANT-3 as the Transmit output using the antenna selection drop down box. Make sure to un-check the Lock box because transmitter and receiver will not be using the same antenna. To enable the RX Loop feature, check the box labeled Use RX1 Out to RX1 In Loop. See Figure 5 for an example of how PowerSDR is configured to use the ANT-3 for transmit, ANT-2 for receive on the primary receiver and the RX LOOP for routing the RX signal through an external preamp with a separate RX2 antenna on the ANT-1 transceiver antenna connector.
   
Figure 5 - RX2 SO2R/Diversity Reception Configuration with Separate RX1 and TX Antennas with the RX Loop Feature Enabled.


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced


Wide Band Decode Capabilities for CW Skimmer with RX2

0
0
Wide Band Decode Capabilities for CW Skimmer with RX2

System Dependencies
Minimum PowerSDR Version: 1.18.3
Applicable Hardware: FLEX-5000

Content provided by: Ed, W2RF / FlexRadio Systems

Many CW Skimmer users have asked for a way to expand the decode bandwidth beyond 24khz with a FLEX-5000. This is possible if you have a FLEX-5000 RX2 (second receiver). Assuming you already have CW Skimmer set up to work with the FLEX-5000 and PowerSDR using the Direct I/Q feature, here is the procedure for configuring wide band decoding for CW Skimmer on 20m:

In this configuration, the frequency of RX2 is fixed at 14.056.000. Changing it requires you to manually change the CW Skimmer LO frequency.

Procedure
PowerSDR Configuration
  1. Use PowerSDR 1.18.3 and above
  2. On the Setup-Audio->VAC page select the option to use the RX2
  3. On the Setup->Audio page, set the sampling rate to 96 KHz and the buffer size to 1024 (for this example)
  4. Set the RX2 VFO frequency to 14.056.000 MHz
  5. Make sure SR (spur reduction) is off

CW Skimmer Configuration
  1. Set the Radio Type to SoftRock (NOT SoftRock-IF)
  2. Set the CW Pitch to 600 (or whatever you use for the PowerSDR Pitch Frequency)
  3. Set the LO Frequency to 14046400 (RX2 freq - 9khz IF freq - 600hz vfo pitch)
  4. Set the Sample Rate to 96khz
  5. Start PowerSDR then CW Skimmer


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

How to use the Memory Form

0
0
How to Use the Memory Form

System Dependencies
Minimum PowerSDR Version: 2.1.5
Applicable Hardware: All FlexRadio Systems SDRs

Content provided by: FlexRadio Systems Engineering

An enhanced Memory form that incorporates new features and supports the new FM Repeater mode of operation is available with PowerSDR v2.1.5. The new Memory form (or window) is designed primarily for FM mode, but can be used with any mode. A representative screen shot of a populated Memory form is shown below.

PowerSDR Enhanced Memory Form
(Click on the image to display a higher resolution version)

As you see, each memory form record consists of different data fields. The table below describes each memory channel field in the memory channel entry.

Memory Form Field Description
Group This is a "free form" field that you can categorize memories based on user defined group name
RX Frequency This is the receiver frequency for VFO-A
Name This is the name of the memory that is displayed in the Channel drop down box on the console when in FM mode
DSP Mode This defines the Mode of operation for the memory entry. All PowerSDR modes are valid and selectable using the drop down box
Tune Step This defines the Tune Step value for the memory entry. All PowerSDR Tune Step values are valid and selectable using the
drop down box
RPTR (Repeater mode) This determines if the radio is operating in simplex or Repeater mode. High, Low and Simplex values are valid and selectable
using the drop down box
RPTR Offset This defines the Repeater offset frequency in MHz. Valid only in FM mode
CTCSS This check box determines if a CTCSS tone is added when transmitting. Valid only in FM mode
CTCSS Freq This defines the CTCSS frequency or sub-audible tone in Hz transmitted. Valid only in FM mode
Deviation This determines the transmit frequency deviation selectable using the drop down box. Valid only in FM mode
Power This determines the transmit power in watts. Valid values are 0-100
Split This determines if the radio is in SPLIT mode. If this option is selected, the radio is automatically taken out of Repeater mode and
put into SIMPLEX mode. Refer to the KB article How to Use FM Repeater Mode for additional information.
TX Frequency This defines the transmit frequency. It is a user defined value that is valid only in the simplex mode of operation.
The default value is the RX frequency unless you are copying data from VFO-A to memory when the radio is in Split mode and the
TX frequency is different than the RX frequency
RX Filter This determines the defined RX filter specific for the DSP mode. NONE is the only valid option for FM mode
RX Filter Low This displays the RX filter low cut point. It does not define the RX filter low cut value in FM mode
RX Filter High This displays the RX filter high cut point. It does not define the RX filter high cut value in FM mode
Comments This is a "free form" field that you can add comments specific to the memory channel
AGC Mode This defines the AGC setting. The AGC setting is selectable using the drop down box
AGC-T This determines the AGC Threshold for the memory channel. Valid values are 0-100


Getting Started with Using Memory Channels

To open the Memory form, select Memory from the PowerSDR menu bar.

There are several operations that can be performed to add, delete, manage and select a memory (or memory channel). The following sections will describe these operations in greater detail.


How to Add a Memory Channel

Adding a memory channel to the Memory database is easy. It will take the currently configured parameters on the PowerSDR console and store them as a memory channel "record" that can be recalled later.

  1. Open the Memory Form from the PowerSDR menu bar by left clicking on it
  2. Left click on the ADD button at the bottom of the Memory form
  3. A new memory channel will be added to the memory form at the bottom.
  4. At this point you can customize or change values in the new memory channel. Changes you make to the memory channel record are automatically saved to the database so there is no need to do anything to save the changes
Adding a Memory Channel
(Click on the image to display a higher resolution version)


How to Select a memory Channel form the Memory Channel Form
Once you have created a memory channel using the ADD feature, you can recall or Select the memory channel which is change the PowerSDR operating mode to the parameters defined in the memory channel. There are two ways to select a memory channel from the Memory database. You can select the memory channel directly from the Memory form or you can select the memory channel from the PowerSDR console when operating in FM mode. This example selects the memory channel from the Memory form.

  1. Open the Memory Form from the PowerSDR menu bar by left clicking on it
  2. Left click on the SELECT button at the bottom of the Memory form
  3. The information in the memory channel will be transferred to the PowerSDR console
Selecting a Memory Channel from the Memory Form
(Click on the image to display a higher resolution version)


How to Select a Memory Channel from the PowerSDR Console

As noted above, there are two ways to select a memory channel. The following example demonstrates the second way of selecting a memory channel by using the option in the PowerSDR console when operating in FM mode.

  1. From the PowerSDR console, select the FM mode
  2. In the FM mode specific control area on the console left click on the Channel drop down box
  3. A listing of all memory channels will be displayed (see screenshot below).
  4. Left click on the memory of your choice. In the example below the SkyWarn memory channel is being selected.
  5. The information in the memory channel will be transferred to the PowerSDR console

Selecting a Memory Channel from the PowerSDR console
(Click on the image to display a higher resolution version)


How to Copy a Memory Channel

If you want to make a copy of an existing memory channel to use as a starting point or template for creating a new memory channel, you do this by executing the following procedure.

  1. Open the Memory Form from the PowerSDR menu bar by left clicking on it
  2. Using your mouse, left click on the far left hand side of the memory channel you want to use as the source information. The memory record will highlight and there will be a right pointing triangle in the far left hand side indicating that the memory channel has been selected.
  3. Left click on the COPY button at the bottom of the Memory form
  4. A new memory channel will be added to the memory form at the bottom.
  5. At this point you can change values in the new memory channel to create a new unique memory channel. Changes you make to the memory channel record are automatically saved to the database so there is no need to do anything to save the changes.
How to Sort Memory Channels

You can change the sort order of the memory channels by simply clicking on the column header.

Left clicking on the memory column header once will display asmall upward pointing triangle indicating that the column is sorted inascending order from top to bottom. Left clicking on the column header again willdisplay a small downward pointing triangle indicating that the column issorted in descending order from top to bottom.

How to Delete a Memory Channel

You can delete unwanted or un-needed memory channels by using the Delete feature in the Memory form.
  1. Open the Memory Form from the PowerSDR menu bar by left clicking on it
  2. Using your mouse, left click on the far left hand side of the memory channel you want to delete. The memory record will highlight and there will be a right pointing triangle in the far left hand side indicating that the memory channel has been selected.
  3. Left click on the DELETE button at the bottom of the Memory form
  4. A confirmation dialog box will appear asking you "Are you sure you want to remove the selected row(s)?". Left click on YES to delete or NO to abort this operation
  5. If you clicked YES, the memory channel was removed from the Memory database.

Modifying Data in a Memory Channel

Once you have a memory channel defined, you can change any of the data fields on the memory channel record. Note that if you change the value of one field, that it does not necessarily update other fields in the memory channel record. As an example, if you change from Simplex to Repeater mode with a positive 0.600 MHz offset, the TX Frequency is not updated to reflect a TX frequency that is 0.600 MHz greater than the RX Frequency.




This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

How to Install or Upgrade the FLEX Firewire Driver

0
0
How to Install or Upgrade the FLEX Firewire Driver

System Dependencies
Minimum PowerSDR Version: 1.10.0
Applicable Hardware: FLEX-5000 & FLEX-3000

Content provided by: FlexRadio Systems Engineering


UPDATE: This procedure is no longer necessary when using PowerSDR 2.0.22 and above as the Firewire driver installer is integrated into the PowerSDR installer.

The FLEX family of Firewire-based software defined radios communicates with your personal computer running Windows XP, Vista or Windows7 via a Firewire (IEEE-1394) connection. Like any piece of hardware that communicates with Windows, a hardware or device driver is required. The Firewire enabled FLEX family of software defined radios is no exception. Before starting this procedure, you will need to download the current version of the FLEX Firewire driver to the computer that is connected to the SDR hardware. You can obtain the latest FLEX-5000/3000 Firewire driver from a link on the FlexRadio Systems home page.

NOTE: The FLEX software defined radio *MUST* be completely turned off or disconnected from your computer before starting this procedure. You will be instructed when to connect or turn on your FLEX software defined radio in the procedure below.

NOTE: The FLEX Firewire driver, version 3.4.0.x and above the driver installed package contains both a 32-bit and a digitally signed 64-bit kernel mode device driver, therefore the FLEX Firewire driver will work with *all* versions of 64-bit Windows without requiring any special operating modes, such as disabling the Windows x64 driver signing requirement.

REQUIREMENT: All hardware or device drivers, including the FLEX Firewire driver, must be installed with user rights of administrator under Windows. Not all user accounts have these elevated rights, especially the defaualt accountes in Vista and Windows7. If you install the FLEX Firewire driver on these operating systems and you are not absolutely certain that your login account has the required elevated rights to properly install the driver, then you need to use a feature of these operating systems to install or run a program with full administrator rights.

To do this, right click on the FLEX Firewire installed program and select the option "Run as Administrator". If your user login does not have sufficient rights, you will be prompted to provide user credentials (password) for the administrator account to continue installing the FLEX Firewire driver. For Windows operating systems with UAC (User Account Control) enabled, make sure you answer affirmatively (Yes) for any and all prompts during driver installation.


Upgrading the FLEX Firewire Driver

If you are upgrading to a new version of the FLEX Firewire driver, you must follow the procedure outlined below in order to make sure that the old driver is completely removed from your system before the new updated driver will install properly.

Step 1
. Turn off the FLEX software defined radio hardware by powering it down completely.

Step 2.
Uninstall the existing FLEX Firewire driver. The driver can be uninstalled using the uninstall menu option in the FlexRadio Systems application folder or by using the Add or Remove Programs option in the Windows Control Panel. Make sure the FLEX software defined radio is turned off along with PowerSDR before uninstalling the Firewire driver.

Step 3.
Reboot your computer. This assures that the drivers are completely removed from memory.

Step 4.
Follow the procedure, Installing the FLEX Firewire Driver below for installing the new Firewire device driver.


Installing the FLEX FireWire Driver - For Windows XP, Vista & Win7
The directions below will instruct you how to properly install the FLEX Firewire driver for the Firewire-based FLEX software defined radios. The screen shots used in the procedure are from a Windows XP operating system. The screens will look a little bit different when installing on Windows Vista and Win7 due to the way Vista and Win7 renders dialog boxes, but the window content is identical. Also, the FLEX Firewire driver version numbers will be a bit different too.

Step 1.
After downloading both PowerSDR and the FLEX FireWire driver to your computer from the FlexRadio Web site (you can get the driver from the FlexRadio Systems home page), install or load the FLEX FireWire device driver software to your computer first. Once the FLEX FireWire device driver is fully installed, then you will enable it by powering up the FLEX software defined radio.

Before we start, it is always a best practice to to close down any running applications before installing any type of hardware device driver. Open applications may inadvertently interfere with the proper installation of the Firewire device driver.


NOTE: The FLEX software defined radio *MUST* be completely turned off or disconnected from your computer before starting this procedure. You will be instructed when to connect or turn on your FLEX software defined radio in the procedure below.

Open up the folder where you downloaded the FLEX FireWire driver. Either double left click or right click on the FLEX Firewire driver installation icon and select Run as Administrator to start the driver installation.




Step 2. After the FLEX Firewire driver Setup Wizard is displayed, left click on NEXT to begin the driver installation.




Step 3. After clicking the NEXT button, the Select Destination Location screen is displayed. It is recommended that you use the default location of C:\Program Files\FlexRadio. Left click on NEXT to continue.




Step 4. After clicking the NEXT button, the Select Additional Tasks screen is displayed. If you do not want the FLEX Firewire Control Panel icon on your desktop, un-check the “Create a desktop icon” option. It is highly recommended that you place a FLEX Firewire Control Panel icon on your desktop. You will use this control panel to manage your software defined radio. Left click on NEXT to continue.




Step 5. After clicking the NEXT button, the Ready to Install screen is displayed. Verify that the options selected in the previous two steps are correct. If not, left click on the BACK button to change any of the incorrect options. Left click on NEXT to continue.




Step 6. After clicking the NEXT button, the Installing screen will be displayed. A Software Installation warning may also appear (if not, skip to Step 7). This warning is displayed because the hardware driver has not passed the formalized Windows Logo Testing program, which is not an issue as most hardware drivers are not Windows Logo certified. The FLEX Firewire driver has been extensively tested and will not destabilize or impair your system. Left click on Continue Anyway to proceed.




Step 7. After the file transfer is complete, the Completing the FlexRadio Setup Wizard screen will be displayed and you will be prompted to reboot your computer. Please select the option, Yes, to restart the computer now.

Before left clicking on the FINISH button, make sure that your FLEX Firewire-based software defined radio is powered off. THIS IS VERY IMPORTANT. You must complete the driver installation before powering on the FLEX software defined radio.

Once you have verified that the FLEX software defined radio is not powered on left click on the FINISH button to reboot the computer.




Step 8. After your computer has completely rebooted, power on your FLEX software defined radio by pressing the power button.

Windows Vista and Win7 Installation Procedure Deviation: Windows Vista and Win7 performs Steps 8 - 13 without any user intervention or displaying installation status dialog boxes. If you are installing on Windows Vista or Win7, skip to Step 14.

The following steps are applicable to Windows XP only:

The Found New Hardware Wizard dialog box is displayed once Windows XP discovers that the FLEX software defined radio, a new piece of hardware, has been connected. Select the option, No, not this time when you are prompted to use Windows Update to search for software. Left click on the NEXT button once you have made the proper selection to continue.




Step 9. The Found New Hardware Wizard will recognize that you are trying to install a FlexRadio FLEX software defined radio. Depending on the model of radio attached to your computer, the driver will properly identify the specific FLEX software defined radio you are installing. In the example above, the radio is a FLEX-5000. Select the option, Install the software automatically (Recommended), and left click on the NEXT button once you have made the proper selection to continue.




Step 10. After clicking the NEXT button, the Found New Hardware Wizard screen will be displayed momentarily.



Then a Hardware Installation warning may be shown. This warning, like the one in Step 6 is displayed because the hardware driver has not passed the formalized Windows Logo Testing program. Left click on Continue Anyway to proceed.




Step 11. After clicking the Continue Anyway button, you will observe the driver files being installed. See the screen below.




Step 12. After the driver files are installed you will see the Completing the Found New Hardware Wizard dialog box to indicate that the wizard has finished installing the software for the FlexRadio FLEX software defined radio. Left click on the FINISH button to continue.




Step 13. The FlexRadio Systems FLEX Firewire driver has three (3) sub-driver components. The first sub driver, the FlexRadio Systems FLEX-xxxx core driver component was just installed in steps 8 - 12. There are two additional sub-driver components that must installed to complete the driver installation process.

NOTE: After the FlexRadio Systems FLEX-x000 core driver component completes, repeat steps 8 - 12 for the two (2) FlexRadio MIDI drivers. You will install a total of three (3) sub-driver components. Do NOT stop installing the FLEX Firewire sub-drivers until all have been loaded.

After all of the sub-drivers have been properly installed, You should see a prompt in the bottom right had corner of your display that indicates that your new hardware is ready to use.

Step 14. The last step is to verify that the FLEX software defined radio is properly communicating with your computer. During Step 4, you should have instructed the driver installer program to place a FLEX Firewire icon on your desktop.


The FLEX Firewire Console icon may or may not look like the icon pictured to the left depending on your driver version, but will have the label
"FlexRadio".

Double click on the FlexRadio icon to display the FLEX Firewire Control Panel. If the driver was properly installed, you will see the name of your FlexRadio Systems FLEX software defined radio in the Device Description text box. If the driver is not installed properly or the FLEX software defined radio is either not connected or turned off, you will receive a Device Not Found error message when you start the FLEX software defined radio.







This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file. You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced

FLEX-5000 & FLEX-3000 EEPROM / Firewire Diagnostic Tool

0
0
FLEX-5000 & FLEX-3000 EEPROM / Firewire Diagnostic Tool

System Dependencies
Minimum PowerSDR Version:
N/A
Applicable Hardware: FLEX-5000 & FLEX-3000

Content provided by: FlexRadio Systems Engineering

The Windows executable available for download below is a diagnostic tool that can be used to verify that your FLEX-5000 / FLEX-3000 Firewire device driver is loaded properly and you computer is properly communicating with the FLEX-5000/3000 transceiver. There are two procedures documented here
  • Reading EEPROM Data From the FLEX-5000 or FLEX-3000
  • Exporting EEPROM Data to a CSV File
CAUTION: There is also an IMPORT function for importing data from a CSV file into your EEPROM. Do not use this feature unless you are 100% certain that the data you are importing is compatible with your radio or explicitly instructed to do so by the FlexRadio Development Team. Importing invalid data could possibly lead to EEPROM data corruption that can only be remedied by sending in your radio to the Service and Repair Department for repair. Correcting this problem would not normally be covered under warranty repair. CAVEAT UTILITOR!

Reading EEPROM Data From the FLEX-5000


To use the FLEX-x000_EEPROM_Tool to read EEPROM data, use the following instructions:
  1. Download the FLEX-x000_EEPROM_Tool.exe file from the FlexRadio web site (See associated links below)
  2. Turn on the FLEX-5000 or FLEX-3000
  3. Double left click on the executable file, FLEX-x000_EEPROM_Tool.exe 
  4. Select the proper model of SDR in the upper left hand box
  5. Then click on the READ button to query the EEPROM data.
If your computer is properly communicating with the FLEX-5000/3000, then a screen will be displayed showing the current SDR model, and the serial number and revision numbers for installed hardware components (uninstalled hardware will be grayed out):
  • Transceiver Board (HTRX)
  • Antenna Tuning Unit (ATU)
  • Second Receiver (RX2)
  • Power Amplified (HPA)
  • Radio Frequency I/O (RFIO)
  • 2 meter transverter (XVTR)


If your computer is not properly communicating with the SDR hardware, then an error screen will be displayed like the one shown below.




Exporting EEPROM Data to a CSV File


To use the FLEX-5000_EEPROM_Reader to export EEPROM data, use the following instructions:

  1. Download the FLEX-5000_EEPROM_Tool.zip file from the FlexRadio web site (See associated links below)
  2. Turn on the FLEX-5000 or FLEX-3000
  3. Double left click on the extracted file, FLEX-5000_EEPROM_Tool.exe 
  4. Select the proper model of FLEX-5000 in the upper left hand box
  5. Then click on the EXPORT button to query the EEPROM data.
  6. The button will turn RED and the application will loose focus (grayed out) while the EEPROM data is being read and the CSV (comma separated values) file for 45-60 seconds.
  7. When complete the EXPORT button will revert back to the original color and the program will come back into focus.
  8. Once completed, there will be a CSV file in the folder from which you ran the program. It will have a file name like xxxx-xxxx.csv where xxxx-xxxx is the radio's serial number.

The file will have a series of hexadecimal values written out. This file can be used by FlexRadio Software Development Team to diagnose possible EEPROM data integrity issues.


This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

FLEX-x000 EEPROM Tool

Selecting High Performance Firewire Cards for FlexRadio Transceivers

0
0
Selecting High Performance Firewire Cards for FlexRadio Transceivers

  System Dependencies
  Minimum PowerSDR Version:     N/A  
  Applicable Hardware:     Any Firewire based SDR  

Content provided by: FlexRadio Systems Engineering

If you are considering using a non-motherboard Firewire host adapters for the FLEX-5000, FLEX-3000 or the SDR-1000 using a Firewire based sound card, look at "high end" DV certified Firewire host adapters. These will provide the best performance and compatibility. Many, but not all motherboard integrated Firewire host adapters are not well suited for real-time audio applications because they share IRQs with many other integrated devices, such as USB ports. Sharing IRQs with other devices induces unwanted latency and has been known to cause audio drop outs.

NOTE: A lot of poor performance and audio drop outs and freeze up problems have been resolved by switching from using the motherboard Firewire interface to one that is installed in the computers peripheral bus (PCI, PCI-E, PCMCIA or ExpressCard)

Cautionary Statement: It has come to the attention of FlexRadio Systems' Support that Firewire card manufacturers are changing chipsets without notice. Some of these chipset substitutions are ones that are not fully compatible with the FLEX Firewire driver. While we try to keep this list accurate ad up to date, it is in the buyer's best interest to verify the chipset utilized in a particular card before purchasing it.


Helpful Hints:
  • Use a card that is specifically "approved" for DV editing packages. These cards have better stability (free of jitter) and performance than other Firewire cards.
  • It is recommended that the card you get is using an up to date TI or Lucent AGERE FW323 chipset. Some manufacturers are starting to change to VIA for cost reasons. Other chip sets, such as VIA may work fine, but the TI and Lucent products seem to be the most compatible.
  • For one of these cards, you are going to pay between $15 to $80 (USD) depending on the bus type.
  • Do not use a Firewire card that also has USB or any other interface ports integrated on the same card (aka a "combo" card). These are not designed to be high throughput devices are are not best suited for using with FlexRadio Systems' FireWire based transceivers.
  • Do not use Firewire cards that are combo 1394a and 1394b host controllers unless you are using Windows 7. The 1394b host bus adapters do not have native support under Windows XP and Vista.
  • If your motherboard has a specialized PCI slot for communications (usually it is orange), install your Firewire adapter in that slot. These slots usually do not share IRQ (system interrupts) with other motherboard peripherals.
  • If your motherboard has a PCI Express 1x slot, this is the best bus type for a Firewire host controller since it does not share interrupts with other motherboard peripherals.
  • Use high quality Firewire cables with multiple shields and gold connectors. Also use the shortest cable possible.
  • If you have an existing Firewire port on your computer, try it out first before buying a different Firewire controller.
  • Buy your Firewire card at a local retailer. If it doesn't work you can easily return it.

Firewire Cards Reported *not* to work well with FlexRadio Transceivers:
  1. Adaptec FireConnect 4300 card
  2. Any Adaptec PCMCIA based cards
  3. SYBA-PCI-Express 1x 1394A model SD-PEX-NEC4F
  4. StarTech PCI-1394B_3
  5. StarTech PEX-1394A2 PCI-Express Card
  6. Best Connectivity / Syba SD-PEX30009 (in newer i5 and i7 PCs)

NOTE: There have been numerous reports of laptop Firewire ExpressCards not working with Windows. The FLEX Firewire drivers appears to load correctly and is recognized by the software, but does not properly send data between the FLEX hardware and the laptop. This problem is most common on Vista operating systems, but has been reported on XP too.

Firewire Cards Reported to work well with FlexRadio Transceivers:

DISCLAIMER: The Firewire cards listed below are ones used by FlexRadio owners successfully with Firewire based sound cards (SDR-1000) and native Firewire SDRs such as the FLEX-5000A and FLEX-3000. These cards may no longer be available from their respective manufacturers nor are they qualified or endorsed component by FlexRadio Systems. FlexRadio makes no claim to their compatibility with your specific system (PC) and the cards are not directly supported by FlexRadio Systems. Caveat


Syba  (http://www.syba.com/)

Model or Description: Firewire 1394a 3+1 controller
Bus Type: PCI

Recommended for the FLEX-5000A/3000 - Uses the Lucent AGERE FW323 chipset
  • Confirmed to work with FLEX-5000 on Windows XP-Professional
 
 


Best Connectivity - A division of Syba Technologies, Ltd.
(http://www.syba.com/)

Model or Description: Express Card
Bus Type: ExpressCard (34 mm)
  • Confirmed to work with the FLEX-5000 on Windows XP-Professional
 
  • Texas Instrument Firewire Chipset XIO2200 Chipset
  • 2-ports FireWire 1394a with 400Mb/s
  • Compliant with ExpressCard/34 standard
  • IEEE 1394-1995 Standard compliant, for High Performance Serial Bus and P1394A Supplement 4.0
  • 1394 OpenHCI Specification V1.0 and V1.1 compliant
  • Data transfer rate: 100/200/400 Mbps
  • Fully plug & play and hot plug supported
  • For Windows 98SE/Me/2000/XP/XP 64-bit/Vista/Win7 


Model or Description: PCI 1394a/b Firewire card
Bus Type: PCI
  • Confirmed to work with the FLEX-5000 and FLEX-3000 on Windows7
 
  • Firewire 1394b ports x 2
  • Firewire 1394a port x 1
  • Transfer rate up to 800Mb/s
  • Support 32-Bit 33MHz PCI Interfacing
  • Compliant with 1394 OpenHCI Specification V1.2
  • Full Backward compatible to FireWire 400 1394a specification
  • Support 800/400/200/100Mb/s data transfer rate
  • TI Chipset


ADS Pyro
(http://www.adstech.com/)

Model or Description: PCI 64R2 or ADS Pyro PCI 64
Bus Type: PCI (64-bit)

Note: The ADS PYRO PCI 64R2 has replaced the ADS Pyro PCI 64
  • Confirmed to work with FLEX-5000 on Windows XP-Professional
  • Confirmed to work with FA-66 on Windows XP-Professional
 
  • TI Chipset


SIIG
(http://www.siig.com/)

Model or Description: PCI 1394a Firewire card
Bus Type: PCI

Many of their FireWire host controllers use the TI chipset. Below is a representative picture of a 1394a PCI host controller.
  • Confirmed to work with FLEX-5000 on Windows XP-Professional
   


Model or Description: PCI-E 1394a Firewire card
Bus Type: PCI-E
  • Confirmed to work with FLEX-5000 on Windows XP-Professional
   


Sonnet
(http://www.sonnettech.com/)

Modelor Description:
Allegro Express FW400 (FW400-E)
BusType: PCI-E
  • Confirmed to work with FLEX-5000 on Windows XP-Professional and Vista

  • TI Chipset
  • External power connector for powered devices
  • Three (3) 1394a 6-pin connectors (2 external/1 internal)
  • RoHS Compliant


Inland Products
(http://inlandproduct.com/)

Modelor Description:
Pro PCI-E
Bus Type: PCI-E 1x
  • Confirmed to work with FLEX-5000 & FLEX-3000 on Windows 7
 
  • Two external and one internal 1394a connectors
  • TI chipset
  • Supports data transfer rates of 100,200 and 400 Mbps
  • Built-in 4-pin power connector for receiving extra power supply

Dynex
(http://www.dynexproducts.com/)

Model or Description: PCI-E 1394a/b Firewire Card
Bus Type: PCI-E
  • Confirmed to work with FLEX-5000 & FLEX-3000 on Windows 7
 
  • Supports IEEE P1394b and backward-compatible with 1394a-2000 and 1394-1995 standards
  • 2 port Firewire 800 ports (1394b)
  • 1 port Firewire 400 port (1394a)
  • Built-in 4-pin power connector for receiving extra power supply


SUNIX
(http://www.sunix.com.tw/)

Model or Description: PCI 1394a Firewire card
Bus Type: PCI (64-bit)

These cards are DV qualified and known to use the TI chip set.
  • Confirmed to work with FLEX-5000 on Windows XP-Professional
  • Confirmed to work with FA-66 on Windows XP-Professional
 
 


Micro Innovations
(http://www.mi-products.com/)

Model or Description: PCI 1394a Firewire card
Bus Type: PCI
  • Confirmed to work with FLEX-5000 on Windows XP-Professional
 
 


Belkin
(http://www.belkin.com/)

Model or Description: FireWire 1394a ExpressCard
Bus Type: ExpressCard (34 mm)
  • Confirmed to work with the FLEX-5000/3000 on Windows XP-Professional
 
  • Delivers single-lane (x1) PCI Express throughput support rates of 2.5Gbps
  • Complies with ExpressCard 34mm-wide module specification
  • Built-in 2 external, independent 6-pin FireWire 400 ports
  • Supports 1394 Open Host Controller Interface (OHCI) Specification 1.1
  • Features IEEE 1394a-2000-compliant ports at 100, 200 and 400Mbps
  • Equipped with 1 DC jack for using power adapter to provide 12VDC power output
  • Complies with IEEE 1394 and 1394a
  • Allows you to connect/disconnect devices without powering down the system (hot-swappable)



This KB article may reference additional files that are available on the FlexRadio Systems web site Downloads page. Please use the URL(s) below to download the referenced materials.

An Adobe Acrobat Reader may be required to open the file.You can download Adobe Acrobat from here.

KB Source Document(s):

None Referenced


Viewing all 66 articles
Browse latest View live




Latest Images