Phoenix Research Log Team Mk 1.3. My team is onboard of the Livadia Shipyard and are preparing for an in-depth analysis of the unkown device, which was found derelict in the secor 117Z. We have set up analysis equipment in the hangar bay and attempting full surface scan before opening the device which appears to be some sort of beacon or transmitter. The data of the transmission is in the form of a short repeating tone, threatened with strange data stream, which appear to be some sort of coded message.
Decoding of it will take considerable time and processor power. In the meantime we continue with our surface studies. The device has traces of the Phoenix origin, but the shape and the data stream is nothing we have seen before. Analysis continues.
Principle Investigator supplementary log. The device is still very much a mystery even after a detailed inspection. Most parts seems to be either bespoke made or never intended for open market. There are no aesthetics built into the device and the most remarkable feature we could really note are the faded serial IDs printed onto the parts. Searching for the IDs on the neutral net yields no results. There are a few open market parts installed which was easily identified, and functional analysis suggest they are the main pieces that needs to be frequently replaced from wear and tear to keep it functional. As for the other bespoke components, these are generally in good condition and fit for purposes, but the technology used is somewhat outdated and runs somewhat less efficiently than the direct counterparts available on the current market. Nonetheless, it is not obsolete and still does the job perfectly.
Speculation dates the device to be a several decade old, but has been up until recently maintained. Given both the current state of the hardware and software installed, the current hypothesis suggest either 1) it was once state of the art military grade at the time of construction, or 2) a commercial project done privately. The former scenario is more likely given the commercial alternative would have some traces on the open market, as a business would try to reoperate some cost eventually.
---
Listening and analysing the coded message on a repeating loop, it seems some parts of the data stream have been degraded whilst in open space. Focusing on repairing these parts separately should speed up the decoding process overall
Log 1.5. We've studied surface of the object and made several attempts to connect our apparatus. Surface scan showed that under the side panel with factory number AP4521 should exists backup connectors, so we would be able to launch beacon systems and load all necessary data without attempt of destruction method. We have attempted to warm up the panel to expand the metal, but on 700c temperatures we had to cancel our attempt. According to rays shots the inner plate started to deform significantly. So we have no more options to open it, we are preparing the surface for destruction method.
Log 1.6 Unfortunately, the object plates prevent revealing even by using an angle machine. Though it gives us some additional information about its origin. Most likely it was constructed in the last two decades, when our shipbuilders used better alloys to be able to consume more damage by the photon cannons. At the final attempt we have brought an industrial laser to rip off the external plate. The operation went successful, although the connectors were burnt, but our engineers already attempted to recover them, although due to limited space of the niche and metal structure we have not so many chances.
Principle Investigator supplementary log. Investigating the newly exposed internals behind the shell uncovered an intricate piece of engineering within the device. Unfortunately progress was limited due to the confined spaces of the devices itself. It seems we will need to devise a bespoke circuit and bring the connections outside, not much of an issue as we don't expect to recast the device in open space again. The bespoke circuit will be designed to fully repair what was damage, but also help establish a safe and secure connection our diagnostic machine if we have any hope of code breaking.
Separately, the piece of external plating removed from the device is now being analysed on the workbench. There was nothing spectacular to note from first glance. However, running a crystallography analysis with a sample of a clean fragment yielded some interesting results. The report indicates an unusually increased concentration, and higher grade of Hydrocarbon molecules found in the side panels. Testing an exposed frame from the device also picked up a distinct isotopes in cobalt modules, the signature matches only one region of Sirius, the Walker nebula. Compounding the workman ship of the device points to an assumption... this is either a product, or at least a raw product of Rhineland origin.
Log 1.7 We have attempted to access our database in regard to metal plates, as it seems to be very confusing, hence we never produced ships of such metal. I’ve contacted Nova Young regarding our thoughts, most likely we’re facing some sort of classified or prototype project we are not aware of.
Without an effort we have tried to allocate on opposite side connectors under the body, but scan results weren’t satisfactory… Hold on, probably we’ve found something. Our engineer found the niche and pressed button inside. It unblocked the panel and had been slided downwards. Probably it's what we are looking after. Seems some sort of power and digital connectors with various switches. If the beacon isn’t damaged inside we will be able to connect to its data records swiftly. Investigate continues.
Principle Investigator supplementary log. We made significant leaps in understanding the beacon after finding the hidden unlocking switch. We hooked up the data port with an adaptor and linked it up to the analyst machine. Thankfully there wasn’t any encryption and the rest was straight forward, as the interface and bundles of data appeared on our monitors on a loop.
Reading the beacon log, it looks like the device was automatically deployed from the originator vessel, after it suffered hull stress beyond the acceptable threshold. The vessel appeared on screen is a familiar Bismarck class strangely … if I also recall correctly, looks exactly like one of the vessel in the CoreFleet that failed to make back. Looking at the vessel status last known by the beacon, it doesn’t bode well at all… Reactor offline, fires on multiple decks, hull fissures and oxygen leaks…
Anyway we now have a location on a map - a system somewhere nearby adjacent to Omicrons Theta, but frustratingly not within the known network accessible by Jump holes or jump gate.
Phoenix research log team mk 1.8. This is a final record, all investigation log regarding our find was transferred to the Security department. We made several attempts to decode the origin of the beacon's launch, as it's a quite huge area of the Omicron sector. While we made several simulations of it's vector, the area of launch place reduced greatly. It appears that Vega emergency system, as origin of the beacon is no longer is question, automatically launched the beacon from the area surround of Omicron-74 system.
We've suggested Security department to send the salvage mission as soon as possible, condition of ship systems is critical according to the data analysis of the beacon.