If anyones interested, I have access to a limited number of NIB (new in
box) Furman IP-8 ISO-Patch line isolators. These are Pro (studio grade)
1RU patch panels with 8 fully isolated patch positions. Provide total
d.c. block between source and load and can accommodate unbalanced or
balanced
Some were asking,
links to the digital images and spec sheet for the IP-8 patch bay/ line
isolators.
http://i158.photobucket.com/albums/t94/psk31_bucket/Furman_IP8_Spec.jpg
http://i158.photobucket.com/albums/t94/psk31_bucket/Furman-11.jpg
Dave,
you'll have the same trouble using either DeOxit red or Gold on the
stainless-steel mini-plug [HOSA]. I tried them all. In order to
eliminate the oxidation that occurs over time between the plug and jack
you'd be best advised to re-terminate the cables with 3.5mm gold-plated
plugs. I
Is anyone experiencing occasional snapping or popping on key closure in
cw? I'm finding that the radio infrequently kicks out a very brief snap
either at the onset of tx or on first key closure. Almost sounds like a
static discharge.
Receive is perfect and the various buffer setting
going on.
Eric Wachsmann
FlexRadio Systems
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
radio.biz] On Behalf Of root [knesbitt]
Sent: Saturday, December 23, 2006 3:59 PM
To: flexradio@flex-radio.biz
Subject: [Flexradio] v1.9.0 Level Calibration
Is it me
Is it me or is the input level calibration out by 3 dB in v1.9.0 (795)?
Dumping a -70 dBm into the front end of the SDR (HP 8648C derived)
equates to -67.0 dBm repeatedly for Pre-amp Gain settings of low/Med/High.
Using a new .mdb for this load and have run the Cal routine after
ensuring the
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of root [knesbitt]
Sent: Saturday, December 23, 2006 3:59 PM
To: flexradio@flex-radio.biz
Subject: spam: [Flexradio] v1.9.0 Level Calibration
Is it me or is the input level calibration out by 3 dB in v1.9.0 (795)?
Dumping a -70 dBm
Sorry, in my initial reply I referred to USB when in fact I meant to say
firewire (device).
You should get your active/sync blue LED back and hopefully XP will
re-register this USB device.
Cheers!
Kirb - VE6IV
--
___
FlexRadio mailing list
Internal keyer seems to work fine in iambic mode when tested this am
(svn_741).
Make sure you enable the high resolution P4 clock function on the
internal keyer settings (Pentium class P4 only). Disabling High Res.
clocking under the DSP/Keyer settings, results in staccato like keying
elements
*Jerry,
I would suggest you start at the following values;
PowerSDR audio buffers: 512
PowerSDR DSP buffers: 2048 (if your running at 96 khz sampling rate), or
1024 if your sampling at 48 khz.
D44 ASIO: 512 buffers or equiv. ( I do not own a Delta-44) You may need
to tweak or match the audio
Crit,
not quite clear as to whether you performed the TX Image Rejection procedure or
not. Resetting these values to gain=0 and Phase=0 may not work.
First I'd say after making absolutely sure you have a solid connection on your
to line out cable between the radio and the D44.
perform the Tx
Paul,
I can vouch for the ASUS P5W with the Intel 975X chipset. Not
particularly cheap but far superior performance to my previous AMD
athlon board.
I'm running the P5WD2 with a non-dual core cpu (P-4 HT LGA 775, 3.4 Ghz).
It simply purrs along with 683 feeding a Firebox over 1394. CPU load
Jerry,
I would suggest you call a priest immediately. This has nothing to do
with the electrical length of your pipe..
See: http://www.stmichael.pair.com/ as a starting point
Cheers,
Kirb - VE6IV
--
___
FlexRadio mailing list
SR= Spur Reduction
Kirb - VE6IV
__
Bob,
just downloaded the latest SVN release and still playing with it. So far I
do like it.
I figured out that the button marked Drive is what used to be called
PWR, but what is SR in the DSP group?
Thanks,
73 de Joe - AB1DO
Just wanted to offer this to the group prior to going public. I hope
you'll excuse the b/w.
I have a near new PreSonus Firebox which will soon be surplus to my
needs (going to a different firewire sound device) complete with all the
packaged cables, drivers and 3rd party software (Cubase LE). This
It has come to my attention that PreSonus apparently has a new firmware
release which is reported to addresses the current deficiencies
associated with either the stock firmware (no 96 khz sampling), or the
beta firmware load recently offered (11 khz bleed through problem).
The issue as before
Tim,
yes! I am seeing the same thing here. I have been fooling around this
weekend in WPX CW running in 96 khz mode and dealing with the big
descending noise spike on Tx to Rx (my Firebox is unmodified for 96 k
op). The transmit pop you've identified is definitely there when running
96 but not
Eric,
this is old news when running the Firebox :-)
Actually 0-latency operation is not dependent on running at 96 khz. I am
running my system at 48 khz sampling using the stock Firebox firmware
and new keyer code (external keyer not required). With the PreSonus set
to 512 buffers and *2.5ms*
the last
release, I think we pretty much have this licked.
Bob
root [knesbitt] wrote:
Eric,
this is old news when running the Firebox :-)
Actually 0-latency operation is not dependent on running at 96 khz. I
am running my system at 48 khz sampling using the stock Firebox
firmware
From the man himself;
http://www.kernel.org/pub/linux/kernel/SillySounds/
Kirb - VE6IV
--
Tom Thompson wrote-
Bob,
Since I hear Linux pronounced L-eye-nux and L-i-nux, I want to get off
on the right foot :) How do you pronounce the African word Ubuntu?
Tom Thompson W0IVJ
As the saying goes, a .wav file is worth a thousand words, or in this
case about 360 KB. Building on Bob's comments below I have gone ahead
and recorded a small sound demo of my SDR1K running with the K1EL
K40 keyer interfaced to the COM1 port.
I am running the new keyer code with high
Chris,
see bug# 281 on the tracker. This relates to a similar problem on the COM1 port
and using the PTT line on the K1EL keyer.
Kirb - VE6IV
-
Eric,
It's a little confusing to me in the schematic. It appears that there is
a Dot signal {Tip}, a Dash signal [Ring] and a PTT signal
Just as a follow-up, the reason I am forced to delete/rename the default
.mdb file included in the build is due to an error (too many channels)
which blocks attempts at starting the console. If there's a way to
resolve this error perhaps using the default database will allow the cal
routines
In my response to PreSonus I made it clear that the issue was out
there on the various internet lists. As any manufacture should be
aware, reported problems real or otherwise have a way of propagating
across lists rather quickly. What in a sense may only affect a small
user base may grow into a
Folks,
who's all measured their audio output voltages on the Firebox using the
sound card output voltage test?
I just had opportunity to run this test and found my Firebox is only
pumping out 2.2 vac rather than the spec'ed 6.39 vac. Been working with
[EMAIL PROTECTED] in an attempt to understand
PROTECTED]
Sent: Wednesday, April 05, 2006 3:25 PM
To: 'root [knesbitt]'; FlexRadio@flex-radio.biz;
[EMAIL PROTECTED]
Subject: [SDR-1000] RE: [Flexradio] PreSonus Firebox Output Voltage
Descrepancies
I went back to the drawing board and tried to measure this myself and
had trouble
, VE6IV
root [knesbitt] wrote:
Re-ran the test as per Eric's recommendations below.
Just for clarification, remove the *_To Line Out_ *cable on rear of SDR.
Set V RMS to 1.00
Run Test
Line Out 3 4 terminated across 50 ohm load shows 1.69 vac. Terminating
this line for the test
Just an FYI for those running the PreSonus Firebox with mother boards
equipped with specific Intel chipsets, PreSonus has recommended the
following driver update to resolve a potential intermittent audio
dropout/glitch condition during playback. I'm not sure if this has any
bearing on us or not,
Was wondering if anyones performed comparisons between the Delta-44 and
the Presonus Firebox in regards to latency. I realize that with either
configuration there will be latency through the ASIO drivers, (asio4all
or the M-audio asio), however I'm concerned that some of the values I've
seen
Jimmy,
just read your comments re the Firebox on the Flex reflector. You'll
likely see my query on there as well. I was just wondering if your
current settings (sorry the formatting didn't work to well on your
configuration table) for the Firebox is 1.5 ms or 18 ms?
I can't see how this would work
Sorry everyone. Last post was meant for Jim direct. Lesson to the
wise..all email addresses are intentionally busted on the list headers.
Good idea, just don't try and reply to one ..duh! (it'll turn up on the
LIST).
Kirb - VE6IV
--
Tim,
I'm running/testing a AMD Athlon64 (3200+). The mobo uses the new nVidia
nForce 430 chipset.
This board replaced an ASUS A7V (XP3100+) running the VIA chipset
similar to yours. Both boards report the 3.58 mhz clock on perf.exe :-(
Can you or possibly others tell me how well your system
Curious if people have run the Performance Counter Query Tool
http://lightconsulting.com/~thalakan/perf.exe
http://lightconsulting.com/%7Ethalakan/perf.exe
to determine whether their motherboard and chipset supports the high
resolution clock.
I'm particularly interested in the results obtained
33 matches
Mail list logo
