Cobra Firmware

0 views
Skip to first unread message

Cortney Voegele

unread,
Aug 4, 2024, 9:26:42 PM8/4/24
to efroliwebs
Ifyou are attempting to update CobraNet firmware on an older AudiaFLEX that has AEC-2 cards installed in it, please contact Biamp Tech Support before continuing. This is only necessary if the AudiaFLEX uses the oldest AEC-2 cards. If it uses newer AEC-2W or AEC-2HD cards, then the unit can be updated to the latest firmware without issue.

All units connected to the CobraNet network should appear in the CobraNet Disco window. If not, Click View > Refresh. Each line shows each individual unit, an IP address, MAC address and current firmware version.


This "Javelin" is Asia Games OEM version of VKB Gladiator, basic differences is use of potentiometer instead MaRS sensor in twist axis, and locked firmware, dont allow change buttons configuration, so the base mode button is limited to change grips buttons (2) and POV HAT, but not base buttons operation.


If your M5 is revision 3, don't use (VKB) MaRS but MKZ41 contactless sensor in analog mode, so theoretically no problem for use in MMjoy2 (or other USB controller), but seems by trick do their calibration.


The Cobra is a better functioning stick - it has lots of buttons, at your fingertips, where you need them. No amount of shifting can make the t16000M as useful as the M5 - the M5 can shift too, remember, and give me even more virtual" buttons, but I find virtual buttons just add complexity, in the heat of battle, the last thing I need is more complexity in an already complex system.


Basically, despite the lesser quality of the M5, it's still a better stick - it does take time to adjust as it is a very light touch, and I personally find the twist kinda useless, as simply pressing a button will make it unintentionally twist. I am replacing my M5 with my Warthog stick, though (for my secondary rig) as I have a Mongoos on the way.


Has anyone experienced hardware stability issues with later batches of the WRT1900ACS/AC ? We have been using the WRT1900ACS (AU/NZ, same as the AC v2) in accommodation deployments for guest wifi - using LEDE v17.01.2 and wifidog custom bin image. Only recently we have had a run of bad linksys routers - there's been random reboots and the WAN port intermittently dropping its ethernet link (ie as if someone unplugged the cable), the custom LEDE/wifidog bin image has not been changed and all the previous deployments are fine. The issues start when the connected device count gets up over 10. Some of our sites can reach > 50 connected devices. I'm wondering if there has been some change in components that go into the WRT1900 ?


As to stability, I've never had issues with my 1900ACS, however the most amount of devices I've had connected to it is around 30, but at any given time it's far less for active clients, usually around 15.


As for the 18.06 branch, I'm not sure of what or how things gets cherry-picked. Having a quick look at the branch shows hostap being older for instance which can affect performance. Otherwise driver and kernel is up to date (for the Marvell WRT-series at least).


Thanks for all the help, I have always used the ACv2 firmware as I read some years back on the old openwrt forum that the ACS distributed in AU/NZ was actually the AC v2 and to use the AC v2 firmware.

I've got one of the problem routers here:




Anyway I tried the ACS firmware and flashed that, it flashed no problem also and also confirmed the board name in /tmp/sysinfo is now showing as shelby, where as when I flashed the AC v2 firmware the board showed as cobra. I'm going to test the ACS firmware and see if there is any improvement in stablity.


I remember having the discussion with @sera and a few other users in the 1900AC thread specifically about this, as I wanted to do away with the 1900AC v2 in the WRT AC Series ToH, and just have the rebranded 1900ACS, however it was pointed out they are in fact two difference devices, with someone posting what the actual differences were.






go to openwrt search linksys wrt1900acs v2 compatible for your router after that you can install wifidog.

opkg update

opkg install wifidog

use putty to install this scripts.

If you want to manage routers from cloud use cloudwifizone


As for the firmware, I've found a copy and put it on box where hopefully you can download it. I was able to download myself using edge but Chrome blocked it due to tftp.exe and a false warning about it. This link should be good for 2 weeks:


If anyone else runs into this, i tried the above linked instructions and the postupg worked, but the rootupg still failed with bad data crc..



After some more searching, i found some instructions that had a "kernupg' command in between thet postupg and rootupg..

I did that and it was successful and then the rootupg worked after as well.



Thanks again to Steve for the files and help.


"Our concerned team has informed us that post your message and download issue in the forum: -IT-forum/bd-p/ecostruxure-it-forum



Could you please check and let us know?



Kind Regards,

Schneider Electric Exchange Support"


The 550/570 units are different than the ones discussed previously in this thread and will use a different firmware. You should be able to find the firmware by simply searching the SE or APC web sites but I've provided links to the firmware and release notes for you:


Wireless sensor networks (WSNs) are exposed to a variety of attacks. The quality and complexity of attacks are rising day by day. The proposed work aims at showing how the complexity of modern attacks is growing accordingly, leading to a similar rise in methods of resistance. Limitations in computational and battery power in sensor nodes are constraints on the diversity of security mechanisms. We must apply only suitable mechanisms to WSN where our approach was motivated by the application of an improved Feistel scheme. The modified accelerated-cipher design uses data-dependent permutations, and can be used for fast hardware, firmware, software and WSN encryption systems. The approach presented showed that ciphers using this approach are less likely to suffer intrusion of differential cryptanalysis than currently used popular WSN ciphers like DES, Camellia and so on.

3a8082e126
Reply all
Reply to author
Forward
0 new messages