PCCAN-USB + Evaluation

[Archie]

Hi

I have a bit of a problem with installation of the tools. An old project became relevant again when the customer wants a few modifications. Sadly the person with the knowledge is no longer working here and the instructions for setting up the environment lacks everything for the PCAN parts

We have a PCAN-USB hardware with a disc containing the Pcanviewer for USB and drivers ver. 2.42.2.0. That installs without any problem and I get feedback from the hardware we connect to the computer using the PCAN-USB module. No problems there.

We also have the PCAN Evaluation version 2.4 wich also installs without a hitch. I use the NetConfig to set up the required network for the project and the software we have written once upon a time in Visual C++ accepts the networks and uses it. No problem there either.

However... how to connect so that the VC++ software using the network to communicate with the hardware via the PCAN-USB hardware-module?

We have a old screenshot of the PCANViewer supplied with Evaluation talking witht he hardware using a NetConfig constructed network connected to USB, but we are at a loss as how to achive this connection? The Evaluation software simply ignores the USB-module when it is attached to the computer?

Any help with this is greatly appreciated!

We have tried installing Evaluation first and then the hardware and vice versa without success. There are no parameters in the software to install the USB-mdoule in the Evaluation packet either.

We are doing this on a Windows XP SP3 computer.

[PEAK-Support]

Dear,
first of all please be carefull to use the old 2.42 USB drivers. They will crash on new PCs with Intel iCore CPUs. Please take a look at an other Thread in this Forum
You also need to Update your PCAN-Evaluatiuon. For this please send (BY E-MAIL) your Developer or Evaluation License Number to support[at]peak-system.com (please do not post in this forum the Serno!)
To your basic question:
The PCAN-Evaluation or Developer use the CANAPI2.DLL to coummunicate with the driver by using internal CAN Net, This CAN net could be connected to a real CAN Hardware attached to the PC. When you write your own software with the CANAPI2.DLL it is possible to use a pre defined NET, using the NetCfg Tool, or generate a NET on runtime. The PCAN-View Monitoring Tool could connect to a predefined Net, but also coul generate his own Net at runtime. If PCAN-View and your Software do not use the same Net - only one of them can connect to the real Hardware. The other one is simply a internal Net without Hardware. The easy way to test it, is to start the PCANStat Tool first, and see how the differnet Applications connect to the Hardware:

PCAN-STat show PCAN-Explorer connected to virtual CAN Net and PCAN-View connected to real Hardware

PCAN-Stat-01.jpg (119.51 KiB) Viewed 13076 times

[Archie]

Thanks for the quick answer!

Yes, our software uses a predefined Net (done in NetConfig). Problem right now is that NetConfig dosen't see the USB hardware so the predefined nets can only be internal nets.



The PCANviewer supplied with Evolution can't see the USB hardware either, but the PCANview-USB can.



So question is, how can I get NetConfig too accept and use the USB-hardware? Could it be that this is impossible until I update the driver and the Evolution software due to the hardware in the new computer? Sounds a bit farfetched, but stranger things has happend before

In PCANstat I get two types of networks.



One is USB and when I use PCANview-USB to connect to the external card using a CAN-bus I see that network and the other type is call Peakcan and the strictly internal nets show up there with info on the predefined net that the software connects to.

For reference : the screendump mentioned previous that is the only documentation we have on how to use the PCAN in the project :/

[PEAK-Support]

First of all please use newer versions of the PCAN-View which do not care which Hardware is used.
PCAN-View
Then please open in the Controll Panel the PCAN2 cpl and set the PCAN-USB as aktive device!
But you use very old software releases - as i told please send serial number to our support for update.

[Archie]

Ah, that was the last detail that escaped us entirely. Now it all works

And we are updating since that is (almost) always a good idea


Thanks!

[PEAK-Support]

Problem solved -- Thread closed