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.
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.
09-18-2019 07:21 AM
we want to upgrade the firmware for NI 9860 via NSysCfg. Is this possible ?
Upgrading the firmware for cRIO-9033 with the file "cRIO-9033_7.1.0.cfg" from the directory "C:\Program Files (x86)\National Instruments\Shared\Firmware\cRIO\7735" with the function NISysCfgUpgradeFirmwareFromFile from NISysCFG worked.
For the XNET module it did not work with the the firmware file "ens9860_2PortFpga.enb" from C:\ProgramData\National Instruments\NI-XNET\firmware, which seems to be the correct file because of the version information in the file "ens9860_2PortFpga.enh", which we compared with the version information of the firmware which NI MAX offers to install. NISysCfgUpgradeFirmwareFromFile fails with the error code NISysCfg_NotImplemented.
NI Max is able to upgrade the firmware. But only when we used the combobox in NI Max to select the firmware by it's version. Choosing the firmware file "ens9860_2PortFpga.enb" manually in NI Max via it's path and trying to upgrade also fails (error code 80004001).
So we thought NISysCfgUpgradeFirmwareVersion from NISysCFG might work. It seems to return always success but do nothing. Anyway we would need a "...FromFile" method, which would run with only the NSysCfg libs and a firmware file.
Solved! Go to Solution.
02-04-2020 03:23 PM
Hi, abdelam,
Did you ever find a solution for this? We have the same issue - we can not get the NISysCfgUpgradeFirmwareVersion because it looks for firmware versions available on the cRIO target and doesn't find any.
Thanks,
James
02-10-2020 03:43 AM
02-10-2020 11:15 AM
Thanks for the reply! We've still had some issues with it, but hopefully we'll get them sorted out