Differences

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

--- gecko-systems:gecko3com:start [2017/03/06 12:20] – external edit 127.0.0.1
+++ gecko-systems:gecko3com:start [2021/12/20 10:49] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== GECKO3COM ======
 GECKO3COM defines the communication between the GECKO3main and a USB Master e.g. a computer.
-{{:huce:microlab:projects:internal:gecko:gecko3com.jpg?300|}}
+{{:gecko-systems:gecko3com:gecko3com.jpg?300|}}
 The USB master communicates over the EZ-USB with the FPGA or the flash.
@@ Line 9: / Line 9: @@
 GECKO3COM uses a USB standard class, USBTMC, this makes is easy to send and receive data from the FPGA to Matlab or Labview!
-<note tip>FIXME Tutorial: [[:tutorials:gecko3com_simple_tutorial]]</note>
+<note tip>FIXME Tutorial: [[tutorial:]]</note>
-Firmware EEPROM file: {{:huce:microlab:projects:internal:gecko:gecko3:gecko3com:gecko3com_1.0.zip|}}
+Firmware EEPROM file: {{:gecko-systems:gecko3com:gecko3com_1.0.zip|}}
 ===== Aim ====
@@ Line 31: / Line 31: @@
 On Linux you can use the VISA API or normal file I/O (//echo//, //cat// in a shell or //fopen()//, //fprintf()// in C) with the USB-TMC driver.\\
-{{:huce:microlab:projects:internal:gecko:gecko3:gecko3com:tmcoverusb.png?600|Overview over the different software, driver and OS combinations to access GECKO3COM}}
+{{:gecko-systems:gecko3com:tmcoverusb.png?600|Overview over the different software, driver and OS combinations to access GECKO3COM}}
 ==== Driver installation ====
 Read the installation manual for your operating system:
-  * [[huce:microlab:projects:internal:gecko:gecko-system:gecko3com:installing_linux]]
+  * [[gecko-systems:gecko3com:installing_linux]]
-  * [[huce:microlab:projects:internal:gecko:gecko-system:gecko3com:installing_windows]]
+  * [[gecko-systems:gecko3com:installing_windows]]
-  * [[huce:microlab:projects:internal:gecko:gecko-system:gecko3com:installing_osx]]
+  * [[gecko-systems:gecko3com:installing_osx]]
 ==== Protocols ====
-{{:systems:gecko3com:scpi.png|}}
-All commands understood by the GECKO3COM are listed in the [[:systems:gecko3com:command_reference]]
+All commands understood by the GECKO3COM are listed in the [[gecko-systems:gecko3com:command_reference]]
 === SCPI ===
-The //Standard Commands for Programmable Instruments// defines a standard set of commands to control programmable test and measurement devices. The physical communication link is **not** defined by SCPI. In our case this is [[systems:gecko3com:start#usbtmc|USBTMC]]. SCPI commands are ASCII textual strings as defined by IEEE488. {{:huce:microlab:projects:internal:gecko:gecko3:gecko3com:scpi-99.pdf|SCPI 99 Standard}}
+The //Standard Commands for Programmable Instruments// defines a standard set of commands to control programmable test and measurement devices. The physical communication link is **not** defined by SCPI. In our case this is [[gecko-systems:gecko3com:start#usbtmc|USBTMC]]. SCPI commands are ASCII textual strings as defined by IEEE488. {{:gecko-systems:gecko3com:scpi-99.pdf|SCPI 99 Standard}}
 === IEEE 488 ===
-This standard was defined for communicating with devices and is also known as GPIB or HP-IB. This original standard defines the protocol, the physical layer as well the connector. In the GECKO3COM system we use [[systems:gecko3com:start#usbtmc|USBTMC]] instead of the GPIB physical layer, other modern interfaces are LXI (Ethernet) and PXI (PCI). The higher level protocol definition of IEEE 488 is used on these interfaces, this includes structure of a message, number and unit representation error handling and other essentials.
+This standard was defined for communicating with devices and is also known as GPIB or HP-IB. This original standard defines the protocol, the physical layer as well the connector. In the GECKO3COM system we use [[gecko-systems:gecko3com:start#usbtmc|USBTMC]] instead of the GPIB physical layer, other modern interfaces are LXI (Ethernet) and PXI (PCI). The higher level protocol definition of IEEE 488 is used on these interfaces, this includes structure of a message, number and unit representation error handling and other essentials.
 [[http://standards.ieee.org/reading/ieee/std_public/description/im/488.2-1992_desc.html|IEEE-488.2: Standard Codes, Formats, Protocols, and Common Commands for Use With IEEE-488.1]]
@@ Line 65: / Line 64: @@
 The GECKO3main module contains a EZ-USB processor to control the USB traffic. The EZ-USB acts as a command splitter.\\
-After the start up of a GECKO3main, the system is by default in the state where it listens on the USB port for TMC (see [[systems:gecko3com:start#usbtmc|USBTMC]]) or [[systems:gecko3com:start#firmware_update|DFU]] commands. The EZ-USB interprets and executes the commands. Since the FPGA is in this case empty no commands or data are forwarded from the USB to the FPGA.
+After the start up of a GECKO3main, the system is by default in the state where it listens on the USB port for TMC (see [[gecko-systems:gecko3com:start#usbtmc|USBTMC]]) or [[gecko-systems:gecko3com:start#firmware_update|DFU]] commands. The EZ-USB interprets and executes the commands. Since the FPGA is in this case empty no commands or data are forwarded from the USB to the FPGA.
-{{:huce:microlab:projects:internal:gecko:gecko3:gecko3com:beforecontentswitch.png|Before context switching. All commands are routed to the EZ-USB}}\\
+{{:gecko-systems:gecko3com:beforecontentswitch.png|Before context switching. All commands are routed to the EZ-USB}}\\
 **Before context switching:** All commands are routed to the EZ-USB
@@ Line 73: / Line 72: @@
 The FPGA should be programmed at this time to be able to interpret IEE488 commands.
-{{:huce:microlab:projects:internal:gecko:gecko3:gecko3com:aftercontentswitch2.png|After context switching. All commands are routed to the FPGA}}\\
+{{:gecko-systems:gecko3com:aftercontentswitch2.png|After context switching. All commands are routed to the FPGA}}\\
 **After context switching:** All commands are routed to the FPGA