Differences

This shows you the differences between two versions of the page.

--- open_source:ccgx:start [2015-02-12 22:08] – Page moved from opensource:open_source:ccgx:start to open_source:ccgx:start mvader
+++ open_source:ccgx:start [2019-06-22 20:58] (current) – [Other tips] mvader
@@ Line 1: / Line 1: @@
-====== CCGX Introduction ======
+====== CCGX Hardware and software introduction ======
 ===== Hardware =====
-The CCGX is based on the Technexxion board TAM-3517, which is using the Texas Instruments Sitara AM3517 ARM processor:
+The CCGX is based on the Technexion board TAM-3517, which is using the Texas Instruments Sitara AM3517, containing a ARM Cortex-A8 microprocessor:
 {{ :opensource:ccgx:tam-3517.png?nolink |}}
 ===== Software =====
-==== Linux ====
+==== Linux kernel & OS ====
-CCGX image / distro is based on Poky.
+The software platform of the CCGX is called Venus: Victron Energy Unix like distro with a linux kernel. It is based on and built with OpenEmbedded, a build framework for embedded Linux. It has all kinds of tools, mechanisms and recipes to build the Linux kernel and make a full embedded Linux rootfs. Maintained versions are listed here: https://wiki.yoctoproject.org/wiki/Releases.
-Poky can be thought of as a reference distribution. It is maintained by an organisation called the Yocto Project and based on Open Embedded.
-Taken directly from the Yocto Project website (www.yoctoproject.org): “…The Yocto Project™ is an open source
-collaboration project that provides templates, tools and methods to help you create custom Linux-based
-systems for embedded products regardless of the hardware architecture". Some of their projects that are relevant
-to the CCGX are Poky and Bitbake.
-Open Embedded is a build environment for embedded linux, and has all kinds of tools, mechanisms and recipes to build the Linux kernel and make a full embedded Linux rootfs. Maintained version are listed here,
-https://wiki.yoctoproject.org/wiki/Releases.
-Angström, a well known linux distribution for embedded, is built using Open Embedded, and also related to Poky. Victron is not using Angström.
-For more introduction, refer to the websites of Poky and Open Embedded. And this blog is also interesting:
-http://blogs.mentor.com/chrishallinan/blog/2012/04/13/yocto-versus-poky-versus-angstrom-etc/
+To build the Venus yourself, see:
+https://github.com/victronenergy/venus
 ==== Victron software ====
@@ Line 41: / Line 27: @@
   * gps_dbus \\ also written in C. Open source: [[https://github.com/victronenergy/dbus_gps|https://github.com/victronenergy/dbus_gps]].
   * dbus_qwacs \\ C++, using the QT library. Reads data from wireless AC sensors connected via an Ethernet-DECT gateway. Open source: [[https://github.com/victronenergy/dbus_qwacs|https://github.com/victronenergy/dbus_qwacs]]
-  * dbus-fronius \\ writeen in C++, communications to Fronius PV inverters via LAN/Ethernet. Open source: [[https://github.com/victronenergy/dbus-fronius]]
+  * dbus-fronius \\ written in C++, communications to Fronius PV inverters via LAN/Ethernet. Open source: [[https://github.com/victronenergy/dbus-fronius]]
+  * dbus-motordrive \\ https://bitbucket.org/oceanvolt/dbus_motordrive
 === Other processes ===
@@ Line 48: / Line 35: @@
   * vrmlogger \\ Written in Python, takes data from the dbus and submits it to the VRM Portal. [[https://vrm.victronenergy.com/|https://vrm.victronenergy.com/]]
   * localsettings \\ Written in Python, takes care of user settings. All other processes read and write their settings through this daemon via D-Bus. The daemon is an interface between D-Bus and the file /data/conf/settings.xml. Open source: [[https://github.com/victronenergy/localsettings|https://github.com/victronenergy/localsettings]].
-  * dbus_modbustcp \\ Written in C++, uses QT. Modbustcp server that can be used to access data of all products connected to the CCGX. See our [[http://www.victronenergy.com/upload/documents/Whitepaper-Data-communication-with-Victron-Energy-products_EN.pdf|Data communication whitepaper]] for more information. Open source: [[https://github.com/victronenergy/dbus_modbustcp|https://github.com/victronenergy/dbus_modbustcp]]
+  * dbus_modbustcp \\ Written in C++, uses QT. Modbustcp server that can be used to access data of all products connected to the CCGX. See our [[https://www.victronenergy.com/upload/documents/Whitepaper-Data-communication-with-Victron-Energy-products_EN.pdf|Data communication whitepaper]] for more information. Open source: [[https://github.com/victronenergy/dbus_modbustcp|https://github.com/victronenergy/dbus_modbustcp]]
   * dbus-systemcalc-py \\ Written in Python, publish PV totals and other system readings on D-Bus. The overviews on the CCGX get their information from this service (com.victronenergy.system). Open source: [[https://github.com/victronenergy/dbus-systemcalc-py]]
@@ Line 54: / Line 41: @@
 As visible in above project list, part of the sources is already available. All that is open source is available on [[https://github.com/victronenergy/|https://github.com/victronenergy/]]. The rest is still on Victrons internal git servers, and where possible slowly being moved to github.
-==== Plans currently being worked on ====
-  * Have a local version of https://vrm.victronenergy.com including database run on the CCGX itself, using php/hiawatha and sqlite.
-  * Secure VNC (http://www.victronenergy.com/live/ccgx:ccgx_vnc), and make it useable remotely when the CCGX is behind a firewall.
-==== Future plans ====
-Functionality wise, the plans are (in random order):
-  * Make support for more types of sensors (temp sensors etc)
-  * Be able to use BMV's to read current from for example a dc wind generator, and show on overview and VRM portal
-  * Make more of the project open source
-  * Further mature alarms, and add SMS and email notifications
-  * Make it usable as a UPS-replacement. local website, emailalerts, battery minutes remaining, etc.
-  * Add SNMP (UPS-MIB)
-===== Connecting =====
-Connecting via SSH:
-You need to enable the remote support feature in the menu to turn the ssh server on. After logging in you can, in case you don't want the ccgx to build and maintain a reverse ssh tunnel into our support server, disable that service (service/ssh-tunnel)
-Connecting on the console:
-Console is connected to the VE.Direct 1 port on the back, 115k2 / 8N1. Note that a normal VE.Direct to USB interface cable won't work, since you need to power the VE.Direct port on the CCGX from the outside. A small mod can be made to the interface cable. Note that you need to enable the console functionality on the port, since normally it is taken by the VE.Direct process.
-TODO add how to do that.
 ===== Other tips =====
-  * to make a screenshot, first press and hold the down button, and then press the up button. The screenshot will be saved to /opt/color-control/gui/. It will overwrite the previous one.
+  * to make a screenshot, first press and hold the down button, and then press the up button. The screenshot will be saved with the name snapshot.png in /opt/color-control/gui/ or /service/gui. Making a new screenshot overwrites the previous one.
 ===== DISQUS =====
 ~~DISQUS~~