|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: BDC-comm for 2CAN
Can you confirm that FIRST 2.29 firmware is loaded on the 2CAN?
The 2.29 crf is in the zip with the bdc_comm.exe on our website. 2CAN Firmware version is at the bottom of the webpage and also can be retrieved thru the firmware utility. That error can happen if BDC_Comm can't "find" the 2CAN or if it fails to load the DLLs it uses to find/connect to the 2CAN. Can you confirm that all the files in bdc-comm (CTR-2CAN supported) - 1_7_2013.zip are uncompressed together in the same directory. The directory should have a bdc_comm.exe, along with bdc-2can.dll and 2CAN_Comm.dll Since you can get to the webdash I'm thinking something else is stopping bdc_comm.exe from finding the 2CAN. Usually it's a firewall issue. Are you connecting an Ethernet cable directly between the laptop and 2CAN or going over wireless? It shouldn't matter but a direct cable connection might help narrow down the issue. |
|
#2
|
||||
|
||||
|
Re: BDC-comm for 2CAN
Yes. The firmware utility says that the connected 2CAN is on firmware 2.29.
The 2CAN is connected directly to the laptop with an ethernet patch cable. I will have to check on the DLL's and the folder. Now that you mention it, the BDC-Comm.exe file, rather than a shortcut, may have been on the desktop of both of the laptops we tried. I know that when it worked earlier, we were just running the program out of the unzipped folder it came in. I think one of our aspiring programmers was "optimizing" or "organizing" the laptops... -- Len |
|
#3
|
||||
|
||||
|
Re: BDC-comm for 2CAN
Thanks again Omar!
It was indeed the missing DLL files. Apparently the executables were copied to the desktop, and the remainder of the folder thrown away or stashed somewhere else. -- Len |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|