Rich

Which IP address are you using to connect? There should be several printed in the output log when the game loads: If none of those work, try specifying your IP address and port manually in the Telemachus config file.

Thread closed, this is old.

Not quite, those sliders refer to the current inputs you are providing. The figures in the table relate to this diagram, and should be the same as the numbers reported by MechJeb (when I have fixed them). I welcome suggestions, that is one of the primary functions of this thread

Glad to hear that it is bringing people some enjoyment, this makes the development process worthwhile. Below is a screenshot of the last feature that I wish to include in the next release of Telemachus (before I start refactoring, polishing and testing). Everything works except for the roll reading which is causing me some problems and as you can see there is a read out of your current SOI. As for differences between the antennas, currently there is no functional difference. However I am toying with the idea of making one low power and limiting the data rate, and the other with higher data rate and a proportional power drain.

Experimental builds will not be made public, but they represent my intend with regard to features I wish to include into future releases. I suspect IVA is possible (given the cameras are active in the flight scene), but showing the map view will probably not work as it is probably inactive unless you are in the map view. Detecting SOI changes is currently possible, I hope to use this in conjunction with Kerbal Maps to provide a map of the body in the current SOI, your ground track, and the positions of other vessels.

Thanks will PM you if I have anything which needs testing. The camera integration has not been released yet as it is currently highly experimental.

Glad to see it is coming in handy . Attitude feedback is much needed and I was doing some research into this last night with the aim of including it in the 1.4.0.0 release of Telemachus. Not sure when this will be ready, but I hope to enter the testing phase as soon as I have the attitude sussed.

Hola Short Circuit. By default Telemachus attempts to listen on all available network interfaces, the error you are getting occurs when something is preventing it from listening. Have you tried disabling your firewall and anti-virus software just so we can try to isolate the issue? The other action to try is to specify both the port and IP address you wish to use in the configuration file; you can obtain a list of potential IP addresses by using the ipconfig command on windows and the ifconfig command on OSX/Linux. I know of at least one other person who has had this issue, so I will invest some time in printing more detailed error and help messages in this area.

I have considered this option but there are potential scalability issues with regard to the amount of data you are loading into the web browser. Ideally the data needs to be buffered into a file so that mission data can be logged for an arbitrary length of time, but with the restrictions placed on web applications in the area of local file handling I might as well give in and delegate the logging to to KSP.

I have been thinking about logging for such a long time, I really want to find a way in which I can log the data on the web browser end, but due to restrictions I have not discovered a scalable way of doing this. It looks like I will need to extend the API to allow for logging on the KSP side, then build a web page which allows you to start/stop and specify which information you are recording. In other news, I am working on tables for the next release as shown in the screenshot below. Yep, it is simple but I want the "core" functionality to work on as many devices as possible, however other people are free to create more complex device specific designs if they wish.

It will work over the Internet if your port forwarding is set up correctly, I try to set up a quick mission such as obtaining orbit and test it with people in IRC before a new release.

Another shout out for Dell monitors, I have 2 and they have lasted a good 5 years. The power port is a little loose on the older of the two, but I have moved it up and down the country at least 15 times.

If you are familiar with JavaScript and HTML then it is certainly possible to create custom visualisations using the API provided, since the web pages are served from the KSP PluginData folder. While both the velocity and the dynamic pressure can be accessed via the API, the thrust information has yet to be added (thanks for reminding me that I need to put this and vessel weight in ). However, custom graphs without writing your own code is still a work in progress.

You would need to teach yourself, or find someone with the skills to do so. Personally I am not so great a creating visually appealing user interfaces (hence my reliance on jquery ui), I am more of a crazy systems engineer who does things like build web servers where they shouldn't be. The next update will enable the web server to serve images (jpeg and png currently), this will be a handy feature for anyone trying to make custom user interfaces.

Sorry for the double post, but I had to investigate this gravity effect you were experiencing (a mixture of curiosity and wanting to check there was not a bug in Telemachus). It seems like the gravity sensor has a limited range as demonstrated in the screenshot below.

Now that you mention it the gravity graph that Telemachus produces does exhibit a strange stepping behaviour, which none of the others do - they are much smoother. Will have to investigate.

Heh, no time for test versions on the last two releases as those bugs were stinkers and required immediate release. Still more bug fixing and a few optimisation to do.

Telemachus pulls the gravity reading directly from each of the sensors on your ship, which off the top of my head are only accurate to 2 decimal places. Better hope the KSC develops some better sensors . You can of course get a more accurate reading from the game internally, but it takes aways some of the realism if you magically pluck values from the ship completely bypassing any sensors you have installed.

Another small update on the SpacePort (version 1.3.2.0). No new features but it fixes an epic bug which can cause the game to crash when you open the Telemachus landing page. The sooner I sort out these stability issues the sooner I can add more features

Small update on the SpacePort (version 1.3.2.0). I managed to fix a disaster of a bug which could cause Telemachus to crash during long missions. Not many new features because I am trying to focus on improving stability, however I have added resource graphs for electric charge, liquid fuel and oxidiser.

Cool as long as it's working, not sure why the other model didn't work. The extension issue is only something I can fix, which it is for the next release.

Try using the following address 127.0.0.1:8080/telemachus/information.html

Managed to do some testing on my Android phone, it took ages to load - but it did load. Will need to find someone with an iPhone to conduct more tests, or develop a debug version to give to you guys.

That is the plan, I want to provide enough information for you to do entire missions in IVA or from your kitchen. I will have a think about writing a better tutorial for sending the data to a tablet device. I have also conducted two simple test missions involving an Internet connection from the UK to Canada, will also include this in the guide.

Thanks for your comprehensive effort, it will certainly help me when I look at this when I get home.