¿ªÔÆÌåÓý

Date

Re: Dire Wolf Connected Mode 9600 baud

 

Roger that Kevin.

I also need a good cheat sheet by my side when I see those useful mnemonics.

John

On Mon, May 1, 2017 at 5:05 PM, Kevin Utzy krutzy62@... [direwolf_packet] <direwolf_packet@...> wrote:
?

John,

I posted this because I really would like to know what that data is telling me.? Right now all my levels are maxed out.? Possibly over modulation and clipping?? When the BBS gets moved what meaning information can I get from the message?

I did read that 9600 article last night and it was very informative.? Just trying to learn as much as I can.? :-)

Kevin
KA4RNH


On 5/1/2017 3:25 PM, John Huggins john.huggins.ee@... [direwolf_packet] wrote:
?
Kevin,

According to the...


...document, the indicators are more about tuning accuracy at 9600 (very different from the meanings at 1200).

By the looks of the audio level messages, it seems our two systems are, more or less, very well tuned to each other.

John

On Mon, May 1, 2017 at 3:06 AM, Kevin Utzy krutzy62@... [direwolf_packet] <direwolf_packet@yahoogroups.com> wrote:
?
[Attachment(s) from Kevin Utzy included below]

First I'd like to say I love this program and I hope the development continues!

I am try debug an issue with Dire Wolf at 9600 baud in connected mode.? My configuration:
Windows 7 Ultimate
Dire Wolf V1.4
Outpost 3.2
SignaLink USB
Kenwood TS-2000 (the SignaLink is plugged into the ACC2 data port)
Connecting with a SCS Tracker USB BBS node (AX.25 v2.0)

I have been very successful at 1200 baud with the test sessions and pleased.
I would like to get 9600 baud like running.? I have had some success but it is erratic.? I've looked at the documentation and I am having trouble finding more detailed information on the specifics of what the messages are saying, especially the audio level message.? See below.




If somebody can help decipher I would appreciate it.

73,
Kevin
KA4RNH




Virus-free.




Re: Dire Wolf Connected Mode 9600 baud

 

¿ªÔÆÌåÓý

John,

I posted this because I really would like to know what that data is telling me.? Right now all my levels are maxed out.? Possibly over modulation and clipping?? When the BBS gets moved what meaning information can I get from the message?

I did read that 9600 article last night and it was very informative.? Just trying to learn as much as I can.? :-)

Kevin
KA4RNH


On 5/1/2017 3:25 PM, John Huggins john.huggins.ee@... [direwolf_packet] wrote:

?
Kevin,

According to the...


...document, the indicators are more about tuning accuracy at 9600 (very different from the meanings at 1200).

By the looks of the audio level messages, it seems our two systems are, more or less, very well tuned to each other.

John

On Mon, May 1, 2017 at 3:06 AM, Kevin Utzy krutzy62@... [direwolf_packet] <direwolf_packet@...> wrote:
?
[Attachment(s) from Kevin Utzy included below]

First I'd like to say I love this program and I hope the development continues!

I am try debug an issue with Dire Wolf at 9600 baud in connected mode.? My configuration:
Windows 7 Ultimate
Dire Wolf V1.4
Outpost 3.2
SignaLink USB
Kenwood TS-2000 (the SignaLink is plugged into the ACC2 data port)
Connecting with a SCS Tracker USB BBS node (AX.25 v2.0)

I have been very successful at 1200 baud with the test sessions and pleased.
I would like to get 9600 baud like running.? I have had some success but it is erratic.? I've looked at the documentation and I am having trouble finding more detailed information on the specifics of what the messages are saying, especially the audio level message.? See below.




If somebody can help decipher I would appreciate it.

73,
Kevin
KA4RNH




Virus-free.



Re: Dire Wolf Connected Mode 9600 baud [1 Attachment]

 

Kevin,

According to the...


...document, the indicators are more about tuning accuracy at 9600 (very different from the meanings at 1200).

By the looks of the audio level messages, it seems our two systems are, more or less, very well tuned to each other.

John

On Mon, May 1, 2017 at 3:06 AM, Kevin Utzy krutzy62@... [direwolf_packet] <direwolf_packet@...> wrote:
?
[Attachment(s) from Kevin Utzy included below]

First I'd like to say I love this program and I hope the development continues!

I am try debug an issue with Dire Wolf at 9600 baud in connected mode.? My configuration:
Windows 7 Ultimate
Dire Wolf V1.4
Outpost 3.2
SignaLink USB
Kenwood TS-2000 (the SignaLink is plugged into the ACC2 data port)
Connecting with a SCS Tracker USB BBS node (AX.25 v2.0)

I have been very successful at 1200 baud with the test sessions and pleased.
I would like to get 9600 baud like running.? I have had some success but it is erratic.? I've looked at the documentation and I am having trouble finding more detailed information on the specifics of what the messages are saying, especially the audio level message.? See below.




If somebody can help decipher I would appreciate it.

73,
Kevin
KA4RNH




Virus-free.



dire wolf on mac osx

 

can someone help get dire wolf up and runnging on max osx 10.9.5 ?? I have it installed and running on ubuntu 16.04 LTS, but can't get it to go on mac osx.? thanks in advance!

david



Erratic GPS Signal blocking TBeacons with Telemetry

 

My students and I have been using Direwolf as a remote dashboard in our Super Mileage Vehicle race cars that the students have built. ??


We seem to have identified an issue, possibly not with Direwolf directly, but with how we are using it.?


It appears that the call for building the TBeacon are blocking if GPS signal is lost, setting up a situation where we loose packets for minutes....?


Is there a recommended approach to handle the following situation:?


If there is a GPS fix ?then send a Tbeacon with telemetry embedded via commentcmd,

else just send a telemetry beacon without position.


Thanks for you feedback.?


Tim KD9DBG?



???


Dire Wolf Connected Mode 9600 baud

 

¿ªÔÆÌåÓý

First I'd like to say I love this program and I hope the development continues!

I am try debug an issue with Dire Wolf at 9600 baud in connected mode.? My configuration:
Windows 7 Ultimate
Dire Wolf V1.4
Outpost 3.2
SignaLink USB
Kenwood TS-2000 (the SignaLink is plugged into the ACC2 data port)
Connecting with a SCS Tracker USB BBS node (AX.25 v2.0)

I have been very successful at 1200 baud with the test sessions and pleased.
I would like to get 9600 baud like running.? I have had some success but it is erratic.? I've looked at the documentation and I am having trouble finding more detailed information on the specifics of what the messages are saying, especially the audio level message.? See below.




If somebody can help decipher I would appreciate it.

73,
Kevin
KA4RNH




Virus-free.


Re: Getting PTT working

 

David,
After thoroughly reviewing the Bill of Materials, it did state the proper 555 timer (TLC555); a big oversight on my part. I'm assuming that the BOM has all of the correct components listed, I just needed to be a bit more careful. But to the uninitiated, this has been a good learning experience. ?Hope someone else can learn from my mistake. ?Thanks for your help and support.
Lee


---In direwolf_packet@..., <dranch@...> wrote :


Hello Lee,

?
Thanks for your suggestions on the direction to take to troubleshoot the problem.

Yeah.. troubleshooting over email is hard so I usually tend to start simple and work your way up.



First, if I could change my pay check like I inadvertently changed the resistor values that would be good! ?I mistakenly used a 100k ohm instead of a 100 ohm resistor in a couple of places (learn by mistakes). ?That fixed one issue. Secondly, the 555 timer I ordered was not a CMOS timer thus the minimum power requirement for the current timer is 4.5v where the RPi can only supply 3.3. ?I've ordered up the correct timer and have high hopes that this will completely fix the problems.

Oh.. those "substitutions" would do it!? Curious, where did you get the wrong part values from?? We should work on getting those materials clearer so others don't do the same thing.? I actually have one of those boards here too and I even sourced all the parts but I still need to build it.? :-)

--David
KI6ZHD


Re: Q-construct difference between two versions of Dire Wolf? TOPIC CHANGE.

 

Greg,
The more 30m HF Rx Only Igates the better!!
I have travelled the Simpson Desert (twice), NT, Cape York and Karumba and the 30m APRS coverage was fabulous. Most of the stations I "hit" were on the coast as far a field as Esperance WA and I even managed a packet into Japan.
During a trip into Bendethra (NSW), a ZL rxed a few of my packets.
I run a Rx Only Igate and although I'm only credited with a few posits (as per aprs.fi), I certainly receive a lot.
I'm using Direwolf on an Odroid (Raspberry Pi like thing) which has been running for years.
Good luck with your endeavours and remember, assistance is only an email away.

Ian
VK1IAN

On 30/04/17 13:42, 'Greg Winterflood' winterflood@... [direwolf_packet] wrote:
G¡¯day, I¡¯m new.



Some blokes in Sydney suggested I set up a Receive only iGate in Alice Springs, Central Australia, which is about 1,500 kilometres [932 miles] from anywhere.



When I go bush, I take a Satellite Phone. HF is so unreliable, as Franklin D Roosevelt and Winston Churchill discovered, prompting Arthur C Clarke, in 1945, to advocate geostationary radio relay stations 35,000 kilometres above the equator!



However, people still venture out this way with Tiny Trackers and other locating devices ¨C so I am happy to be part of a ¡®mantle of safety¡¯.



I am ever interested to learn something new, so took up the suggestion from the Sydney blokes, and currently have VK8KMD-10 running on an RPi3. The receiver is a Yaesu FT-817; but the Sydney blokes are organizing a dedicated Codan 7004 receiver for me, so that I can return the FT-817 to normal use. Not that I really need it because I¡¯ve got 2 FT-817s ?



My question is about the sentence below, written by Mike, NA5SS, which he highlighted ted in yellow:



qAO - (letter O) Packet is placed on APRS-IS by a receive-only iGate from RF. The callSSID following the qAO is the callSSID of the IGate. Note that receive-only IGates are discouraged on standard APRS frequencies. Please consider a bidirectional IGate that only gates to RF messages for stations heard directly.

I don¡¯t understand why my receive-only iGate should be discouraged. I¡¯m happy to run an antenna, a receiver, an RPi3 running Dire Wolf, and an ethernet cable to the outside world, so that any APRS equipped adventurer is able to be followed by friends or family.



My first guess at an answer to my question, is that receive-only iGates clog up the system in crowded locations.



As the Northern Territory has a population density of 0.2 people per square kilometre [0.08 per square mile] is there a problem with my receive-only iGate?



73



Greg



Greg Winterflood VK8KMD

5 Burke Street

EAST SIDE, ALICE SPRINGS

NT AUSTRALIA 0870

0428 884 205




Re: Digipeating Path

Tony Ross
 

On 04/29/2017 03:53 PM, Matthew Pitts daywalker_blade_2004@... [direwolf_packet] wrote:

I suspect the digipeater he's talking about would be run by a guy that doesn't want to change, or it would have been done by now. Some APRS digi owners simply do not want to acknowledge changes that they didn't agree with. It's equally possible the owner doesn't know about it, of course.
Far too many operators subscribe to the idea "don't fix it if it isn't broke", without understanding that every software is broken. Those authors that learn of problems that care are upgrading continually.


Re: Q-construct difference between two versions of Dire Wolf? TOPIC CHANGE.

 

Don't worry, receive only I-gates don't clog up anything. They're totally passive listening posts on the local RF network and their Internet traffic gets deduplicated vs anyone else who heard the same packet.?

Receive only I-gates do not break messaging. Receive-only I-gates of course don't have the ability to RF-gate ack packets back to the originating station, but neither does "no I-gate at all", so I don't think telling people to not set up I-gates because it breaks something is accurate. The very unclear wording on that statement in the q construct documentation causes arguments constantly. Transmitting RF-gates are better for the network* than Rx-only I-gates, which are better for the network than nothing.?

*- There is some arguments to be made that a network made entirely of RF-gates isn't ideal, but that's a subtle network design debate for something APRS essentially never suffers from.

The fact that Kenwood radios beep when they hear their Digi echo isn't relevant in a debate between an Rx-only I-gate and an RF-gate. Neither type of I-gate digipeats.?


If you're willing and able to set up an RF-gate instead of just an RX I-gate, that is a better thing to do. If you are only interested in setting up an RX I-gate, all the more power to you.?

Kenneth Finnegan

On Apr 29, 2017 22:32, "Max Harper kg4pid@... [direwolf_packet]" <direwolf_packet@...> wrote:
?

The main reason for discouraging receive-only igates is that it breaks messaging, which would be nice to have in such a isolated location. Also Radios like the Kenwood D700/D710 and D7/D72/D74 will make a?distinctive sound when they hear their own packets digied. Receive only igates don't cause any?other problems to my knowledge.

Max KG4PID

From: "'Greg Winterflood' winterflood@... [direwolf_packet]" <direwolf_packet@yahoogroups.com>
To: direwolf_packet@yahoogroups.com
Sent: Saturday, April 29, 2017 10:43 PM
Subject: [direwolf_packet] Re: Q-construct difference between two versions of Dire Wolf? TOPIC CHANGE.

?
G¡¯day, I¡¯m new.
?
Some blokes in Sydney suggested I set up a Receive only iGate in Alice Springs, Central Australia, which is about 1,500 kilometres [932 miles] from anywhere.
?
When I go bush, I take a Satellite ?Phone. HF is so unreliable, as Franklin D Roosevelt and Winston Churchill discovered, prompting Arthur C Clarke, in 1945, to advocate geostationary radio relay stations 35,000 kilometres above the equator!
?
However, people still venture out this way with Tiny Trackers and other locating devices ¨C so I am happy to be part of a ¡®mantle of safety¡¯. ?
?
I am ever interested to learn something new, so took up the suggestion from the Sydney blokes, and currently have VK8KMD-10 running on an RPi3. The receiver is a Yaesu FT-817; but the Sydney blokes are organizing a dedicated Codan 7004 receiver for me, so that I can return the FT-817 to normal use. Not that I really need it because I¡¯ve got 2 FT-817s ?
?
My question is about the sentence below, written by Mike, NA5SS, which he highlighted ted in yellow:
?
qAO - (letter O) Packet is placed on APRS-IS by a receive-only iGate from RF. The callSSID following the qAO is the callSSID of the IGate. Note that receive-only IGates are discouraged on standard APRS frequencies. Please consider a bidirectional IGate that only gates to RF messages for stations heard directly.

I don¡¯t understand why my receive-only iGate should be discouraged. I¡¯m happy to run an antenna, a receiver, an RPi3 running Dire Wolf, and an ethernet cable to the outside world, so that any APRS equipped adventurer is able to be followed by friends or family.
?
My first guess at an answer to my question, is that receive-only iGates clog up the system in crowded locations.
?
As the Northern Territory has a population density of 0.2 people per square kilometre [0.08 per square mile] is there a problem with my receive-only iGate?
?
73
?
Greg ?
?
Greg Winterflood VK8KMD
5 Burke Street
EAST SIDE, ALICE SPRINGS
NT AUSTRALIA 0870
0428 884 205
?




Re: Q-construct difference between two versions of Dire Wolf? TOPIC CHANGE.

 

The main reason for discouraging receive-only igates is that it breaks messaging, which would be nice to have in such a isolated location. Also Radios like the Kenwood D700/D710 and D7/D72/D74 will make a?distinctive sound when they hear their own packets digied. Receive only igates don't cause any?other problems to my knowledge.

Max KG4PID


From: "'Greg Winterflood' winterflood@... [direwolf_packet]"
To: direwolf_packet@...
Sent: Saturday, April 29, 2017 10:43 PM
Subject: [direwolf_packet] Re: Q-construct difference between two versions of Dire Wolf? TOPIC CHANGE.

?
G¡¯day, I¡¯m new.
?
Some blokes in Sydney suggested I set up a Receive only iGate in Alice Springs, Central Australia, which is about 1,500 kilometres [932 miles] from anywhere.
?
When I go bush, I take a Satellite ?Phone. HF is so unreliable, as Franklin D Roosevelt and Winston Churchill discovered, prompting Arthur C Clarke, in 1945, to advocate geostationary radio relay stations 35,000 kilometres above the equator!
?
However, people still venture out this way with Tiny Trackers and other locating devices ¨C so I am happy to be part of a ¡®mantle of safety¡¯. ?
?
I am ever interested to learn something new, so took up the suggestion from the Sydney blokes, and currently have VK8KMD-10 running on an RPi3. The receiver is a Yaesu FT-817; but the Sydney blokes are organizing a dedicated Codan 7004 receiver for me, so that I can return the FT-817 to normal use. Not that I really need it because I¡¯ve got 2 FT-817s ?
?
My question is about the sentence below, written by Mike, NA5SS, which he highlighted ted in yellow:
?
qAO - (letter O) Packet is placed on APRS-IS by a receive-only iGate from RF. The callSSID following the qAO is the callSSID of the IGate. Note that receive-only IGates are discouraged on standard APRS frequencies. Please consider a bidirectional IGate that only gates to RF messages for stations heard directly.

I don¡¯t understand why my receive-only iGate should be discouraged. I¡¯m happy to run an antenna, a receiver, an RPi3 running Dire Wolf, and an ethernet cable to the outside world, so that any APRS equipped adventurer is able to be followed by friends or family.
?
My first guess at an answer to my question, is that receive-only iGates clog up the system in crowded locations.
?
As the Northern Territory has a population density of 0.2 people per square kilometre [0.08 per square mile] is there a problem with my receive-only iGate?
?
73
?
Greg ?
?
Greg Winterflood VK8KMD
5 Burke Street
EAST SIDE, ALICE SPRINGS
NT AUSTRALIA 0870
0428 884 205
?



Re: Audio "Feedback"

 

Still have problems with the bleeding, no matter how I go about it, even as suggested. Works on some radios but not all. My Icom IC-T90A is horrific with the bleeding.


Re: Q-construct difference between two versions of Dire Wolf? TOPIC CHANGE.

Greg Winterflood
 

¿ªÔÆÌåÓý

G¡¯day, I¡¯m new.

?

Some blokes in Sydney suggested I set up a Receive only iGate in Alice Springs, Central Australia, which is about 1,500 kilometres [932 miles] from anywhere.

?

When I go bush, I take a Satellite ?Phone. HF is so unreliable, as Franklin D Roosevelt and Winston Churchill discovered, prompting Arthur C Clarke, in 1945, to advocate geostationary radio relay stations 35,000 kilometres above the equator!

?

However, people still venture out this way with Tiny Trackers and other locating devices ¨C so I am happy to be part of a ¡®mantle of safety¡¯. ?

?

I am ever interested to learn something new, so took up the suggestion from the Sydney blokes, and currently have VK8KMD-10 running on an RPi3. The receiver is a Yaesu FT-817; but the Sydney blokes are organizing a dedicated Codan 7004 receiver for me, so that I can return the FT-817 to normal use. Not that I really need it because I¡¯ve got 2 FT-817s ?

?

My question is about the sentence below, written by Mike, NA5SS, which he highlighted ted in yellow:

?

qAO - (letter O) Packet is placed on APRS-IS by a receive-only iGate from RF. The callSSID following the qAO is the callSSID of the IGate. Note that receive-only IGates are discouraged on standard APRS frequencies. Please consider a bidirectional IGate that only gates to RF messages for stations heard directly.

I don¡¯t understand why my receive-only iGate should be discouraged. I¡¯m happy to run an antenna, a receiver, an RPi3 running Dire Wolf, and an ethernet cable to the outside world, so that any APRS equipped adventurer is able to be followed by friends or family.

?

My first guess at an answer to my question, is that receive-only iGates clog up the system in crowded locations.

?

As the Northern Territory has a population density of 0.2 people per square kilometre [0.08 per square mile] is there a problem with my receive-only iGate?

?

73

?

Greg ?

?

Greg Winterflood VK8KMD

5 Burke Street

EAST SIDE, ALICE SPRINGS

NT AUSTRALIA 0870

0428 884 205

?


Re: Digipeating Path

 

¿ªÔÆÌåÓý

I suspect the digipeater he's talking about would be run by a guy that doesn't want to change, or it would have been done by now. Some APRS digi owners simply do not want to acknowledge changes that they didn't agree with. It's equally possible the owner doesn't know about it, of course.


Matthew Pitts

N8OHU


On 4/29/2017 6:33 PM, Max Harper kg4pid@... [direwolf_packet] wrote:

?
I'm not so sure that I would just ignore it. If I knew the digipeater and could find the owner?I would be complaining. It's about time we started cleaning up the APRS infrastructure.

Max KG4PID


From: "mike_ph4@... [direwolf_packet]"
To: direwolf_packet@...
Sent: Saturday, April 29, 2017 4:51 PM
Subject: [direwolf_packet] Re: Digipeating Path

?
So it is an issue with the digipeater then. Good to know. I didn't have a lot to compare to with the path standards. The digipeater has been running for 18 years, so that has a lot to do with.. So I'll just have to ignore the way it's failing to mark the used hop.




Re: Digipeating Path

 

I'm not so sure that I would just ignore it. If I knew the digipeater and could find the owner?I would be complaining. It's about time we started cleaning up the APRS infrastructure.

Max KG4PID


From: "mike_ph4@... [direwolf_packet]"
To: direwolf_packet@...
Sent: Saturday, April 29, 2017 4:51 PM
Subject: [direwolf_packet] Re: Digipeating Path

?
So it is an issue with the digipeater then. Good to know. I didn't have a lot to compare to with the path standards. The digipeater has been running for 18 years, so that has a lot to do with.. So I'll just have to ignore the way it's failing to mark the used hop.



Re: Digipeating Path

 

So it is an issue with the digipeater then. Good to know. I didn't have a lot to compare to with the path standards. The digipeater has been running for 18 years, so that has a lot to do with.. So I'll just have to ignore the way it's failing to mark the used hop.


Re: Digipeating Path

 

On Sat, Apr 29, 2017 at 8:38 AM, wb2osz@... [direwolf_packet]?<direwolf_packet@...>?wrote:

Seeing "WIDE1" without the "*" is rather odd.
"WIDE1" is a known defect with some early digipeater firmware that it wouldn't correctly set the H flag on consumed n-N aliases, so additional logic needs to be added to every other digipeater package to correctly handle these dangling aliases.
--
Kenneth Finnegan

On Sat, Apr 29, 2017 at 8:38 AM, wb2osz@... [direwolf_packet] <direwolf_packet@...> wrote:
?

Under the usual rules, this would not get digipeated.
NA7Q>APX202:MEGLER*,WIDE1,WIDE2-1
The Digipeater looks for the first address in the via path which has not been used.   This would be the one after "*".
The digipeater decides whether "WIDE1" would be eligible.  It is not because the remaining hop count (SSID) is 0.
Seeing "WIDE1" without the "*" is rather odd.  You would not expect to see this.  When the remaining hop count is 0 you would expect the address to be marked as being used.  There are two possibilities here.
(1) The originating station used something like "WIDE1-1,WIDE1,WIDE2-1" which is not a sensible thing to do.  or
(2) The first digipeater is not behaving properly.  Suppose the originating station used "WIDE1-1,WIDE2-1" which is fairly common.   The first digipeater should change it to "MEGLER*,WIDE2-1".   There are a couple implementations that change it to the form "MEGLER,WIDE1*,WIDE2-1" which is confusing.  This looks like it went thru 2 digipeaters and the second one did not identify itself. 
Both "MEGLER*,WIDE2-1" and "MEGLER,WIDE1*,WIDE2-1" would be eligible for digipeating.   
There is some discussion about this in the User Guide.



Re: Digipeating Path

 

Under the usual rules, this would not get digipeated.
NA7Q>APX202:MEGLER*,WIDE1,WIDE2-1
The Digipeater looks for the first address in the via path which has not been used.   This would be the one after "*".
The digipeater decides whether "WIDE1" would be eligible.  It is not because the remaining hop count (SSID) is 0.
Seeing "WIDE1" without the "*" is rather odd.  You would not expect to see this.  When the remaining hop count is 0 you would expect the address to be marked as being used.  There are two possibilities here.
(1) The originating station used something like "WIDE1-1,WIDE1,WIDE2-1" which is not a sensible thing to do.  or
(2) The first digipeater is not behaving properly.  Suppose the originating station used "WIDE1-1,WIDE2-1" which is fairly common.   The first digipeater should change it to "MEGLER*,WIDE2-1".   There are a couple implementations that change it to the form "MEGLER,WIDE1*,WIDE2-1" which is confusing.  This looks like it went thru 2 digipeaters and the second one did not identify itself. 
Both "MEGLER*,WIDE2-1" and "MEGLER,WIDE1*,WIDE2-1" would be eligible for digipeating.   
There is some discussion about this in the User Guide.


Re: Getting PTT working

David Ranch
 

¿ªÔÆÌåÓý


Hello Lee,

?
Thanks for your suggestions on the direction to take to troubleshoot the problem.

Yeah.. troubleshooting over email is hard so I usually tend to start simple and work your way up.



First, if I could change my pay check like I inadvertently changed the resistor values that would be good! ?I mistakenly used a 100k ohm instead of a 100 ohm resistor in a couple of places (learn by mistakes). ?That fixed one issue. Secondly, the 555 timer I ordered was not a CMOS timer thus the minimum power requirement for the current timer is 4.5v where the RPi can only supply 3.3. ?I've ordered up the correct timer and have high hopes that this will completely fix the problems.

Oh.. those "substitutions" would do it!? Curious, where did you get the wrong part values from?? We should work on getting those materials clearer so others don't do the same thing.? I actually have one of those boards here too and I even sourced all the parts but I still need to build it.? :-)

--David
KI6ZHD


Re: Getting PTT working

 

David,

Thanks for your suggestions on the direction to take to troubleshoot the problem.

First, if I could change my pay check like I inadvertently changed the resistor values that would be good! ?I mistakenly used a 100k ohm instead of a 100 ohm resistor in a couple of places (learn by mistakes). ?That fixed one issue.

Secondly, the 555 timer I ordered was not a CMOS timer thus the minimum power requirement for the current timer is 4.5v where the RPi can only supply 3.3. ?I've ordered up the correct timer and have high hopes that this will completely fix the problems.

Sometimes it takes a question or two to get going down the right path and that is what you've provided - thanks.?

Lee