dreamportNonoo's personal homepage2017-07-04T12:12:38Zhttp://dp.nonoo.hu/feed/atom/WordPressNonoohttp://www.nonoo.hu/<![CDATA[New videos]]>http://dp.nonoo.hu/?p=26002017-07-04T12:12:38Z2017-07-04T12:11:49Z
]]>0Nonoohttp://www.nonoo.hu/<![CDATA[2016 recap]]>http://dp.nonoo.hu/?p=25922016-12-21T20:56:36Z2016-12-21T20:56:36ZIt’s been quite a while since I last posted here (more than a year ago…). Let’s see what happened with me this year:
Quit my daily job and started an own company called SharkRF.
I’ll try to post here more frequently than once a year :)
]]>0Nonoohttp://www.nonoo.hu/<![CDATA[Linux USB HDD fix]]>http://dp.nonoo.hu/?p=25742015-12-08T19:57:58Z2015-12-08T19:57:58ZI partitioned and formatted a 2TB HDD connected with an USB HDD adapter to a Debian system running under VMware, copied the files and moved the HDD to an old P4 system with Debian and a non-AHCI capable BIOS. The HDD showed up as a 232.9GB one:
1 2
Device Boot Start End Sectors Size Id Type
/dev/sdc1 256 488378645 488378390 232.9G 83 Linux
After googling a while I found out that the problem is with the BIOS reporting the HDD to the OS as if it had 512 bytes long sectors, not 4096 ones.
I could mount the ext4 file system with losetup by telling that it starts at byte no. 8*256 = 2048:
1 2
losetup /dev/loop0 /dev/sdc -o 2048
mount /dev/sdc1 /home/storage4
A permanent fix is to edit the HDD’s MBR partition table to have the file system start at the correct byte no. I exported the partition table to a text file with sfdisk:
1
sfdisk -d /dev/sdc > sdc.partitions.sfdisk.text
Then opened the file and edited the start value to 2048, and size to 8*488378390=3907027120. After that I wrote back the partition table to the drive:
1
cat sdc.partitions.sfdisk.text | sfdisk /dev/sdc
After running partprobe everything was all right again.
1 2 3 4 5 6 7 8 9
Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0006aac3
Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 3907029167 3907027120 1.8T 83 Linux
]]>0Nonoohttp://www.nonoo.hu/<![CDATA[1080p YouTube videos on chinese Android TV boxes]]>http://dp.nonoo.hu/?p=25722015-12-08T19:46:04Z2015-12-08T19:46:04ZA few weeks ago I ordered an Android TV box called U BOX i one (i828) from gearbest.com. To my suprise, the updated YouTube app only played videos at 360p resolution. The stock app works fine, but I wanted to use the latest one. After googling a while I found a Japanese site with the fix:
Clear YouTube app cache and data in Android settings / App settings
Reboot
Optionally you may need to open a terminal before rebooting and enter these commands:
1 2 3 4
su
wm size 2560x1440
wm density 320
reboot
And after the system booted up:
1 2 3
su
wm size reset
wm density reset
]]>9Nonoohttp://www.nonoo.hu/<![CDATA[Some recent videos]]>http://dp.nonoo.hu/?p=25692015-11-01T18:24:40Z2015-11-01T18:24:40ZAs I updated my blog quite a while ago, here are a few videos in a bunch:
]]>0Nonoohttp://www.nonoo.hu/<![CDATA[dmrshark updates]]>http://dp.nonoo.hu/?p=25652015-11-01T17:57:13Z2015-11-01T17:57:13ZI’ve been working on dmrshark in the past few months. Most of the improvements can be seen online at the Hungarian network’s live status page, or you can check the project’s GitHub page.
The new features are:
The info column shows decoded SMS messages and GPS coordinates.
dmrshark decodes voice calls and calculates their current and average RMS volumes. There’s a circle which varies it’s color according to the volume and helps setting the correct mic gain.
Several new columns added to the repeater table.
dmrshark can record decoded voice data to .mp3 files. Recorded files of the Hungarian network can be downloaded from the archive page.
Live streaming via WebSockets or HTTP are now supported.
DMR messages can be sent from an external SQL database table (see the Hungarian live status page). Both Hytera and Motorola formats are supported.
Data packet sending and receiving with full FEC encoding/decoding and selective retransmission.
SMS format conversion is supported. If you send an SMS from a Hytera transceiver to a Motorola (or Chinese one), dmrshark detects that the message send was unsuccessful and retries sending your message in the opposite (in this case, Motorola) format.
If you send the message “help” (without quotation marks) to dmrshark’s DMR ID (7777), you can get the supported command list in SMS.
If the first word of a message to 7777 is an email address, and the other words are the message, dmrshark will send the message as an email to the given destination address.
If you send the word “ping” to 7777, it will answer with “pong”.
If you send the word “info” to 7777 with a callsign or DMR ID as the second word, it will give you info back about the given callsign/ID from the callsign book database.
If you send a message to 7777 with the first word being a callsign and the rest are the message, it will be sent to the APRS-IS system as an APRS message.
APRS message sending/receiving to and from APRS-IS
GPS position decoding and sending to the APRS network. Both time and button triggered Hytera GPS position packets can be decoded. DMR data ack is sent after a successful GPS position packet has been decoded, so the transceivers won’t send duplicate position packets unnecessarily.
Echo service is available on 7777, in both timeslots and both private and group calls. After the echo test ends, dmrshark will send you back your average RSSI and RMS volume values during the echo test. This echo test SMS gets sent also after a normal DMRplus echo test sent to TS2/9990.
Most of the FEC algorithms are used not only for error checking but for error correction too. Most of the DMR protocol’s packets can be decoded and displayed in the log.
]]>1Nonoohttp://www.nonoo.hu/<![CDATA[Raspberry Pi Sensors]]>http://dp.nonoo.hu/?p=25622015-11-01T17:31:34Z2015-11-01T17:30:03ZAnother great book from PacktPub. The subtitle is great to give a short description on what this book is about: “Integrate sensors into your Raspberry Pi projects and let your powerful microcomputer interact with the physical world“.
It begins with an introduction to Linux, basic electronics, communication protocols, so everyone who is interested in the topic can begin tinkering, you don’t need to be an embedded Linux expert. The chapters cover very interesting topics like measuring distance using ultrasonic sensors, measuring temperature, air pressure, humidity, using a photoresistor, an A/D converter, how to process and store gathered data, and lastly how to use OpenCV for simple image processing.
I recommend this book for everyone who want to learn building something with sensors connected to the Raspberry Pi.
]]>0Nonoohttp://www.nonoo.hu/<![CDATA[dmrshark]]>http://dp.nonoo.hu/?p=25532015-06-10T09:56:22Z2015-06-10T09:56:22ZIn the last 2 weeks I’ve been working on a software called dmrshark in my free time. It uses libpcap to analyse the traffic of a Hytera IPSC network.
It can be used for:
Tracking calls, logging to a text file, and/or inserting them to a remote MySQL-compatible database.
Automatic and periodic reading of repeater timeslot RSSI values during calls and also inserting them to the remote database.
Updating a remote database table with currently active repeaters and their info (ul/dl freqs, type, fw version etc.).
I’m planning other features as well, development hasn’t stopped of course :)
Here’s a video of an early preview version which only supported DMR packet structure decoding and logging to the text console:
]]>6Nonoohttp://www.nonoo.hu/<![CDATA[Hytera RD625 DMR repeater tests, VoIP setup]]>http://dp.nonoo.hu/?p=25462015-05-25T14:04:53Z2015-05-25T14:04:53ZI’ve translated my recent blogpost on ham-dmr.hu, so here’s some info about the Hytera RD625 DMR repeater and about setting up VoIP communications.
We’ve measured the bandwidth required for the repeater to communicate with the DMR master software to transfer one timeslot. The result is 15-17 kbit/s for both up and download directions, so the bandwidth required is about 35 kbit/sec, if there’s someone talking on one timeslot. We’ve conducted the tests using a 3G internet connection with an 8 slot length jitter buffer. The latency of our 3G connection is quite high, but the voice communication remained perfect. I’ve made a video about the tests:
Some interesting facts
The blue LED under the D sign is on when the repeater is communicating with the master software. When the repeater connects to the master, a voice says on TS2 TG9 that the reflector 4770 got connected.
The repeater doesn’t care about an unplugged Ethernet cable, it won’t ask for a new IP address. It doesn’t care about DHCP lease timeouts, it only asks for an IP address in DHCP mode only when we power it on.
All 3G connections are NATted in Hungary, so there’s no external address and connection tracking for the UDP packets, so incoming packets can’t find a way to the repeater. We had the repeater plugged into a Routerboard, which had the 3G stick in it, and we created a VPN tunnel to our server and set the default gateway for that VPN connection. This way we had an external IP address and could set up our firewall to pass through UDP packets destined to the repeater.
The repeater uses the following UDP ports: 62005 (status, heartbeat, etc.), 62006 (general traffic), 62007 (management info, RDAC)
Setting up a SIP server (Asterisk)
It’s important to mention that an amateur radio network can’t be connected to other telecommunication systems for replacing them, so it’s forbidden to connect the DMR system to the GSM phone network. This post is only about experimentation.
I don’t explain all the details about setting up an Asterisk server, there’s a lot of info about it on the net.
First we have to create entries in sip.conf for the DMR users we want to allow starting outgoing calls:
The structure of the user ID: call type (1 – private, 2 – group) + timeslot + DMR ID, example: 1 – private call, 1 – timeslot, 2161005 – DMR ID, so it’s 112161005. More about on the structure later.
To be able to receive calls, we have to create extensions for the users in extensions.conf:
This way if we call the number 1 on the SIP server, we will dial DMR user 2161005 with a private call on timeslot 1.
Setting up the repeater for VoIP
First, enable Telephone Interconnection Enable in Phone->Phone System, then enter the Asterisk server’s IP address to Gateway IP. PBX Access Code is the SIP password, Phone Gateway ID is the number, which has to be called on the handheld device in a group or private call. Connect Code should be #1, Disconnect Code should be #2. Radio De-key Beep should be enabled, so the called party will hear a beep when we release the PTT so he/she will know when we finished talking and can hear what he/she says.
Setting up a PD785G for VoIP
First, we have to add a Phone Systeme in the Hytera CPS at Phone System menu. Set the Phone Gateway ID to the Gateway ID (we tested using the gateway ID 666 as can be seen on the video above), Connect Code button should be set to P1-re, number should be #1, Disconnect Code button should be set to P2, number should be #2.
The Phone System should be set to the previously added one on the digital channels where we want to use it.
Starting and stopping a call
To start a VoIP call from the handheld radio, we have to enter the previously set Gateway ID in a private or a group call, press the PTT continuously, and then we have to enter the number to call (make sure DTMF keypad is previously got enabled in the CPS!). Release the PTT button after entering the number. To pick up an incoming call, press the PTT, press the green button, and then release the PTT. This can be done because we have set the Connect Code button to P1 previously, so pressing P1 will enter the Connect Code (it was set to #1) instantly. To hang up a call, press the PTT, then press the red button, and then release the PTT (this will enter the Disconnect Code).
SIP registration, user management
If we enable the Dial-up Mapping in the repeater CPS, then the repeater will try to register to all of the Phone IDs to the SIP server which are in the list. If the SIP server receives a call for a Phone ID, then the repeater will call the Radio ID associated with that Phone ID.
If Dial-up Mapping is off, then the repeater will try to register the previously mentioned calltype+timeslot+DMR ID format Radio IDs (not Phone IDs!) on the SIP server. If we add time slot 1, Radio ID 9 as a group call, then it will register on the SIP server with the ID 219. If we call 219 on the SIP server, then the call will be automatically routed to timeslot 1 talk group 9. This call can be interrupted by any DMR user with the usual PTT press + red button + PTT release combination.
If we start a call from a Radio ID which is not in the mapping list, then the repeater will try to register it on the SIP server when starting the call. This means that only those DMR users can start a call who has a SIP user in Asterisk.
]]>10Nonoohttp://www.nonoo.hu/<![CDATA[Hytera tests]]>http://dp.nonoo.hu/?p=25382015-05-13T20:49:38Z2015-05-13T20:49:38ZI had two PD785Gs this evening with me so I couldn’t resist to do the glass of water test :)
Today we tested the bandwidth and the VoIP integration of the Hytera RD625. I’ve made a (Hungarian) tutorial on how to set up Asterisk, the repeater and a handheld radio to be able to make and receive VoIP calls.
Another great book from PacktPub. The subtitle is great to give a short description on what this book is about: “Integrate sensors into your Raspberry Pi projects and let your powerful microcomputer interact with the physical world“.
