Raspberry Pi/Projects/Wallboards - Revision history

R00t: /* Solution */

2015-06-19T03:03:33Z

‎Solution

2015-06-19T03:02:34Z

‎Solution

2015-06-14T16:39:39Z

‎Checklist

2015-06-14T15:37:46Z

‎init.d script

2015-06-14T15:34:37Z

‎Checklist

2015-06-14T15:15:20Z

‎Checklist

2015-06-14T15:11:21Z

‎Checklist

2015-06-14T15:09:53Z

‎Checklist

2015-06-14T15:07:32Z

‎Checklist

2015-06-14T15:07:19Z

‎Checklist

@@ Line 13: / Line 13: @@
 The classical method of sending signals to these monitors would be to utilize 5 strand RGB cables to each monitor and run them back to repeaters to duplicate signals.  This has the drawbacks of an excess of cabling needed, signal repeaters which can be unreliable, and no way to individually customize each screen if desired.
 ====Solution====
-Use a raspberry pi 2 for each monitor, driving the signal from the hdmi out. The raspberry pi would then VNC into a windows VM running the required software and displaying the call center information.  This would allow the existing network infrastructure to be used as only a network connection and AC power is required per display.
+Use a raspberry pi 2 for each monitor, driving the signal from the hdmi out. The raspberry pi would then VNC into a windows VM running the required software and displaying the call center information.  This would allow the existing network infrastructure to be used as only a network connection and AC power is required per display.  Wireless could have removed the network connection requirement, but wasnt considered reliable enough for a continuous 13hr+ per day connection.
 ==Configuring the Raspberry Pi 2==

@@ Line 13: / Line 13: @@
 The classical method of sending signals to these monitors would be to utilize 5 strand RGB cables to each monitor and run them back to repeaters to duplicate signals.  This has the drawbacks of an excess of cabling needed, signal repeaters which can be unreliable, and no way to individually customize each screen if desired.
 ====Solution====
-Use a raspberry pi 2 for each monitor, driving the signal from the hdmi out. The raspberry pi would then VNC into a windows VM running the required software and displaying the call center information.
+Use a raspberry pi 2 for each monitor, driving the signal from the hdmi out. The raspberry pi would then VNC into a windows VM running the required software and displaying the call center information.  This would allow the existing network infrastructure to be used as only a network connection and AC power is required per display.
 ==Configuring the Raspberry Pi 2==

@@ Line 330: / Line 330: @@
   | change hostname
   | <div style="font-size: 200%;">&#x2611;</div>
-  | <code><nowiki>~$ sudo hostname newhostname</nowiki></code><br>
+  | <code><nowiki>~$ sudo nano /etc/hostname</nowiki></code><br>
 <code><nowiki>~$ sudo nano /etc/hosts</nowiki></code><br>
-<code><nowiki>127.0.0.1     newhostname</nowiki></code><br>
+<code><nowiki>127.0.0.1     newhostname</nowiki></code>
   |-
   | lynx installed

@@ Line 185: / Line 185: @@
   USER=pi
   HOME=/home/pi
   export USER HOME
@@ Line 195: / Line 196: @@
      export DISPLAY=:0
      #Insert your favoured settings for a VNC session
-     setsid /usr/bin/vncviewer -shared -fullscreen -noraiseonbeep 10.45.9.157 -p /home/pi/.vnc/passwd > /dev/null 2>&1 &
+     setsid /usr/bin/vncviewer -shared -fullscreen -noraiseonbeep $vnchost -p /home/pi/.vnc/passwd > /dev/null 2>&1 &
      ;;
@@ Line 232: / Line 233: @@
 Enable dependency based boot sequence
   ~$ update-rc.d vncviewer defaults
 ===Add to Cron Job===
 Add the following script as a cronjob file

@@ Line 331: / Line 331: @@
 <code><nowiki>~$ sudo nano /etc/hosts</nowiki></code><br>
 <code><nowiki>127.0.0.1     newhostname</nowiki></code><br>
 |}

@@ Line 325: / Line 325: @@
   | <code><nowiki>~$ sudo passwd pi</nowiki></code><br>
 <code><nowiki>Enter new UNIX password:</nowiki></code>
 |}

@@ Line 320: / Line 320: @@
 <code><nowiki># restrict 127.0.0.1</nowiki></code><br>
 <code><nowiki># restrict ::1</nowiki></code>
 |}

@@ Line 315: / Line 315: @@
 <code><nowiki>server per1-ops-ntp1.sys.silversky.com iburst</nowiki></code><br>
 <code><nowiki>server per1-ops-ntp2.sys.silversky.com iburst</nowiki></code>
 <br>
 <code><nowiki># Local users may interrogate the ntp server more closely.</nowiki></code><br>