I wanted to tidy up all the wiring in the battery case. So I shut the whole system down and did just that. This process did consist of pulling each Longmon communication cable, tidying up the wiring and then plugging it all back in. It did not consist of disconnecting the Shuntfrom the Watchmon itself, but did require disconnecting the communication cablesfrom the CMU and plugging them back in. Reconnecting the whole communication network between the Longmon's was done starting at the lowest cell, without the Watchmon itself being powered. I then powered it back up after the whole network had been reconnected. And then I got a timeout error. I tried doing a network test but got nothing back. I cannot resync because there is no communication between the Watchmon and the network.
So I then started checking all the wiring. It makes sense that it is the wiring but I continuity checked all the cables and everything checks out fine.
I will once again go through all the wiring. I wonder if it might be technically OK to just loop the whole communication of the Watchmon's transmit and receive together and bypass the network in total to verify if the Watchmon itself has a problem. But I do not want to do anything that will harm the Watchmon while I pursue this.
Also, I cannot find exactly what the reset button on the Watchmon does on Batrium's website. I assume it resets everything back to the factory settings in the Watchmon's internal memory? And I don't know how that could affect this communication problem but I could try that as well.