| 3 | | =='''Notes for v6.2''' ''Posted August 2012''== |
| 4 | | * Added support for [http://www.mangocomm.com/products/kits/warp-v3-kit WARP v3]. In this release, the source models and software for WARPLab are different for WARP v3 than the v1 and v2 hardware. In a future release, these will merge back together to a common code base. |
| 5 | | * Added a new WARPLab command to verify network settings from within Matlab. If it even seems like WARPLab isn't working, simply run warplab_networkCheck(N) from the Matlab command line (where N is the number of nodes in your setup). This will run a series of diagnoses to help figure out what the problem is. |
| 6 | | * We introduced a bug in the prior 6.1 release that made the processing of sync packets jittery. This has been fixed in this release. |
| 7 | | * '''Notes for v6.1''' ''Posted July 2012'' |
| 8 | | * Small, but important, bug fix. MAC addresses for each node were not updated based on dip switch value. This made any setup larger than 1 node fail due to arp table collisions. This has been resolved. v6.0 is deprecated and should not be used |
| 9 | | * '''Notes for v6.0''' ''Posted July 2012'' |
| 10 | | * Design defaults to using gigabit Ethernet on WARP v2 Hardware (Virtex-4) |
| 11 | | * Improved packet handling on WARP v2 for fewer packet drops |
| 12 | | * Sync packets now sent as proper broadcast IP frames (X.X.X.255). Manual ARP table entries for sync packets no longer necessary. |
| 13 | | * Small change to M-code reference to reduce likelihood of "failed to receive ACK" error. |
| 14 | | * Thanks to a modified pnet for Matlab's UDP handling, WARPLab is sped by ~10x |
| 15 | | * '''Notes for v5.2''' ''Posted December 2009'' |
| 16 | | * Can store RSSI data in the 4x4 design |
| 17 | | * Consolidated the Sysgen models. Now there is one Sysgen model, {{{warplab_mimo_4x4.mdl}}}, that implements the full system: 4 radios with I/Q and RSSI buffers. The 2x2 MIMO and 4x4 MIMO [wiki:WARPLab/RefDesign Reference Designs] are identical except the 2x2 Design leaves two paths of the model unconnected. |
| 18 | | * Minor update: Added the Null MGT wrapper core to the project (see note at the end of the [wiki:HardwareUsersGuides/FPGABoard_v2.2/MGTs FPGA Board user guide]) |
| 19 | | * '''Notes for v5.1''' ''Posted November 2009'' |
| 20 | | * Builds upon the features of Version 5 |
| 21 | | * Support for both Version 1 and 2 of the FPGA Board |
| 22 | | * Single C-code base for both the 2x2 and 4x4 Reference Designs |
| 23 | | * Interoperable across both versions of the FPGA Boards |
| 24 | | * '''Notes for v5.0''' ''Posted September 2009'' |
| 25 | | * Includes Automatic Gain Control (AGC). Previous versions of WARPLab required Manual Gain Control (MGC), the user was required to set receiver gains manually. Now AGC or MGC can be selected by M-code functions. |
| 26 | | * RSSI data read is supported by the 2x2 MIMO bitstream but not by the 4x4 MIMO bitstream |
| 27 | | * Continuous transmission mode is supported by both the 2x2 and 4x4 bitstreams |
| | 3 | == Bitstreams == |
| | 4 | |
| | 5 | == Reference Design== |
| | 11 | |
| | 12 | = WARPLab Revision History = |
| | 13 | |
| | 14 | == '''Notes for v6.2''' ''Posted August 2012'' == |
| | 15 | * Added support for [http://www.mangocomm.com/products/kits/warp-v3-kit WARP v3]. In this release, the source models and software for WARPLab are different for WARP v3 than the v1 and v2 hardware. In a future release, these will merge back together to a common code base. |
| | 16 | * Added a new WARPLab command to verify network settings from within Matlab. If it even seems like WARPLab isn't working, simply run warplab_networkCheck(N) from the Matlab command line (where N is the number of nodes in your setup). This will run a series of diagnoses to help figure out what the problem is. |
| | 17 | * We introduced a bug in the prior 6.1 release that made the processing of sync packets jittery. This has been fixed in this release. |
| | 18 | |
| | 19 | == '''Notes for v6.1''' ''Posted July 2012'' == |
| | 20 | * Small, but important, bug fix. MAC addresses for each node were not updated based on dip switch value. This made any setup larger than 1 node fail due to arp table collisions. This has been resolved. v6.0 is deprecated and should not be used |
| | 21 | * '''Notes for v6.0''' ''Posted July 2012'' |
| | 22 | * Design defaults to using gigabit Ethernet on WARP v2 Hardware (Virtex-4) |
| | 23 | * Improved packet handling on WARP v2 for fewer packet drops |
| | 24 | * Sync packets now sent as proper broadcast IP frames (X.X.X.255). Manual ARP table entries for sync packets no longer necessary. |
| | 25 | * Small change to M-code reference to reduce likelihood of "failed to receive ACK" error. |
| | 26 | * Thanks to a modified pnet for Matlab's UDP handling, WARPLab is sped by ~10x |
| | 27 | == '''Notes for v5.2''' ''Posted December 2009'' == |
| | 28 | * Can store RSSI data in the 4x4 design |
| | 29 | * Consolidated the Sysgen models. Now there is one Sysgen model, {{{warplab_mimo_4x4.mdl}}}, that implements the full system: 4 radios with I/Q and RSSI buffers. The 2x2 MIMO and 4x4 MIMO [wiki:WARPLab/RefDesign Reference Designs] are identical except the 2x2 Design leaves two paths of the model unconnected. |
| | 30 | * Minor update: Added the Null MGT wrapper core to the project (see note at the end of the [wiki:HardwareUsersGuides/FPGABoard_v2.2/MGTs FPGA Board user guide]) |
| | 31 | == '''Notes for v5.1''' ''Posted November 2009'' == |
| | 32 | * Builds upon the features of Version 5 |
| | 33 | * Support for both Version 1 and 2 of the FPGA Board |
| | 34 | * Single C-code base for both the 2x2 and 4x4 Reference Designs |
| | 35 | * Interoperable across both versions of the FPGA Boards |
| | 36 | == '''Notes for v5.0''' ''Posted September 2009'' == |
| | 37 | * Includes Automatic Gain Control (AGC). Previous versions of WARPLab required Manual Gain Control (MGC), the user was required to set receiver gains manually. Now AGC or MGC can be selected by M-code functions. |
| | 38 | * RSSI data read is supported by the 2x2 MIMO bitstream but not by the 4x4 MIMO bitstream |
| | 39 | * Continuous transmission mode is supported by both the 2x2 and 4x4 bitstreams |
