This is an old revision of the document!
Zbrain SDK Z4 revision history
4.2.0
release date: soon
release type: cumulative, tested
LabVIEW Version: 2013 (LabVIEW 2011: target only update for bug fixes without new features)
changes:
4.1.4
release date: 27.03.2014
release type: cumulative, tested
LabVIEW Version: 2011 and 2013
changes:
Horizontal text alignment (left, right and center) added. For existing code, the VI ZB.lcd.drawtext.vi must be redropped from the palette.
Touch close VI added.
UART enable handshaking signals (RTS CTS) vi added to advanced palette.
ZB.ethernet.tcp.connection.state.vi added. This VI is used to check if a connection is ready for sending or has received data.
New timeout control added to Mass Storage Device VI. For existing code, the VI must be redropped from the palette. The functionality of the VI is the same as before if nothing is wired to the timeout control.
The dataref functionality has been reworked. Some bugs have been fixed. A new VI ZB.adc.dataref.info.vi has been added. A example that shows how to use the VIs is in work.
Not all released events have been reported on capacitive displays.
New VI ZB.adc.overflow.vi has been added. This VI is used to check if the buffer has run full and data might be lost.
4.1.3
release date: 11.09.2013
release type: cumulative, tested
LabVIEW Version: 2011
changes:
New CAN functions added. (This feature is in beta phase, partly functional and not systematically tested)
solution to
issue 4000013: DINB-CH0 and DINB-CH1 on ZMC not usable.
-
solution to
issue 4000015: NAND flash Mass Storage read access data corruption
Caching was not fully disabled for debuggable applications when caching was enabled for optimized applications.
Minor changes to vi lib and toolchain.
4.1.2
release date: 20.06.2013
release type: cumulative, tested
LabVIEW Version: 2011
changes:
solution to
issue 4000010: ZB.files.ref.open.vi file status was not returned in FDM.
solution to
issue 4000011: unknown file error / Invalid path specified for file/directory
solution to
issue 4000012: Application can crash after executing ZB.etehrnet.ipaddress.vi
Faster compilation times on small source code changes by incrementally building the C project.
Minor not functional changes in VIs and Toolchain.
Timeout in cap touch driver. Position updates faster than 40ms will be ignored.
4.1.1
release date: 08.05.2013
release type: cumulative, tested
LabVIEW Version: 2011
changes:
-
The VI ZB.files.msd.vi has a new input “display refnum”
solution to
issue 4000000E:
“Cache settings had no effect”
The data and instruction cache settings in the project tab had no affect on the built executable.
Cache can be enabled to gain up to 5x speed in optimized applications.
Cache is disabled in debuggable applications.
The DOUT open generic (ZB.open.dout.vi) has an additional boolean control to set the output active or inactive when opened. This prevents the outputs from producing a possibly disruptive pulse when first opening and setting later. This input is in Z3 since update Firenze SP2.
The Ethernet open has a new input “timeout”. The vi exits with a error if the timeout elapsed before a ethernet connection could be established. A boolean output indicates if a timeout occurred.
The VI can still hang for some minutes, when DHCP is selected, but no DHCP server can be reached.
The VI ZB.ethernet.ipaddress.vi returned a random string when IP address was improper configured.
The VI ZB-lcd.drawtext.vi could cause the target to hang up, when a area bigger than the screen was chosen on full VGA displays.
Support for
capacitive multi touch displays on Z48-C1 target. Read more in the
displays article.
solution to
issue 400000F: “ADC DMA driver for the ADAD7656 chip (ZMC) did not work in all applications”.
The Ethernet configuration cluster has not been typedefed
The parameter device did not recognize loaded tables as valid.
4.1.0
release date : 28.03.2013
LabVIEW Version: 2011
This is the first official release.
Changes to previous beta versions (4.0.4 .. 4.0.11) and to the Zbrain SDK Z3 for LabVIEW 9.0 are not listed here
1),
1),
1),
1),
1)
This is the build date as displayed in the SDK. Due to tests that run on every target and for organizational reasons the actual release date will differ from this date.
2),
2),
2),
2),
2)
This can be installed on any previous installation from 4.1.0 on
3),
3),
3),
3),
3)
This release might be wrongly marked as beta in the SDK (up to 4.1.1). It is a tested release.