1 Topic by mrass

  • mrass
  • Member
  • Offline
  • Registered: 2012-06-29
  • Posts: 4

Topic: Nion ne not booting after assigning updated project role

After connecting to a nion ne with nware and using the "upload and connect" to retrieve the role and making a minor change (replaced a image) and then using the "deploy"  I get the message "1 unit not responding" after pressing cancel, ignoring the message, it will try to assign the role but doesn't finish and says under status role stopped.
I'd guess the nion is hang up, power cycling did not help and the mute/fault led remains lit.
Any suggestions on how to bump this unit back into action and wat could have caused this behaviour?
Many thanks in advance.

2 Reply by mrass

  • mrass
  • Member
  • Offline
  • Registered: 2012-06-29
  • Posts: 4

Re: Nion ne not booting after assigning updated project role

Fixed. had modified the project role in nware 1.6.6a while the nion is running 1.6.3
now reinstalled nware 1.6.3 and retried it now works fine.
Probably very logical to most users but maybe worth a sticky for the occasional users?

3 Reply by JoshM

  • JoshM
  • JoshM
  • Recording Engineer at Burnt Orange Studio
  • Offline
  • From: Meridian, MS
  • Registered: 2007-08-13
  • Posts: 1,498

Re: Nion ne not booting after assigning updated project role

The version numbers between the firmware in all target devices in a given project file must always match. The version of NWare on any and all computers used to access that project (both regular NWare and NWare:Kiosk) also must match the target devices firmware. This is particularly important when deploying, when just connecting or "Upload and Connect"ing to an existing project, there is some room for flexibility. 

You probably could have rectified your situation by updating the firmware in the NION to whatever version of NWare you were running on your computer. However, down-grading the version of NWare also works, as you found.

Josh Millward
Burnt Orange Studios

JoshM's Website