Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the BPQ32
group.

   File        : /Sally128.zip
   Uploaded by : nl3snk <pd0snk@...>
   Description : Sally 1,28 host/user program to run with bpq32

You can access this file at the URL:
http://groups.yahoo.com/group/BPQ32/files/Sally128.zip

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/l/us/yahoo/groups/original/members/web/index.htmlfiles

Regards,

nl3snk <pd0snk@...>

--- In BPQ32@yahoogroups.com, "ng7m" <m.matthew.george@...> wrote:
>
> Many may find this interesting, i'm running BPQ on Windows Server 2008 64bit
and it's working just fine.
>
> With the 64bit version the 32 bit code of BPQ and other programs i'm running
execute via the WoW (Windows on Windows) 32 bit emulation... BPQ code is
obvioulsy 32 bit code.
>
> I'm also running AR-Cluster and AGW PE Pro on this same setup... all of this
code is working fine through the 32bit WoW emulation.  AR-Cluster and AGWPE have
been running fine like this for months. Very, very reliable on the server class
machine I use.
>
> One thing of interest is that when BPQ was installed with Ron's installer, the
bpq32.dll was automatically installed here:
>
> C:\Windows\SysWOW64
>
> So the OS knows you are installing 32 bit code and it takes care of the
location of the install.
>
> Ron mentioned that there have been questions about running BPQ on Vista, so
this should give us a good idea that it would work where Windows 2008 is using a
similar Vista OS kernal.
>
> Regards
>
> mg NG7M
>


This is also the thing with windows 7 witch also uses the WoW.
In windows 7 there is a windows XP implented.
So programs made for XP should also run fine in Windows 7.

You need the PRO/ultimate version of 7 for this to work.

73's Danny

----- Original Message -----

From: D.Calder

To: BPQ32@yahoogroups.com

Sent: Friday, May 01, 2009 4:03 PM

Subject: RE: [BPQ32] BPQ32 works on Windows Server 2008 64 bit

Which version of 08 are you using? Standard or what? I use 2003 enterprise and wouldn’t mind going up.

Thanks,

73 Dave

Dave Calder

n4zkf@n4zkf.com

www.n4zkf.com

From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Ron Stordahl
Sent: Friday, May 01, 2009 4:02 PM
To: BPQ32@yahoogroups.com
Subject: Re: [BPQ32] BPQ32 works on Windows Server 2008 64 bit

mg

You are the first to report that BPQ32 runs on Windows Server 2008.  I had heard that WS2008 was 'Vista like', however clearly it goes beyond Vista in having the WoW 32 bit emulation mode.  The installer I use is the NSIS system http://nsis.sourceforge.net/Main_Page

It installs bpq32.dll in the appropriate (depending upon the particular OS from Win95 thru XP).  Apparently it knows also where this belongs in WS2008, and maybe Vista too.  Credit the NSIS package with the needed smarts.

But what all this comes down to is the relentless move to Vista and then Windows 7.  I do not look forward to the changes which will likely have to be made in BPQ32 and likely also the installer.  I have several ham programs which fail to work in Vista and so far I am hiding my head in the sand as I reverted to XP!

Ron, N5IN

---

From: ng7m <m.matthew.george@gmail.com>
To: BPQ32@yahoogroups.com
Sent: Friday, May 1, 2009 1:50:50 PM
Subject: [BPQ32] BPQ32 works on Windows Server 2008 64 bit

Many may find this interesting, i'm running BPQ on Windows Server 2008 64bit and it's working just fine.

With the 64bit version the 32 bit code of BPQ and other programs i'm running execute via the WoW (Windows on Windows) 32 bit emulation... BPQ code is obvioulsy 32 bit code.

I'm also running AR-Cluster and AGW PE Pro on this same setup... all of this code is working fine through the 32bit WoW emulation. AR-Cluster and AGWPE have been running fine like this for months. Very, very reliable on the server class machine I use.

One thing of interest is that when BPQ was installed with Ron's installer, the bpq32.dll was automatically installed here:

C:\Windows\SysWOW64

So the OS knows you are installing 32 bit code and it takes care of the location of the install.

Ron mentioned that there have been questions about running BPQ on Vista, so this should give us a good idea that it would work where Windows 2008 is using a similar Vista OS kernal.

Regards

mg NG7M

>...
> This email message is a notification to let you know that
> a file has been uploaded to the Files area of the BPQ32
> group.
>
>   File        : /Sally128.zip
>   Uploaded by : nl3snk <pd0snk@...>
>   Description : Sally 1,28 host/user program to run with bpq32


Hi,
Just a note to say that this is a very old version of Sally.

Should anyone be interested in the most recent version it is available at
http://www.ntsx.co.uk/

Hi,

Did not know there is a new version available :D
Ill take a look at it :)

Danny.

--- In BPQ32@yahoogroups.com, "ted9465" <ted_c@...> wrote:
>
> >...
> > This email message is a notification to let you know that
> > a file has been uploaded to the Files area of the BPQ32
> > group.
> >
> >   File        : /Sally128.zip
> >   Uploaded by : nl3snk <pd0snk@>
> >   Description : Sally 1,28 host/user program to run with bpq32
>
>
> Hi,
> Just a note to say that this is a very old version of Sally.
>
> Should anyone be interested in the most recent version it is available at
http://www.ntsx.co.uk/
>

I receive the following error when I click on AGW to BPQ

blind(sock)failed Error 10048

Can anyone tell what this is and how to fix it.

Thanks

Stephen,

This is normally caused by running agwtobpq and agwpe with both listening on the
same port (usually 8000).

In most cases, there is no need to run bpq32 and agwpe. If you do need both (for
example if you are using sound card modems) then you need to change the port in
agwpe to say 8001, and change the bpqtoage config to match.

Other possibilities are you are running another application which uses port
8000, or you are running two copies of agwtobpq.

73,
John G8BPQ

-----Original Message-----
From: "Stephen" <ve1mpf@...>
To: BPQ32@yahoogroups.com
Sent: 03/05/09 22:25
Subject: [BPQ32] Blind Sock error

I receive the following error when I click on AGW to BPQ

blind(sock)failed Error 10048

Can anyone tell what this is and how to fix it.

Thanks

-----Original Message-----
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com]On Behalf Of Ron Stordahl
Sent: 01 May 2009 16:27
To: BPQ32@yahoogroups.com
Subject: Re: [BPQ32] new version of KISS???

Rick and Bill

I was unaware of the issue with the KISS implementation in the Kenwood D710. 

Has this been discussed on other forums?  Such as TAPR, aprssig, UIView etc?

I am sure John G8BPQ will be interested to learn of this.  He is currently sailing, and out of range, but should find out soon enough!

It should be up to Kenwood to fix this, but I won't hold my breath!

Ron, N5IN

---

From: Rick Muething <rmuething@cfl.rr.com>
To: BPQ32@yahoogroups.com
Sent: Thursday, April 30, 2009 7:27:02 PM
Subject: RE: [BPQ32] new version of KISS???

Bill/All

 

The 710 “bug” is not a violation of the KISS protocol…it is the result of trying to use the same serial port for both a TNC and a Front panel control. The problem is when in KISS mode (which sends binary packets “encapsulated in the KISS protocol”  it is possible to have the character sequence “TC 0<Cr>”  as binary or  character data within the KISS encapsulation. This sequence will be interpreted by the serial port controller in the Control head of the D710 as “escape to control mode” and which will switch the serial interface from TNC mode to front panel control mode.  This can have disastrous affects when trying to transfer binary files using KISS. 

 

One solution would be to entice Kenwood to modify the firmware in the control head to having entered the KISS protocol to ignore all mode control commands including “TC 0<Cr>”. This would require using the standardized escape KISS sequence {0xC0, 0xFF, 0xC0} prior to any control panel commands and then re enabling KISS to continue TNC operation…This gets tricky and is very likely to impact existing programs that now work.

 

The solution we used and which appears to work well and is solid is to escape the “C” character.  So when any data is sent to the TNC in KISS mode if there is an ASCII “C” it is replaced by the sequence <0xDB>”C” which essentially escapes the “TC 0<Cr>” sequence. The KISS protocol (in the D710’s KISS TNC implementation) removes the <0xDB> which is the frame escape so no modification of the transmitted data stream is actually made. Thanks to Peter Woods for figuring this out.

 

73,

 

Rick Muething, KN6KB

Winlink Development Team

 

---

From: BPQ32@yahoogroups. com [mailto:BPQ32@ yahoogroups. com] On Behalf Of T L Roberson
Sent: Thursday, April 30, 2009 5:56 PM
To: BPQ32@yahoogroups. com
Subject: Re: [BPQ32] new version of KISS???

 

Bill I have use a D710 for packet every since they went on the market and never had a problem one. I am running it with RMS Packet on 145.010 at present time.       Robby/W5SEG --- On Thu, 4/30/09, Bill Vodall WA7NWP <wa7nwp@gmail. com> wrote: From: Bill Vodall WA7NWP <wa7nwp@gmail. com> Subject: [BPQ32] new version of KISS??? To: BPQ32@yahoogroups. com Date: Thursday, April 30, 2009, 1:39 PM The new Kenwood D710 is a packet dream. 9600 and 1200 baud, built in TNC and dual band frequency agile. Wow. Is any body using one for packet? Planning on it? It turns out the D710 has a KISS bug. At least it's a bug in my opinion... I think we should let Kenwood know (loudly) that they've violated the KISS protocol. Or should we all change our KISS drivers? If the D710 was programmed to look for a simple time delay around the "TC 0<cr>" sequence the whole potential problem would be eliminated.. . Fortunately the D710 is flash updated... 73 Bill - WA7NWP ----- From an APRS group: Packet using the D710's built in TNC in Native KISS mode with special escape code to avoid the problem sequence "TC 0<Cr>" that would cause escape from TNC mode. This allows large packet sizes and messages sizes (up to 120 K compressed in Winlink)

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.287 / Virus Database: 270.12.4/2077 - Release Date: 04/29/09 18:03:00

-----Original Message-----
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com]On Behalf Of peter joseph
Sent: 04 May 2009 18:11
To: BPQ32@yahoogroups.com
Subject: RE: [BPQ32] new version of KISS???

hi could d700 work with wfbb 700i... Peter From the desk of 9Y4PJ..,,     Peter --- On Mon, 5/4/09, John Wiseman <john.wiseman@ntlworld.com> wrote: From: John Wiseman <john.wiseman@ntlworld.com> Subject: RE: [BPQ32] new version of KISS??? To: BPQ32@yahoogroups.com Date: Monday, May 4, 2009, 12:51 PM  If something like that was reported to me, I would certainly consider it a bug, and I guess Rick's workarouund is as good as any, But I wonder if the problem has ever been seen in real life compressed mail? I calculate the odds of a particular 40 bit sequence occuring by chance as 2 ** 40, or around a trillion to one. Of course it is much more likely in plain text - a message reportnig the problem couldn't be sent!   If anyone using a D710 is having this problem, i'd be happy to fix it immediately, otherwise I'll add Rick's workaround next time I change the code.   73, John G8BPQ     -----Original Message----- From: BPQ32@yahoogroups. com [mailto:BPQ32@ yahoogroups. com]On Behalf Of Ron Stordahl Sent: 01 May 2009 16:27 To: BPQ32@yahoogroups. com Subject: Re: [BPQ32] new version of KISS??? Rick and Bill I was unaware of the issue with the KISS implementation in the Kenwood D710.  Has this been discussed on other forums?  Such as TAPR, aprssig, UIView etc? I am sure John G8BPQ will be interested to learn of this.  He is currently sailing, and out of range, but should find out soon enough! It should be up to Kenwood to fix this, but I won't hold my breath! Ron, N5IN From: Rick Muething <rmuething@cfl. rr.com> To: BPQ32@yahoogroups. com Sent: Thursday, April 30, 2009 7:27:02 PM Subject: RE: [BPQ32] new version of KISS??? Bill/All   The 710 “bug” is not a violation of the KISS protocol…it is the result of trying to use the same serial port for both a TNC and a Front panel control. The problem is when in KISS mode (which sends binary packets “encapsulated in the KISS protocol”  it is possible to have the character sequence “TC 0<Cr>”  as binary or  character data within the KISS encapsulation. This sequence will be interpreted by the serial port controller in the Control head of the D710 as “escape to control mode” and which will switch the serial interface from TNC mode to front panel control mode.  This can have disastrous affects when trying to transfer binary files using KISS.    One solution would be to entice Kenwood to modify the firmware in the control head to having entered the KISS protocol to ignore all mode control commands including “TC 0<Cr>”. This would require using the standardized escape KISS sequence {0xC0, 0xFF, 0xC0} prior to any control panel commands and then re enabling KISS to continue TNC operation…This gets tricky and is very likely to impact existing programs that now work.   The solution we used and which appears to work well and is solid is to escape the “C” character.  So when any data is sent to the TNC in KISS mode if there is an ASCII “C” it is replaced by the sequence <0xDB>”C” which essentially escapes the “TC 0<Cr>” sequence. The KISS protocol (in the D710’s KISS TNC implementation) removes the <0xDB> which is the frame escape so no modification of the transmitted data stream is actually made. Thanks to Peter Woods for figuring this out.   73,   Rick Muething, KN6KB Winlink Development Team From: BPQ32@yahoogroups. com [mailto:BPQ32@ yahoogroups. com] On Behalf Of T L Roberson Sent: Thursday, April 30, 2009 5:56 PM To: BPQ32@yahoogroups. com Subject: Re: [BPQ32] new version of KISS??? Bill I have use a D710 for packet every since they went on the market and never had a problem one. I am running it with RMS Packet on 145.010 at present time.       Robby/W5SEG --- On Thu, 4/30/09, Bill Vodall WA7NWP <wa7nwp@gmail. com> wrote: From: Bill Vodall WA7NWP <wa7nwp@gmail. com> Subject: [BPQ32] new version of KISS??? To: BPQ32@yahoogroups. com Date: Thursday, April 30, 2009, 1:39 PM The new Kenwood D710 is a packet dream. 9600 and 1200 baud, built in TNC and dual band frequency agile. Wow. Is any body using one for packet? Planning on it? It turns out the D710 has a KISS bug. At least it's a bug in my opinion... I think we should let Kenwood know (loudly) that they've violated the KISS protocol. Or should we all change our KISS drivers? If the D710 was programmed to look for a simple time delay around the "TC 0<cr>" sequence the whole potential problem would be eliminated.. . Fortunately the D710 is flash updated... 73 Bill - WA7NWP ----- From an APRS group: Packet using the D710's built in TNC in Native KISS mode with special escape code to avoid the problem sequence "TC 0<Cr>" that would cause escape from TNC mode. This allows large packet sizes and messages sizes (up to 120 K compressed in Winlink) No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.287 / Virus Database: 270.12.4/2077 - Release Date: 04/29/09 18:03:00

----- Original Message -----

From: John Wiseman

To: BPQ32@yahoogroups.com

Sent: Tuesday, May 05, 2009 1:31 AM

Subject: [BPQ32] Chat Server

Hi,

 

I am writing a windows based replacement for the FastChat server that a few of you are using. I would like to add a facilitty to link servers together, and it seems sensible to be compatible with oither systes. Does anyone have a spec for the NOS convers linking protocol?

 

73,

John G8BPQ

 

-----Original Message-----
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com]On Behalf Of Hank Oredson
Sent: 05 May 2009 15:03
To: BPQ32@yahoogroups.com
Subject: Re: [BPQ32] Chat Server

Here's the protocol for the RoundTable chat server:

// Copyright (C) 1987 - 2008
// H. N. Oredson

 

// RoundTable server.

 

// Protocol version.

 

#define FORMAT       1
#define FORMAT_O     0   // Offset in frame to format byte.
#define TYPE_O       1   // Offset in frame to kind byte.
#define DATA_O       2   // Offset in frame to data.

 

// Protocol Frame Types.

 

#define id_join   'J'    // User joins RT.
#define id_leave  'L'    // User leaves RT.
#define id_link   'N'    // Node joins RT.
#define id_unlink 'Q'    // Node leaves RT.
#define id_data   'D'    // Data for all users.
#define id_send   'S'    // Data for one user.
#define id_topic  'T'    // User changes topic.
#define id_user   'I'    // User login information.

 

// RT protocol version 1.
// First two bytes are FORMAT and Frame Type.
// These are followed by text fields delimited by blanks.
// Note that "node", "to", "from", "user" are callsigns.

 

// ^AD<node> <user> <text>        - Data for all users.
// ^AI<node> <user> <name> <qth>  - User information.
// ^AJ<node> <user> <name> <qth>  - User joins.
// ^AL<node> <user> <name> <qth>  - User leaves.
// ^AN<node> <node> <alias>       - Node joins.
// ^AQ<node> <node>               - Node leaves.
// ^AS<node> <from> <to>   <text> - Data for one user.
// ^AT<node> <user> <topic>       - User changes topic.

 

// Connect protocol:

 

// 1. Connect to node.
// 2. Send *RTL
// 3. Receive OK. Will get disconnect if link is not allowed.
// 4. Go to it.

 

// Disconnect protocol:

 

// 1. If there are users on this node, send an id_leave for each user,
//    to each node you are disconnecting from.
// 2. Disconnect.

----- Original Message -----

From: John Wiseman

To: BPQ32@yahoogroups.com

Sent: Tuesday, May 05, 2009 1:31 AM

Subject: [BPQ32] Chat Server

Hi,

 

I am writing a windows based replacement for the FastChat server that a few of you are using. I would like to add a facilitty to link servers together, and it seems sensible to be compatible with oither systes. Does anyone have a spec for the NOS convers linking protocol?

 

73,

John G8BPQ

 

----- Original Message -----

From: John Wiseman

To: BPQ32@yahoogroups.com

Sent: Tuesday, May 05, 2009 7:11 AM

Subject: RE: [BPQ32] Chat Server

Thanks, Hank.

 

Is there any loop detection mechanism?

 

 

John

 

 

 

-----Original Message-----
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com]On Behalf Of Hank Oredson
Sent: 05 May 2009 15:03
To: BPQ32@yahoogroups.com
Subject: Re: [BPQ32] Chat Server

Here's the protocol for the RoundTable chat server:

// Copyright (C) 1987 - 2008
// H. N. Oredson

 

// RoundTable server.

 

// Protocol version.

 

#define FORMAT       1
#define FORMAT_O     0   // Offset in frame to format byte.
#define TYPE_O       1   // Offset in frame to kind byte.
#define DATA_O       2   // Offset in frame to data.

 

// Protocol Frame Types.

 

#define id_join   'J'    // User joins RT.
#define id_leave  'L'    // User leaves RT.
#define id_link   'N'    // Node joins RT.
#define id_unlink 'Q'    // Node leaves RT.
#define id_data   'D'    // Data for all users.
#define id_send   'S'    // Data for one user.
#define id_topic  'T'    // User changes topic.
#define id_user   'I'    // User login information.

 

// RT protocol version 1.
// First two bytes are FORMAT and Frame Type.
// These are followed by text fields delimited by blanks.
// Note that "node", "to", "from", "user" are callsigns.

 

// ^AD<node> <user> <text>        - Data for all users.
// ^AI<node> <user> <name> <qth>  - User information.
// ^AJ<node> <user> <name> <qth>  - User joins.
// ^AL<node> <user> <name> <qth>  - User leaves.
// ^AN<node> <node> <alias>       - Node joins.
// ^AQ<node> <node>               - Node leaves.
// ^AS<node> <from> <to>   <text> - Data for one user.
// ^AT<node> <user> <topic>       - User changes topic.

 

// Connect protocol:

 

// 1. Connect to node.
// 2. Send *RTL
// 3. Receive OK. Will get disconnect if link is not allowed.
// 4. Go to it.

 

// Disconnect protocol:

 

// 1. If there are users on this node, send an id_leave for each user,
//    to each node you are disconnecting from.
// 2. Disconnect.

----- Original Message -----

From: John Wiseman

To: BPQ32@yahoogroups.com

Sent: Tuesday, May 05, 2009 1:31 AM

Subject: [BPQ32] Chat Server

Hi,

 

I am writing a windows based replacement for the FastChat server that a few of you are using. I would like to add a facilitty to link servers together, and it seems sensible to be compatible with oither systes. Does anyone have a spec for the NOS convers linking protocol?

 

73,

John G8BPQ

 

Here's the source for the old Linux linked convers system server.
This is the same system JNOS interacts with.  I'm not familiar with
any documents actually describing the protocol.

<http://radio.linux.org.au/pkgdetail.phtml?sectpat=packet&ordpat=subsection&desc\
pat=&pkgid=66>

JNOS source will also probably be a good reference.

I don't know if this works with the Round Table system Hank mentioned.

73
Bill - WA7NWP

On Tue, May 5, 2009 at 1:31 AM, John Wiseman <john.wiseman@...> wrote:
>
>
> Hi,
>
> I am writing a windows based replacement for the FastChat server that a few
> of you are using. I would like to add a facilitty to link servers together,
> and it seems sensible to be compatible with oither systes. Does anyone have
> a spec for the NOS convers linking protocol?

I want to thank all for your help. I have everything running as I want. The
problem I was have with DX-Spider and BPQ was I did enable BPQ in Spider but
failed to dis-enable AGW both were trying to connect.
It all works now so that you, I post this as others may have same problem. If
you do and I can help just let me know.
73
Stephen



--- In BPQ32@yahoogroups.com, "Stephen" <ve1mpf@...> wrote:
>
> I receive the following error when I click on AGW to BPQ
>
> blind(sock)failed Error 10048
>
> Can anyone tell what this is and how to fix it.
>
> Thanks
>

BPQ32_410i_2009May09 just released!

A new release, BPQ32_410i_2009May09 is now available on the BPQ32 Yahoo Group
site. The links are on the home page following the description of the group at:
http://groups.yahoo.com/group/BPQ32/

The BPQ32 Installer automatically selects the update mode if BPQ32 exists in the
selected install location and retains your current configuration while updating
all the program components.

Description of changes from the release document:

BPQ32_410i_2009May09:

BPQTelnetServer to 2.1.5.1 raising the number of users as defined in
BPQTelnetServer.cfg which was previously limited to 249.

BPQCfg.exe to 1.0.6.2 by adding a `C' style multiline comment feature to
bpqcfg.txt thus:

   /* This begins a multi-line comment
   Statement (1 or more lines)
   */ ;This ends a multi-line comment

This is useful in commenting out a range of lines in bpqcfg.txt. Refer to the
examples in the \Examples folders.

BPQAXIP.dll to 1.14.1.1 by adding two new options to the BPQAXIP.cfg file and
changing the default behavior to NOT add information to BPQ32's nodes table for
AX/IP/UDP nodes which are not explicitly listed in the bpqaxip.cfg file.  The
default behavior can be modified with these commands:

   DONTCHECKSOURCECALL ;This option allows entries in the NODES table
                       ;from stations sending you nodes broadadcasts
                       ;without the corresponding node being
                       ;configured in bpqaxip.cfg.

   AUTOADDMAP          ;This option automatically adds the node call
                       ;and address of a node for which you do not
                       ;have a pre-arranged fixed entry in
                       ;bpqaxip.cfg. If the option DONTCHECKSOURCECALL
                       ;is specified then the AUTOADDMAP option is
                       ;ignored.

Thanks to John Wiseman G8BPQ for his continuing work to enhance BPQ32.

73 Ron Stordahl N5IN

On April 12th in message # 1866 from Bill Vodall WA7NWP titled "Automatic AXIP"
a request was made to allow nodes not included in the static list in bpqaxip.cfg
to be automatically added to the list of nodes to which connections are
permitted.

While John G8BPQ had security reservations about this, he has added this feature
in the release which was issued on 2009/May/09.

It is applicable only via AX/UDP and only when the AUTOADDMAP option is included
in bpqaxip.cfg.

The response is on the same UDP port number as the incoming packet.

Ron Stordahl, N5IN

For any Sysops that are linked to me...

I will be taking both the DxCluster and the BPQ
Node offline between May 13th and May 18th. I
will resume normal operations of both on May 18th.

I'm sorry to use this 'group' as a method of
reaching all of you, but I unfortunately do not
have all your 'current' email addresses.

73, Mark K2CAN

I need help with the tuning of a mfj1270C.

Robby

Jim try this:

Change R56 from 7.5K to 4.7K
Jumper out cap C71
Remove cap C73

Let me know if you need more help.

73

Mike Melnik N9PMO
Web Site: www.n9pmo.com
 
-----Original Message-----
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of
James Wagner
Sent: Friday, May 29, 2009 11:21 AM
To: BPQ32@yahoogroups.com
Subject: Re: [BPQ32] MFJ-1270C




A KISS chip does not solve issues like receive and transmit audio levels. 

Jim Wagner
KA7EHK

--- On Thu, 5/28/09, Edward Tune <ottotune@...> wrote:

From: Edward Tune <ottotune@...>
Subject: Re: [BPQ32] MFJ-1270C
To: BPQ32@yahoogroups.com
Date: Thursday, May 28, 2009, 8:42 PM
Robby, not sure what you mean by 'tuning' but put a KISS chip in it and your
tuning is done.
 
Regards,
Otto, KV7J
On Thu, May 28, 2009 at 5:45 PM, Thurman L Roberson <w5seg@swbell. net>
wrote:

I need help with the tuning of a mfj1270C.

Robby

Jim

The modification I sent will increase your AFKT TX levels, as for the
receive
Level, are you pulling the audio from a DATA Jack, this would be a low level

Output as the RX audio is from the receiver's discriminator typically used
for
9600 Radio Speed BAUD, if I understand the brief description of the problems
you are having, the problems with Both Receive and TX (AFSK) or (FSK)
output?

Mike Melnik N9PMO
Web Site: www.n9pmo.com
 
-----Original Message-----
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of
James Wagner
Sent: Friday, May 29, 2009 1:50 PM
To: BPQ32@yahoogroups.com
Subject: RE: [BPQ32] MFJ-1270C




It was not my problem. I was just responding to the previous responder who
suggested that all you need to do is install a KISS ROM. My suggestion is
that there ARE actual "tuneup" things that are appropriate for one of those
TNCs.

Jim, KA7EHK

--- On Fri, 5/29/09, Mike MelInik <mmelnik1@...> wrote:

From: Mike Melnik <mmelnik1@...>
Subject: RE: [BPQ32] MFJ-1270C
To: BPQ32@yahoogroups.com
Date: Friday, May 29, 2009, 9:37 AM
Jim try this:

Change R56 from 7.5K to 4.7K
Jumper out cap C71
Remove cap C73

Let me know if you need more help.

73

Mike Melnik N9PMO
Web Site: www.n9pmo.com
 
-----Original Message-----
From: BPQ32@yahoogroups. com [mailto:BPQ32@yahoogroups. com] On Behalf Of
James Wagner
Sent: Friday, May 29, 2009 11:21 AM
To: BPQ32@yahoogroups. com
Subject: Re: [BPQ32] MFJ-1270C

A KISS chip does not solve issues like receive and transmit audio levels. 

Jim Wagner
KA7EHK

--- On Thu, 5/28/09, Edward Tune <ottotune@gmail. com> wrote:

From: Edward Tune <ottotune@gmail. com>
Subject: Re: [BPQ32] MFJ-1270C
To: BPQ32@yahoogroups. com
Date: Thursday, May 28, 2009, 8:42 PM
Robby, not sure what you mean by 'tuning' but put a KISS chip in it and your
tuning is done.
 
Regards,
Otto, KV7J
On Thu, May 28, 2009 at 5:45 PM, Thurman L Roberson <w5seg@swbell. net>
wrote:

I need help with the tuning of a mfj1270C.

Robby