Re: [Flexradio] Receiver dies 2 min after power-up, ideas?
This is exactly what it looks like when/if the DDS quits running. Contact us directly about getting the unit serviced. You might look through the various ECOs on the private downloadp age if your unit is not up to date. Eric Wachsmann FlexRadio Systems > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > radio.biz] On Behalf Of Wayne Roth > Sent: Friday, September 30, 2005 1:57 PM > To: FlexRadio@flex-radio.biz > Subject: [Flexradio] Receiver dies 2 min after power-up, ideas? > > My SDR-1000 (an older rev box with RFE, no PA or tuner, parallel port > interface) receives fine for the first couple of minutes then goes deaf. > Cycling the DC power restores the receiver for another couple minutes, > then > it dies again. Just before it craps out, the baseline as viewed on the > spectral display raises from -130 to about -70 a couple times along with > an > increase in the white noise, then drops to -140. All frequencies appear > to > be dead. Restarting the software has no effect, so it's a hardware issue. > I have yet to open the enclosure and get the scope out, just wondering if > anyone has seen this, or has a suggestion on where to start looking. > > Best Regards, > Wayne > WA2N / 5 Austin Tx > > > ___ > FlexRadio mailing list > FlexRadio@flex-radio.biz > http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Re: [Flexradio] Linux jDttSP
Edson -- Thanks for being patient :-) I am in the process of implementing a stand-alone little machine based on the VIA EPIA mini-atx mother board and the control application I am implementing is the first piece of a remote controlled SDR-1000 + little DSP-dedicated computer. Wonderful. This is very much what we were hoping would happen. Please keep us informed about how it's going. One of the things we're eager to find out is whether running the system entirely from ram disk will iron out some of the glitches associated still with using jsdr on a totally vanilla OS configuration, that is, with no low-latency patches, not running jack as root, and so on. Can you tell us a little about the new goodies in the new version? Unfortunately there's not much that will be dramatically obvious from the outside, apart from better performance. A lot of it is simple clean-up of the source and overhaul of the source directories. A certain amount is making convenient at the user level some capabilities which have been unused so far, like multiple receivers and the aux signal buses. There's a little bit of syntactic sugar on the update commands which makes them selectively recordable and replayable. Basically what it means is that you can get the radio to a desired state, save that, and restore it at will, without a console. An elementary facility, not meant to replace real memories or a database. There are some new experimental features like wavelet noise mitigation and MIDI input to the keyer. Unfinished but there to play with. If Bob is comfortable with it, the new mode that implements a soft transponder. Maybe the more interesting gadgets are outboard of jsdr, strictly speaking. There's a jack-to-python module, a test signal generator, and a couple of jack clients to assist in compressing the user-side audio streams and streaming them over LAN. Basically it's window dressing on what amounts to a thorough course of software-engineering hygeine and regualar professional care, like a heavy dose of Listerine. Ok. For TX, would the behavior be the same or would the LSB/USB mode change anything? RX and TX are completely symmetrical, except for a small processing stage on TX which eliminates residual DC. This is separate from the DC blocker on TX audio input which is meant to compensate for crummy soundcards. Very 73 Frank AB2KT
Re: [Flexradio] Receiver dies 2 min after power-up, ideas?
Hi Wayne, I had this problem with my SDR-1000. Every time I got out the probes to see what was going on it would not do it (not that they would have helped much since the it is a bear to get a probe into the board stack). Finally I isolated it to one of a handful of crappy looking solder joints on the PIO board (bottom of the stack). I just touched up all the bad looking solder joints until the problem when away. I haven't had a problem since (3+ months). It would do exactly what you describe - display jumps up higher than baseline a few times, white noise, and then nothing... with baseline below -140... Have you tried rapping the case a few times? Generally it would restore mine for a few minutes before it did it again. I think in my case the excessive heat generated by the regulator on the PIO board aggravated any substandard solder joints by thermal expansion and contraction over time. At least it is something to look at. 73 de Phil N8VB On 9/30/05, Wayne Roth <[EMAIL PROTECTED]> wrote: > My SDR-1000 (an older rev box with RFE, no PA or tuner, parallel port > interface) receives fine for the first couple of minutes then goes deaf. > Cycling the DC power restores the receiver for another couple minutes, then > it dies again. Just before it craps out, the baseline as viewed on the > spectral display raises from -130 to about -70 a couple times along with an > increase in the white noise, then drops to -140. All frequencies appear to > be dead. Restarting the software has no effect, so it's a hardware issue. > I have yet to open the enclosure and get the scope out, just wondering if > anyone has seen this, or has a suggestion on where to start looking. > > Best Regards, > Wayne > WA2N / 5 Austin Tx > > > ___ > FlexRadio mailing list > FlexRadio@flex-radio.biz > http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz > -- Philip A Covington http://www.philcovington.com
Re: [Flexradio] Error reading bandinfo table
For those who can't wait until the next version of PowerSDR is available, I have corrected as per Eric's directions the band info of the PowerSDR.mdb database file for version 1.4.5. I have tested it here and it seems to work OK. The zip file ( www.hamsdr.com/dnld.aspx?id=41 ) is available from the public download area at hamsdr.com. The file I uploaded has no stations memorized, so before trying this database, make sure you make a copy of your existing one first, just to be on the safe side. Naturally there are absolutely no guarantees. Enjoy, 73 de Joe, AB1DO - Original Message - From: Eric Wachsmann - FlexRadio To: 'Ignacio Cembreros' ; flexradio@flex-radio.biz Sent: Friday, September 30, 2005 12:11 Subject: Re: [Flexradio] Error reading bandinfo table Further, you can easily copy+paste the table data from Access into Excel and use a formula to find problem areas (i.e. overlapping frequencies). Eric Wachsmann FlexRadio Systems -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio CembrerosSent: Friday, September 30, 2005 11:00 AMTo: flexradio@flex-radio.bizSubject: Re: [Flexradio] Error reading bandinfo table I sent a previous response regarding the same subject. This not applies to Art, mainly because he is asking how to manipulate the database, so I assume he didn´t it before.But if somebody has modified the default entries of a previous versión in the BandText table (i.e.to include a more detailed band plan) and you import this database in the current version, it is more than posible that you get this alarm in several places. So if you import a modified table, check every register and edit any inconsistency i.e. band segmrentes that are nested or overlapped with others. An alternbate method is to make a sweep of the whole HF, in 100Khz increments, and noting where the alarms appear and the edit the table in those places.73 de Ignacio, EB4APLEric Wachsmann - FlexRadio wrote: Art, I assume based on the subject that you are talking about the database issue. If you have Microsoft Access, you can edit the file yourself fairly easily. Open the file and you will see a list of the Tables. Double click on the one calls BandText. This will give you a list of the entries in that table. There are two entries that cause problems in 1.4.5 beta prev 1. The first has a Low frequency of 1.999 and the other has a Low of 3.635. Delete these two entries (highlight, right click, select Delete Record, confirm) and everything will be peachy. If you dont have MS Access, you could probably talk someone here on the reflector into doing this for you if you email them the file (make sure to zip the database so virus programs dont strip the attachment). Eric Wachsmann FlexRadio Systems -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED]Sent: Thursday, September 29, 2005 10:19 PMTo: flexradio@flex-radio.bizSubject: [Flexradio] Error reading bandinfo table How do I solve this problem with 1.4.5 beta prev 1 ? Thanks, Art ___FlexRadio mailing listFlexRadio@flex-radio.bizhttp://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Re: [Flexradio] Receiver dies 2 min after power-up, ideas?
Wayne Roth wrote: My SDR-1000 (an older rev box with RFE, no PA or tuner, parallel port interface) receives fine for the first couple of minutes then goes deaf. Cycling the DC power restores the receiver for another couple minutes, then it dies again. Just before it craps out, the baseline as viewed on the spectral display raises from -130 to about -70 a couple times along with an increase in the white noise, then drops to -140. All frequencies appear to be dead. Restarting the software has no effect, so it's a hardware issue. I have yet to open the enclosure and get the scope out, just wondering if anyone has seen this, or has a suggestion on where to start looking. Best Regards, Wayne WA2N / 5 Austin Tx ___ FlexRadio mailing list FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz When I had problems like that, it related to problems with the sound card setup. In the most extreme case, I had configured the wrong card. If you're receiving at all, that's not your problem. However, to take another possibility I've seen, if you have your SDR sound card set as any of the Windows default sound devices, some very strange results can happen. This can happen in ways mysterious. Check all your sound card settings for the SDR and any nonSDR cards. Check that you don't have bad defaults and check that you have things like reverb turned off, the correct mixers and microphone et. al. settings set on or off. Larry WO0Z
[Flexradio] Receiver dies 2 min after power-up, ideas?
My SDR-1000 (an older rev box with RFE, no PA or tuner, parallel port interface) receives fine for the first couple of minutes then goes deaf. Cycling the DC power restores the receiver for another couple minutes, then it dies again. Just before it craps out, the baseline as viewed on the spectral display raises from -130 to about -70 a couple times along with an increase in the white noise, then drops to -140. All frequencies appear to be dead. Restarting the software has no effect, so it's a hardware issue. I have yet to open the enclosure and get the scope out, just wondering if anyone has seen this, or has a suggestion on where to start looking. Best Regards, Wayne WA2N / 5 Austin Tx
Re: [Flexradio] Error reading bandinfo table
Further, you can easily copy+paste the table data from Access into Excel and use a formula to find problem areas (i.e. overlapping frequencies). Eric Wachsmann FlexRadio Systems -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio Cembreros Sent: Friday, September 30, 2005 11:00 AM To: flexradio@flex-radio.biz Subject: Re: [Flexradio] Error reading bandinfo table I sent a previous response regarding the same subject. This not applies to Art, mainly because he is asking how to manipulate the database, so I assume he didn´t it before. But if somebody has modified the default entries of a previous versión in the BandText table (i.e.to include a more detailed band plan) and you import this database in the current version, it is more than posible that you get this alarm in several places. So if you import a modified table, check every register and edit any inconsistency i.e. band segmrentes that are nested or overlapped with others. An alternbate method is to make a sweep of the whole HF, in 100Khz increments, and noting where the alarms appear and the edit the table in those places. 73 de Ignacio, EB4APL Eric Wachsmann - FlexRadio wrote: Art, I assume based on the subject that you are talking about the database issue. If you have Microsoft Access, you can edit the file yourself fairly easily. Open the file and you will see a list of the Tables. Double click on the one calls “BandText.” This will give you a list of the entries in that table. There are two entries that cause problems in 1.4.5 beta prev 1. The first has a Low frequency of 1.999 and the other has a Low of 3.635. Delete these two entries (highlight, right click, select Delete Record, confirm) and everything will be peachy. If you don’t have MS Access, you could probably talk someone here on the reflector into doing this for you if you email them the file (make sure to zip the database so virus programs don’t strip the attachment). Eric Wachsmann FlexRadio Systems -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 29, 2005 10:19 PM To: flexradio@flex-radio.biz Subject: [Flexradio] Error reading bandinfo table How do I solve this problem with 1.4.5 beta prev 1 ? Thanks, Art
Re: [Flexradio] Error reading bandinfo table
I sent a previous response regarding the same subject. This not applies to Art, mainly because he is asking how to manipulate the database, so I assume he didn´t it before. But if somebody has modified the default entries of a previous versión in the BandText table (i.e.to include a more detailed band plan) and you import this database in the current version, it is more than posible that you get this alarm in several places. So if you import a modified table, check every register and edit any inconsistency i.e. band segmrentes that are nested or overlapped with others. An alternbate method is to make a sweep of the whole HF, in 100Khz increments, and noting where the alarms appear and the edit the table in those places. 73 de Ignacio, EB4APL Eric Wachsmann - FlexRadio wrote: Art, I assume based on the subject that you are talking about the database issue. If you have Microsoft Access, you can edit the file yourself fairly easily. Open the file and you will see a list of the Tables. Double click on the one calls “BandText.” This will give you a list of the entries in that table. There are two entries that cause problems in 1.4.5 beta prev 1. The first has a Low frequency of 1.999 and the other has a Low of 3.635. Delete these two entries (highlight, right click, select Delete Record, confirm) and everything will be peachy. If you don’t have MS Access, you could probably talk someone here on the reflector into doing this for you if you email them the file (make sure to zip the database so virus programs don’t strip the attachment). Eric Wachsmann FlexRadio Systems -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 29, 2005 10:19 PM To: flexradio@flex-radio.biz Subject: [Flexradio] Error reading bandinfo table How do I solve this problem with 1.4.5 beta prev 1 ? Thanks, Art
Re: [Flexradio] Error reading bandinfo table
Art, I assume based on the subject that you are talking about the database issue. If you have Microsoft Access, you can edit the file yourself fairly easily. Open the file and you will see a list of the Tables. Double click on the one calls “BandText.” This will give you a list of the entries in that table. There are two entries that cause problems in 1.4.5 beta prev 1. The first has a Low frequency of 1.999 and the other has a Low of 3.635. Delete these two entries (highlight, right click, select Delete Record, confirm) and everything will be peachy. If you don’t have MS Access, you could probably talk someone here on the reflector into doing this for you if you email them the file (make sure to zip the database so virus programs don’t strip the attachment). Eric Wachsmann FlexRadio Systems -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 29, 2005 10:19 PM To: flexradio@flex-radio.biz Subject: [Flexradio] Error reading bandinfo table How do I solve this problem with 1.4.5 beta prev 1 ? Thanks, Art
Re: [Flexradio] Linux jDttSP
Hi Frank, Thanks for the quick response. Frank Brickle wrote: Edson -- Yipes! I can't thank you enough for pointing this out. We've had a couple of other reports about problems with the spectum output and have been going nuts trying to figure out what was going on, because I have been unable to duplicate the problem. There was a lengthy process of negotiation back and forth between Bob and myself concerning exactly what would go where in the spectrum computation, so that we'd have something that worked on both the Linux and Windows sides. It was my job ultimately to reconcile them in the codebase. Just at the time this was happening there were big problems at SourceForge with updates to CVS that got dropped on the floor. The problem actually pushed me to look into the code to find out how things work. In short, the wrong version (half-corrected) was the one that got into CVS. It was pure sloppiness that I did not go back and test the CVS version that finally showed up. My sincerest apologies. No need for apologies. On the contrary, I would like to thank you and Bob for the superb work you have done. It is quite fun to play with sdr under Linux. I am in the process of implementing a stand-alone little machine based on the VIA EPIA mini-atx mother board and the control application I am implementing is the first piece of a remote controlled SDR-1000 + little DSP-dedicated computer. I'm not going to correct the CVS at this time since, first, you've made the correct fix, and second, because there is a major new release coming out shortly. We're switching to FFTW3 and the code and data structures associated with all those computations are somewhat different. That is very exciting! I am tempted, but am not going to ask for when the release will be! :-) I know how hard it is to get software releases out. Can you tell us a little about the new goodies in the new version? Now, to your questions. [1] *My* Linux version is correct, and yours isn't, because I screwed up. No surprise there. No problem at all. I just wanted to confirm that I was not doing something stupid. [2] The place to get the raw spectrum is not inside jDttSP but rather from the jack ports. If you need it inside jDttSP it can easily be provided, depending on what you're going to do with it. The way it is now does work quite nicely. I was planing a large 4096-pixels panadapter, but instead of scrolling the spectogram image, I can leverage jDttSP to do it for me. I have some old code for a spectogram I wrote some time ago and will adapt it for working with jack. [3] The USB/LSB behavior is exactly as you describe. Switching sidebands is actually accomplished above jDttSP merely by altering the filter settings as you have done. Ok. For TX, would the behavior be the same or would the LSB/USB mode change anything? Thanks again, 73, -- Edson
[Flexradio] USB-to-parallel adapter power management update
If you're using the USB adapter, please download and install the updated Sdr1kUsb-Installer.exe from the FlexRadio web site. The installer will prompt you to replace three files on your computer. Only the Sdr1kUsb.dll file has changed since the original release. It doesn't make any difference whether or not you replace the other two (sdr1k_ezusbfx.inf and ezusb.sys). This update resolves the issue of the USB adapter not responding after computer wakes up from standby or hibernation. It seems some computers haven't had this problem, while on other systems it has been necessary to un/replug the USB cable to reset the device driver after wakeup. Apparently the Cypress EZ-USB driver that we're using is not fully compatible with power management on all systems. The updated software will use Windows device installation functions to restart the unresponsive device driver. This could be described as the software equivalent of un/replugging the USB cable. It seems to do the trick. Please note that you should still close the PowerSDR application first before putting your computer into standby or hibernation. This is a valid recommendation for all users, not just a USB issue. Many hardware devices sometimes seem to wake up in a slightly different state than they were before standby. I have tested this with PowerSDR and I often get a PortAudio error message "Device unavailable" after standby. You can send USB related bug reports, questions and comments either to [EMAIL PROTECTED] or the FlexRadio e-mail reflector. 73, Sami OH2BFO
Re: [Flexradio] Linux jDttSP
Edson -- Yipes! I can't thank you enough for pointing this out. We've had a couple of other reports about problems with the spectum output and have been going nuts trying to figure out what was going on, because I have been unable to duplicate the problem. There was a lengthy process of negotiation back and forth between Bob and myself concerning exactly what would go where in the spectrum computation, so that we'd have something that worked on both the Linux and Windows sides. It was my job ultimately to reconcile them in the codebase. Just at the time this was happening there were big problems at SourceForge with updates to CVS that got dropped on the floor. In short, the wrong version (half-corrected) was the one that got into CVS. It was pure sloppiness that I did not go back and test the CVS version that finally showed up. My sincerest apologies. I'm not going to correct the CVS at this time since, first, you've made the correct fix, and second, because there is a major new release coming out shortly. We're switching to FFTW3 and the code and data structures associated with all those computations are somewhat different. Now, to your questions. [1] *My* Linux version is correct, and yours isn't, because I screwed up. No surprise there. [2] The place to get the raw spectrum is not inside jDttSP but rather from the jack ports. If you need it inside jDttSP it can easily be provided, depending on what you're going to do with it. [3] The USB/LSB behavior is exactly as you describe. Switching sidebands is actually accomplished above jDttSP merely by altering the filter settings as you have done. 73, and again, many thanks. Frank AB2KT Edson Pereira wrote: Good Evening! This is a question to Bob or Frank regarding jDttSP on Linux. I am trying to get a Qt-based GUI implemented to control jDttSP and have noticed that the spectrum data was not being correctly written to the spectrum FIFO. After some tracing, I've found that the problem was due to the fact that the window[] function array for the spectrum FFT was not being initialized. For testing I've initialized the window[] in init_spectrum() for the moment. Later I may include it in update.c. Now I have spectrum data coming out of the FIFO, but I've noticed that when setting the spectrum to PRE_FILT, the spectrum slides on the frequency axis following the setOsc setting. Trying SEMI_RAW does not work unless I set the mode to SPEC (setMode SPEC). But this changes the audio filtering and does not change the spectrum sliding behavior. One more thing I have noticed is that there is no change in the demodulator when I set the mode to USB or LSB (setMode USB|LSB). The only way I can switch SSB sidebands is by modifying the filter passband to negative values. My questions are: 1. Is the initialization of the window[] function left out in the Linux code? 2. Would there be a way to get a snapshot of the full 48 kHz raw complex spectrum without any interference from the tuning? 3. Is the USB/LSB behavior correct? Many thanks, -- Edson, pu1jte, n1vtn, 7n4ncl ___ FlexRadio mailing list FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
[Flexradio] Linux jDttSP
Good Evening! This is a question to Bob or Frank regarding jDttSP on Linux. I am trying to get a Qt-based GUI implemented to control jDttSP and have noticed that the spectrum data was not being correctly written to the spectrum FIFO. After some tracing, I've found that the problem was due to the fact that the window[] function array for the spectrum FFT was not being initialized. For testing I've initialized the window[] in init_spectrum() for the moment. Later I may include it in update.c. Now I have spectrum data coming out of the FIFO, but I've noticed that when setting the spectrum to PRE_FILT, the spectrum slides on the frequency axis following the setOsc setting. Trying SEMI_RAW does not work unless I set the mode to SPEC (setMode SPEC). But this changes the audio filtering and does not change the spectrum sliding behavior. One more thing I have noticed is that there is no change in the demodulator when I set the mode to USB or LSB (setMode USB|LSB). The only way I can switch SSB sidebands is by modifying the filter passband to negative values. My questions are: 1. Is the initialization of the window[] function left out in the Linux code? 2. Would there be a way to get a snapshot of the full 48 kHz raw complex spectrum without any interference from the tuning? 3. Is the USB/LSB behavior correct? Many thanks, -- Edson, pu1jte, n1vtn, 7n4ncl
