From HPSDRwiki
Revision as of 16:09, 2 December 2009 by VK2NRA (Talk | contribs) (HERMES: move image out of box)

Jump to: navigation, search

The HPSDR Project

Q. I have a question that is not covered in this FAQ. How/who do I ask?

A. After searching for an answer and not finding it, usually the best way is to post your question on the HPSDR Discussion List (reflector). This allows two things to happen: (1) it permits someone other than the very busy developers to answer he question if they can, and (2) it allows everyone on the list to gain the benefit of any reply.

Q. How do I get in direct email contact with project leaders?

A. The project leaders are active on the HPSDR Discussion List and you may contact them by posting a message to the list.

Q. What is the status of the various boards or modules?

A. Here's the scoop on some as of May 23, 2009:

  • ATLAS - in production, order through http://tapr.org
  • PINOCCHIO - in production, order through http://tapr.org
  • OZY - 1st production run - Sold out - PCB are available. Order through http://tapr.org
  • JANUS - 1st production run - currently being shipped. Order through http://tapr.org
  • MERCURY - 1st production Order through http://tapr.org
  • MERCURY-EU - alpha - see Gerd, DJ8AY
  • PENELOPE - 1st production run - Sold Out - PCB are available Order through http://tapr.org, available from Gerd, DJ8AY
  • LPU - in production - available in kit form. Order through http://tapr.org
  • ALEX - Pre-production
  • PENNYWHISTLE - Pre-production
  • EXCALIBUR - Pre-production
  • PANDORA - Pre-production

All others - in various stages of design/development -- see their wiki pages or the HPSDR website.

Q. What modules would I need to get a working HPSDR transceiver on the air?

A. It is important to remember the goals of HPSDR. All modules are not meant to be combined together to make a “single flavor” HPSDR transceiver. A number of different combinations will be possible (examples: Horton or Mercury for the receiver). How the modules are used and combined are in the hands of the experimenter/builder. Some users may not even wish to make an entire transceiver out of the modules (example: SDR1000 owners who only want to use Atlas, Ozy, and Janus to replace their sound cards).

In the words of Phil Covington, project leader for a number of the modules, “HPSDR was not formed to be a manufacturer of finished Ham Radio equipment. Its primary purpose is to develop a High Performance SDR in a modular fashion by experimentation with various methods.”

If your only goal is to get “on the air” with an SDR transceiver, there may be cheaper and/or easier routes to achieve this goal (Softrock or Flexradio).

If your goal is high performance software defined radio with a “roll your own” mentality, then the HPSDR modules should enable the creation of your own high performance SDR transceiver.

Q. Will the modules be offered in kit or assembled form, and what about cost?

A. Atlas and Pinocchio are offered as a bare board and kit of parts. Ozy and Janus are offered either bare board or assembled and tested. A hard to get partial parts kit is being offered or Janus. Future module costs to be determined.

Q. Will Ozy and Janus "bare boards" be available?

A. Bare boards (not kits of parts) are available through TAPR.

Q. Why doesn't TAPR offer a kit of parts or at least the hard to obtain parts for Ozy or Janus?

A. A partial kit of harder to obtain parts is being offered for Janus. Potential users may certainly get together for a group buy on other parts needed to complete the boards. There are several reasons for TAPR (or HPSDR) not offering complete kits: (1) being an all-volunteer organization, it would take tremendous manpower to break the parts down to individual kits and package them, (2) there is a very large support problem for kit builders whose boards do not work when completed, and (3) the cost of a kit of parts would be about equal or may exceed the cost of an assembled and tested board.

Q. Will the Gerber files (PCB artwork) be available for anyone's use?

A. Yes. They are released under the new TAPR open source hardware license called OHL. The board designer may restrict to non-commercial use. The OHL license was finalized and approved in May 2007. For License information see Open hardware license or Non-Commercial hardware license. The Schematics, Gerber files and Bill of Materials (BOM) area available of the Support webpage.

Q. Why not put OZY and JANUS on a single board?

A. The overall HPSDR project design philosophy has been to partition the design into modules small enough to allow experimentation with part and design changes and to be able to put together a system meeting individual needs. Putting the ADC chip with associated circuit on the Janus board allows a future (and hopefully better) chip to be used on a similar board, but keeping Ozy for the interface and control. Flexibility is the goal.

Q. How much better will the Ozy-Janus combination be in terms of performance when used with the SDR-1000 in place of a sound card such as the Delta 44?

A. To be determined -- but of course, we expect better results. There are some preliminary results on the wiki and in the discussion list.

Q. Will a Ozy-Janus-Atlas combination work with my PowerSDR software used for my Flex Radio SDR-1000 in place of a sound card in my PC?

A. Yes, that was one of the early goals of the HPSDR group. Phil, VK6APH, did confirm with Gerald and Eric at the Flex-Radio meeting at the Dayton Hamvention 2007 that Ozy/Janus will be fully supported in future releases in their 'mainstream' releases of PowerSDR. Bill, KD5TFD, will be working with Eric from Flex to accomplish this. At this point it is not known exactly when, and what version the support will begin, but it will happen. Direct all questions regarding Janus/Ozy to the HPSDR Discussion List (and NOT the Flex-Radio list), as folks have been doing and admirably responding. The arrangement with Flex-Radio required the donation of a working Ozy/Janus to Flex-Radio and this has been accomplished after TAPR approved the expense.

Q. What will be an appropriate software for companions like Janus + Ozy + Phoenix + (Alex??) ?

A. These boards, and also with the addition of Mercury, will run using PowerSDR. --Phil VK6APH

Q. Is the HPSDR project going to use Windows or some flavor of Linux?

A. Yes! (Eventually both, that is...but, currently, the supported OS is WinXP). There is currently work being done for Linux and dttsp.

Q. What are the recommended minimum system requirements for the PC I will use for the HPSDR?

A. USB 2.0 is a requirement. Currently, the OS recommendation is WinXP. Windows 2000 is NOT recommended as the USB 2.0 stack on Windows 2000 is just too slow.

At this time, there are no solid recommendations for minimum CPU or RAM that are based on actual testing with HPSDR hardware of how low we can go.

FlexRadio does have Minimum Recommended PC Configurations for systems using the PowerSDR software. Since the HPSDR hardware may use PowerSDR, these specs are probably a good guide to what would be advisable for the HPSDR. FlexRadio's numbers from their website are as follows:

  • Processor: Min: 1.5GHz Recommended: 3.2GHz+ or greater
  • Memory: Min: 512MB Recommended: 1GB+ (use the fastest RAM available)

Q. What user name and password do I use to access the HPSDR svn repository?

A. None is required for reading the SVN, only required to place something in the repository. The IP address of the repository is shown on the resources page of the main HPSDR.org website.

Q. Will HPSDR be developed for higher frequencies like those used for satellite and space communications, e.g. VHF, UHF and Microwave?

A. There is a group doing SDR for microwave: [1] Current HPSDR projects could certainly be used as an IF for a transverter, but there is nothing going on with HPSDR that is specifically aimed at microwave.

The HPSDR Wiki

Q. Do I need to log in?

A. Those who contribute by editing the wiki need to have a login.

Q. How do I get a account? (a login)

A. Request it from the wiki system operator, email: Dave, KV0S

Q. What if I find that a correction is needed in the wiki?

A. Reports such as this are welcomed by the wiki system operator, email: Dave, KV0S

ATLAS Backplane

Q. What is the recommended means of powering ATLAS?

A. The LPU or Demeter (not available yet).

The ATX 20 pin power connector on the Atlas board enables the use of standard PC power supplies. (Please Note: There is no reason that you cannot utilize a non-PC power supply regulated and wired to provide the proper voltages to the 20pin connector. A non-PC power supply could also enable custom current limiting of the voltages going to the 20 pin connector, an advisable setup when testing or prototyping boards plugged into ATLAS. An analog power supply may be an attractive option for users particularly concerned about spurious emissions in the HF band which some low cost PC power supplies may produce.)

If you choose to use an ATX computer power supply care should be taken that the -12V current requirement is met. (Note of warning: some versions of the attractive picoPSU do not provide proper -12V current capacity. Check before you buy.)

As a reference for current requirements (reported by Bill Tracey May, 11, 2007), Ozy/Janus used by a SDR100 had the following current usage:

+12v: 200 ma
+5v: 180 ma
-12v: 70 ma

Obviously additional boards connected to the Atlas board will increase these numbers.

Projections of current requirements for other boards are(as reported by Phil Harman, June 6, 2007):

+12v: 200 ma
+5v: 300 ma
+12v: 200 ma
+5v: 500 ma

Q. Will the Atlas be offered assembled?

A. Probably not. It is fairly easy to assemble with a very minimal amount of surface mount parts. There are quite a few solder pads due to the 96 pin connectors. If you are not able to do this work yourself, our advice is to ask on the HPSDR Discussion List (reflector) to see if you can pay someone to do the work for you.

Q. Can solder paste and a hot air heat gun (or oven) be used on Atlas for "all those connections" ?

A. It is possible, but at least one report indicates problems with the center row on the connectors. If considering doing this, we suggest you ask on the discussion list. If anyone has had success or failure, please report it to the wikisysop so we can update this reply.

Q. Will a larger (or smaller?) number of slots version be offered?

A. Possibly, if the need and demand warrant. Nothing is in the plans right now (as of May 2007).

Q. I don't see assignment of all the bus pins. Is there a list somewhere?

A. Some are not assigned a function yet, due to the developing nature of the HPSDR project and the use of the FPGA.


Q. Availability?

A. The bare board and connectors are now available from TAPR http://tapr.org


Q. Will the USB connection from Ozy to my PC require anything special in terms of USB port specification or drivers?

A. A USB 2 connection will be required on the PC. Most modern PCs have this as standard. With MS Windows, for the USB driver we are using the LibUsb-Win32 library which is a free download from http://libusb-win32.sourceforge.net/ A Linux version is also available, see http://www.linux-usb.org/ and http://libusb.sourceforge.net/ . Experience will tell us if there are any problems with certain types of USB2 ports.

Q. Why do we need a "configuration device" when the software can just load the FPGA via USB and the Cypress CY7C68013 (FX2) chip? The schematic shows the programming pins connected from FX2 GPIO pins to FPGA.

A. It does load via USB and this is how OZY is normally used. BUT, there will come a time when someone wants to use the OZY without PC attached and the configuraton device allows this possibility.

Q. Is the design of Ozy such that it can be used for other purposes than SDR?

A. We certainly hope so and expect that some will use it as a learning tool or development platform for other projects not even remotely related to SDR. It provides an inexpensive piece of hardware for many purposes.


Q. Is Janus a "sound card" ?

A. NO! The usual meaning of a sound card is one which plugs into a personal computer (ISA, PCI, or other bus). The Janus module plugs into our Atlas bus and contains some of the components of the usual sound card. It also requires the Ozy or similar interface to use it in applications which call for a PC sound card.

Q. Will I be able to use Janus for other non-SDR sound applications with my PC?

A. In theory, Yes! This will require a Windows or Linux driver; there is no reason one can't be written, we just need a volunteer!


Q. Why are there no output RF filters on the Penelope PCB?

A. This is due to a number of reasons. Firstly, whilst Penelope is primarily an HF ( and VHF/UHF on alias) exciter it can be used for other functions. For example, when used with Mercury it can form a low level signal source as a tracking generator or VNA. For these functions the lack of output filters is an advantage.

Secondly, Penelope generates RF directly at the desired output frequency by synthesizing the required RF waveform using a DAC. The lack of mixers, DDS, frequency synthesizer etc means the output spectrum of Penelope is particularly clean. In fact the spurious output at 0.5w meets the FCC requirements without additional filtering.

Thirdly, Penelope is an exciter. Whilst we expect it will be used by QRP operators as is we also expect it to be used to drive a higher power amplifier. In the latter case the user will most likely provided external filtering as part of this power amplification.

Fourthly, Penelope does provide a 55MHz LPF that can be placed in circuit after the DAC and prior to the 0.5W PA. If desired the user can add external bandpass filters here. Alternatively, the filter can be bypassed and/or an external VHF/UHF filter fitted such that the alias output of the DAC can be used on the higher bands.

Fifthly, if is desirable to use LPFs that may be also be used before Mercury. The IP3 performance of Mercury is very good and using small inductors, that are quite acceptable for removing the harmonics from Penelope, results in a significant degradation in IP3 performance.

An external set of filters will be provided as part of the Alex project.

Additionally, HPDR is a journey and not a destination! We fully expect higher performance DACs to be come available in the future. These newer devices will still require some form of output filtering. By using external filters the cost of replacing the exciter board is reduced.



Q. What is the Hermes HPSDR Project?

A. Hermes extends the successful OpenHPSDR Mercury, Penelope and Atlas on one PCB board with one FPGA. We do not see Hermes as the ultimate project, just a convenient version in a small package. Many will find the small package inconvenient for the add-on like Excalibur or specialized experimentation.

Hermes is an experimental platform for future development. Hermes is NOT a commercial turn-key product. If you are looking for a full featured out-of-the-box SDR transceiver, you should look at the units from Flex-Radio or similar companies.

Q. Where is the Hermes Project Wiki?


Q. What is the History of the Hermes Project?

A. http://openhpsdr.org/hermes.html

Hermes - A proposed DUC/DDC Transceiver

Project Leader: Kevin M0KHZ

Following the outstanding success of Mercury and Penelope, and while investigating the verilog code for both, I had the insane idea of merging the verilog code of Mercury and Penelope into a single fpga! I played around with this idea for a while and the more I thought about it the more I liked the idea.

So here is the proposal, to develop a single board HPSDR based on the hardware of Mercury and Penelope and a single large fpga.

This board would have PC connectivity by USB. I’m planning to squeeze this all onto Euro Card sized PCB (100 x 160 mm), and if I utilize both sides I might even have room for a Pennywhistle type PA  :).

Q. What are the Objectives of the Hermes Project?

A. http://openhpsdr.org/hermes.html Hermes is simply the Mercury, Penelope and Atlas on one board with one FPGA. We do not see Hermes as the ultimate project, just a convenient version in a small package. Many will find the small package inconvenient for the add-on like Excalibur.

Hermes is an experimental platform for future development. Hermes is NOT a commercial turn-key product. If you are looking for a full featured out-of-the-box SDR transceiver, you should look at the units from Flex-Radio or similar companies.

Q. How does the Hermes architecture work?


Q. Where is the software and firmware for Hermes?

A. The proposed OpenHPSDR Hermes software implementations are:

Q. Where are the schematics?

A. (to be developed)

Q. Where are the board layout files?

A. (to be developed)

Q. Where are the VHDL files?

A. (to be developed)

Q. Where is the Users Manual?

A. (to be developed)

Q. Where is the Builders Manual?

A. (to be developed)

Q. Where is the Troubleshooting Guide?

A. (to be developed)

Q. Is there an in-depth technical manual?

A. (to be developed)

Q. Where can I get the orientation and training DVD?

A. (to be developed)

Q. Where can I get a power point presentation for my club meeting?

A. (to be developed)

Q. Is there an online Internet Hermes/Apollo radio for me to control remotely?

A. (to be developed)

Q. Where is the Teamspeak voice over Internet activity?


  • OpenHPSDR Teamspeak IP address
  • Reference to the Teamspeak Users Installation Guide (pdf)

Q. What is a DDC receiver see Mercury?

A. DDC is the abbreviation for the term Digital Down Conversion. DDC receivers are able to finally fulfill the dream that has been expressed in Ham Radio magazines for 50 years – to place the digital processing of analog RF information closer to the antenna. The OpenHPSDR Mercury receiver accomplishes that goal. In the OpenHPSDR Mercury and Hermes projects, the antenna is connected to a modern integrated circuit chip. The chip in this case is a very fast Analog to Digital conversion device called the LTC2208. The Mercury and Hermes designs are designed to be supplemented by bandpass, attenuation, and pre-amp circuits.

Q.How does the ADC (Analog to Digital) chip work?

A. The Linear Technologies 2208 is a high speed, state-of-the-art, Analog to Digital conversion integrated circuit. The specifications for the LTC2208 can be found on the Linear Technologies website. The LTC-2208 illustrates the beginning of a most exciting new era in Ham Radio. The ADC offers us the ability to convert analog RF signals to digital signals. The conversions happen in the Mercury and Hermes at the blazing rate of 125 Million Samples Per Second! I realize that this is a difficult concept to grasp. There is a great deal of helpful material available on the Internet and from various magazines and books. The ARRL DSP book written by Doug Smith KF6DX has several chapters devoted to various aspects of digital sampling of analog signals. New Linear Technologies devices allow experimetners to build affordable equipment that processes the digital representation of the entire RF spectrum throughout the HF bands (.05Mhz through 55Mhz). Digital processing gives us extraordinary filters, AGC, MDS, BDR and other level handling that is far beyond any of our older analog circuit designs. The software doesn't change values as equipment heats up and image rejection is always at it's mathematically optimum value. The ability of the LTC-2208 to sustain 125 million samples per second couples it to various algebraic and mathematical methods that are processed easily inside a miniature computer like the Cyclone-III FPGA. A CW signal on 3.552Mhz appears on the output pins of the LTC-2208 among the stream of discrete numerical values ranging from -32768 to +32767. The LTC-2208 converts the RF impulses to decimal values using all sixteen bits of it's internal circuitry. During every tick of your wall clock, the LTC-2208 presents one hundred and twenty five million samples of the RF spectrum at it's output pins. Each numerical sample is an aggregate value of the RF energy throughout the HF spectrum. It is the job of the logic elements in the Cyclone III FPGA to interpret, separate, filter, convert, and prepare the numerical values so that they can be post-processed by the Athena software framework. The Athena software will convert the numerical data back into human viewable form using the magic of DSP and Fourier transforms. The digital signals from the LTC-2208 are passed without interference to the Cyclone-III FPGA in a continuous stream where they are processed in real time. The LTC-2208 includes specialized randomization technology that can be selectively turned on to clarify the signal to noise ratio of it's digital output. You may wish to read some of the excellent digital signal processing material available at no cost on the World Wide Web. Terminology such as “time domain” and “frequency domain” will easily be related to oscilloscope patterns that we are all familiar with. In addition to the ARRL DSP book, another popular text is The Scientist and Engineer's Guide to Digital Signal Processing By Steven W. Smith, Ph.D.

Q. What is a DUC transmitter or exciter?

A. (to be developed)

Q. What are the Hermes performance specifications?

A. (to be developed)

Q. What is the function of the Cyclone FPGA Chip?

A. FPGA is the abbreviation for a Field Programmable Gate Array. One of the best discussions about FPGA's is on the Wikipedia. An FPGA is a reconfigurable and programmable set of basic logic elements like gates. All the computers (CPU's) that we use have similar basic logic elements at their most detailed level. Wikipedia says that applications of FPGA's include digital signal processing, software defined radio, aerospace, defense systems, medical imaging, computer vision, speech recognition, cryptography, bioinformatics, and computer hardware emulation. Fortunately, the exciting complexity and reconfigurability of these logic elements can be expressed in human readable form by using a Hardware Description (programming) Language from Verilog(R) called VHDL.

Q. What is the "CORDIC" algorithm?

A. (from the Wikipedia webpage CORDIC)

CORDIC COordinate Rotation DIgital Computer is a simple and efficient algorithm to calculate hyperbolic and trigonometric functions. It is commonly used when no hardware multiplier is available (e.g., simple microcontrollers and FPGAs) as the only operations it requires are addition, subtraction, bitshift and table lookup.

The modern CORDIC algorithm was first described in 1959 by Jack E. Volder. It was developed at the aeroelectronics department of Convair to replace the analog resolver in the B-58 bomber's navigation computer,[1] although it is similar to techniques published by Henry Briggs as early as 1624. John Stephen Walther at Hewlett-Packard further generalized the algorithm, allowing it to calculate hyperbolic and exponential functions, logarithms, multiplications, divisions, and square roots.

Originally, CORDIC was implemented using the binary numeral system. In the 1970s, decimal CORDIC became widely used in pocket calculators, most of which operate in binary-coded-decimal (BCD) rather than binary. CORDIC is particularly well-suited for handheld calculators, an application for which cost (eg, chip gate count has to be minimised) is much more important than is speed. Also the CORDIC subroutines for trigonometric and hyperbolic functions can share most of their code.

Some good web references are:

Q. How do signals get from the Analog (RF) to the Digital (I/Q) domain?


Q. How do analog (microphone) signals get to the digital domain?


Q. What are the three "Generations" of SDR technology?

A. The three "Generations" are:

  1. the Analog Phasing or "Weaver" method
  2. the "Tayloe" or QSD (Quadrature Sampling Detector/mixer)
  3. the Direct Down Conversion (DDC/ADC) method

Q. Are there any other Generation-III transceivers?

A. Yes there are several that have appeared in various magazines:

Q. What is the purpose of the I2C bus in the Hermes project?


Q. Why did OpenHPSDR decide to make this an Open Source design?


Q. What is the overall architecture of the Hermes Transceiver?

A. [insert picture here showing block diagram]

  Athena Software Framework <---> Hermes <---> Apollo <---> Antenna

Q. Will Hermes be a truly "TOR" capable QSK CW rig? (where ARRL defines TOR = T/R time < 20ms)


Q. Will Hermes operate on popular digital modes such as PSK31, ALE, and EasyPal digital SSTV?


Q. What is the Apollo part of the OpenHPSDR project?"

A. Apollo is to be a companion 15W PA and Low Pass Filter for Hermes, see: APOLLO

Q. Where is the QSD that I see in so many other SDR designs?

A. There is no Quadrature Sampling Detector or Mixer in the Hermes design. All that work is done with clever mathematics inside the Cyclone FPGA chip using the digitized RF directly from the LTC-2208 Analog to Digital (ADC) chip connected to the antenna (via bandpass/preamp).

Q. Can I build it into my own enclosure (chassis)? A. Yes. The design is flexible and you are encouraged to build Hermes into whatever configuration pleases you. HPSDR hopes to offer a chassis for Hermes that will be pre-punched for all the attachments and connectors.

Q. Can I build Hermes into my own OEM product for sale?

A. No, the open hardware license allows you to build and enjoy the Hermes transceiver, however you may not build your own commercial product using the HPSDR copyrighted boards and design.

Q. Where is the Rx Image Rejection adjustment?

A. Image rejection is done with 30 digit floating point precision inside the FPGA where it surpasses any analog design in performance across the entire Rx/Tx spectrum.

Q. Is the Hermes transceiver reverse polarity protected?

A. Yes, there is protection in the power supply and on each board. Of course the builder should take every possible protection to insure that the power supply is connected properly.

Q. What is the Dynamic Range of the Hermes (Mercury) receiver?

A. 130dBm

Q. What are the plans for support of "Gig-E" ethernet?

A. Built into your mITX computer supporting the Hermes.

Q. What are the plans for support of USB-3?

A. USB-3 has just appeared in various exotic motherboards. We do not expect USB-3 to be an important factor for Hermes until 2011.

Q. What is Undersampling?


Q. How is Hermes/Apollo different from the Flex-Radio(c) 5000, 3000, and 1500?


Q. What is the difference between the Hermes Mercury DDC Rx and the QuickSilver from Phil N8VB Software Radio Laboratory LLC?


Q. What power supply is recommended?


Q. What High Voltage MOSFET's are used in the Power Amplifier?


Q. Does Hermes include a "Class-A" bias adjustment?


Q. What commercial Linear Amplifiers will Hermes work with?


Q. Can Hermes operate in the VHF/UHF spectrum?


Q. What are the future plans for the Hermes OpenHPSDR Project?


Q. What is the Apollo board and do I need it?

A. Apollo Discussion

Q. How is the Apollo board integrated or connected to the Hermes transceiver?


Q. Where is the OpenHPSDR mailing list?


  http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/ archives
  http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org subscriptions
  http://openhpsdr.org/ main organization webpage

Q. How do I record I/Q (RF) data?


Q. How do I record Rx audio for later playback?


Q. I am a talented programmer, how can I help?


Q. How do multiple receiver channels work?


Q. How much data can I expect to pump through a USB 2.0 connection?


Q. Is there a Linux version of the server and GUI?


Q. Is there an iMAC version of the server and GUI?


Q. Is this the Flex-Radio(R) PowerSDR(c) software in disguise?


Q. How is Hermes software different from PowerSDR(c)?


Q. What have you changed in the Dttsp module?


Q. Will Hermes software work with the G3UKB Acorn project?


Q. Can I resize the Hermes GUI to fit my large expensive monitor?


Q. Do you offer color choices or "skins" for the GUI? like a Collins gray or Heathkit green?


Q. How do I compile the source code on my MAC/LIN/WIN machine?


Q. How do I add a feature to the GUI?


Q. How wide is the panadapter (spectrum) display?


Q. Will you ever implement the Cathy Moss 3D waterfall?


Q. Will the Hermes GUI work on my Netbook or small laptop?


Q. Will the Hermes server work on my Netbook or small laptop?


Q. Will the Hermes server and GUI work remotely from each other across the Internet?


Q. What is your plan for OpenGL display enhancement?


Q. What is your plan for DirectX on Windows platforms?


Q. Will Hermes server and GUI work on WindowsXP, Vista, Windows-7?


Q. What are the server commands?


Q. What are the CAT commands and how are they implemented?


Q. What support is available?


Q. Can I subscribe to future upgrades and support options?


Q. Is custom programming available?


Q. How large is the OpenHPSDR organization?


Q. Do you have a European distributor or dealer?


Q. Do you have an .AU or .NZ distributor or dealer?


Q. Can I purchase bare boards and populate them myself?


Q. Can I buy the chips individually?


Q. How are the Hermes hardware and software legally protected?


Q. Is your Intellectual Property copyrighted or otherwise protected?


Q. What is the Warranty period?


Q. What does the warranty cover?


Q. What shipping and insurance options are available?


Q. How do I avoid the excessive "VAT" tax in my country?


Q. Do you accept payment via PayPal(R)?


Q. Who do I call for help?


Q. How can I contribute to the future success of the Hermes project?




Project leaders, developers, documenters: feel free to contribute answers -- especially where it says "TBD" or "Answer pending."

General Readership: have a suggested question that should be here? Email: Dave, KV0S