1 Topic by zhangye

  • zhangye
  • Member
  • Offline
  • Registered: 2007-12-14
  • Posts: 41

Topic: Help about HF2

I have one NION3 ,the firmware is 1.6.1f .
I have 7 cobranet devices, these cobranet devices chip is CS496102.
My problem :
1.When these 7 cobranet devices power off at the same time by about 5~7 times,the nion will have fault.The Nion log tell me HF2.
2.I running Cobranet Discovery software,I found the nion's error code is 2949122.
3.I find out the 2949122 from cobranet Programmer’s Reference Version 2.2,that means "Too much control packets received." "Excessive broadcast control traffic on network." My question:
1.What does "Too much control packets received" mean? How many control packets means "Too much" ?
2. Does manange switch can to solved it ?

Thanks.

Last edited by zhangye (2012-08-15 05:53:54)

2 Reply by JianyeZ

  • JianyeZ
  • JianyeZ
  • NWare GUI Engineer
  • Offline
  • From: ShangHai,China
  • Registered: 2010-12-02
  • Posts: 27

Re: Help about HF2

After so many years,questions are still questions.
hf2,xdab lose clock,cab offlines,incompelte nware help files……

Life is rough so you gotta be tough.
                                      -Johnny Cash  smile

JianyeZ's Website

3 Reply by Fergy

  • Fergy
  • MM Tech Support
  • Offline
  • From: The Home Office--Meridian
  • Registered: 2007-08-15
  • Posts: 334

Re: Help about HF2

I would disagree with JianyeZ, as we do have several topics and articles about CobraNet in the Help Files, including "Working with CobraNet" found here;

http://peaveyoxford.com/kc/index.htm#5955

Also, please keep in mind that CobraNet is owned by Cirrus Logic, and that additional help can be found at http://CobraNet.info

That said, when a CobraNet device is first turned on, it sends out a multicast packet called the "Reservation Packet".  This is the discovery process, where both the Conductor and the Performers find out where and what the other CobraNet devices are on the network.

This network packet is sent many times a second when the device first comes on the network, and is then reduced to about once per second, and even down to as little as once every 5 seconds, depending on how busy the network might be.

So if you turn on several CABs at the same time, you can see how the existing CobraNet devices (those that are already on the network) could be overwhelmed for a moment or two.  There have been some improvements to the recover phase of the CM-1 and CM-2 CobraNet devices in recent years, so check what version of firmware is being used by the NION and CABs.

More information can be found in Josh's latest post to this thread;

http://www.peaveyoxford.com/forum/viewtopic.php?id=231

Since you are saying you have only 7 CobraNet devices, this next is probably not the problem, but if you have a large network of CobraNet devices, and this is just a small project that is part of the bigger system, then it could be too many devices for the Conductor to manage.  Typically, I try to stay below 45 transmitters (a transmitter is any CobraNet device that is a input, CAB 8i, or CAB 4n or 8n that has inputs, plus all NIONs that is putting digital audio on the network).  The CM-1 and CM-2 can handle more than that, but the network would need to be flawlessly done, and I would be double-checking the usage cycle of all CM-1 using this software package from our CobraNet Guru, Steve.  This software is called "CM-1 Usage Device-cycle", and can be found here;

http://mm.peavey.com/downloads/index.cf … item_id=83

The other possible issue is that there are other products or devices on the CobraNet network that are also using a discovery process to find each other.  Video products that use the network for control and connection can cause this type of problem.  So yes, a manage switch would help solve both this and having too many CobraNet devices on a single network.

Fergy

Make it intuitive, never leave them guessing.