Help! Function ECI111_GetInfo not working with CAN-IB200/PCIe v1.6 on Intime4.2


#1

The function ECI111_GetInfo() is not working with CAN-IB200/PCIe v1.6 on Intime4.2, I get an error 0xE0FE000D.

My software and the demo fails in ECI111_GetInfo with the new v1.6 IB200/PCIe board. When I run the demo (ldrta.exe INtimeEciDemo.rta) I get:

ECI Demo for CAN-IB2x0 / PCIe (104) <<
ECI111_Initialize…succeeded.
ECI111_GetInfo…failed with error code: 0xE0FE000D. The available resources are insufficient to perform this request.
-> Returning from ECI Demo for CAN-IB2x0 / PCIe (104) <-
-> Closing INtime ECI API Demo program <-

A board I have that is labeled CAN-IB200/PCIe v1.4 works fine. I think the hardware is newer than the software. We really need this to work. Any ideas?

The demo is from:
https://www.ixxat.com/support/file-and-documents-download/file-and-document-overview?indexCatalogue=ixxat-downloads&searchQuery=intime&wordsMode=0

I tried INTime5.2 too, but received:
ECI111_GetInfo…failed with error code: 0xE0FE000D. The available resources are insufficient to perform this request.


#2

We have escalated this case and are waiting for a response from the IXXAT team.


#4

Hi I am still awaiting a response. Can somebody please try it themselves?

I created a case 201909-8576. Deryck Beliveau suggested I try a later version of INtime since he saw somebody else used a 5, 6.2 versions of INtime with success. I tried 5.2, 6.3 but still get an error. BTW, is there a way to add a comment to a case in https://mysupport.hms.se without creating a new case? Pushing the “Create Comment” button created another case for me.


#5

Hello Mark,
My suggestion was to use a newer verison of the ECI drivers running on the PC. My though is that the newer version of the card needs the newer drivers. What version of the ECI drivers are you running?

We have them hosted on the Ixxat site here: https://www.ixxat.com/support/file-and-documents-download/drivers/eci-driver

and my colleague also provided a newer version for windows here:

You can download the files by visiting the following link:
https://fileshare.hms.se?container=H69w72g6hZ6gs9nf2L58Rg3hc56b2B63VL9jD4sH9Ks9F

The file share will expire on 2019-10-05 09:47


#6

The files on fileshare.hms.se has a newer INtime 6.3 release. I ran the demo, it looks like it is working!

I hope you can patch the 4.2 version too, otherwise we have to ask customers to uninstall and re-install newer INtime versions on their PCs, which can be scary.


#7

Great! Thanks for letting us know - I’ll pass that on to the developers.


#8

Hi Mark,

Can you provide more info about the resources the IB card is using? You can find this info in device manager in the properties menu for the card.
ibcard_resources

Deryck


#9

Here is what mine says:


#10

#11

Thank you, I have forwarded this to my colleagues. Hopefully this will help resolve the issue with the 4.2 version.

Deryck


#12

Can they send me something to try?


#13

Hello Mark,

The developers are looking into the issue but I don’t have any additional info yet.

Deryck


#14

Hi Deryck,

Can you ask them if they can reproduce the problem?


#15

Hello Mark,

We have created an updated version of the ECI version for 4.2. Unfortunately we do not have a way to test this update ourselves. Please give the driver a test and let me know if you run into any issues. Due to the size of the file I am unable to upload it here, you should have received an email from our file share server with a download link.

The this version was adapted to include the recent changes in the ECI driver with the exception of the features not included in INTime 4.2.

Deryck


#16

Thanks for your efforts.

When I run it now, it gets further, but still errors. I tried with and without polling.

ECI Demo for CAN-IB2x0 / PCIe (104) <<

ECI111_Initialize…succeeded.

…\EciDemo111.c:126

ECI111_GetInfo…failed with error code: 0xE0FE0017. ECI is in wrong state to perform this request.

…\EciDemo111.c:132

-> Returning from ECI Demo for CAN-IB2x0 / PCIe (104) <-

-> Closing INtime ECI API Demo program <-


#17

Hi Mark,

Thank you for testing the drivers. I am following up with my team to see if we can update the driver further.

Deryck


#18

Hi Mark,

The developers are asking if you could use the logging function of the ECI. I am waiting on some more instructions on how to use this but my colleague is saying with INtime you should be able to output to the console. It looks like ECI_logging.h would need to be included.

If you are not sure how to do this I should be following up shortly with better instructions.

Deryck


#19

Hi Mark,

The following zip has a modified version of the ECI demo with the logger functions enabled. Can you run this and provide us with the logs.
INtime_IB200_demo_with_EciLogger.zip (5.4 KB)

There are 3 additonal functions:
void StartLogging(); -> start the logging mechanism
void ShowLogging(); -> show the data logging till now
void StopLogging(); -> stop the logging complete

Deryck


#20

Thanks Deryck, this was the output:

INtime ECI API Demo program <<

ECI Demo for PC-I 04 / PCI <<

ECI002_Initialize…succeeded.

ECI002_GetInfo…failed with error code: 0xE0FE000E. The device or resource could not be found.

-> Returning from ECI Demo for PC-I 04 / PCI <-

ECI Demo for CAN-IB1x0 / PCIe (Mini), (104) <<

ECI005_Initialize…succeeded.

ECI005_GetInfo…failed with error code: 0xE0FE000E. The device or resource could not be found.

-> Returning from ECI Demo for CAN-IB1x0 / PCIe (Mini), (104) <-

ECI Demo for iPC-I 320 / PCI <<

ECI101_Initialize…succeeded.

ECI101_GetInfo…failed with error code: 0xE0FE000E. The device or resource could not be found.

-> Returning from ECI Demo for iPC-I 320 / PCI <-

ECI Demo for iPC-I XC16 / PCI (PMC) <<

ECI105_Initialize…succeeded.

ECI105_GetInfo…failed with error code: 0xE0FE000E. The device or resource could not be found.

-> Returning from ECI Demo for iPC-I XC16 / PCI (PMC) <-

ECI Demo for CAN-IB2x0 / PCIe (104) <<

Result of ECI111_LogConfig: unknown error code, ECIDRV_GetErrorString() not initialized

Result of ECIDRV_LogStart: unknown error code, ECIDRV_GetErrorString() not initialized

ECI111_Initialize…succeeded.

ECI111_GetInfo…failed with error code: 0x00000006. unknown error code or error message not found

Result of ECI111_LogRead: Operation finished successfully.

LOG entry 0 Enter: ECIDRV_GetErrorString(dwError = 0x00000000)

LOG entry 1 Leave: ECIDRV_GetErrorString() => szErrString = “unknown error code, ECIDRV_GetErrorString() not initialized”

LOG entry 2 Enter: ECIDRV_Initialize(dwCount = 4, astcHwPara = 0x0040C58C)

LOG entry 3 Enter: ECIDRV_Release()

LOG entry 4 Enter: DriverDestroy(dwBoardIndex = 0)

LOG entry 5 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 6 Enter: DriverDestroy(dwBoardIndex = 1)

LOG entry 7 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 8 Enter: DriverDestroy(dwBoardIndex = 2)

LOG entry 9 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 10 Enter: DriverDestroy(dwBoardIndex = 3)

LOG entry 11 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 12 Enter: DriverDestroy(dwBoardIndex = 4)

LOG entry 13 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 14 Enter: DriverDestroy(dwBoardIndex = 5)

LOG entry 15 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 16 Enter: DriverDestroy(dwBoardIndex = 6)

LOG entry 17 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 18 Enter: DriverDestroy(dwBoardIndex = 7)

LOG entry 19 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 20 Enter: DriverDestroy(dwBoardIndex = 8)

LOG entry 21 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 22 Enter: DriverDestroy(dwBoardIndex = 9)

LOG entry 23 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 24 Enter: DriverDestroy(dwBoardIndex = 10)

LOG entry 25 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 26 Enter: DriverDestroy(dwBoardIndex = 11)

LOG entry 27 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 28 Enter: DriverDestroy(dwBoardIndex = 12)

LOG entry 29 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 30 Enter: DriverDestroy(dwBoardIndex = 13)

LOG entry 31 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 32 Enter: DriverDestroy(dwBoardIndex = 14)

LOG entry 33 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 34 Enter: DriverDestroy(dwBoardIndex = 15)

LOG entry 35 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 36 Enter: DriverDestroy(dwBoardIndex = 16)

LOG entry 37 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 38 Enter: DriverDestroy(dwBoardIndex = 17)

LOG entry 39 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 40 Enter: DriverDestroy(dwBoardIndex = 18)

LOG entry 41 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 42 Enter: DriverDestroy(dwBoardIndex = 19)

LOG entry 43 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 44 Enter: DriverDestroy(dwBoardIndex = 20)

LOG entry 45 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 46 Enter: DriverDestroy(dwBoardIndex = 21)

LOG entry 47 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 48 Enter: DriverDestroy(dwBoardIndex = 22)

LOG entry 49 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 50 Enter: DriverDestroy(dwBoardIndex = 23)

LOG entry 51 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 52 Enter: DriverDestroy(dwBoardIndex = 24)

LOG entry 53 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 54 Enter: DriverDestroy(dwBoardIndex = 25)

LOG entry 55 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 56 Enter: DriverDestroy(dwBoardIndex = 26)

LOG entry 57 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 58 Enter: DriverDestroy(dwBoardIndex = 27)

LOG entry 59 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 60 Enter: DriverDestroy(dwBoardIndex = 28)

LOG entry 61 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 62 Enter: DriverDestroy(dwBoardIndex = 29)

LOG entry 63 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 64 Enter: DriverDestroy(dwBoardIndex = 30)

LOG entry 65 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 66 Enter: DriverDestroy(dwBoardIndex = 31)

LOG entry 67 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 68 Leave: ECIDRV_Release() => hResult = 0x00000000

LOG entry 69 Enter: ErrorListInit_US()

LOG entry 70 Leave: ErrorListInit_US() => hResult = 0x00000000

LOG entry 71 Leave: ECIDRV_Initialize() => hResult = 0x00000000

LOG entry 72 Enter: ECIDRV_GetInfo(dwHwIndex = 0, pstcHwInfo = 0x0040CEF4)

LOG entry 73 Enter: DriverOpen(dwBoardIndex = 0)

LOG entry 74 Enter: DriverCreate()

LOG entry 75 Leave: DriverCreate() => pDriver = 0x00007D88

LOG entry 76 Enter: DriverDestroy(dwBoardIndex = 0)

LOG entry 77 Leave: DriverDestroy() => hResult = 0x00000000

LOG entry 78 Leave: DriverOpen() => hResult = 0x00000006

LOG entry 79 Leave: ECIDRV_GetInfo() => hResult = 0x00000006

LOG entry 80 Enter: ECIDRV_GetErrorString(dwError = 0x00000006)

LOG entry 81 Leave: ECIDRV_GetErrorString() => szErrString = “unknown error code or error message not found”

Result of ECI111_LogStop: Operation finished successfully.

-> Returning from ECI Demo for CAN-IB2x0 / PCIe (104) <-

-> Closing INtime ECI API Demo program <-


#21

Thank you Mark, this has been forwarded to the developer. I don’t have much feedback yet but the developer indicated he we might need to try to narrow down further where the issue is. I will follow up shortly once I have more info.

Deryck