I am trying to use All Star Link without modifying a cm 108 chip. I am trying to use the GPIO pins on the Odroid U3 expansion I/O board to control the repeater logic signals (COR/PTT) but all I could find was information on using either the GPIO pins on the cm108 fob (which must be modified to use) or using a parallel port. The Odroid U3 doesn’t have a parallel port and I think the native GPIO pins should have the capacity to use the COR/PTT signals.
I can’t find any information on how to go about using the native GPIO pins on an sbc for All Star Link. Is there a way to do this?
My thoughts on an approach to this:
create a driver or port that uses the GPIO pins as a parallel port
provide a memory address to the rpt.conf file that has a value corresponding to the GPIO status so that it may be read as a parallel port
alter the software to use native GPIO as another option as opposed to parallel port
I am not sure how to approach any of these options. I think option 3 would be best but I don’t know how this is possible. May i get some suggestions or help regarding this? Thanks!
Date: Mon, 27 Apr 2015 14:21:41 -0700
From: lcejaqui@ucsc.edu
To: app_rpt-users@ohnosec.org
Subject: [App_rpt-users] All Star Link GPIO Odroid U3
I am trying to use All Star Link without modifying a cm 108 chip. I am trying to use the GPIO pins on the Odroid U3 expansion I/O board to control the repeater logic signals (COR/PTT) but all I could find was information on using either the GPIO pins on the cm108 fob (which must be modified to use) or using a parallel port. The Odroid U3 doesn’t have a parallel port and I think the native GPIO pins should have the capacity to use the COR/PTT signals.
I can’t find any information on how to go about using the native GPIO pins on an sbc for All Star Link. Is there a way to do this?
My thoughts on an approach to this:
create a driver or port that uses the GPIO pins as a parallel port
provide a memory address to the rpt.conf file that has a value corresponding to the GPIO status so that it may be read as a parallel port
alter the software to use native GPIO as another option as opposed to parallel port
I am not sure how to approach any of these options. I think option 3 would be best but I don’t know how this is possible. May i get some suggestions or help regarding this? Thanks!
First I will say I don't know first hand any of the product you are using
and someone who does may have a better answer for you.
Once you can construct a command line to turn the gpio pin on and off, or
read the pin,
you can use "on event" command in rpt.conf in conjunction with that gpio
command string to equate it to cor and ptt activation.
Sorry I can't be more specific, but it is a direction to look at and I
think it would work. There are probably other methods to do the same.
...mike/kb8jnm
···
I am trying to use All Star Link without modifying a cm 108 chip. I am
trying to use the GPIO pins on the Odroid U3 expansion I/O board to
control
the repeater logic signals (COR/PTT) but all I could find was information
on using either the GPIO pins on the cm108 fob (which must be modified to
use) or using a parallel port. The Odroid U3 doesn't have a parallel port
and I think the native GPIO pins should have the capacity to use the
COR/PTT signals.
I can't find any information on how to go about using the native GPIO pins
on an sbc for All Star Link. Is there a way to do this?
My thoughts on an approach to this:
1. create a driver or port that uses the GPIO pins as a parallel port
2. provide a memory address to the rpt.conf file that has a value
corresponding to the GPIO status so that it may be read as a parallel port
3. alter the software to use native GPIO as another option as opposed to
parallel port
I am not sure how to approach any of these options. I think option 3 would
be best but I don't know how this is possible. May i get some suggestions
or help regarding this? Thanks!
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
to the bottom of the page. Enter your email address and press the
"Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message to
the list detailing the problem.
Date: Mon, 27 Apr 2015 14:21:41 -0700
From: lcejaqui@ucsc.edu
To: app_rpt-users@ohnosec.org
Subject: [App_rpt-users] All Star Link GPIO Odroid U3
I am trying to use All Star Link without modifying a cm 108 chip. I am trying to use the GPIO pins on the Odroid U3 expansion I/O board to control the repeater logic signals (COR/PTT) but all I could find was information on using either the GPIO pins on the cm108 fob (which must be modified to use) or using a parallel port. The Odroid U3 doesn’t have a parallel port and I think the native GPIO pins should have the capacity to use the COR/PTT signals.
I can’t find any information on how to go about using the native GPIO pins on an sbc for All Star Link. Is there a way to do this?
My thoughts on an approach to this:
create a driver or port that uses the GPIO pins as a parallel port
provide a memory address to the rpt.conf file that has a value corresponding to the GPIO status so that it may be read as a parallel port
alter the software to use native GPIO as another option as opposed to parallel port
I am not sure how to approach any of these options. I think option 3 would be best but I don’t know how this is possible. May i get some suggestions or help regarding this? Thanks!
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
As Doug mentioned, we've got an innovative solution for Telemetry
management in development now. The goal is to address GPIO across multiple
platforms with a consistent API and easily extend-able method. So, while
we don't have immediate plans for U3 support, users wishing to add new
capabilities (like U3 GPIO) will be delighted!
As the old saying goes....more details soon.
73, David KB4FXC
···
On Mon, 27 Apr 2015, Doug Crompton wrote:
Luis,
This is already done and in testing on the RPi2 and will be in the next update in about a month at hamvoip.org.
73 Doug
WA3DSP WA3DSP Amateur Radio Resources
Date: Mon, 27 Apr 2015 14:21:41 -0700
From: lcejaqui@ucsc.edu
To: app_rpt-users@ohnosec.org
Subject: [App_rpt-users] All Star Link GPIO Odroid U3
I am trying to use All Star Link without modifying a cm 108 chip. I am trying to use the GPIO pins on the Odroid U3 expansion I/O board to control the repeater logic signals (COR/PTT) but all I could find was information on using either the GPIO pins on the cm108 fob (which must be modified to use) or using a parallel port. The Odroid U3 doesn't have a parallel port and I think the native GPIO pins should have the capacity to use the COR/PTT signals.
I can't find any information on how to go about using the native GPIO pins on an sbc for All Star Link. Is there a way to do this?
My thoughts on an approach to this:1. create a driver or port that uses the GPIO pins as a parallel port2. provide a memory address to the rpt.conf file that has a value corresponding to the GPIO status so that it may be read as a parallel port3. alter the software to use native GPIO as another option as opposed to parallel port
I am not sure how to approach any of these options. I think option 3 would be best but I don't know how this is possible. May i get some suggestions or help regarding this? Thanks!
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
First I will say I don't know first hand any of the product you are using
and someone who does may have a better answer for you.
Once you can construct a command line to turn the gpio pin on and off, or
read the pin,
you can use "on event" command in rpt.conf in conjunction with that gpio
command string to equate it to cor and ptt activation.
Sorry I can't be more specific, but it is a direction to look at and I
think it would work. There are probably other methods to do the same.
...mike/kb8jnm
I am trying to use All Star Link without modifying a cm 108 chip. I am
trying to use the GPIO pins on the Odroid U3 expansion I/O board to
control
the repeater logic signals (COR/PTT) but all I could find was information
on using either the GPIO pins on the cm108 fob (which must be modified to
use) or using a parallel port. The Odroid U3 doesn't have a parallel port
and I think the native GPIO pins should have the capacity to use the
COR/PTT signals.
I can't find any information on how to go about using the native GPIO pins
on an sbc for All Star Link. Is there a way to do this?
My thoughts on an approach to this:
1. create a driver or port that uses the GPIO pins as a parallel port
2. provide a memory address to the rpt.conf file that has a value
corresponding to the GPIO status so that it may be read as a parallel port
3. alter the software to use native GPIO as another option as opposed to
parallel port
I am not sure how to approach any of these options. I think option 3 would
be best but I don't know how this is possible. May i get some suggestions
or help regarding this? Thanks!
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
to the bottom of the page. Enter your email address and press the
"Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message to
the list detailing the problem.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.