Hello I just recently upgraded some old installatioin from ros 6 to recent version ros 7.19.2 and on SXT SA5 ac is not possible to set indoor (or any instalation) mode anymore. It shows error “couldnt change interface - allowed installation type is outdoor (6)”.
So my question is why allowed instalation type changed after upgrade to recent RoS and if there is anywhere list of devices/regulatory domain which not support indoor instalation mode.
For info:
board-name: SXT SA5 ac
model: SXT G-5HPacD r2
revision: r2
firmware-type: qca9550
factory-firmware: 6.42.7
current-firmware: 7.19.2
Hello, it is intended primary for outdoor, but that doesnt mean that cant be used in specific indoor scenarios (like covering industrial halls or long corridors - which is frompoint of RF regulation indoor spaces). But question is not about for what is intended but why alloved set changed after upgrade and if there is any list which one device not allow such mode. Btw for some non etsi countries it allow indoor mode, so it is just bound to regulatory domain table, not to radio itself.
Indoor and Outdoor frequencies are defined in country regulations, if a device is not certified for use in indoor scenarios (due to high power etc.), you can’t use those frequencies.
I understand that device is certified somehow, have regulatory domain table etc…
But you want t say that by upgrade to ros 7 device lost its certification for indoor?
And also original question: is there anywhere list of devices which not support indoor (no matter for what reason) - as I need to avoid them for such type of installation ?
Actually for me only way to get know this is really to try set indoor and test if get error or not - not found any remark on website about devices not capable for indoor and either in ros command prompt not found any parameter which show this - if I print country info and radio properties it is same in both devices whch support and not support indoor.
Country rules change, drivers change, many things could affect this.
It’s not clear to me why you don’t simply use outdoor frequencies, if you say the distance is large and you have permission to use a device like this indoors?
Should still work to use no_country_set + superchannel and be careful to manually set the correct frequency to meet the regulations and be compatible with compliant client devices - laptops, phones etc. However I’m keeping all my outdoor devices on latest stable (mature) 6.x - has anything changed about regulatory rules in recent 7.x?
As explained, country regulations change. Also vendors (MT included) are forced to make devices conform to regulations better.
One example: some 10 years ago 5GHz WiFi devices finally started to conform to DFS regulations and max EIRP limits. So when people purchased newer and “better” devices, the coverage actually got worse in certain conditions.
Unlike most other vendors who only release software updates for particular device models for a limited period of time and radical change in device’s behaviour is unlikely, MT provides software updates for quite old devices … and users can thus experience the “newer and better” effect on their old devices.
The reason for MT to restrict certain devices to outdoor only frequencies is the same: to reduce possibility for users to misconfigure their devices (either accidentally or on purpose) and cause problems to other users of same frequency band.
No, regulatory agencies don’t take answer “it’s device user’s responsibility to use device properly” from vendor as a viable solution anymore, decades of experience shows it differently.
So if you have a legitimate use case where built-in constraints block you from legitimate use, then you can carefully apply some workarounds, @marekm already mentioned one way.
Yes that is one of reason because DFS not only delay startup but in noisy enviroment also sometimes false trigger.
Another reason is that coverage for such areas is planed and measured afterwards - you cant just change channel because of radio upgrade as that means replan and measure everything again.
Almost for sure something changed between 6.x and 7.x - Ill try to play with it more when there will be next possible maintenance, but if I remember right (really not sure beause have to make it somehow working in very constrained time) latest 6.x version allow setting indoor and 7.x dont allow on same device.
You have to re-plan and measure if country regulations change … at least in my country (ETSI member) changes in regulations (luckily they are not frequent) apply to all installations, existing and new alike.
but problem is that regulations not changed since installation (there were some updates in general/public license, bit without impact to this). Problem is that device which allowed selecting of indoor mode not allow such anymore after upgrade to ROS 7. It is not problem that some frequecies/power settings is unavaliable, but whole indoor mode si blocked - cant be set if regulation domain is set to anything ETSI related (for some other reg domain it is possible to set, but not tried if really works).
And main problem is that upgrade remove whole indoor mode witout anywere noted. Iam OK if device not support indoor, but need to know that in advance, not found such when upgrading existing instalation. That is worst nightmare on technician that mfg remove in update some feature which is currently in use - as it means rollback everything to previous version.
We’re running in circles. The thing is that device in question was only certified for outdoor … but older ROS versions did not limit settings to allowed values for this scope. Now, ROS enforces country limitations (and certification) and setup is suddenly broken for you. I feel your pain but you can’t expect MT to keep ignoring certification limits.
As already mentioned: you should still be able to use your device for the same purpose as you did it before, but you may have to alter configuration … in the way which might seem to be counter-intuitive but never the less. Intuitive way should be the way which results in device configured to conform all local regulations within the scope of intended use of device (and your use violates of the later). Since you’re out of intended use, you’re on your own regarding legality of your setup.