This page contains answers to common questions handled by our support staff, along with some tips and tricks that we have found useful and presented here as questions.

• Why is the IFM failing to open the network interface?
• Why is my program getting random crashes in dbgheap while using Peak Components?
• Why doesn't the sample application run to completion?
• Which network interfaces work with Peak?

Why is the IFM failing to open the network interface?

We have run Peak Components™ on both WinNT 4.0 and Win95 operating systems using PCLTAs, PCLTA-10s, PCC-10s, and PCNSIs. Your problem may be that your network interface is configured as an NSI. Use your Echelon® Tools to convert the network interface to a standard LonTalk® network interface.

• Under Win95:
  The best test is if nodeutil can open the network interface, the Peak Components IFM should be able to also.
  
  
• Under WinNT:
  If you can successfully run the diagnostics program using the LONWORKS® NI application under the Control Panel, the Peak IFM should work properly as well. If you want to test using nodeutil, you will need 16-bit access to the driver. For the PCLTA, this requires the following line of code in your config.nt: device=%SystemRoot%system32\pcltados.sys. See the documentation for your card for details.

Back to Top

Why is my program getting random crashes in dbgheap while using Peak Components?

Peak Components was built using the (debug) multithreaded DLL option under Visual Studio. You must use this option also.

Back to Top

Why doesn't the sample application run to completion?

When the sample application returns an error code, the code is logged and the application closes down. The sample application includes Neuron® IDs and Network Variable names for nodes in our lab. You must change the Neuron IDs and Network Variable names to match your hardware and recompile the application. If you look at the PkCliDemo.log you will notice which error code was returned. Error codes are listed in the documentation as well as the help file. Your real application should handle these error codes and prompt the user to take some corrective action.

Back to Top

Which network interfaces work with Peak?

Devices supported under WinNT 4.0:

• Easylon PC Interface
• Easylon PC Interface (PCI)
• Echelon 32-bit drivers (PCLTA, PC-NSS, et. al.)

Note: the 16-bit interface (WLDV) is supported under WinNT too, but we advise against using it, since 32-bit drivers for the devices are usually available and offer a performance advantage compared to 16-bit drivers.

Devices supported under Windows® 95/98:

• Device Easylon PC Interface
• Echelon 32-bit driver (PCLTA-10, PCC-10, et. Al.)
• Echelon 16-bit driver (PCLTA, PC-NSS, et. Al.)