All,
I have been working on several enhancements (features, fixes, documentation, and
robustness improvements). This new release is 0.3.0.0 and is posted in the
files section. The help has had significant enhancements incuding information
for use with Flex radios.
Unfortunately one of the important robustness improvements to the Frame sync
coding is NOT compatible with prior 0.1.x.x or 0.2.x.x. versions. This will
require an uninstall of those versions and a new install of version 0.3.0.0.
None of your existing settings will be lost in this process if you follow the
ReadMeFirst file contained in the 0.3.0.0 Full install.zip.
My testing has shown these changes provide an improved robustness and I don't
beleive any further significant changes will be required to the protocol causing
incompatibilities. I expect to enable auto udpateing on the next release after
0.3.0.0.
Good luck. Thanks again for all your feedback. If you find a problem or don't
understand something in the help let me know...that is how we have made such
good progress.
73,
Rick Muething, KN6KB
Hi Yussi - I copied your CQ OK and called you but no contact. I am still
listening on 14073.
73 Terry GW0EZY
--- In V4Protocol@yahoogroups.com, "Juhani" <yufenau@...> wrote:
>
> Im QRV now on 14073 for any.
> 73 "Yussi" OH7TE
>
Got it working...I think!
I need some clarification on the ARQ mode. When I attempt to send a note to a
connected station why does it keep sending the same not several times for 30
sec?
I see this happens when calling CQ which I presume is correct.
Did I miss a setting or set something incorrectly?
Ted, WB2LOU
CQ is really just a specially formatted data frame. It is just meant to tell others you are available and what your call signs is....Just like a voice or CW CQ.
You make an ARQ connection when someone calls you and you ACK their connect request....once that happens you are “connected”. Now data sent (from the ISS ...the station initiating the connection) will flow when:
1) There is data in the outbound queue (not just in the keyboard text window).
2) There is propagation to the other station (the IRS)
3) The IRS Acknowledges a successful decode with an ACK
4) That ACK is received by the ISS allowing it to advance to the next frame of data.
If you don’t have 2 AND 3 AND 4 then the ISS repeats the data until you get 2) 3) and 4) or you timeout (depends on your timeout setting in the setup (default = 90 sec). This is pretty much the way virtually all ARQ mechanisms work.
There is no operational difference in Version 0.3.0.0 and versions 0.2.x.x. except the change in the coding for the frame type and that makes the two versions incompatible as I said.
I need some clarification on the ARQ mode. When I attempt to send a note to a connected station why does it keep sending the same not several times for 30 sec?
I see this happens when calling CQ which I presume is correct.
Did I miss a setting or set something incorrectly?
0.3.0.0 down loaded fine on my Laptop using VISTA. No lock ups so far during
some testing.
I have one issue I'm curious about and was noticeable in past revisions.... The
Two Tone test is a great tool for setting the average
output. I'm using a Bird 43 Watt Meter and set the two tone level to exactly 50
Watts using the Icom USB Audio level control. (IC-7200) When I transmit
from the text window, I average about 79 or 80 Watts. I think the reason is
because of the multi tone V4 average
over only 2 tones. Does this look about right?
Thanks;
Chuck, WA7BRL
0.3.0.0 down loaded fine on my Laptop using VISTA. No lock ups so far during some testing.
I have one issue I'm curious about and was noticeable in past revisions.... The Two Tone test is a great tool for setting the average output. I'm using a Bird 43 Watt Meter and set the two tone level to exactly 50 Watts using the Icom USB Audio level control. (IC-7200) When I transmit from the text window, I average about 79 or 80 Watts. I think the reason is because of the multi tone V4 average over only 2 tones. Does this look about right?
Ed; This is where I got it:
You can access this file at the URL:
http://groups.yahoo.com/group/V4Protocol/files/V4ChatSetup%200.3.0.0.zip
73;
Chuck
----- Original Message -----
From: "Ed Woods WD9DVA" <wd9dva@...>
To: V4Protocol@yahoogroups.com
Sent: Monday, June 6, 2011 12:49:52 PM
Subject: Re: [V4Protocol] Latest V4 Chat
Chuck where is the latest ver (3.0.0.0) found? 73 Ed WD9DVA
Some stations hrd today on 14 but no ARQ link contacts.
I must say that Europen Multipsk ALE400 ARQ FAE working like good an American
car Buick.
BUT: We know that V4 is under BETA test and here in EU are patience for better
performance of V4.
All the best power for Rick et al!
73 "Yussi" OH7TE
The V4 waveform ONLY sends two tones at the same time during the leader which is the same as the two tone wave form. This waveform will show a typical (on an AVERAGE reading wattmeter) value of about 70 Watts at 100 wats PEP.
The rest of the waveform for V4 is pure FSK sending only one tone at a time with no phase discontinuity. Depending on the peak to average reading capability of the meter it will show different values but the peak value AND average of the FSK waveform is 84% of the peak value of the two tone waveform. The reason for this is just to minimize transmitter heating of the high duty cycle wave during long periods as the ISS sending data.
In all cases the important fact is that the level for the two tone test to NOT generate significant ALC since that would cause distortion and splatter of the signal. If the two tone test does not generate ALC the data waveform should not either since it is 84% of the peak value.
I am really missing something, so I'll ask my dumb question. How do you ACK the connect request? I ask for 2 reasons...First when a station calls there seems to be a auto connection made and from that point nothing I want to send via <Ctrl>Enter seems to xmit. Second if Itry using the ARQ Call dialog box with the stations call a red message shows stating :Not while connected." I have dug throught the help files and find no logical answer.
Ted, WB2LOU
On Mon, Jun 6, 2011 at 2:59 PM, Rick Muething <rmuething@...> wrote:
CQ is really just a specially formatted data frame. It is just meant to tell others you are available and what your call signs is....Just like a voice or CW CQ.
You make an ARQ connection when someone calls you and you ACK their connect request....once that happens you are connected. Now data sent (from the ISS ...the station initiating the connection) will flow when:
1) There is data in the outbound queue (not just in the keyboard text window).
2) There is propagation to the other station (the IRS)
3) The IRS Acknowledges a successful decode with an ACK
4) That ACK is received by the ISS allowing it to advance to the next frame of data.
If you dont have 2 AND 3 AND 4 then the ISS repeats the data until you get 2) 3) and 4) or you timeout (depends on your timeout setting in the setup (default = 90 sec). This is pretty much the way virtually all ARQ mechanisms work.
There is no operational difference in Version 0.3.0.0 and versions 0.2.x.x. except the change in the coding for the frame type and that makes the two versions incompatible as I said.
I need some clarification on the ARQ mode. When I attempt to send a note to a connected station why does it keep sending the same not several times for 30 sec?
I see this happens when calling CQ which I presume is correct.
Did I miss a setting or set something incorrectly?
Ted, WB2LOU
-- You cannot change history, but you can make history ! Education is the only legal cure for stupidity.
doing some testing, station to station.
...V4Chat starts now in ARQ mode:disconnected.
...cursor is in the receive window. Why...
In that mode, without a connection, the receive windows shows (prints)
garbeled characters...
Robert V31AE
testing station to station
Station A calls Station B (call sign)
Just let them idle ... (no keyboard entry)
Both station disconnect after a set time
CW id from A sent twice!
Robert V31AE
Read the help files on establishing an ARQ conneciton. Here is the summary.
1) If you want to call CQ follow the process described. ARQ Call on the Calling menu click Send CQ. This sends a 30 second connect request to call sign CQ (that is not a legitimate call sign so no one will auto answer.)
2) If someone hears your CQ and wants to call you. (Or you want to answer someone elses) you use the Call call sign with their specific call.
3) In the TNC form it shows if you are connected or not and to which station. It also shows whether you are the IRS (receiving station) or the ISS (sending station)
4) To enter data type it into the keyboard text box. Hit <Ctrl> Return to move entered text to the outbound queue. If you are the ISS it will start sending data waiting after each frame for the (AUTOMATIC) ACK from the other side. You NEVER have to manually Send an ACK or NAK that is the job of the protocol and its described in nauseating detail in the state diagrams and protocol spec. The V4 TNC implements the protocol just like a hardware TNC implements the Pactor or Packet protocol.
If you are the IRS you wont be able to send until the other side has finished and sends an IDL frame (again totally automatic).
Think of this being the way two people would Talk (hence the name V4 Chat) He sends ....you listen...when he is done sending, you send he listens. The protocol protects against having two senders or two listeners....Always one is ISS and one is IRS and those rolls are exchanged whenever the senders buffer goes empty (all the data has been sent and ACKed) and the other side (the IRS) as something to send (data in the output queue.) Its all automatic and once a connection is made it requires ONLY typing data into the keyboard box and typing <Ctrl> Enter to move it to the output queue. That mechanism was developed in the early versions to allow you to edit text in the text box BEFORE committing it to transmission.
Read though the help on the ARQ operation and look at the state diagrams. Also look at the V4 TNC form...it shows in big letters who is the IRS and the ISS and which station you are connected to. If you are connected it wont let you send out a connect request (Not while connected) ...only ONE connection to ONE station at a time in ARQ mode (anything else would be total chaos!).
I am really missing something, so I'll ask my dumb question. How do you ACK the connect request? I ask for 2 reasons...First when a station calls there seems to be a auto connection made and from that point nothing I want to send via <Ctrl>Enter seems to xmit. Second if Itry using the ARQ Call dialog box with the stations call a red message shows stating :Not while connected." I have dug throught the help files and find no logical answer.
Ted, WB2LOU
On Mon, Jun 6, 2011 at 2:59 PM, Rick Muething <rmuething@...> wrote:
CQ is really just a specially formatted data frame. It is just meant to tell others you are available and what your call signs is....Just like a voice or CW CQ.
You make an ARQ connection when someone calls you and you ACK their connect request....once that happens you are connected. Now data sent (from the ISS ...the station initiating the connection) will flow when:
1) There is data in the outbound queue (not just in the keyboard text window).
2) There is propagation to the other station (the IRS)
3) The IRS Acknowledges a successful decode with an ACK
4) That ACK is received by the ISS allowing it to advance to the next frame of data.
If you dont have 2 AND 3 AND 4 then the ISS repeats the data until you get 2) 3) and 4) or you timeout (depends on your timeout setting in the setup (default = 90 sec). This is pretty much the way virtually all ARQ mechanisms work.
There is no operational difference in Version 0.3.0.0 and versions 0.2.x.x. except the change in the coding for the frame type and that makes the two versions incompatible as I said.
I need some clarification on the ARQ mode. When I attempt to send a note to a connected station why does it keep sending the same not several times for 30 sec?
I see this happens when calling CQ which I presume is correct.
Did I miss a setting or set something incorrectly?
Ted, WB2LOU
-- You cannot change history, but you can make history ! Education is the only legal cure for stupidity.
Please read the help! This is all described in there. This allows you to monitor ARQ or FEC data while being in the ARQ mode (disconnected) . If you can’t decode the signal and get garbled text (red strikethrough) it is because there is either no signal or it is too weak or off frequency. Once connected to a specific call sign you will get ONLY bold BLack text (always error free) in the receive window. If you want to clear the old ([pre connected) text simply right click on the window.
The idea is to allow you to operate from the keyboard (This IS a keyboard mode) without having to go back and change from Monitor or FEC to ARQ There is no differenced in the data in either ARQ or FEC...just the protocol.
1) Someone enters their call sign as “CQ”. Actually this CAN’T happen....there is a filter on the call sign setup to INSURE it is a legitimate Amateur or MARS call sign.
2) (This is what likely happened) Someone is calling CQ Another QSO on the Same or nearby frequency is on going (and an ACK from that QSO is interpreted by the station calling CQ as an ACK). I can probably build protection in the protocol for that so a call to CQ can never recognize an ACK and therefore will ALWAYS time out.
But this brings up an issue I observed today...One frquency several people calling CQ, calling stations or trying to work a connection ALL at the same time ALL on the same frequency...Hey guys this is a 200 Hz narrow band mode not spread spectrum! You can’t have two QSOs on the same frequency at the same time. (same for Pactor, Amtor, WINMOR etc...Packet can time share a frequency at the expense of throughput).
Well I was one of those part call signs and it was my first ever contact with V4
so was probably finger trouble at my end. Will keep trying though.
Bob
--- In V4Protocol@yahoogroups.com, "Juhani" <yufenau@...> wrote:
>
> Many signals hrd but and only minor parts of call sigh etc, no link connects
here in "EU" on 14073.
> So we wait fix of SW.
> 73 "Yussi" OH7TE
>
The newest V4 Version does not work properly on my old XP PC (delays and
improper FEC copy) , altough I had no problems with the previous V4
versions. I have no problems with WINMOR but I also had similar problems
with older WINMOR versions.
73
Gert, OE3ZK
----- Original Message -----
From: "Bob Thornton" <bob.thornton@...>
To: <V4Protocol@yahoogroups.com>
Sent: Tuesday, June 07, 2011 9:44 AM
Subject: [V4Protocol] Re: V4 last SW
> Well I was one of those part call signs and it was my first ever contact
> with V4 so was probably finger trouble at my end. Will keep trying though.
>
> Bob
>
> --- In V4Protocol@yahoogroups.com, "Juhani" <yufenau@...> wrote:
>>
>> Many signals hrd but and only minor parts of call sigh etc, no link
>> connects here in "EU" on 14073.
>> So we wait fix of SW.
>> 73 "Yussi" OH7TE
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
With eg. Bob G3WKW, most only parts of call decoded, only sometimes 100%.
Hrd many stations this morning but no real link estabilised.
CUL soon, "Yussi" OH7TE
Rick. Hope some of your frame sync ideas may benefit WINMOR later.
Some of the most difficult part of a WM link is decoding the first response.
Once linked, it always works. Cause of the starting trouble is usually due to
noisy background for client.
73 de la7um Finn
--- In V4Protocol@yahoogroups.com, "kn6kb" <rmuething@...> wrote:
>
> All,
>
> I have been working on several enhancements (features, fixes, documentation,
and robustness improvements). This new release is 0.3.0.0 and is posted in the
files section. The help has had significant enhancements incuding information
for use with Flex radios.
>
> Unfortunately one of the important robustness improvements to the Frame sync
coding is NOT compatible with prior 0.1.x.x or 0.2.x.x. versions. This will
require an uninstall of those versions and a new install of version 0.3.0.0.
None of your existing settings will be lost in this process if you follow the
ReadMeFirst file contained in the 0.3.0.0 Full install.zip.
>
> My testing has shown these changes provide an improved robustness and I don't
beleive any further significant changes will be required to the protocol causing
incompatibilities. I expect to enable auto udpateing on the next release after
0.3.0.0.
>
> Good luck. Thanks again for all your feedback. If you find a problem or don't
understand something in the help let me know...that is how we have made such
good progress.
>
> 73,
>
> Rick Muething, KN6KB
>
Read the help files on establishing an ARQ conneciton. Here is the summary.
1) If you want to call CQ follow the process described. ARQ Call on the Calling menu click Send CQ. This sends a 30 second connect request to call sign CQ (that is not a legitimate call sign so no one will auto answer.)
2) If someone hears your CQ and wants to call you. (Or you want to answer someone elses) you use the Call call sign with their specific call.
3) In the TNC form it shows if you are connected or not and to which station. It also shows whether you are the IRS (receiving station) or the ISS (sending station)
4) To enter data type it into the keyboard text box. Hit <Ctrl> Return to move entered text to the outbound queue. If you are the ISS it will start sending data waiting after each frame for the (AUTOMATIC) ACK from the other side. You NEVER have to manually Send an ACK or NAK that is the job of the protocol and its described in nauseating detail in the state diagrams and protocol spec. The V4 TNC implements the protocol just like a hardware TNC implements the Pactor or Packet protocol.
If you are the IRS you wont be able to send until the other side has finished and sends an IDL frame (again totally automatic).
Think of this being the way two people would Talk (hence the name V4 Chat) He sends ....you listen...when he is done sending, you send he listens. The protocol protects against having two senders or two listeners....Always one is ISS and one is IRS and those rolls are exchanged whenever the senders buffer goes empty (all the data has been sent and ACKed) and the other side (the IRS) as something to send (data in the output queue.) Its all automatic and once a connection is made it requires ONLY typing data into the keyboard box and typing <Ctrl> Enter to move it to the output queue. That mechanism was developed in the early versions to allow you to edit text in the text box BEFORE committing it to transmission.
Read though the help on the ARQ operation and look at the state diagrams. Also look at the V4 TNC form...it shows in big letters who is the IRS and the ISS and which station you are connected to. If you are connected it wont let you send out a connect request (Not while connected) ...only ONE connection to ONE station at a time in ARQ mode (anything else would be total chaos!).