Date   

Dmr Utils

Steve Siesel [K4KSA]
 

Steve….

 

I did a apt-get install pip  and then not knowing about DMR utils did  a

 

pip install bitstring

pip install bitarray

pip install Twisted

 

I did get the following errors as noted in the red below.

 

Then I did get (git) DMR Utils… and did a

 

Pip install –upgrade .

and got this output:

 

Unpacking /srv/dmr_utils

  Running setup.py (path:/tmp/pip-MHENhJ-build/setup.py) egg_info for package from file:///srv/dmr_utils

 

Downloading/unpacking bitarray (from dmr-utils==0.1.7)

  Downloading bitarray-0.8.1.tar.gz (46kB): 46kB downloaded

  Running setup.py (path:/tmp/pip-build-dVC387/bitarray/setup.py) egg_info for package bitarray

 

Installing collected packages: bitarray, dmr-utils

  Running setup.py install for bitarray

    building 'bitarray._bitarray' extension

    arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c bitarray/_bitarray.c -o build/temp.linux-armv7l-2.7/bitarray/_bitarray.o

    bitarray/_bitarray.c:9:20: fatal error: Python.h: No such file or directory

     #include "Python.h"

                        ^

    compilation terminated.

    error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1

    Complete output from command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-dVC387/bitarray/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-HqQRt9-record/install-record.txt --single-version-externally-managed --compile:

    running install

 

running build

 

running build_py

 

creating build

 

creating build/lib.linux-armv7l-2.7

 

creating build/lib.linux-armv7l-2.7/bitarray

 

copying bitarray/__init__.py -> build/lib.linux-armv7l-2.7/bitarray

 

copying bitarray/test_bitarray.py -> build/lib.linux-armv7l-2.7/bitarray

 

running build_ext

 

building 'bitarray._bitarray' extension

 

creating build/temp.linux-armv7l-2.7

 

creating build/temp.linux-armv7l-2.7/bitarray

 

arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c bitarray/_bitarray.c -o build/temp.linux-armv7l-2.7/bitarray/_bitarray.o

 

bitarray/_bitarray.c:9:20: fatal error: Python.h: No such file or directory

 

#include "Python.h"

 

                    ^

 

compilation terminated.

 

error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1

 

----------------------------------------

Cleaning up...

Command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-dVC387/bitarray/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-HqQRt9-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /tmp/pip-build-dVC387/bitarray

Storing debug log for failure in /root/.pip/pip.log

root@DMRLink:/srv/dmr_utils#


Re: Dmr Utils

Steve N4IRS
 

       apt-get install python-dev -y
    apt-get install python-pip -y
        apt-get install python-twisted -y
    pip install bitstring
    pip install bitarray

        cd /opt
        git clone https://github.com/n0mjs710/dmr_utils.git
        cd dmr_utils/
    pip install --upgrade .

On 06/24/2017 06:51 PM, Steve Siesel [K4KSA] wrote:

Steve….

 

I did a apt-get install pip  and then not knowing about DMR utils did  a

 

pip install bitstring

pip install bitarray

pip install Twisted

 

I did get the following errors as noted in the red below.

 

Then I did get (git) DMR Utils… and did a

 

Pip install –upgrade .

and got this output:

 

Unpacking /srv/dmr_utils

  Running setup.py (path:/tmp/pip-MHENhJ-build/setup.py) egg_info for package from file:///srv/dmr_utils

 

Downloading/unpacking bitarray (from dmr-utils==0.1.7)

  Downloading bitarray-0.8.1.tar.gz (46kB): 46kB downloaded

  Running setup.py (path:/tmp/pip-build-dVC387/bitarray/setup.py) egg_info for package bitarray

 

Installing collected packages: bitarray, dmr-utils

  Running setup.py install for bitarray

    building 'bitarray._bitarray' extension

    arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c bitarray/_bitarray.c -o build/temp.linux-armv7l-2.7/bitarray/_bitarray.o

    bitarray/_bitarray.c:9:20: fatal error: Python.h: No such file or directory

     #include "Python.h"

                        ^

    compilation terminated.

    error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1

    Complete output from command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-dVC387/bitarray/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-HqQRt9-record/install-record.txt --single-version-externally-managed --compile:

    running install

 

running build

 

running build_py

 

creating build

 

creating build/lib.linux-armv7l-2.7

 

creating build/lib.linux-armv7l-2.7/bitarray

 

copying bitarray/__init__.py -> build/lib.linux-armv7l-2.7/bitarray

 

copying bitarray/test_bitarray.py -> build/lib.linux-armv7l-2.7/bitarray

 

running build_ext

 

building 'bitarray._bitarray' extension

 

creating build/temp.linux-armv7l-2.7

 

creating build/temp.linux-armv7l-2.7/bitarray

 

arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c bitarray/_bitarray.c -o build/temp.linux-armv7l-2.7/bitarray/_bitarray.o

 

bitarray/_bitarray.c:9:20: fatal error: Python.h: No such file or directory

 

#include "Python.h"

 

                    ^

 

compilation terminated.

 

error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1

 

----------------------------------------

Cleaning up...

Command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-dVC387/bitarray/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-HqQRt9-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /tmp/pip-build-dVC387/bitarray

Storing debug log for failure in /root/.pip/pip.log

root@DMRLink:/srv/dmr_utils#



Re: Dmr Utils

Cort N0MJS <n0mjs@...>
 

Try installing python-dev. That's where python.h lives

Sent from my iPhone

On Jun 24, 2017, at 5:56 PM, Steve N4IRS <szingman@...> wrote:

       apt-get install python-dev -y
    apt-get install python-pip -y
        apt-get install python-twisted -y
    pip install bitstring
    pip install bitarray

        cd /opt
        git clone https://github.com/n0mjs710/dmr_utils.git
        cd dmr_utils/
    pip install --upgrade .

On 06/24/2017 06:51 PM, Steve Siesel [K4KSA] wrote:

Steve….

 

I did a apt-get install pip  and then not knowing about DMR utils did  a

 

pip install bitstring

pip install bitarray

pip install Twisted

 

I did get the following errors as noted in the red below.

 

Then I did get (git) DMR Utils… and did a

 

Pip install –upgrade .

and got this output:

 

Unpacking /srv/dmr_utils

  Running setup.py (path:/tmp/pip-MHENhJ-build/setup.py) egg_info for package from file:///srv/dmr_utils

 

Downloading/unpacking bitarray (from dmr-utils==0.1.7)

  Downloading bitarray-0.8.1.tar.gz (46kB): 46kB downloaded

  Running setup.py (path:/tmp/pip-build-dVC387/bitarray/setup.py) egg_info for package bitarray

 

Installing collected packages: bitarray, dmr-utils

  Running setup.py install for bitarray

    building 'bitarray._bitarray' extension

    arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c bitarray/_bitarray.c -o build/temp.linux-armv7l-2.7/bitarray/_bitarray.o

    bitarray/_bitarray.c:9:20: fatal error: Python.h: No such file or directory

     #include "Python.h"

                        ^

    compilation terminated.

    error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1

    Complete output from command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-dVC387/bitarray/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-HqQRt9-record/install-record.txt --single-version-externally-managed --compile:

    running install

 

running build

 

running build_py

 

creating build

 

creating build/lib.linux-armv7l-2.7

 

creating build/lib.linux-armv7l-2.7/bitarray

 

copying bitarray/__init__.py -> build/lib.linux-armv7l-2.7/bitarray

 

copying bitarray/test_bitarray.py -> build/lib.linux-armv7l-2.7/bitarray

 

running build_ext

 

building 'bitarray._bitarray' extension

 

creating build/temp.linux-armv7l-2.7

 

creating build/temp.linux-armv7l-2.7/bitarray

 

arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c bitarray/_bitarray.c -o build/temp.linux-armv7l-2.7/bitarray/_bitarray.o

 

bitarray/_bitarray.c:9:20: fatal error: Python.h: No such file or directory

 

#include "Python.h"

 

                    ^

 

compilation terminated.

 

error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1

 

----------------------------------------

Cleaning up...

Command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-dVC387/bitarray/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-HqQRt9-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /tmp/pip-build-dVC387/bitarray

Storing debug log for failure in /root/.pip/pip.log

root@DMRLink:/srv/dmr_utils#



Re: Dmr Utils

Steve Siesel [K4KSA]
 

Thanks to both, got them all in!

 

 

From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Cort N0MJS
Sent: Saturday, June 24, 2017 7:06 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Dmr Utils

 

Try installing python-dev. That's where python.h lives

Sent from my iPhone


On Jun 24, 2017, at 5:56 PM, Steve N4IRS <szingman@...> wrote:

       apt-get install python-dev -y
    apt-get install python-pip -y
        apt-get install python-twisted -y
    pip install bitstring
    pip install bitarray

        cd /opt
        git clone https://github.com/n0mjs710/dmr_utils.git
        cd dmr_utils/
    pip install --upgrade .

On 06/24/2017 06:51 PM, Steve Siesel [K4KSA] wrote:

Steve….

 

I did a apt-get install pip  and then not knowing about DMR utils did  a

 

pip install bitstring

pip install bitarray

pip install Twisted

 

I did get the following errors as noted in the red below.

 

Then I did get (git) DMR Utils… and did a

 

Pip install –upgrade .

and got this output:

 

Unpacking /srv/dmr_utils

  Running setup.py (path:/tmp/pip-MHENhJ-build/setup.py) egg_info for package from file:///srv/dmr_utils

 

Downloading/unpacking bitarray (from dmr-utils==0.1.7)

  Downloading bitarray-0.8.1.tar.gz (46kB): 46kB downloaded

  Running setup.py (path:/tmp/pip-build-dVC387/bitarray/setup.py) egg_info for package bitarray

 

Installing collected packages: bitarray, dmr-utils

  Running setup.py install for bitarray

    building 'bitarray._bitarray' extension

    arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c bitarray/_bitarray.c -o build/temp.linux-armv7l-2.7/bitarray/_bitarray.o

    bitarray/_bitarray.c:9:20: fatal error: Python.h: No such file or directory

     #include "Python.h"

                        ^

    compilation terminated.

    error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1

    Complete output from command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-dVC387/bitarray/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-HqQRt9-record/install-record.txt --single-version-externally-managed --compile:

    running install

 

running build

 

running build_py

 

creating build

 

creating build/lib.linux-armv7l-2.7

 

creating build/lib.linux-armv7l-2.7/bitarray

 

copying bitarray/__init__.py -> build/lib.linux-armv7l-2.7/bitarray

 

copying bitarray/test_bitarray.py -> build/lib.linux-armv7l-2.7/bitarray

 

running build_ext

 

building 'bitarray._bitarray' extension

 

creating build/temp.linux-armv7l-2.7

 

creating build/temp.linux-armv7l-2.7/bitarray

 

arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c bitarray/_bitarray.c -o build/temp.linux-armv7l-2.7/bitarray/_bitarray.o

 

bitarray/_bitarray.c:9:20: fatal error: Python.h: No such file or directory

 

#include "Python.h"

 

                    ^

 

compilation terminated.

 

error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1

 

----------------------------------------

Cleaning up...

Command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-dVC387/bitarray/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-HqQRt9-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /tmp/pip-build-dVC387/bitarray

Storing debug log for failure in /root/.pip/pip.log

root@DMRLink:/srv/dmr_utils#

 


Re: AMBEtest4.py

Steve N4IRS
 

On 06/24/2017 04:39 PM, Steve Siesel [K4KSA] wrote:

The power supply on the RPi3 is 5V 3A…..

Should I grab (git) the HB product next? Is that in the N4IRS Repository?

 

 

From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Saturday, June 24, 2017 4:35 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] AMBEtest4.py

 

Well,
At least it did not fail. As I said in the post, if it fails you have no chance. If it passes, you have a shot. It's worth a try.
So far I can cause a failure if I use a lower current power supply. With a 5V 1.35A PS powering a RPi2 I can get AMBEtest4 to fail. It's repeatable. I am going to bring up DIAL RC1 Analog_Bridge and HB_Bridge. The plan it to continue to expand the testing to try to find what is causing the failures. We want to get to a point where if the confidence test passes, Analog_Audio will work, every time. 

On 06/24/2017 04:25 PM, Steve Siesel [K4KSA] wrote:

Steve,

 

Here is my results of a DV3000u in a RPi 3!

 

Thoughts?

Steve

K4KSA

 

 

root@DMRLink:/home/test/DV3000/Analog_Bridge# python AMBEtest4.py -n -s /dev/ttyUSB0

Setting serial port

Serial port parameters:

Port name:      /dev/ttyUSB0

Baudrate:       460800

Byte size:      8

Parity:         N

Stop bits:      1

Xon Xoff:       False

RTS/CTS:        False

DST/DTR:        False

*********************

Testing Reset DV3000

Test result: Success (6100010039)

Testing Get Product ID

Test result: Success (61000b0030414d4245333030305200)

Testing Get Version

Test result: Success (6100310031563132302e453130302e585858582e433130362e473531342e523030392e42303031303431312e433030323032303800)

Testing Set DSTAR Mode

Test result: Success (610002000a00)

Testing Reset DV3000

Test result: Success (6100010039)

Testing Set DMR Mode

Test result: Success (610002000a00)

Testing Decode AMBE

Test result: Success (6101420200a0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000ffff0001ffff000100000000000000000000ffff00000000000000000000000100000001000000000000ffff000000000000000000000001000000000000ffffffff000000000000000000000000000000000000000000000001000000000000ffff000000000001000000000000ffff00010001000000010000ffff00000000000000000000000000010000ffff0000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000ffff00010000ffff000000010000)

Testing Encode PCM

Test result: Success (61000b010148954be6500310b00777)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0001000000000001000000010000000000010000ffff0000ffff000000000000000000000000ffff00000000000000000000ffff00000000ffff0000000000000001000000010000ffff0001000000000000000000000000000000000000000100000000000000000000000000000000ffff0001ffff00000001000000010000000100000001ffffffff0000ffff0000ffff0001ffff00010000ffff0001ffff0001000000000000ffff0001ffff00000001ffff000000000000000000000000000000000000ffff0000ffff000100000000000100000001ffff0000000000000000ffff000000010000000000000000000100000000000000000000ffff000100000001000000000000ffff0000ffff00000000ffff0001ffff0000000000000001ffff0000000000000001ffff00000000ffff00000000000000000000)

Testing Encode PCM

Test result: Success (61000b010148a61ae1f1abaca4432b)

Testing Decode AMBE

Test result: Success (6101420200a00001ffff00000001ffff000000000000000000000001ffff00000000000000000000ffff0000000000000000ffff0001000000000000ffff000000000001ffff0000000000000001ffff0001ffff000000000000000000000001ffff000000000000000000000001ffff0000000000000000000100000000000000010001ffff00010000000000010001000000000000000000000001ffffffff0001ffff0000ffff0000000100000001ffff0001ffff00000000ffff0001ffff0001ffff0001000000000001ffff000100000000000000000001ffffffff0000000000010000000100010000000100000000000000010000ffffffffffff0001ffff0001ffff00000001ffff0001ffff0001ffff00000000ffff000100000001000000000001000000010000000100000000ffff0000ffffffff0000ffff00000000ffff0000)

Testing Encode PCM

Test result: Success (61000b010148fb836133dbbc308bb3)

Testing Decode AMBE

Test result: Success (6101420200a000010000ffff0000ffff000000010001000100000001ffff00000001ffff00010000ffff00000000ffffffff0001ffff00010000ffff0001ffff0001000100000001ffff000000000000000100000001ffff0001ffff00000000ffff0001ffff0001000000000000ffff0001ffff0000ffff00010000ffff0001ffff0001000000000000000000000000000100000000000000000000000100010000000000000000000000000000000000000001000000000000ffff0000ffff0001000000000001ffff000000000000000000000000000000000000ffff00000000ffff000000010000ffff000000010000000000000000ffffffffffff000000000000ffff0000000000000001ffff0001000000000001ffff00000000000000000000000000000001000000010000ffff0000000000000000000000000000000100000000)

Testing Encode PCM

Test result: Success (61000b010148dba06231d9b850abb3)

Testing Decode AMBE

Test result: Success (6101420200a00000ffff000000000000000000000000ffff0001000000000000000000010000000000000000ffff00000000ffffffff0000000000000001ffff000000000001000100000001ffff0000000000000000ffff000000000000ffffffff00000000ffff000000000000000000000000000000000001000100000000000000000000000000000001000000010000ffff0000ffff000000000000000100000000ffff0000000000000000ffff00010000ffff000000000000ffff0000000000000000000000010000000000010000000000000000000000000000000000000000000000000000000000010000ffff0000000000000001ffff000000000001000000000000ffff00000000ffff00000000000100010001ffff00000001ffff000000000000ffff00000001ffff000000000001000000000001ffff00000001ffff0000)

Testing Encode PCM

Test result: Success (61000b010148a8c327379de4f08f3b)

Testing Decode AMBE

Test result: Success (6101420200a00000000000000000ffff000100000001000000000000000000000000000000000000ffff00000000000000000000000100000001000000000000ffff0000ffff0000ffff00000000ffff0000000100010000000000000000000100000000ffff0000000000000001ffff000000000000000000000000ffff000000000000000000000001000000000000ffff00000000ffff000000000000000000000000000000010001000000010000000100000000000000000000ffff0000ffff0000000000000001ffff000100000001000100000000ffff00000000000000000000ffff00000000ffff000000010000000100000000ffffffff0000000000000001ffff0000ffff00000001000000010000000000000000000000000001000000010000ffff000000000000ffff000000000001000000000001ffff0000000100000000)

Testing Encode PCM

Test result: Success (61000b010148bbc20517bfd0b0cb2f)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0000000000000000ffff0001000000010000ffffffffffff000000010000ffffffff0000ffff0000000000000001000000000000000000000001000000010000000000000000000000000000ffff00000000000000000000000100000000000100000000ffff000000010000ffff00010000ffff0001ffff00000000000000000001ffffffff00000000000000010000000000000000ffff000000000000000000000001000000000000ffff0000000000000000ffff0001000000000000ffff00010001ffff0001000100000000ffff0000000000000000000000000000000100000000000000000000000000000000000000010000ffff0000ffff00010000ffff000000000000000100010000000000000001000000000000000000000000ffff000000000000000000000000000000000001ffff00000000ffff0001)

Testing Encode PCM

Test result: Success (61000b01014888f125379cd5d0ab6f)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0000000100000001ffff000100000000000000000001ffff00000000ffff000100000000ffffffff0001ffff0000000000000000000000000000000000000000000100010000ffff00000000000000000000ffff000000010000ffff00000000ffff000000000001ffff00000000ffff000000000000000000000000000000010000000000000000000000000001000000000000000000000000ffff000000000000000100000000000100000001ffff0000000000000000ffff0000ffffffff00000000000000000001000000010000ffff00000000000000000000ffff00000000000000000000000000000000ffffffff0000ffff0000000000000001000000000001000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000010000ffff00000000ffff0001)

Testing Encode PCM

Test result: Success (61000b01014899e025359fe0b08f2b)

Testing Decode AMBE

Test result: Success (6101420200a0000000000000ffff00000000ffffffff00000000000000010000ffff00010000ffff0000000000000000000100000000000100010000ffff000000000000000100000000ffff000000000000ffff00000000ffff00010000ffff0000000000000000000000000001ffff0000000000000000ffff00010001000000000000000000000001000000000000000000000000ffff00000000ffff0000000000010001ffff00000000ffff00000001ffffffff000000000000ffff0000000100000001000000000000ffff000100000000000000010001000000010000000000000000ffff0000000000000000000000000000000100000000ffff000000000000000100000001000000000000ffff00000000000000000000ffff000000000000000100010000ffff0001ffff0000000000000000000000000000ffff000000000000)

Testing Encode PCM

Test result: Success (61000b010148b543ad63cdd4a8033f)

Testing Decode AMBE

Test result: Success (6101420200a00000ffff0001000000000000ffff0000000000010001ffff000000000000000000010000000100000000000100000000ffff00000001ffff0001000000000001ffff00000000000000000000000000010001000000000000000000000000000000000000000000000000ffffffff0000000000000000000000000000000000010000ffff00000001000000010000ffffffffffff0000ffff0000000100000000ffff0001000000000000000000000000ffff00000001000000000000000000000000000000000000000000000000ffff00000001ffff00000000000000000000000000000001000100000000ffff000000000001ffffffff0001ffff0000ffff000000010000000100010000000000000000000100010001000000000000000000000000000000010000ffff000000000000000000000000ffff00010000ffff)

Testing Encode PCM

Test result: Success (61000b01014886528d21a9f0fc032f)

root@DMRLink:/home/test/DV3000/Analog_Bridge#

 



Re: Image....

Steve N4IRS
 

Steve,
Sorry I missed this question. For Analog_Bridge and either HB_Bridge or IPSC_Bridge I suggest the AllStarlink RC1 image. For MMDVM based systems, I have started recommending Pi-Star Image. It's a very clean Raspbian based image with a nice web UI.

Steve 


"PTT-Only" talkgroups in bridge_rules.py

David Andrzejewski KD8TWG
 

I have a simple setup, where I have two IPSC networks bridged.  I'd like to take a talkgroup that is "full-time" on one IPSC network and make it activated with PTT on the other.  My thinking is this:

* On the "full-time" IPSC network, ACTIVE = True, and ON and OFF are empty.
* On the "part-time" network, ACTIVE = False, and ON would contain that talk group ID?

Thanks!

- Dave


Re: "PTT-Only" talkgroups in bridge_rules.py

Cort N0MJS <n0mjs@...>
 

I would recommend using confbridge.py instead of bridge.py… it’s so, so, so much easier for this kind of stuff and far less prone to mistakes. 

Yes, you’ll have to re-write your bridge rules file one time, but it’s seriously a lot easier.

0x49 DE N0MJS

On Jun 28, 2017, at 3:44 PM, david via Groups.Io <david@...> wrote:

I have a simple setup, where I have two IPSC networks bridged.  I'd like to take a talkgroup that is "full-time" on one IPSC network and make it activated with PTT on the other.  My thinking is this:

* On the "full-time" IPSC network, ACTIVE = True, and ON and OFF are empty.
* On the "part-time" network, ACTIVE = False, and ON would contain that talk group ID?

Thanks!

- Dave

Cort Buffington
785-865-7206


Re: "PTT-Only" talkgroups in bridge_rules.py

David Andrzejewski KD8TWG
 

Got it. I can do that. That said, at least for my education, am I correct on this stuff?


-- 

David Andrzejewski
E-mail/iMessage/Jabber: david@...
PGP Key ID: 5EBA8A72


On Jun 28, 2017, at 16:53, Cort N0MJS <n0mjs@...> wrote:

I would recommend using confbridge.py instead of bridge.py… it’s so, so, so much easier for this kind of stuff and far less prone to mistakes. 

Yes, you’ll have to re-write your bridge rules file one time, but it’s seriously a lot easier.

0x49 DE N0MJS

On Jun 28, 2017, at 3:44 PM, david via Groups.Io <david@...> wrote:

I have a simple setup, where I have two IPSC networks bridged.  I'd like to take a talkgroup that is "full-time" on one IPSC network and make it activated with PTT on the other.  My thinking is this:

* On the "full-time" IPSC network, ACTIVE = True, and ON and OFF are empty.
* On the "part-time" network, ACTIVE = False, and ON would contain that talk group ID?

Thanks!

- Dave

Cort Buffington
785-865-7206


Brandmeister

David Andrzejewski KD8TWG
 

I'm interested in connecting a conf bridge between my repeater and brandmeister.  How is this typically handled?


Re: Brandmeister

Steve N4IRS
 

David,
First a few questions. What type of repeater is is? MMDVM? Motorola? All available TGs or a subset?
More information about what you are trying to accomplish will help us answer.

73, Steve N4IRS

On 6/29/2017 9:40 AM, David Andrzejewski KD8TWG via Groups.Io wrote:
I'm interested in connecting a conf bridge between my repeater and brandmeister.  How is this typically handled?
_._,_._,_


HBlink-HB_Bridge Logging

G7RPG - Peter Kendall
 

Would it be possible to get a time/date stamp output in the logging for
HBlink-HB_Bridge ?


Thanks
Peter


Re: Brandmeister

David Andrzejewski KD8TWG
 

It's a Motorola repeater.  I'm currently using DMRLink's confbridge to connect to it and to the K4USD cBridge, both via IPSC. My thought here is that we could potentially carry select additional talk groups and/or reflectors from BrandMeister as well as the standard talk groups we get from K4USD.  Obviously I wouldn't bridge anything between K4USD and BM, only between those two sources and the repeater. :)


Re: HBlink-HB_Bridge Logging

Steve N4IRS
 

in hblink.cfg:
LOG_HANDLERS: console-timed or
LOG_HANDLERS: file-timed or
LOG_HANDLERS: console-timed,file-timed

Steve

On 6/29/2017 10:44 AM, G7RPG - Peter Kendall wrote:
Would it be possible to get a time/date stamp output in the logging for
HBlink-HB_Bridge ?


Thanks
Peter



Re: Brandmeister

Steve N4IRS
 

Below is a section of my conference bridge configuration for confbridge.py
The DMR-MARC is a connection to a c-Bridge and BM_3108 is a connection to BrandMeister.
Walton, IRSC etc are my repeaters.

Hope this helps.


    'STATEWIDE': [
            {'SYSTEM': 'DMR-MARC',  'TS': 2, 'TGID': 3112,    'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'STN2100',   'TS': 2, 'TGID': 3112,    'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'Walton',    'TS': 2, 'TGID': 3112,    'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'IRSC',      'TS': 2, 'TGID': 3112,    'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'N4IRR',     'TS': 2, 'TGID': 3112,    'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'N4IRS',     'TS': 2, 'TGID': 3112,    'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
       ],

    'TAC310': [
            {'SYSTEM': 'DMR-MARC',  'TS': 2, 'TGID': 310,     'ACTIVE': True,  'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'STN2100',   'TS': 2, 'TGID': 310,     'ACTIVE': True,  'TIMEOUT': 2, 'TO_TYPE': 'ON',   'ON': [310,],     'OFF': []},
            {'SYSTEM': 'Walton',    'TS': 2, 'TGID': 310,     'ACTIVE': True,  'TIMEOUT': 2, 'TO_TYPE': 'ON',   'ON': [310,],     'OFF': []},
            {'SYSTEM': 'IRSC',      'TS': 2, 'TGID': 310,     'ACTIVE': True,  'TIMEOUT': 2, 'TO_TYPE': 'ON',   'ON': [310,],     'OFF': []},
            {'SYSTEM': 'N4IRR',     'TS': 2, 'TGID': 310,     'ACTIVE': True,  'TIMEOUT': 2, 'TO_TYPE': 'ON',   'ON': [310,],     'OFF': []},
            {'SYSTEM': 'N4IRS',     'TS': 2, 'TGID': 310,     'ACTIVE': True,  'TIMEOUT': 2, 'TO_TYPE': 'ON',   'ON': [310,],     'OFF': []},
        ],

    'TCOAST': [
            {'SYSTEM': 'BM_3108',   'TS': 2, 'TGID': 31123,   'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'STN2100',   'TS': 2, 'TGID': 31123,   'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'Walton',    'TS': 2, 'TGID': 31123,   'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'IRSC',      'TS': 2, 'TGID': 31123,   'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'N4IRR',     'TS': 2, 'TGID': 31123,   'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
            {'SYSTEM': 'N4IRS',     'TS': 2, 'TGID': 31123,   'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],         'OFF': []},
        ],


On 6/29/2017 10:46 AM, David Andrzejewski KD8TWG via Groups.Io wrote:
It's a Motorola repeater.  I'm currently using DMRLink's confbridge to connect to it and to the K4USD cBridge, both via IPSC. My thought here is that we could potentially carry select additional talk groups and/or reflectors from BrandMeister as well as the standard talk groups we get from K4USD.  Obviously I wouldn't bridge anything between K4USD and BM, only between those two sources and the repeater. :)
_._,_._,_


Re: HBlink-HB_Bridge Logging

Cort N0MJS <n0mjs@...>
 

To point out the comments in the sample config file above the [LOGGER] section (emphasis added):

# SYSTEM LOGGER CONFIGURAITON
#   This allows the logger to be configured without chaning the individual
#   python logger stuff. LOG_FILE should be a complete path/filename for *your*
#   system -- use /dev/null for non-file handlers.
#   LOG_HANDERLS may be any of the following, please, no spaces in the
#   list if you use several:
#       null
#       console
#       console-timed
#       file
#       file-timed
#       syslog
#   LOG_LEVEL may be any of the standard syslog logging levels, though
#   as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones
#   used.
#


On Jun 29, 2017, at 9:47 AM, Steve N4IRS <szingman@...> wrote:

in hblink.cfg:
LOG_HANDLERS: console-timed or
LOG_HANDLERS: file-timed or
LOG_HANDLERS: console-timed,file-timed

Steve

On 6/29/2017 10:44 AM, G7RPG - Peter Kendall wrote:
Would it be possible to get a time/date stamp output in the logging for
HBlink-HB_Bridge ?


Thanks
Peter








Cort Buffington
785-865-7206


Re: HBlink-HB_Bridge Logging

Steve N4IRS
 

Well,
While we are highlighting things

On 6/29/2017 11:01 AM, Cort N0MJS wrote:
To point out the comments in the sample config file above the [LOGGER] section (emphasis added):

# SYSTEM LOGGER CONFIGURAITON
#   This allows the logger to be configured without chaning the individual
#   python logger stuff. LOG_FILE should be a complete path/filename for *your*
#   system -- use /dev/null for non-file handlers.
#   LOG_HANDERLS may be any of the following, please, no spaces in the
#   list if you use several:
#       null
#       console
#       console-timed
#       file
#       file-timed
#       syslog
#   LOG_LEVEL may be any of the standard syslog logging levels, though
#   as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones
#   used.
#


On Jun 29, 2017, at 9:47 AM, Steve N4IRS <szingman@...> wrote:

in hblink.cfg:
LOG_HANDLERS: console-timed or
LOG_HANDLERS: file-timed or
LOG_HANDLERS: console-timed,file-timed

Steve

On 6/29/2017 10:44 AM, G7RPG - Peter Kendall wrote:
Would it be possible to get a time/date stamp output in the logging for
HBlink-HB_Bridge ?


Thanks
Peter








Cort Buffington
785-865-7206



Re: HBlink-HB_Bridge Logging

Cort N0MJS <n0mjs@...>
 

yeah, I did that and still have screwed up my own logging by forgetting it before :)

On Jun 29, 2017, at 10:04 AM, Steve N4IRS <szingman@...> wrote:

Well,
While we are highlighting things

On 6/29/2017 11:01 AM, Cort N0MJS wrote:
To point out the comments in the sample config file above the [LOGGER] section (emphasis added):

# SYSTEM LOGGER CONFIGURAITON
#   This allows the logger to be configured without chaning the individual
#   python logger stuff. LOG_FILE should be a complete path/filename for *your*
#   system -- use /dev/null for non-file handlers.
#   LOG_HANDERLS may be any of the following, please, no spaces in the
#   list if you use several:
#       null
#       console
#       console-timed
#       file
#       file-timed
#       syslog
#   LOG_LEVEL may be any of the standard syslog logging levels, though
#   as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones
#   used.
#


On Jun 29, 2017, at 9:47 AM, Steve N4IRS <szingman@...> wrote:

in hblink.cfg:
LOG_HANDLERS: console-timed or
LOG_HANDLERS: file-timed or
LOG_HANDLERS: console-timed,file-timed

Steve

On 6/29/2017 10:44 AM, G7RPG - Peter Kendall wrote:
Would it be possible to get a time/date stamp output in the logging for
HBlink-HB_Bridge ?


Thanks
Peter








Cort Buffington
785-865-7206



Cort Buffington
785-865-7206


Re: HBlink-HB_Bridge Logging

G7RPG - Peter Kendall
 

Yeah got it now, thanks guys. I did see that and assumed (incorrectly) that timed meant it only output logging for a period of time.

I'll go back under my shell.


Peter 


On 29/06/2017 16:01, Cort N0MJS wrote:
To point out the comments in the sample config file above the [LOGGER] section (emphasis added):

# SYSTEM LOGGER CONFIGURAITON
#   This allows the logger to be configured without chaning the individual
#   python logger stuff. LOG_FILE should be a complete path/filename for *your*
#   system -- use /dev/null for non-file handlers.
#   LOG_HANDERLS may be any of the following, please, no spaces in the
#   list if you use several:
#       null
#       console
#       console-timed
#       file
#       file-timed
#       syslog
#   LOG_LEVEL may be any of the standard syslog logging levels, though
#   as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones
#   used.
#


On Jun 29, 2017, at 9:47 AM, Steve N4IRS <szingman@...> wrote:

in hblink.cfg:
LOG_HANDLERS: console-timed or
LOG_HANDLERS: file-timed or
LOG_HANDLERS: console-timed,file-timed

Steve

On 6/29/2017 10:44 AM, G7RPG - Peter Kendall wrote:
Would it be possible to get a time/date stamp output in the logging for
HBlink-HB_Bridge ?


Thanks
Peter








Cort Buffington
785-865-7206



Re: HBlink-HB_Bridge Logging

Steve N4IRS
 

Can't count the number of times I've screwed up the logging section.

On 6/29/2017 11:06 AM, Cort N0MJS wrote:
yeah, I did that and still have screwed up my own logging by forgetting it before :)

On Jun 29, 2017, at 10:04 AM, Steve N4IRS <szingman@...> wrote:

Well,
While we are highlighting things

On 6/29/2017 11:01 AM, Cort N0MJS wrote:
To point out the comments in the sample config file above the [LOGGER] section (emphasis added):

# SYSTEM LOGGER CONFIGURAITON
#   This allows the logger to be configured without chaning the individual
#   python logger stuff. LOG_FILE should be a complete path/filename for *your*
#   system -- use /dev/null for non-file handlers.
#   LOG_HANDERLS may be any of the following, please, no spaces in the
#   list if you use several:
#       null
#       console
#       console-timed
#       file
#       file-timed
#       syslog
#   LOG_LEVEL may be any of the standard syslog logging levels, though
#   as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones
#   used.
#


On Jun 29, 2017, at 9:47 AM, Steve N4IRS <szingman@...> wrote:

in hblink.cfg:
LOG_HANDLERS: console-timed or
LOG_HANDLERS: file-timed or
LOG_HANDLERS: console-timed,file-timed

Steve

On 6/29/2017 10:44 AM, G7RPG - Peter Kendall wrote:
Would it be possible to get a time/date stamp output in the logging for
HBlink-HB_Bridge ?


Thanks
Peter








Cort Buffington
785-865-7206



Cort Buffington
785-865-7206


181 - 200 of 9595