Jump to content


System Architect file looses Device Address 4 cts


  • Please log in to reply
4 replies to this topic

#1 mike

mike
  • Members
  • 3 posts

Posted 20 November 2006 - 08:18 PM

Once I save a file in System Architect using version 1.20 and then re-open the same file, the dvice addresses are reset to default addresses.  This only happens with my CTs amplifiers in a dataframe that contains both iTechs and CTs amps.  Any advice?

#2 Bradford Benn

Bradford Benn

    Power User

  • Admin
  • 1,025 posts

Posted 21 November 2006 - 01:41 PM

Hi Mike-

I can not recreate your problem here. Are you sure that you do not have two devices set to the same address?
-=Brad

Bradford Benn
Business Development Manager - Crown International
http://www.crownaudio.com/

#3 mike

mike
  • Members
  • 3 posts

Posted 21 November 2006 - 10:15 PM

QUOTE(Brad Benn @ Nov 21 2006, 01:41 PM)
Hi Mike-

I can not recreate your problem here. Are you sure that you do not have two devices set to the same address?
View Post


Fairly sure..... I can send you one of my files and you can see if it opens with the device id's reset.  Normally, I set my id's to the last two octets of my ip range (10.244.80.20 id would be 8020, etc), when I save the file and reopen it, the id's are set to 1,2,3,etc.  Does that make sense?  

This did not start until the 1.20 version of System Architect was installed.

#4 Bradford Benn

Bradford Benn

    Power User

  • Admin
  • 1,025 posts

Posted 22 November 2006 - 08:47 AM

Howdy Mike-

can you send me your file?
-=Brad

Bradford Benn
Business Development Manager - Crown International
http://www.crownaudio.com/

#5 Bradford Benn

Bradford Benn

    Power User

  • Admin
  • 1,025 posts

Posted 22 November 2006 - 11:10 AM

Hi Mike-

I got your file, and we found the problem.  The reason is that the HiQnet addresses are above 60000.  We reserve those addresses for reassigning addresses when there’s a conflict with offline vs. online devices.  If you drop the address range below 60000  your problem will go away.

We should probably have a dialog popup and explain this when a device is encountered.  This is a now a documented issue, but will not be fixed for the next release due to scheduling.
-=Brad

Bradford Benn
Business Development Manager - Crown International
http://www.crownaudio.com/