I’m trying to use a Cisco C-ANT9103 antenna in a Planning project, but I can’t get NetSpot to accept any of the antenna files I’ve tried.
So far I’ve tried .json, .ant, and even .txt. With the JSON version I tried formatting it a couple different ways and removing some parameters that I thought might be causing the parser to fail, but NetSpot rejects everything.
Does anyone have a known-good C-ANT9103 file that imports successfully? Even a sample file for a different antenna would help at this point — I mainly want to see what NetSpot is expecting.
Where did those files actually come from?
Changing the extension or making the JSON “look right” isn’t enough. The importer still expects an antenna pattern in a format it understands. NetSpot’s docs currently list .json, .ant, .ana, .msi, .adf, and .prn as supported antenna formats. .txt isn’t on that list. Also, Cisco publishes the radiation patterns for the C-ANT9103, so whatever file you’re importing should ultimately match the manufacturer’s antenna data, not values reconstructed from a product description.
@Sgimageworkz The original data is from Cisco, but the actual import files were created from AI suggestions. Basically I gave it the C-ANT9103 specs/pattern information and asked it to generate something NetSpot could import. I’ve attached the JSON and ANT versions I tried.
Ah. There’s your problem
Those files aren’t just slightly malformed. They’re not really following a recognizable antenna-pattern file structure in the first place. Changing the line breaks or deleting a couple JSON fields isn’t going to rescue them. AI basically gave you something that looks like antenna data to a human, which is not the same as producing a valid antenna pattern file for RF planning software. Cisco publishes the actual radiation patterns for the C-ANT9103, so that’s what I’d work from rather than having an LLM invent the file structure.
If anyone here on the forum already has a collection of ready-made C-ANT9103_24.msi files for other Cisco antennas, could you please share them? I’d rather not waste time rebuilding everything from specs or digging through documentation again if someone already has working files.