heaton84

Update, release 0.25 is out. Thread here. One thought on the readout scaling.... I could place the decimal point based on UOM. For example: 0000000.0 M 000000.00 KM 00000.000 MM 0000.0000 GM This would let me get away with simple labels on the physical panel, and the virtual panel could infer scaling from this convention. It's either this, or allow for a separate controller to illuminate scaling on the final panel (more $$$). On the physical side of things, I have a rough proof of concept working in MPLAB's simulator. Once I get a few more parts in, I should be able to breadboard up a physical readout!

LEDJeb provides an interface for a physical LED readout based on MAX7219 display modules. It also provides a virtual panel to both facilitate testing, and to be used by those who don't care to invest in the physical display but do have a second monitor to spare. The plugin will be configurable and scalable. You can have one display, or you could have 100 displays. Each display can have a different flight variable assigned to it. Release 0.25 - Linux and Some Customization Download the Binaries (will require Mono on Linux, sorry for non-github link but github is being a pain right now) Source Code on GitHub Release notes: Fixed scaling issues in Linux Mono (rewrote 7-segment code) Added customization of LED readouts (shear/thickness, color, etc.) Added saving/loading of configuration

PM sent on the debug setting. "Configure" is a work in progress. Right now it does absolutely nothing. That reminds me... for anyone who is using this, v0.21 also has the half-done feature of coloring the readouts. Just double-click on the readout you want to color, and pick a color. It won't remember the setting once you close the program... that's part of the "Configure" section I have yet to finish.

Update on the sizing issue: I see where the problem most likely is, I'm just not yet sure how to fix it. I borrowed the 7-segment code from Dmitry Brant, so it's not my own. Looks like the app is running in Mono on linux, which doesn't yet support GraphicsContainer. I will have to modify the code to remove that reference and do the scaling myself. Update on the sockets: Logging code is 50% done. I just need to add logging to the game side. I'm also adding in some config options to give Cortek56 some things to try as I guide him through getting it to work. Linux Binary: A few of you have been asking for the linux version. Sadly at the moment, I don't have a linux machine ready to go to compile and test it. Therefore, I am going to focus on the other issues for now. If someone (BrutalRIP?) wants to supply the linux binaries once we get the sizing hashed out, I would be most appreciative! Minor Update 0.21 is out I'm not going to post a new release thread until 0.3, right now I'm just focusing on existing issues. If this mod gives you trouble, grab 0.21 and do the following: 1. Edit LEDJeb/LEDJebVirtualPanel/bin/Debug/LEDJebVirtualPanel.exe.config with notepad and change this line: <add key="debug" value="false" /> To read as follows: <add key="debug" value="true" /> 2. In your KSP game folder, open Plugins/PluginData/LEDJeb/config.xml with notepad. If it doesn't exist, you'll need to start the game, go to the main menu, then exit. Change the line <int name="DebugMode">0</int> To read as follows: <int name="DebugMode">1</int> Note that if you've already ran LEDJeb 0.2, this file will already be there but the DebugMode won't. Just add the line to the top of the file so it looks like this: <config> <int name="DebugMode">1</int> <int name="DisplayCount">16</int> <int name="UpdateRateMS">100</int> <int name="DataStreamCount">1</int> Once you have done all of that, start the client panel, then the game. Start your flight, things will still be broken BUT... now you can close the game, stop the panel, and pasebin the following files for me: 1. Panel log at LEDJeb/LEDJebVirtualPanel/bin/Debug/LEDJebVirtualPanelLog.txt 2. The game log in your KSP's KSP_Data folder (KSP_Data/output_log.txt) This will greatly help me troubleshoot problems. I will be PM'ing some of you for a bit closer follow-up.

Whoa! Looks like a scaling issue there. Chars are about 25% too big. Anyone with Mono in an ubuntu environment able to troubleshoot something like that? Just running Win7 here. I hope to get the network tracing code in tonight for Windows 8. I remember going from XP to 7 resulted in funny business with sockets. Sounds like 7 to 8 is the same

That is strange. If it shows "waiting for in-game flight" when you're actually in-flight, then the game cannot connect to the client. I will have to add some logging to the socket connection to figure this one out. Been taking a break recently, so hang in there a few days!

Preview of color picker feature. Picker sets "lit" segment color, the background is automatically set to 1/8th the foreground color and it looks good, I think.

It uses a local socket, just as rkman pointed out. I will add a note to comply with the forum rules. This shouldn't broadcast any data over the internet... but then again if someone can connect to your IP and the port this uses (if you're not behind a firewall and not behind a router), then they could in theory start scraping your flight data. In that scenario, I think KSP data is the least of your worries! Please give full-screen a good test and report back. I only have one monitor at the moment, I am mainly using the virtual readout to debug my display protocol. Still working on unit of measurement, as (to also answer Fullmetal99012's question), the overall goal is to aim it at an external display. I just received my display modules tonight, but it will probably be a few weeks before I have a working prototype due to time constraints ( is the display I'm targeting). Anyway, my main concern is how to represent M/KM/MM without additional hardware, or keeping additional hardware to a minimum. One thought is to have M read "12345678", KM read "1234567.8", and MM read "123456.78"... but I'm not convinced that's as user friendly as I'd like. The alternative, since this is modular, is to tack on one more module for misc. indicators.

LEDJeb provides an interface for a physical LED readout based on MAX7219 display modules. It also provides a virtual panel to both facilitate testing, and to be used by those who don't care to invest in the physical display but do have a second monitor to spare. The plugin will be configurable and scalable. You can have one display, or you could have 100 displays. Each display can have a different flight variable assigned to it. Release 0.2 - Beta Than Eva! Download it here! The following issues have been fixed in this release: KSP no longer crashes when closed Decimal points are now shown on the virtual readouts Plugin is no-longer dependent on a TTF font. Issues to tackle going forward: Fix sockets so that they reconnect more gracefully Display chain initialization on reconnect Configuration of client readout (pick colors, customize digits, add/remove panels and labels, allow resizing of window, etc.) Add in-game UI for plugin configuration Better (any) indication of readout scaling. Readouts auto-scale to KM above 99,999,999 meters. Relative inclination is wrong Burn time remaining does not work Time to intercept does not work Edit: To comply with Rule #5 This plugin sends flight data over a network socket, specifically to loopback port 5155. It consists of all flight variables you see on the readout program above, a display count, and nothing more.

Release 0.1 alpha is out! Heads up: it crashes KSP when you close the game. Is anyone familiar with InternalGetGameObject throwing a NullReferenceException?

Ok, I have everything except time to intercept and burn time remaining. The MechJeb stuff on burn time remaining is rather... involved. I have to either rely on MechJeb or extract it all out piece by piece. For "relative inclination" (ascending node), I literally added together the current vessel's obit.inclination and the target vessel's orbit.inclination, and it appears to match the game's ascending node value pretty closely. This seems counter-intuitive, but if it works, it works I guess. Still a bit of cleanup to get things less... Kerbal.... and I want to get decimal points working. Then, I think I'm ready to share an early release. For hardware, I'm looking at a Microchip PIC 16F628A. Since I am designing with daisy-chained MAX7219's in mind, the protocol is a bit wonky but it definitely works.

Close ! I just had to use Planetarium.GetUniversalTime() instead of GetPlanetariumTime(). That works. Many thanks! Here's what I'm doing with it: http://forum.kerbalspaceprogram.com/threads/106192-LEDJeb-A-Physical-*and*-Virtual-LED-Readout

Thanks! I was starting to look into MechJeb, but you are right, it's a large project. I at least have a starting point of what to look for... will report back if I can't figure it out. I am using sockets. The ultimate goal is to feed the data out via a serial port to drive a real display, so this was the closest mechanism I could find that I could boil down to an interface quickly. Oh, you. Heh, yeah I'll fix that. Thanks for the feedback!

How do I get the distance to the active target, it's relative velocity and the ascending/descending node numbers for it's orbit?

I'm searching high and low and having a hard time trying to get the next maneuver node. Could someone point me in the right direction? Thanks.