I have installed the Flex D-Star dongle on my Flex-6500. Simplex operation works except that the callsign extension and Message do not print on a D-Star Icom ID-5100 radio I was talking to..
In repeater mode, my system will not bring up a D-Star repeater when I press PTT. But when I release PTT, the repeater transmits a short burst and the D-Star Client prints a line with Called station identified as ********. See below. The TX EQ on the 6500 is OFF, The frequency I am using is 1 kHz below the nominal frequency as this seems to be more reliable. This is with the D-Star repeater KE5RCS but I get the same result with W5KA. Both local.
In simplex mode, my parameters are:
I am running SmartSDR v.1.6.21. Can anyone help with these problems?
Ron W5RKN
In repeater mode, my system will not bring up a D-Star repeater when I press PTT. But when I release PTT, the repeater transmits a short burst and the D-Star Client prints a line with Called station identified as ********. See below. The TX EQ on the 6500 is OFF, The frequency I am using is 1 kHz below the nominal frequency as this seems to be more reliable. This is with the D-Star repeater KE5RCS but I get the same result with W5KA. Both local.
In simplex mode, my parameters are:
I am running SmartSDR v.1.6.21. Can anyone help with these problems?
Ron W5RKN
Posted 3 years ago
I am having the same issue, and have identified the problem. The radio or dongle, or software, whatever is TRUNCATING the beginning of the transmission, in other words, your ID string at the beginning of transmit is being generated, but the radio is late in transmitting, so that portion ends up not sent. The repeater rejects it because there is no ID. Hence the ************ AN aggravating problem that I would love to see resolved. Maybe flex can fix this top where there is a short 1/2 second delay buffer to ensure all is transmitted?????
Tim - W4TME, Customer Experience Manager
I have entered this problem report into our bug tracker as issue #4613 for additional investigation. Thank you for the defect report.
so cant you pad your transmission id with enough spaces to cover that 1/2 second delay so then the first thing transmitted would be your id?
Make sure that your transmit low cut is set to 0. If you bring your low
cut up, you will start truncating your data stream. The call sign is
the first thing to truncate, then the message.
have set low cut to 0
problem persists.
problem persists.
Tim:
How are we coming on this bug???? Looks like that is all that stands between it working?
Peter
How are we coming on this bug???? Looks like that is all that stands between it working?
Peter
By posting this thread EVERY SINGLE DAY until they engage that's how. It should remain on TOP of the stack at all times. While they re at it, what about the ANF and NB issues, these two issues are FOUR years old.....??????????????
Have you not learned by now? wining and complaining every day will NOT change anything. NOTHING, Flex will hold the course and continue with thier plans as they see fit.
Perhaps D star never will work any better, who knows?
I suspect out of all Flex customers less than 1% are using D star with the Flex.
Perhaps D star never will work any better, who knows?
I suspect out of all Flex customers less than 1% are using D star with the Flex.
Oh really? Tell that to the civil rights marchers Whining not wining by the way
oops yes my spelling needs correction...
I'm going to push this thread to the top EVERY SINGLE DAY until this is addressed. Along with the Noise Blanker now FOUR years out, and the automatic notch filter issues as well. If this thread is closed, I'll start a new one, if I am banned I will start a web page and post on every single solitary forum I can find. I insist these issues be dealt with. FRS has an obligation to deal with foundational issues like this before embarking on other new projects.
Peter
Peter
W2PP, this thread is not likely to close, and you will not be banned. You are not causing that much of a problem for Flex. Just a customer that demands things to happen the way you want them. Nothing new.
Flex has given a long explanation as to how they prioritise things and what order.
Flex has given a long explanation as to how they prioritise things and what order.
Thank you for that. I’m still going to post every day I’d engage in a sit in in the Austin office if I could.
Bill,
I think you are very much mistaken by saying "Just a customer that demands things to happen the way you want them. Nothing new." This is far from that. There are many many post that can come under that assumption BUT the DSTAR issues is far from one of them. These radios were advertised as supporting DSTAR and in fact USB Dongles sold under the belief that it worked..WRONG. All we are proposing is that we get what we paid for and not wait years and years for this to happen. Customers should be able to "demand" what they paid for PERIOD.
I think you are very much mistaken by saying "Just a customer that demands things to happen the way you want them. Nothing new." This is far from that. There are many many post that can come under that assumption BUT the DSTAR issues is far from one of them. These radios were advertised as supporting DSTAR and in fact USB Dongles sold under the belief that it worked..WRONG. All we are proposing is that we get what we paid for and not wait years and years for this to happen. Customers should be able to "demand" what they paid for PERIOD.
Because it is not working to your satisfaction, have you asked for a refund?
I (we) do not want a refund..we just want it to work as promised and I am sure the majority of readers here would agree. Especially after more than three years. Vendors, not matter whom, need to pay attention and "get it done".
The Dv3000 Usb stick worked fine for the first year or so. Then FLEX did a dstar waveform software update, and now we have the decoding, timing issue. The stick works fine running software on a PC or RASPBERRY PI.
Ron Parsons
I tried all combinations of "KE5RCS C" and "KE5RCS G" in both RPT1 and RPT2 but no change in operation. As I understand, RPT1 should have "C" as I am going into the repeater C module. If not using the gateway. RPT2 can also have C to have the voice come back out on the C module. G is used for the gateway.
What I don't understand is why the repeater output is off while I am transmitting, but the repeater transmits a short burst after I quit transmitting that is printed with CALLED: ********.
Ron W5RKN