LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

cRIO 9035 profibus module not supported

Solved!
Go to solution

Hello again,

 

recently I had to re install the PC host (harddisk died). Now the Profibus module is no longer there, how could that happen?

I am worried that if I try to find it through the profibus configurator, it will delee whatever is on there and it will no longer do anything/ At least the cRIO is still running, but off course I can not change / compile the software that goes onto the cRIO

 

Steffen01_0-1687768588726.png

 

0 Kudos
Message 1 of 6
(683 Views)

Hi Steffen,

 


@Steffen01 wrote:

recently I had to re install the PC host (harddisk died). Now the Profibus module is no longer there, how could that happen?


That module most probably is not from NI, but from a 3rd party provider. Did you install the drivers for that specific module as supplied of that 3rd party?

 

(Do you have any type number or other specific information for that module?)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 6
(657 Views)

Hi GerdW

 

its that one

https://www.ni.com/en-au/support/model.crio-pb-ms.html

from Kunbus ex Comsoft. Seems they no longer exist, now its part of VIPM. Drama is, we still have LV2015 and the Comsoft configurator II is no longer in the www.

I think / hope I installed all the drivers. FPGA, realtime, Ni-RIO, profibus VISA

 

Cheers,

 

Steffen

0 Kudos
Message 3 of 6
(650 Views)

Hi Steffen,

 


@Steffen01 wrote:

its that one

https://www.ni.com/en-au/support/model.crio-pb-ms.html

from Kunbus ex Comsoft. Seems they no longer exist, now its part of VIPM. Drama is, we still have LV2015 and the Comsoft configurator II is no longer in the www.


Then you better look for the drivers in the backup/archive of your company server.

I usually backup all relevant drivers on our server…

 

Btw. I found the "Comsoft configurator II" using Google search, but you better use a good virus scanner before executing the file!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 6
(646 Views)

Hi GerdW,

 

no backup ;-( was on the harddisk that turned itself into a solid state drive. Lucky I kept anything else on a 2nd disk. Except the Kunbus stuff. I found a few drivers, but seems version does not match. cRIO is very particular about that. I am hoping of getting rid of that profibus device soon.

 

Cheers,

 

Steffen

0 Kudos
Message 5 of 6
(621 Views)
Solution
Accepted by topic author Steffen01

problem solved. In VIPM is a small dropdown, then I can select ver 3.0.0.1. Now its happy

0 Kudos
Message 6 of 6
(600 Views)