ORx automatic boot script?

If I use my DIY ORx receiver, at the start, every time I apply a short manual config stepps, to start the receive process.
It consists of this stepps:

  • plug in the small wall-power unit, produce 12 Volt to the PCTV usb unit/and for the LNA
  • plug the larger power unit to drive the USB hub, and all the system with 5 Volt.
  • some minutes later, I start the web browser at my desktop machine, connected to the same router, as used for RaspberryPi too, at my home LAN. Pointing the browser to the web server,s url, at the ORx receiver.
  • at this point, start the librarian. In its menu I navigate to the Dashboard menu item, open the web interface page at the server 9981 port, and start the tvheadend config pages.
  • choose the configuration menu, and applay some options on it.
  • navigate to the Services submenu, choose the Outernet broadcast service, click the Play item. After this start a Test process. It can be check on the Status submenu on the tvheadend menu structure.
  • click second time this Play menu item, it start a Run process, and the tvheadend page disappeared, and come up a browser plugin page, processing the incoming data stream, actually the outernet logo picture only.
    The used URL like this:

After this the system is start to receive the incomming files, (with the ondd daemon) and save them in the working downloads dir.
If I close the browser windows with the plugin on the host machine, the receiver remain in configured state, and continuously receive the data stream.
In the process list there are this two processes runing with the following parameters:
root 2358 1 13 07:40 ? 00:02:05 /usr/sbin/ondd -d --pid-file /var/run/ondd.pid -o /var/spool/downloads
hts 2442 1 5 07:40 ? 00:00:45 /usr/bin/tvheadend -f -u hts -g video

The question come here:
are there any script to make automatically this config stepps? I havenot enough overview about the tvheadend and the other cooperating processes, to make this stepps automatically.

If you feel adventurous, you could disable the TVHE daemon, and modify the ONDD init script so that it runs ONDD like so: /usr/sbin/ondd -f 1721 -s 27500 -p V -o /var/spool/downloads -i.

NOTE TO OTHERS: The switches above are specifically for HotBIrd 13E.

Let me know how it goes. I’m very curious to see if this works.

thank you for the command line.
I started with it early morning, and left it alone. To check now, afternoon, I found in a separate dir 213 files in 18 Mb size.
It arrived in two time frames:
7.47 – 11.38 108 files 18 Meg
14.44 – 14.46 15 files 76 kbyte

The used command:
/usr/sbin/ondd -f 1147 -s 27500 -p V -o /var/spool/down -i

Here are some info messages, from the ssh terminal window:
07:17:13.225 [main] v1.0.1
event: 0x0
signal: 55442 00000
signal: 55442 00000

event: 0x1f
signal: 55442 00100
signal: 55442 00100

07:42:42.216 [ipd] Continuity error: 11 => 4
signal: 55442 00100
signal: 55442 00100

07:47:15.134 [filed] completed content/225a32d9161f3bd82e186cead4a75532.zip
signal: 55442 00100
signal: 55442 00100
07:47:17.151 [filed] completed content/a021d7eba8933ff08081c4ffc8dc8dda.zip
signal: 55442 00100

Some other messages from the userlog file:
Mar 29 15:35:24 raspberrypi ipd[24620]: [ipd] Continuity error: 13 => 7
Mar 29 15:36:52 raspberrypi ipd[24620]: [filed] files/apps/librarian_weather.zip failed hash check
Mar 29 15:40:01 raspberrypi ipd[24620]: [ipd] Continuity error: 6 => 0
Mar 29 15:44:39 raspberrypi ipd[24620]: [ipd] Continuity error: 13 => 7


sry, I made a mistake with the reffered command line.
From the process list this is, what running now:
24620 ? Sl 84:21 /usr/sbin/ondd -f 1721 -s 27500 -p V -o /var/spool/down

I dont know, what is the 1721 value for the frequency, I tried the others, but this is the working version.

Frequency should be L-band frequency. I’m not 100% sure about the technicalities because it’s not my area of expertise, but I can tell you how it’s calculated:

For Universal LNB:

  1. If transponder frequency is larger than 11700MHz, then subtract 10600.
  2. If transponder frequency is less than 117000MHz, then subtract 9750.

For NA Ku LNB: always subtract 10750 from the frequency.

As for the -t switch (needs tone), it is irrelevant for Ku LNB, and for Universal, you need it if the transponder frequency is above 11700MHz.

I’ll whip up a small app that gives you the correct ONDD command line for a given set of params (with obligatory use at your own risk disclaimer).

EDIT: Find the tool this this thread.

thank you for this online calculator.
It is really a nice tool. I used the same, as the calculated command line, first time with addtional -i switch, and second time with & at the end. I modified the out-dir, to see clearly, what are the newly arrived files, using this option: -o /var/spool/down


I think -i is mostly for debug so it prints out those messages. As for changing the download directory, you should be aware that Librarian uses the same directory, so you’ll need to change Librarian’s configuration or symlink to the original location.if you want to see the same files in Librarian. IIRC, the Librarian conf on Raspbian is located at /usr/local/lib/python2.7/dist-packages/librarian/librarian.ini.

I used a more simple approache: I create this new ./down dir for the test period only. I left the working receiver at home for 5-6 hours, and I checked the downloaded files there, when I accessed it again.
It was create by the system(?) ondd(?) this new subdirs: ./down/content, ./down/files/apps. After I checked the new files, I moved them to the standard working dir, into ./download/content/ So, I dont need to modify the librarian config to see them.

The directory structure under ./down is a mirror of our content pool.