Module Number and SSID allocation.
**********************************************************
If the ‘Top Level’ is the same, so is the SSID!
If the ‘Top Level’ is different in any way; a new SSID must be assigned! :D 

Examples:	Module Hardware Revisions:

Module Number              	Top-Level           SSID
40-612-002                 	40-612-002          2056
40-612A-002                	40-612A-002       	2275       <- Shared SSID
40-612A-002-M              	40-612A-002     	2275       <- Shared SSID

You can see that there was a new SSID assigned,
as there was a change from “40-612-002” to the new ‘A’ variant “40-612A-002”;
So that required a new SSID.
Hence, it will show up differently In Device Manager (40-612-002).

Whereas in the case of 40-612A-002 and the 40-612A-002-M,
they share the same SSID as the ‘Top Level’ (“40-612A-002”) is the same 😃 
And thus will appear as the same in Device Manger (40-612A-002). 



Example: Module Ranges:

Module Number              	Top-Level           SSID
41-761A-001				   	40-761A-001			12700
41-761A-501				   	40-761A-001			12744
41-761A-502				   	40-761A-001			12745
41-761A-503				   	40-761A-001			12746
41-761A-504				   	40-761A-001			12747

These all have different 'Top Level' information,
Hence, they need new SSIDs assigned to them. 

Example: BRICs

Module Number              	Top-Level           SSID
40-561A-122-180x16			40-561A-122			2206		
40-561A-122-210x16			40-561A-122			2206		<- 
															 + Hardware Change, From Xilinx to Lattice
40-561B-122-60x8			40-561B-122			12753		<- 
40-561B-122-90x8			40-561B-122			12753		<- 
															 + Module Number changed, so the 'Top level' has now changed
40-561B-121-60x8			40-561B-121			12749		<- 
40-561B-121-90x8			40-561B-121			12749

**********************************************************