[paparazzi-commits] [paparazzi/paparazzi] f818f3: [datalink] W5100 ethernet chip implementation

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/paparazzi/paparazzi
  Commit: f818f390132c4288c0154c371b76cf8272c41e3e
      
https://github.com/paparazzi/paparazzi/commit/f818f390132c4288c0154c371b76cf8272c41e3e
  Author: Gerard Toonstra <address@hidden>
  Date:   2012-11-07 (Wed, 07 Nov 2012)

  Changed paths:
    A conf/firmwares/subsystems/fixedwing/telemetry_w5100.makefile
    M sw/airborne/firmwares/fixedwing/main_ap.c
    M sw/airborne/subsystems/datalink/datalink.h
    M sw/airborne/subsystems/datalink/downlink.h
    A sw/airborne/subsystems/datalink/w5100.c
    A sw/airborne/subsystems/datalink/w5100.h
    A sw/ground_segment/python/udp_link/datalink_to_w5100.py
    A sw/ground_segment/python/udp_link/proxy_udp_multicast_to_link.py

  Log Message:
  -----------
  [datalink] W5100 ethernet chip implementation
Complete implementation for the W5100 ethernet chip, which allows telemetry to 
be sent over ethernet/wifi, replacing the xbee.
It also reads command packets. Hooking this up to the ground station requires 
one to run 2 UDP scripts,
which proxy the data from the ethernet connection to the paparazzi UDP ports 
that are open,
reusing earlier work done on UDP links through an overo I think?

See below for possible configuration details.

It is recommended to use the WIZ811MJ breakout board of sparkfun,
as others have issues with the SPI_EN gate not connected through an inverter,
leaving the chip activate during other comms on the same IP bus (if this 
appies).

Connect the chip on the external SPI1.
You can configure the multicast ip, port and (fixed) ip in the airframe file:

<subsystem name="telemetry" type="w5100">
  <configure name="W5100_IP" value="192,168,2,2"/>
  <configure name="W5100_SUBNET" value="255,255,255,0"/>
  <configure name="W5100_MULTICAST_IP" value="1,1,1,1"/>
  <configure name="W5100_MULTICAST_PORT" value="5432"/>
</subsystem>
The ground segment includes two additional python scripts, which work as 
proxies on the local machine.

I'm still looking for a solution on the while loop in the get/set functions.
The chip unfortunately cannot send multiple bytes in one transaction,
so one byte of telemetry actually costs 4 bytes on the SPI bus,
plus more to query read/write pointers and perform the actual sending.

Throughput on SPI is about 0.3Mb/s maximum.
I did not change the telemetry file, but it should be possible to increase the 
frequency of certain messages there.
I don't feel the need to do that however and it may slow down other loops.

closes #318


  Commit: 5b50ae58b9c27f1d7e5fe869613862f2d0d33f59
      
https://github.com/paparazzi/paparazzi/commit/5b50ae58b9c27f1d7e5fe869613862f2d0d33f59
  Author: Felix Ruess <address@hidden>
  Date:   2012-11-07 (Wed, 07 Nov 2012)

  Changed paths:
    M sw/airborne/mcu_periph/spi.h
    M sw/airborne/subsystems/datalink/w5100.c

  Log Message:
  -----------
  cleanup trailing whitespaces


Compare: 
https://github.com/paparazzi/paparazzi/compare/80a1e1445d83...5b50ae58b9c2