difference between debug and release

[franky71]

Hallo,

I'm in trouble with sending CAN-Message to servo-controllers (Lust).  In debug -mode all works fine, but in release it seem's that there some leaks in the message.

I've already added some delays between send-orders, but it doesn't help.

the CAN is a USB-adapter from PEAK.

1. Does CVI make some changes as I include the peak.dll (included in my project) from debug to release?

2. Is there some alternative of using the Delay-Command in windows?.

greetings

F.A.

[Andre_Saller]

When you switch from debug-mode to release mode, all additional code that is used for debugging is removed, so your application might get smaller and faster, anything else should perform in the same way as before. If your device you are controlling is very timing-sensitive it could be that the speed-difference causes these problems. You could use timer-controls our even better an asynchroneous timer (found in the toolslib) to gurantee stable timing.

[jr_2005]

Another difference is that local (automatic) variables within a function are initialised to 0 for the debug mode, whereas they remain uninitialised (and thus guaranteed to be garbage) for the release mode (unless you initialise them explicitly, obviously). Not that anyone would ignore the compilation warnings about using uninitialised variables, of course...

JR

[curosman]

Debug mode and Release mode are different configurations for building your .Net
project. Programmers generally use the Debug mode for debugging step by step
their .Net project and select the Release mode for the final build of Assembly
file (.dll or .exe). follow link for more information

http://net-informations.com/faq/net/debug-release.htm

cros.