Today, we achieved stable two way communication to the RP elsewhen. Two way communications have been intermittent at best until now. At first it was believed that the nature of the Russel Process of translocation was causing the disruption in data communications. Even increasing power to the Null Field Energy Transceiver Array would improve the signal to noise ratio of the communications as expected, but the data signal would just stop periodically even though the sub-band signal implied that communication was still possible. Finally is was discovered that a given USB component (used to monitor and attenuate the Null Field flux) was not performing as expected and the waveform would drift out of phase resulting in a de-sync condition. The next regular synchronization process would then restore the phase of the local and remote transceivers and communications would continue. The component has now been replaced with another brand of the same component, and communications protocols are operating as expected. However, Windows continues to increment the attenuators id number each time it is plugged in and now identifies this device as as attenuator 438 even though it is the only one connected to the system. Moving off of the experimental diagnostics gantry and onto the stable 5.0 hardware gantry should resolve this issue for regular use. This illustrates the need to throughly test all third party components even though the manufactures indicate that the device is completely compliant with established standards. Standards! Look it up. I truly hate it when a manufacturer shrugs off inconsistencies and incompatibilities with a released product and still label it as “Standards Compliant” since most people will never have a problem with it.

Powering down the tesla generators for the night,
Adam “Thor” Butt, VGC R&D