Mattew

Wau, this thing. Amazing piece of work! It ll be very helpful. That makes my Kerbals happy. EDIT: I found kind of issue or bug if you want call it like that. Your pluggin/debug program expect that arduino serial port is running at default baud rate setting (38400) and if you change that to any other value (like i did, I am running at 57600) then debug program cant establish connection and wont find control panel. I tryed to change my code to use 38400 and then it connects no problem at all. It is something to look at maybe, have option to select baud rate would be nice EDIT2: I just found config file for build. I did changes and now it works with 57600 also. Still would be nice to have way ti change it without need rebuild program

I think my nixie tube speedometer with its own mCU for communication is beyond simple already and 3 LEDs arent fun anymore Most hardware I got up and running, thinking about design of panel itself. That is why I am asking on auto routines stuff, since it ll need some kind of interface to operate and control (DSKY style maybe?) and that must be taken into account for design I asked about sync issues, bcs i had problems with it in past while running gLCD which took to much time. But good idea with PID, didnt think about that one. I ll look in that. Ty

Yes, this is exactly what ll help. With that info you can easly manuver ship to that node But its beyond my skill to get that info and i think I ll left honor to you, since your work is very impresive as it is now. And hope you make your code someday public Wish I can help tho Those Euler angles, what is thaaat, i dont understand at all, dont lika math that match um, we know curent delta-v of ship atm? Guess its your mod of code right since i dont see that info in packet also @zitronen , do you think that autopilot routines can slow down code/mCU that much so there will be possible desync and com drop between arudino and pc?

So atm we dont have any easy method to interact with nodes. I see that airplane autopilot is doable, we have surface vetors, surface speed, alt so on. Sadly I am rocket guy But I see that autoascend is doable too, but with manual orbital inserection tho. I would like to help on this matter but I dont even know how basic IO plugin works. its so beyond me I ll check other work

Couple of question that came to my mind. I read several post about possibility of implementing MechJeb comands and interacting with MJ using KspIO, but it seem no one was able to achive it. Or atleast on devent level. So any news on this "topic" or still hard to do / impossible? On other hand i start thinking about arduino based autopilot for some actions (ascend guidence for example) but I run in problem of nodes. I mean, we dont have any info on where ships points relative to node right? Something I start call "NDD" (Node Differential Data) which will tell you if you point to node (manuver node, prograde, etc.) or how far you point away of node. Also on matter of autopilot for node manuvers I miss data on Delta-V burned already, basicly mean I dont know how much of burn ship already did. Can we have such data or its not possible at all? And someone have any sort of auto action on their control panel?

Nice project! Keep that up. Have you any progress on DSKY-MechJeb interface or you abadon that idea completly? Just wondering, since I got exactly same idea to make that in my project too, not while ago

Yeah yeah, that is what I mean, sorry for not be clear But it sad we dont have that info within game. Maybe some calculation from other values? But not sure what vlaues and where to get them anyway, so...

About 1.1 version: for me it seem working for 100%. Other topic, noticed you zalking aboit what to include in packet, so can we have more info about nodes? Like burn time and delta v actual ( right now we have only max delta v needed)

Wau, we have 1.1 version?! Amazing Z !! Thanks. I cant play KSP without my nixie tubes Hopefuly they fix graphics soon and we are r2g

Aaaand problem solved I upgrade both pluggin and code and its all fine. Ty for advice Freasmeat !

Should I understand that KSP 1.0.5 and plugin 0.17.1 can have some issues? (like my no axis input control ) We dont have reverse compatibility?

Hey guys again. Went back to my project and added joystick this time. But I cant get them to work for some reason. Arduino read values of pots, aslo code is processed (CPacket.Pitch and rest of them change its values if i move a stick) but game doesnt respont at all. I also forced game to use external values by change setting in config file (all set to 1) but no change. A little weird thing, game STILL respon to keyboard even when config is set to 1. I tryed to take my UNO with unmodified code where joystick was supposed to control Throttle axis but it didnt work either. Rest of things work (Leds, Lcd, Nixie tubes), but seem only controls doesnt work. Anybody get some ideas? I ll be glad for any suggestion. Specs : Build on MEGA2560, code build on KSPIODemo10 with plugin 0.17.1

Seem like lots of ppl having trouble with conection and random disconects. I had same problems, but I figured out what was wrong. At first time I take Mega + GLCD, put it all togather write some code, all good until actual game start. Plugin had problems to connect, sometime it did, sometimes only few handshakes and nothing. Sometimes I got random disconnects and recconects between Arduino and KSP, like controls went out in middle of ascend, then was okay minute later. Tx blink, RX off with random blinks and so on. Tried different ports, buffer setting, serial speeds, no luck. After some time i figured out problem. It was "The Code". As Zitronen said, your code probably is too slow and arduino and kps get "desynchonized" and missmatch pakets of data. Graphic LCD, LCD, TFT displays and so on, is too much time consuming. Solution: Get rid of your LCDs or change code. It realy depends on where you put your code in original demo code. I recomend start by 3 leds, test it, then add display, test it. that is how i made it work. Now I have 4x20 LCD + LEDS + 6 Nixie Tubes driven by Atmega328 comunicate by serial with Mega. All works nice and well. Working on actual controls now. Hope it helps somebody

Yup, they are real. 170V power source needed Got them from old voltmeter many years back. Made in SSSR. Here in better light http://oi60.tinypic.com/o5yfld.jpg Two videos bonus. Short from space station in orbit http://tinypic.com/player.php?v=23h0qjp%3E&s=8#.VgBcU9_tlBf , second vid is launch of Saturn V http://tinypic.com/player.php?v=10nyznl%3E&s=8#.VgBdv9_tlBc Sound in background is little fan cooling switching transistor in 170V power supply.

Hey everyone. After few months VERY slow progress and strugle with KSPio and arduino, I am back here to show you some little of my work. KSP speedometer, "Retro" style. Do somebody like Nixie tubes? No enclosure/control panel yet so its bit messy In night it looks realy cool. Nixies are cool. And here short after launch of "Energia-SPB2" (SuPer Booster so its bit slow on start ) Its 100% custom build, drive code for arduino is from scratch (execpt of KSPio of course )Right now I am working on code optimalisation (for faster processing and make switch between orbital speed and surface speed) and now i can focus on another parts of project.

Yes i have it floating. I never connected Reset pin to anything. I read something about using capacitor on that pin to ensure correct function. I may give a try se what will happen. Btw i have only two buttons right now. Stage button wich is using internal pull-up resistor and menu change button (switch "menus" on GLDC to show different things) that use external pull-down resisor. EDIT: I just did test with capacitors and check wires and so on. No positive results at all. So little desperate i took prototype (with Mega) apart and build mini simple test platform based on uno. Just three leds, stage button, throttle pot. Upload code, do flights and guess what? no errors at all. All smooth all time. (for two hours of playing, we ll se later). So It ll be probably oveloaded mCU due to glcd or i dont realy know. I probably change "theme" of panel from modern with displays and nice light buttons to more retro (apollo) era with analog meters that dont eat my mCU to dinner doing calculations

it maybe case of overload arduino with to much work. But maybe not bcs sadly i run in com drops again and i didnt change anything. No code change or hardware change, just using my prototype. Its better then before bt still getting random drop. Even tryed change usb cable and port and same thing. Closely observing I found its completly random. Com drops during launch, deorbiting, orbital flight and work on orbit. It even happend when game is paused! I start thinks its more hardware problem related since i build it on bredboard. During testing i found when wire from push button isnt properly connected and ends "in air" arduino went crazy and block coms. When wire is connected to gnd or 5v (simulate push or release) in most cases it start working again. Disconect wire and bam, com drops. Is this can be issue? Like noise in wires bcs of not good connections on bredboard and jumpwires?

So I got my testing done. Changed refresh rate in config file one by one and come to 0.2 rate, same as Zitronen suggest and it has possitive results. No more drop outs. everytihng is smooth. So far done 4 flights ground-orbit-ground a 100% of time wokring. I am guessing its realy to much time consuming calculation for GLDC. It will need some heavy optimalisation bcs at this moment, I am refreshing and redrawing everything on it with each program cycle even when nothing change at all. Anyway, thank all for theyr suggestions and ideas. Hopefuly it ll work now and ever And when i get my prototype from breadboard to real control panel i definetly post some pictures

I read all from page 93 to end. But that isnt my issue since i got handshake and data. Maybe zitronen is right about code isnt able to keep up with plugin since most of time whe communication fail is during ascend or descend when game produce mist data (speed, alt and so on) But when ship orbits doing nothing then everything is fine. Most of time. when i come home i try to change refresh rate to be slower and see what happen.

Hello everyone! First thing, very much thanks to Zitronen for making such a amazing plugin/mod and thank to all who help make it even better. Its amazing thing, realy, I love it. And second thing, I need little help from you, experienced builders. As many of you, when i saw way of making physical control panel for ksp i simply couldnt resis and start making my own. Building stuff based on Arduino isnt something new for me so no prob here. I have my prototy build on Mega 2560 board with stuff on breadboard (prototype ). I got my 3 leds, stage button, throttle pot, graphics lcd as info panel. Well everything working well and smoth, control ok, info from ksp/plugin ok, BUT sometimes my comunication just went out from some reason. Green led go off, Tx led on Mega stop blink (Rx still blink), and all data stop go in and out. No controls, no info, nothing. Then sometimes and randomly Tx blink, green led went on, then go off again as no data come in. And weirdest thing is that sometimes I got comunication back complety so i can control/read data from ksp again. I tryed to lower bit rate from 115200 to 57600 and still same. Update rate is same (0.08). Any idea what can cause those com drops? I would love fix it and finalize my panel PS: If this problem is somewhere discused already, just punch me in face with link, but I am sorry i couldnt fine it. And i read all! Hell of reading 99 pages, belive me