Thu, 13 Oct 2011 17:51:27 +0200Configuration manager with DCF in object 0x1F22 rewritten almost from scratch.
Mongo [Thu, 13 Oct 2011 17:51:27 +0200] rev 669
Configuration manager with DCF in object 0x1F22 rewritten almost from scratch.
1. The boot-up message from a device starts a verification of entries
2. If all entries matches the node is started
3. If an entry differs the whole dcf is written and a save is done
4. A reset is send to the node
5. If several boot-up are received at the same time they will be managed one
by one thus only one free sdo client is needed for the whole process.

Mon, 12 Sep 2011 10:52:02 +0200Added some fixes from Jaroslav Fojtik submitted on sourceforge bug tracker:
Mongo [Mon, 12 Sep 2011 10:52:02 +0200] rev 668
Added some fixes from Jaroslav Fojtik submitted on sourceforge bug tracker:
3096348 Missing "break" in states.c/canDispatch()
3096359 Crash inside dcf.c/send_consise_dcf()
3101891 Potencial overflow inside getNodeState()

Tue, 30 Aug 2011 12:14:34 +0200Added include stdlib.h for malloc functions in sdo.c
fbeaulier [Tue, 30 Aug 2011 12:14:34 +0200] rev 667
Added include stdlib.h for malloc functions in sdo.c

Mon, 29 Aug 2011 17:44:49 +0200patch from Stefan Kratochwil <entwicklung@inovel.de> : canfestival-3-fm3_698.patch
fbeaulier [Mon, 29 Aug 2011 17:44:49 +0200] rev 666
patch from Stefan Kratochwil <entwicklung@inovel.de> : canfestival-3-fm3_698.patch
Bug:
If an object dictionary entry was requested whose size exceeds
SDO_MAX_LENGTH_TRANSFERT, the memcpy() call at line 139 of objacces.c overwrites
the memory after *pDestData which causes stack corruption.
-> Bugfix:
The bug was corrected by size checking the requested data. An 'Out of
memory' error message will be generated if the requested data exceeds
SDO_MAX_LENGTH_TRANSFERT.

Additional changes:
Added dynamic buffer allocation for the SDO transfer. This feature can be used
if SDO_DYNAMIC_BUFFER_ALLOCATION is defined in config.h. The size of the
dynamically allocated buffer is controlled with
SDO_DYNAMIC_BUFFER_ALLOCATION_SIZE.
-> Note:
This change removes the detection of OD_LENGTH_DATA_INVALID errors!

Mon, 29 Aug 2011 17:31:55 +0200patch from Christian Taedcke <hacking@taedcke.com> : fix-wrong-resetSDOline-for-sdo-timeout.patch
fbeaulier [Mon, 29 Aug 2011 17:31:55 +0200] rev 665
patch from Christian Taedcke <hacking@taedcke.com> : fix-wrong-resetSDOline-for-sdo-timeout.patch
FIXED: - The sdo line must not be closed at the end of SDOTimeoutAlarm() if the same sdo line is closed and reopened for a new transfer inside the callback. (Patch from Jaroslav Fojtik)

Mon, 29 Aug 2011 16:59:55 +0200CHANGE: SDO block mode added, without CRC support
fbeaulier [Mon, 29 Aug 2011 16:59:55 +0200] rev 664
CHANGE: SDO block mode added, without CRC support
WARNING : API change in client functions

Tue, 16 Aug 2011 14:15:52 +0200timers_unix.c : remove sigint and sigterm catch
fbeaulier [Tue, 16 Aug 2011 14:15:52 +0200] rev 663
timers_unix.c : remove sigint and sigterm catch
sdo : Allow multiple servers
The sdo transfer struct is not anymore referenced by server's node id but by
client or server number in the OD. Node id is not relevant in SDO transfert.