OP25 VirtualBox Project - Run OP25 on Windows 7

[Taylor_425]

Im running it on a windows 10 intel i5 8gb of ram and an SSD, using virtualbox and the latest rendition of Ununtu

 

[WX4JCW]

The only issue I really have is the quit button will not respond


Sent from my iPhone 8 using Tapatalk Pro
Jason WX4JCW
XPR7550 - SDS100

 

[Taylor_425]

This is what i have currently for my command ./rx.py --args 'rtl=0' -N 'LNA:48' -S 960000 -f 771.11875e6 -o 50000 -q -1 -d 10 -T trunk.tsv -V -2 -O loop0 -U -v 10 2> stderr.2

i tried scrolling through the log file but cannot find anything that would point to an issues. But if i restart OP25 audio returns for a few hours, and then drops off, its very difficult to figure out when it drops off as there are only 2 Fire Departments on this system right now and they have not been that busy.

 

[boatbod]

The only issue I really have is the quit button will not respond


Sent from my iPhone 8 using Tapatalk Pro
Jason WX4JCW
XPR7550 - SDS100

Sounds to me like the trunking.py or terminal.py thread either crashed or deadlocked. Normally a crash will result in some info in the stderr log, so I'd have to presume the message passing/queue processing quit working for reasons unknown.

This is what i have currently for my command ./rx.py --args 'rtl=0' -N 'LNA:48' -S 960000 -f 771.11875e6 -o 50000 -q -1 -d 10 -T trunk.tsv -V -2 -O loop0 -U -v 10 2> stderr.2

i tried scrolling through the log file but cannot find anything that would point to an issues. But if i restart OP25 audio returns for a few hours, and then drops off, its very difficult to figure out when it drops off as there are only 2 Fire Departments on this system right now and they have not been that busy.

Have you tried running with the http terminal rather than curses?
(-l http:127.0.0.1:8080)

 

[Taylor_425]

Have you tried running with the http terminal rather than curses?
(-l http:127.0.0.1:8080)[/QUOTE]

I have not I will try that right now. Do you think that might resolve the audio issue?

 

[boatbod]

Have you tried running with the http terminal rather than curses?
(-l http:127.0.0.1:8080)

I have not I will try that right now. Do you think that might resolve the audio issue?[/QUOTE]

I don't know, but it might because the two terminals do operate differently internally. Do you typically leave the terminal running with a plot active, or just the text screen?

 

[Taylor_425]

I normally just minimize the terminal window out of view, it seems to last 3-4 hours then it just stops. I normally only realize it when i listen to a scanner and stream at the same time. It continues to follow the voice channels it just does not produce audio.

After trying your suggestion it is still causing and issue

 

[boatbod]

I normally just minimize the terminal window out of view, it seems to last 3-4 hours then it just stops. I normally only realize it when i listen to a scanner and stream at the same time. It continues to follow the voice channels it just does not produce audio.

After trying your suggestion it is still causing and issue

Once the audio has ceased, if you bring up the terminal screen do you see any activity:
- does the "tsbks" counter keep incrementing?
- do you see any activity on the bottom line where the Frequency displays along with TGID and Tag info?
- what log level are you running? what if anything continues to appear in the log?

Try running "top -H" in a separate window and see what threads related to op25 are active. (post a screen shot)

 

[dbfeng]

Is it possible to have a VU meter for DMR decoded output? If so, how could I do that?

 

[boatbod]

Is it possible to have a VU meter for DMR decoded output? If so, how could I do that?

It should be possible to monitor audio through the sound subsystem.
https://linux-howto-guide.blogspot.com/2009/11/alsa-audio-meter.html

 

[adcockfred]

I agree needs better way to stay on freq. when you are a sleep move ppm up or down

 

[telvana]

Pi 3 odd error ...

I have been fighting with this off and on for about a month now and I've still had the same issue. I am running the latest version of Raspbian, on a Raspberry Pi 3b+, I've tried multiple different SD Cards, and even a different Raspberry PI. Here's the error.

linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown

gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10
built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy soapy redpitaya
*** Error in `python': malloc(): smallbin double linked list corrupted: 0x01444bf0 ***
Aborted


Any suggestions? It works perfectly fine on my desktop with the same exact configuration files, etc.

 

[boatbod]

I have been fighting with this off and on for about a month now and I've still had the same issue. I am running the latest version of Raspbian, on a Raspberry Pi 3b+, I've tried multiple different SD Cards, and even a different Raspberry PI. Here's the error.

linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown

gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10
built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy soapy redpitaya
*** Error in `python': malloc(): smallbin double linked list corrupted: 0x01444bf0 ***
Aborted


Any suggestions? It works perfectly fine on my desktop with the same exact configuration files, etc.

This error has come up previously. I'm trying to recall exactly what the fix was, but I suspect either osmocom driver install or op25 rebuild/reinstall. Have you searched this forum to see if the previous solution was ever posted?

 

[telvana]

This error has come up previously. I'm trying to recall exactly what the fix was, but I suspect either osmocom driver install or op25 rebuild/reinstall. Have you searched this forum to see if the previous solution was ever posted?

Yes, I've looked all over the place and couldn't find a solution. I'm not sure if a re-compile would solve it as this has persisted across a few raspberry pi's, I've never seen that error before and have not the slightest clue how to solve it lol

 

[N6ML]

I have been fighting with this off and on for about a month now and I've still had the same issue. I am running the latest version of Raspbian, on a Raspberry Pi 3b+, I've tried multiple different SD Cards, and even a different Raspberry PI. Here's the error.

linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown

gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10
built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy soapy redpitaya
*** Error in `python': malloc(): smallbin double linked list corrupted: 0x01444bf0 ***
Aborted


Any suggestions? It works perfectly fine on my desktop with the same exact configuration files, etc.

See https://forums.radioreference.com/s...354875-rpi-3-rtl-sdr-op25-23.html#post2976538

 

[ve2vag]

Yes, I've looked all over the place and couldn't find a solution. I'm not sure if a re-compile would solve it as this has persisted across a few raspberry pi's, I've never seen that error before and have not the slightest clue how to solve it lol

I confirm the link above dseven sent you. I was having similar errors.

The only way I was able to successfully compile OP25 on a RPI was this way`:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get build-dep gnuradio
sudo apt-get install libboost-all-dev liblog4cpp5-dev swig cmake gnuplot gnuplot-x11
sudo apt-get install gnuradio gnuradio-dev gr-osmosdr librtlsdr-dev libuhd-dev libhackrf-dev libitpp-dev libpcap-dev git
REBOOT

cd ~
git clone https://github.com/boatbod/op25
cd op25

mkdir build
cd build
cmake ../
make -j4
sudo make install
sudo ldconfig

Hope this helps

 

[N6ML]

I confirm the link above dseven sent you. I was having similar errors.

The only way I was able to successfully compile OP25 on a RPI was this way`:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get build-dep gnuradio
sudo apt-get install libboost-all-dev liblog4cpp5-dev swig cmake gnuplot gnuplot-x11
sudo apt-get install gnuradio gnuradio-dev gr-osmosdr librtlsdr-dev libuhd-dev libhackrf-dev libitpp-dev libpcap-dev git
REBOOT

cd ~
git clone https://github.com/boatbod/op25
cd op25

mkdir build
cd build
cmake ../
make -j4
sudo make install
sudo ldconfig

Hope this helps

install.sh has worked fine for me on raspbian and DietPi for some time now (many months). What happens when you try to use it?

 

[ve2vag]

install.sh has worked fine for me on raspbian and DietPi for some time now (many months). What happens when you try to use it?

Was not working at all after compilation. Did not get any error messages while compiling, but was having segmentation faults, double linked list corrupted errors and such everytime I was trying to run it after that. Only when I did the steps above, the program ran after that without errors. Can't explain why, tought...

I even had to restart from fresh yesterday after screwing my setup, and I've recompiled on my RPI 3B with the same method without issues. So it might be worth a try for telvana to try it also, just in case.

 

[N6ML]

Was not working at all after compilation. Did not get any error messages while compiling, but was having segmentation faults, double linked list corrupted errors and such everytime I was trying to run it after that. Only when I did the steps above, the program ran after that without errors. Can't explain why, tought...

I even had to restart from fresh yesterday after screwing my setup, and I've recompiled on my RPI 3B with the same method without issues. So it might be worth a try for telvana to try it also, just in case.

I'd be willing to bet that all of the issues were unrelated to install.sh (mainly the "rtl:0" thing). If you can reproduce the failure, let us know....

 

[ve2vag]

I'd be willing to bet that all of the issues were unrelated to install.sh (mainly the "rtl:0" thing). If you can reproduce the failure, let us know....

You're probably right. However, with the rtl:0 thing, the error message I was getting was ValueError: No JSON object could be decoded. The seg error, double list corrupted, and such, were received a while back, and with another json for multi_rx. And after recompiling the way described, and using the same other json file, it worked then.