1. Raspberry Pi 4 Software Download
2. Raspberry Pi 4 8gb
3. Install Citrix Receiver Raspberry Pi 4 8gb

Has anyone setup a citrix client on a Pi? I am using the RPITC image for the raspberry pi. I have also tried installing the receiver on Raspbian Jessie but i received the same errors there. Beginning August 2018, Citrix Receiver will be replaced by Citrix Workspace app. While you can still download older versions of Citrix Receiver, new features and enhancements will be released for Citrix Workspace app. Citrix Workspace app is a new client from Citrix that works similar to Citrix Receiver and is fully backward-compatible with. Insert the MicroSD card into the Raspberry Pi and power it on Follow the prompts Install Citrix Receiver Download the following from www.citrix.com Citrix Receiver for Debian - ARM-HF version USB ARM-HF version package from Citrix.com Install Citrix Receiver by opening a terminal and running the following commands.

The Raspberry Pi is a family of low-cost, single-board computers developed by the Raspberry Pi Foundation in the U.K. Since its introduction in 2012, it has emerged as a widely-used platform for embedded system research and project hobbyists. Most users use some form of the Linux operating system on the Raspberry Pi; equipped with several USB ports, quad-core processor, an IEEE 802.3/Ethernet port, IEEE 802.11 WiFi and Bluetooth capability, HDMI connector, audio output, and a general-purpose input/output (GPIO) bus, it is a very powerful tool for research, exploration, teaching, and learning.

There are many documents on the Internet that describe various aspects of using a Raspberry Pi to create a marine Automatic Identification System (AIS) display. While I don't want to repeat all of those sites — and, hopefully, I won't — I wanted to put everything into one place, particularly for other AIS researchers who are looking for a push up the learning curve. I hope that this page accomplishes that goal.

For purposes of this paper, I am assuming that readers understand the fundamentals of AIS. To get a lot more information, check out the USCG Navigation Center's Automatic Identification System Overview, IALA's An Overview of AIS (Edition 2), or the automatic identification system (AIS) article at Wikipedia.

For your viewing pleasure, see my Build A Raspberry AIS talk from Hack The Sea 2.0 at DEF CON 28 (2020).

Table of Contents

Unless specifically noted otherwise, no endorsement of hardware, software, or other items is intended in the discussion below.

Hardware

• Raspberry Pi: Essential hardware, obviously, since this is the title of the paper! There are many sources and I leave that to the reader. Be sure to get the latest version of the hardware. (The information on this page has been tested, and is running, on a Raspberry Pi 3 Model B+. Everything should still work on the current version of the hardware, the Raspberry Pi 4.)

• dAISy Hat AIS Receiver: If you are doing AIS projects, you will need some type of AIS receiver. There are a number of options; one way is to get an external receiver and connect it to the Raspberry Pi's USB port. My suggestion is the dAISy Hat 2-channel AIS receiver, a daughterboard for the Raspberry Pi. Designed by Wegmatt, the primary source is Tindie.

• NOTE: If you use an antenna for your dAISy Hat, note the terminating connector. If it comes with a male BNC plug, it should attach directly to the dAISy Hat's female BNC jack. If it comes with a coaxial cable, it most likely terminates with a male PL-259/SO-239 plug, thus, you will need an adapter. I would recommend getting the SO-239 pigtail or BNC-to-SO-239 adapter when you buy the dAISy Hat.
• A note on antenna connector nomeclature: According to most sources that I can find, references to SO-239 and PL-259 are mated connector pairs for coaxial cable terminations. In general, the SO-239 (aka UHF Female or UHF Jack) is the connector on a radio or chassis and the PL-259 (aka UHF Male or UHF Plug) is the connector on a cable. You may also find a 'male SO-239' or a 'female PL-259' product listings. Be sure to look at the pictures!

• µSD card: The operating system, all files, and on-board storage for the Raspberry Pi reside on a single microSD card. Ideally, get a card with a capacity of 32 GB or 64 GB. Most microSD cards come with an adapter so that they can fit into a computer's SD card slot. If you don't have such a card slot, you might also need to obtain a µSD/SD-to-USB reader.

• Case (optional): Although it is not absolutely necessary to have a case, I would recommend getting the case that comes with the dAISy Hat in order to protect all of the components when everything is in use.

• Other hardware (optional): In order to initially configure the Raspberry Pi, you might also want to have on hand an HDMI-capable monitor, an HDMI cable, and a wireless/USB keyboard and mouse. You should also have an Ethernet cable and router for a network connection or an open WiFi network.

• Antenna (optional): You will need an antenna if you wish to pick up AIS signals from the outside. AIS uses two VHF maritime frequencies, 161.975 MHz and 162.025 MHz. Any antenna that can work in these frequencies — or is labelled 'VHF marine antenna' — ought to work fine for AIS projects. As noted above, be sure to check out the antenna cable connector.

Installing Raspian

Before going any further, I would like you to be aware of an entirely different direction you can take. AISHub offers rPiAIS, an implementation of AIS Dispatcher for the Raspberry Pi. Depending upon what you're trying to do, rPiAIS might be worth looking into.

There are several lightweight Linux (and other) operating systems that can run on the Raspberry Pi. The native OS is Raspian, a variant of Debian. The best source for all of these is the Raspbery Pi Foundation's Downloads page. For starters, my recommendation is to download the New Out Of the Box Software (NOOBS) version.

1. Download the NOOBS ZIP file, unZIP it, and extract the contents to a NOOBS directory your computer.
2. Format the microSD card with the FAT32 file system. (NOTE: If you have a Mac and an SD card 64 GB or greater in size, use the Erase tool in Disk Utility to format the microSD card as MS-DOS (FAT).)
3. To ensure that the SSH service can be used to access the Raspbery Pi (and I think that you should!), a small or empty text file named ssh has to be present in the boot partition. If such a file is not already present, create it and copy to the /boot subdirectory in the NOOBS directory on your computer.
4. Copy the contents of your NOOBS directory onto the SD card.


5. Insert the microSD card into the Raspberry Pi's SD card slot, attach your I/O devices (i.e., keyboard/mouse/monitor), and power it on.
6. A boot screen will appear. Select the option to install full Raspian desktop and let it do its magic! During this period of time, you will be asked for a password and some other pretty standard configuration information, and then asked to reboot.

For additional information, see the Raspberry Pi Software Guide page.

Configuring the Raspberry Pi

This is where you make the Raspberry Pi your own! Enter the configuration menu by clicking on the Raspberry icon in the upper left of the screen, select Preferences, and then select Raspbery Pi Configuration:

• On the System tab:
• Enter a system name in the Hostname: field, e.g., AIS_PI.
• Click the Change Password: button to change the password.


• On the Interfaces tab:
• Be sure that the Serial Port radio button is set to Enable
• To enable SSH and/or VNC, click the appropriate radio button(s). [NOTE: You might need to engage port forwarding and/or make other changes to your firewall to allow SSH/VNC traffic into your network. SSH uses TCP port 22 and VNC uses TCP port 5900.]
• If SSH is enabled, you can also easily get FTP access to the device using any FTP client that supports SSH File Transfer Protocol (SFTP). [Do not confuse SFTP with FTPS; the latter is FTP over SSL/TLS.]


• On the Localisation tab:
• Set your language and country by clicking the Set Locale... button.
• Set your timezone area and location by clicking the Set Timezone... button.
• Set the keyboard model and layout by clicking the Set Keyboard... button.
• If you intend to use WiFi, click the Set WiFi Country... button to select a country.


• Click the OK button

You can perform the same functions from the command line by opening a terminal window and entering:

Additional information on using the command line configuration utility can be found at the Raspberry Pi Foundation's raspi-config page.

Once you've set a WiFi country, the Raspberry Pi should automatically find any available WiFi network that is broadcasting its SSID if a network cable is not physically attached. If you want to connect to any WiFi network that doesn't broadcast an SSID, you will need to edit the /etc/wpa_supplicant/wpa_supplicant.conf file in order to add the hidden network information.

As an example — suppose you have a non-broadcast SSID 'Guest' network that requires no password and a non-broadcast SSID 'Owner' network with the password 'Secret' (using WPA). Open the configuration file by entering the following on the command line (you need to use sudo here because this is a system file):

Now, add the following lines to the config file:

Raspberry Pi 4 Software Download

After adding the lines, press control-O (^O) to write the file and ^X to exit. The Raspi will now see the hidden networks as well as any openly advertised networks.

NOTE: Raspian comes with several easy-to-use text editors. nano, referenced above, is a nice command line editor. A GUI text editor can be found by clicking the Raspberry icon, Accessories, and Text Editor.

Finally, a note about screen resolution. If you access the Raspberry Pi strictly via SSH or VNC, it is referred to as a headless connection. Regardless of whether you access remotely or output to an HDMI monitor, if you don't like the screen resolution, you can always change it by opening the /boot/config.txt file with your favorite text editor (be sure to use sudo). Scroll down to find these lines:

Uncomment the two framebuffer commands by removing the leading hash (#). Save the file, reboot, and your screen resolution will be different! You might need to experiment around a bit to find the right size for your monitor.

Installing dAISy Hat

Installing the dAISy Hat hardware is very straight-forward. You'll probably want to download the dAISy HAT AIS Receiver Manual for additional reference.

If you have played with computer hardware before, then installing the dAISy Hat daughterboard to the Raspberry Pi's GPIO pins won't be a problem. If you haven't done this before, all I can say is to work slowly, align the socket on the board onto the Raspberry Pi's pins carefully, and press the cards together slowly and evenly.

The remainder of this section describes the installation of gpio, a command-line tool that allows you to determine the status of the GPIO pins on the Raspberry Pi. This step is optional; it provides useful information but is not essential to the operation of the dAISy Hat or OpenCPN.

After installing the dAISy Hat, open up a terminal window and enter the following commands in order to 1) ensure that you are in your home directory, 2) download the uart_control program from GitHub into your home directory, 3) change permissions to make it easily executable, 4) install the gpio command, and 5) reboot the Raspberry Pi:

Now that gpio is installed, you can find the status of the GPIO pins by using the command:

To learn about the other GPIO command options, use:

Installing screen

screen is a terminal emulator with which you can communicate directly with the serial port. This provides a mechanism with which to control and manage the dAISy Hat hardware. This step is optional; screen provides useful information but is not essential to the operation of the dAISy Hat or OpenCPN.

screen is not native to Raspian, so you will need to install it by issuing the following command:

The dAISy Hat should be attached to Serial 0 port; under Raspian, note that /dev/serial0 is an alias for /dev/ttyS0. To connect to the hardware, type:

Press <ESC> and you should see a display such as the following:

Note that if you press T, you will enter a mode where you can send AIS test messages (as NMEA 0183 sentences):

If you press <ENTER>, the software will transmit the AIS Type 4 message (Base Station Report) shown here every five seconds. Pressing <ESC> stops the transmission of test messages; pressing <ESC> again returns the device to receive mode. (If you are curious what the message says, use one of the AIS parsing Web sites or my AIS parser software described in the Interpreting the Data< section below.)

You can exit screen by entering command mode (^A), then pressing K (kill process) followed by Y (yes). To obtain a complete list of screen commands and options, type:

OpenCPN

OpenCPN is free, open source chartplotter and maritime GPS navigation software that can run on Android, Fedora, Linux, Mac OS X, Orange Pi, Raspberry Pi, Ubuntu, and Windows systems — it seems about every platform except iOS. While designed to be used while underway or for planning purposes, it also provides a useful tool for AIS projects.

To learn more about OpenCPN, visit OpenCPN.org, the source of all things OpenCPN! In particular, there are a wide variety of manuals to be found at that site, including:

The steps outlined below should work on Raspian version 9 (aka stretch). If you are not sure what version of Raspain or other Linux distro you are using, use the following command:

Prepare for the OpenCPN installation by creating an opencpn directory under your home directory:

PGP Key Management

The first step in order to download and install OpenCPN is to manually create a Pretty Good Privacy (PGP) keyfile. This process will ensure that you have the latest, most current key.

1. Point your browser to the OpenPGP Public Key Server.

• In the Search String field, enter the key 0xC865EB40.
• All options should be OFF except 'Get verbose index of matching keys.'
• Click the Search for a key button.
2. A new Web page, similar to the one below, will open. Click on the C865EB40 link provided in the pub section.

3. This should take you to page similar to the one below that contains the key.

4. Open a text file called opencpn_key (or, use another name if you want). Copy the Web page text starting from '-----BEGIN PGP PUBLIC KEY BLOCK-----' to the end of the page, and paste it into the opencpn_key file; save and close opencpn_key.

Download and Install OpenCPN

Start the OpenCPN installation by typing:

A text editor will open. Move the cursor to the end of the file and add this line (assuming that you are using Raspbian Stretch):

Save the updates and close the file.

Now, install the PGP key, get updated software sources, and install OpenCPN:

There may be some error messages; read them and document any additional commands that you need to execute.

Run and Configure OpenCPN

Run OpenCPN by typing opencpn from the command line or by clicking the Application (Raspberry) icon, Education, OpenCPN from the GUI.

The first thing to do, in almost all cases, will be to load some charts; this is possibly the most painful part of OpenCPN:

1. Click on Options (the crescent wrench or gear icon)
2. Click on Charts
3. Here is where things can get a bit complicated. The easiest way to download charts is to select the Chart Downloader tab.


4. Click the Add button to see the Chart Catalog. From here, you can scroll down to see a variety of chart catalogs. In this case, I select the 'USA - NOAA & Inland charts' catalog.


5. After clicking OK on the catalog, the chart format options will appear. In this case, I have expanded the 'ENC' option. The ENC NOAA charts can be viewed by state, USCG District, and other options. In this case, I select 'by Coast Guard Districts' and scroll down to select '01 CGD' by clicking OK.


6. At this point, download the District 1 catalog into the directory by clicking the Update button. At that point, you should see a bunch of chart names appear in the lower dialogue box. Scroll through the box to select the charts that you want; in this case, two charts from Lake Champlain have been checked off. (In order to make this selection, you need to know the name of the chart(s) you want; knowing the chart number is useful, but only as a way to learn the name because the catalog in OpenCPN only lists names.) Click the 'Download selected charts' button to download the charts to your system.


7. The configuration shown here has charts from California, Connecticut, Florida, and Vermont. If I go back to the OpenCPN chart and scroll out far enough, I see the green boxes representing which charts I have downloaded in those four states. Scroll in closer to get the detail!

Next, configure your data source:

1. As above, click on Options (the crescent wrench or gear icon)
2. Click on Connections
3. Scroll down and click the Add Connection button
4. Under Properties:
• If you are using the dAISy Hat (or other data source on the serial I/O bus):
• Click the Serial radio button
• Select (or enter) '/dev/ttyS0/ or '/dev/serial0' in the DataPort field
• Select a Baudrate of 38400
• Click OK


• If you are using an external device and getting a network-based data feed:
• Click the Network radio button
• Select the protocol (most likely to be TCP but will depend upon your setup)
• Enter the IP address of the device
• Enter the port number used by the protocol
• Click OK

Under Connections, you can check the Show NMEA Debug Window box to see the actual NMEA sentences (screen shots below for the serial and network connections, respectively):

Note that when using OpenCPN with a network data source, the raw data feed can be captured directly using the netcat (nc) or telnet command, in the form:

OpenCPN can also be used as a data server and create a data stream from its input. This is particularly useful if you are reading from a serial interface; OpenCPN can read from serial0, for example, and produce a TCP data stream. Setting this up is very straight-forward:

• Add a new connection, as above.
• Click the Network radio button
• Select the TCP protocol
• Use the IP address 0.0.0.0 since you are using yourself as the source
• Enter the port number you'd like to use (it is best to use a value in the range 1024-65535)
• Uncheck the Receive input on this Port box
• Check the Output on this port box
• Click OK

Raspberry Pi 4 8gb

At this point, you have two open connections, and OpenCPN is accepting input from whatever source you had been using and sending output on your desired TCP port.

Read your raw data stream, as above, from a terminal or any other application using netcat or telnet.

Finally... one of the problems that is immediately apparent from the raw output stream is that AIS lacks timestamp information. While OpenCPN displays a timestamp in the Debug Window, that is not part of the AIS message and, therefore, not a part of the raw data stream that can be captured. To remedy this, I wrote a small Perl program called timestamp_data that can connect to a TCP or UDP socket on a local or remote host, and read a data stream for a specified amount of time. Output is directed to a file complete with a human-readable and Unix epoch-formatted timestamp of when the data was received; fields in the file are delimited with a 'pipe' (|) character. Users can, optionally, also see the data in real-time. The program can be found on my software page.

SIDENOTE: Sending data to OpenCPN

If you have a file filled with AIS messages, it is also possible to send that data to OpenCPN for display. First, you need to set up OpenCPN to listen on a TCP port rather than send. Just create a new OpenCPN connection on the port of your choice to address 0.0.0.0, as shown above, but check the box to 'Receive input on this port.'

There are a variety of methods with which to send the data to OpenCPN at this point. You could just transmit the entire file via netcat:

Using the method above will work but all it does is dump the entire AIS message stream to OpenCPN at one time so you just see the last sentence transmitted by each vessel. If you want to slow things down a little, add a delay between the display of each line in the data file using some shell scripting:

Again, the method above works but it puts in a fixed delay. If you used a tool that attaches a timestamp to your data or you otherwise have a data file with a timestamp on each message (e.g., you got the data using the timestamp_data tool above), you can replay the data in OpenCPN in relative real-time using another one of my tools, play_ais. This program only needs a character-delimited file where each record has a timestamp (in seconds) and valid AIS sentence; a short video about using this approach can be found on my Web page (NOTE: The program was called replay at the time that I made the video).

Another tool that is quite useful for AIS research is the NMEASimulator, an easy-to-use NMEA sentence generator for messages related to position, speed, and heading, among other items. This software is an app that runs only on the Google Chrome browser.

To send information to OpenCPN, you need the IP address and listening port. Enter this information into the NMEA Simulator by clicking on Options, Settings and selecting the Server tab. Be sure to click the Save button.

Start up OpenCPN and then click Start in NMEA Simulator; simulated AIS data should now be displayed on OpenCPN.

Interpreting the Data

There are a variety of sources that will help you interpret the data that you are seeing; i.e., the raw NMEA sentences. The 'AIVDM' sentences that AIS devices typically see are the NMEA 0183 AIS incoming transmissions (as opposed to AIVDO outgoing transmissions). Possibly the best online, open-source reference as to the details of the NMEA sentence content is Eric Raymond's AIVDM/AIVDO protocol decoding page.

There are also a number of AIS parsers online, where you can submit an NMEA sentence for interpretation, as shown below (from the Maritec Solutions online parser):

There are other AIS online parsers with a variety of capabilities, including:

In addition, I have a set of AIS tools (written in Perl) available on my software page. Among other things is an AIS message parser:

If you are looking for real AIS data for research, testing, or curiosity, check out AISHub, an AIS data sharing and vessel tracking site. For data from the area of Daytona Beach/Ponce Inlet, Florida, check out http://ssia-ais.erau.edu/; for a live data feed, telnet or netcat to port 4000 at ssia-ais.erau.edu.

And, finally... if you are working with NMEA 2000 binary data, take a look at the CANboat project.

COPYRIGHT NOTICE

All information on this page © 2019-2020, Gary C. Kessler. Permission to use the material here is extended to any of this page's visitors, as long as appropriate attribution is provided and the information is not altered in any way without express written permission of the author.

I am still quite new to openSUSE, been using about a week now, and am really loving it. I had to install Citrix Receiver 13 for work, and found all the information I needed but it was dispersed throughout many areas. The installation on 64bit systems can be a bit tricky since Citrix is a 32bit based product, with minimal adaptation for 64bit. I would like to make the process easier for anyone else having issues with version 13 on openSUSE 13.1. Thought I would just create a concise consolidated howto that provided all the information in one place. Hopefully someone can find this helpful!
Install required 32-bit libraries via YaST
1.] In YaST make sure to install ALL of the following libraries. I used YaST for this to visually inspect everything before installing and, YaST will find all additional dependencies required.

Install Citrix Receiver Raspberry Pi 4 8gb

• List of 32-bit libraries to be installed is:

Via Terminal, install the RPM package
2] In Terminal: Install RPM via Zypper as Root:
Ignore the long list of warnings about missing dependencies: lib32asound2 and nspluginwrapper. The installation will work without these libraries, as they are brought in later.

• Select Option # 3

3.] Check there are no missing dependencies:
You should now see a long list of dependencies and their locations listed. This validates all dependecies are installed correctly.

• Uninstall the Citrix ICA Client: zypper remove icaclient
• Install the missing packages that were listed.
• Reinstall the Citrix ICA Client: zypper install ICAClient-13.0.0.256735-0.x86_64.rpm

File Associations
4.] If using KDE, edit the file association application/x-ica.

• Click Kicker start menu, search term 'Association' and open File Associations
• In File associations search 'x-ica' and click on this file type in left pane.
• Add a new application: /opt/Citrix/ICAClient/wfica.sh

5.] Check correct file association in FireFox (not needed for chrome)

• If you've had firefox open, close and restart it.
• Go to 'Menu>Preferences>Applications'
• Make sure Citrix ICA settings file is set to 'Use Citrix Receiver for Linux (in Firefox)'

This is all it took for me to get Citrix Client v13 up and running without a hitch. Some of the items I saw from other pages/post/etc appeared more apt to issues if the correct order was not followed during installation. I had no issues with making sure all basic dependencies were met prior to installing the RPM. I had same issues others had when I attempted installing on my workstation with Arch, so I learned a little from that experience as well.
Troubleshooting:
CA-Certificates errors: '/usr/share/ca-certificates/mozilla' is not available anymore. So a symbolic link to the ssl certificates directory is a workaround.

References:
Citrix System Requirements
Official Citrix Receiver 13.0 Installation Guide
openSUSE Forum post by rbarsoianu
eek, a Geek! Blog- Citrix Receiver 13 on openSUSE 13.1 - Install Guide
SuperUser.com - Citrix 13 Install Guide for Debian
Download 64bit Citrix Receiver for Linux RPM
www.citrix.com/downloads/citrix-receiver/linux/receiver-for-linux-130.html