freebeacon | Automated Beacon for FreeDV
kandi X-RAY | freebeacon Summary
kandi X-RAY | freebeacon Summary
freebeacon is a C library typically used in Internet of Things (IoT), Raspberry Pi applications. freebeacon has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.
When a "trigger" string is detected in the rx FreeDV text message (e.g. "hello beacon", or the beacon callsign), the beacon will transmit a signal report back to you. It requires a "txfilename" wave file to transmit, e.g. some one saying "Hi, I am a FreeDV beacon blah blah". The signal report is encoded into the transmit text message. Make the wave file long enough so that the the signal report is repeated a few times, say 30 seconds. Transmit will stop when the "txfilename" wave file is played once. Freebeacon saves the received audio from the radio AND the decoded audio as wavefiles. Use "wavefilewritepath" to specify where they are written. The file name is a date and time stamp. The length is limited to 60 seconds. If you set "wavefilewritepath" to a listable webserver directory the files will be available for download on the Web. To avoid filling your file system write a cron job to clean these files up once a day. If your input audio device is stereo note we only listen to the left channel. If you have a RS232 serial port (specified with "-c") RTS and DTR is raised on transmit to key your transmitter, and lowered for receive. If you are using Raspberry Pi you can use one of the GPIOs for PTT control of your transmitter using the "--rpigpio" option. You need to use the BCM GPIO number so "--rpigpio 11" uses pin 23 of the GPIO connector. Note FreeDV 700C doesn't have a text channel, so we just record the received file without triggering a Tx response. A whole lot of code was lifted from freedv-dev for this program.
When a "trigger" string is detected in the rx FreeDV text message (e.g. "hello beacon", or the beacon callsign), the beacon will transmit a signal report back to you. It requires a "txfilename" wave file to transmit, e.g. some one saying "Hi, I am a FreeDV beacon blah blah". The signal report is encoded into the transmit text message. Make the wave file long enough so that the the signal report is repeated a few times, say 30 seconds. Transmit will stop when the "txfilename" wave file is played once. Freebeacon saves the received audio from the radio AND the decoded audio as wavefiles. Use "wavefilewritepath" to specify where they are written. The file name is a date and time stamp. The length is limited to 60 seconds. If you set "wavefilewritepath" to a listable webserver directory the files will be available for download on the Web. To avoid filling your file system write a cron job to clean these files up once a day. If your input audio device is stereo note we only listen to the left channel. If you have a RS232 serial port (specified with "-c") RTS and DTR is raised on transmit to key your transmitter, and lowered for receive. If you are using Raspberry Pi you can use one of the GPIOs for PTT control of your transmitter using the "--rpigpio" option. You need to use the BCM GPIO number so "--rpigpio 11" uses pin 23 of the GPIO connector. Note FreeDV 700C doesn't have a text channel, so we just record the received file without triggering a Tx response. A whole lot of code was lifted from freedv-dev for this program.
Support
Quality
Security
License
Reuse
Support
freebeacon has a low active ecosystem.
It has 4 star(s) with 5 fork(s). There are 3 watchers for this library.
It had no major release in the last 6 months.
freebeacon has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of freebeacon is current.
Quality
freebeacon has 0 bugs and 0 code smells.
Security
freebeacon has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
freebeacon code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
freebeacon does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
freebeacon releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of freebeacon
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of freebeacon
freebeacon Key Features
No Key Features are available at this moment for freebeacon.
freebeacon Examples and Code Snippets
No Code Snippets are available at this moment for freebeacon.
Community Discussions
Trending Discussions on Internet of Things (IoT)
QUESTION
Display data from two json files in react native
Asked 2020-May-17 at 23:55
I have js files Dashboard and Adverts. I managed to get Dashboard to list the information in one json file (advertisers), but when clicking on an advertiser I want it to navigate to a separate page that will display some data (Say title and text) from the second json file (productadverts). I can't get it to work. Below is the code for the Dashboard and next for Adverts. Then the json files
...ANSWER
Answered 2020-May-17 at 23:55The new object to get params in React Navigation 5 is:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install freebeacon
Building Method 1 - installs codec 2 libraries on your system:. Note: On my Ubuntu 18 and RPi I had to add an extra search path to the ld.conf.d directory to match the path the codec2 .so was installed in.
Dependancies: sudo apt install git cmake sox libsamplerate0-dev portaudio19-dev libsndfile1-dev libhamlib-dev
Building Method 1 - installs codec 2 libraries on your system: Install codec2: git clone https://github.com/drowe67/codec2.git cd codec2 mkdir build_linux cd build_linux cmake ../ make sudo make install Note: On my Ubuntu 18 and RPi I had to add an extra search path to the ld.conf.d directory to match the path the codec2 .so was installed in. Check it has found libcodec2.so using: ldconfig -v | grep codec2 Build FreeBeacon: cd ~ git clone https://github.com/drowe67/freebeacon.git cd freebeacon mkdir build_linux cd build_linux cmake ../ make
Building Method 2 - without system wide codec 2 installation git clone https://github.com/drowe67/codec2.git cd codec2 && mkdir build_linux && cd build_linux cmake ../ && make Instruct freebeacon cmake to use local codec2 directory: cd ~ git clone https://github.com/drowe67/freebeacon.git cd freebeacon && mkdir build_linux && cd build_linux cmake -DCODEC2_BUILD_DIR=~/codec2/build_linux .. make
Testing: Plug in your USB sound card and USB RS232 devices. Use alsamixer to adjust levels on your sound card. F6 lets you select sound cards Usage: ./freebeacon -h List sound devices ./freebeacon -l Example usage: ./freebeacon -c /dev/ttyUSB1 --txfilename ~/codec2-dev/wav/vk5qi.wav --dev 4 -v --trigger hello Testing your PTT by making it jump straght into tx mode: ./freebeacon -c /dev/ttyUSB1 --txfilename ~/codec2-dev/wav/vk5qi.wav --dev 4 -v --trigger hello -t Testing sound cards on RPi: Note: Make sure your user is in the group audio, otherwise you will see no audio devices: $ groups vk5dgr audio You can add your user to the audio group with: $ sudo addgroup vk5dgr audio Then see if you can detect record devices: $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: Audio [RIGblaster Advantage Audio], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 $ arecord -D hw:1,0 -f S16_LE -r 48000 test.wav $ aplay test.wav Testing: As a first step try playing freebeacon_test.wav from another PC into the freebeacon machine input, this file has the trigger string "hello" in the txt msg.
Dependancies: sudo apt install git cmake sox libsamplerate0-dev portaudio19-dev libsndfile1-dev libhamlib-dev
Building Method 1 - installs codec 2 libraries on your system: Install codec2: git clone https://github.com/drowe67/codec2.git cd codec2 mkdir build_linux cd build_linux cmake ../ make sudo make install Note: On my Ubuntu 18 and RPi I had to add an extra search path to the ld.conf.d directory to match the path the codec2 .so was installed in. Check it has found libcodec2.so using: ldconfig -v | grep codec2 Build FreeBeacon: cd ~ git clone https://github.com/drowe67/freebeacon.git cd freebeacon mkdir build_linux cd build_linux cmake ../ make
Building Method 2 - without system wide codec 2 installation git clone https://github.com/drowe67/codec2.git cd codec2 && mkdir build_linux && cd build_linux cmake ../ && make Instruct freebeacon cmake to use local codec2 directory: cd ~ git clone https://github.com/drowe67/freebeacon.git cd freebeacon && mkdir build_linux && cd build_linux cmake -DCODEC2_BUILD_DIR=~/codec2/build_linux .. make
Testing: Plug in your USB sound card and USB RS232 devices. Use alsamixer to adjust levels on your sound card. F6 lets you select sound cards Usage: ./freebeacon -h List sound devices ./freebeacon -l Example usage: ./freebeacon -c /dev/ttyUSB1 --txfilename ~/codec2-dev/wav/vk5qi.wav --dev 4 -v --trigger hello Testing your PTT by making it jump straght into tx mode: ./freebeacon -c /dev/ttyUSB1 --txfilename ~/codec2-dev/wav/vk5qi.wav --dev 4 -v --trigger hello -t Testing sound cards on RPi: Note: Make sure your user is in the group audio, otherwise you will see no audio devices: $ groups vk5dgr audio You can add your user to the audio group with: $ sudo addgroup vk5dgr audio Then see if you can detect record devices: $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: Audio [RIGblaster Advantage Audio], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 $ arecord -D hw:1,0 -f S16_LE -r 48000 test.wav $ aplay test.wav Testing: As a first step try playing freebeacon_test.wav from another PC into the freebeacon machine input, this file has the trigger string "hello" in the txt msg.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
