From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
ncCreateNotification problem
Ashwini
Member
03-09-2006 01:26 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi my application has stopped getting notifications when i upgraded the NiCan from 2.1.2 to 2.3.2. Surprisingly when I give a breakpoint at the line where i call ncCreateNotification my application starts getting notifications. But this also happens sometimes. Can someone please help me out ....I want to solve this issue urgently.
DirkW
NI Employee (retired)
03-09-2006 10:20 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi Ashwini,
Perhaps you can explain a little more in detail what are you doing with ncgetnotification. Which parameter you are waiting for and are you doing this for the Network Interface or for an Object? Did you run the NI Spy ? A Spy Log would be helpful too.
DirkW
03-10-2006 02:56 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi DirkW,
I want a notification on the state NC_ST_READ_AVAIL and i am doing it for an object.
I tried running the Ni-Spy. When I am using version 2.1.2f the Ni-Spy log contains the message Invoking user callback funtion.But this does not happen when I am using version 2.3.2. According to the NiCan 2.3.2 hardware and software manual there is no change in ncCreateNotification function call as compared to 2.1.2f. I really can't figure out where the problem is.
I want my callback function to be invoked when the state NC_ST_READ_AVAIL is set. Can you please help me out.
I have attached the Ni-Spy capture files for version NiCAN 2.3.2 and NiCAN 2.1.2f for your reference.
regards,
Ashwini.
DirkW
NI Employee (retired)
03-10-2006 10:05 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi Ashwini,
Yes it seems we did some changes to the notification error handling with 2.2, which is also included with 2.3 and makes sense by the way.
In your 2.1.2 spy log file you can see the invoke callback is reporting the error flag. (h11) This means an error occured (hex10 and a frame received (h1)
Invoking NI-CAN user callback (30875856, 17, 11, 0, 1)
Process ID: 0x00000CBC Thread ID: 0x00000FA8
Start Time: 13:59:02.113 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
The new driver stops the callback execution immediately if an error occurs. What makes sense because you can not trust on this error related information.
Perhaps you can change your program in a way to create the notification after Starting the network with ncaction?
DirkW
03-23-2006 02:42 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi,
Thanks a lot for your help.IMy problem is solved.
regards,
Ashwini.
