Mattew

Yeah yeah. I dont just know right words for it Otbit/surface/target. That thing you change by clicking on green speed number on top of navball.

One detail I just find out. Can we get way to change "vector reference" ? I mean if prograde/retro is relative to orbit or surface or target. That would be awesome then.

Well then I link picture of somebody's controler. Look at top left corner. SAS Mode selector! This guy / girl have it even before we have "own code" for it I definetly will add something like that.

Oh, good job! So if I understand that correctly, each mode is called separately on its own. If we want be simple as possible then we need just 10 switches (for each mode) and thats it?

Okay, dumb question SAS mode changes work in way I just change SASMode byte while SAS is active,is that right? Example: Activate SAS mode by button on SASPIN, then in some convenient place in code I do "SASMode = 8" and whoala, my sas is set to "target". I do it right? I dont have time to actualy test in real :/

IT. IS. Happening! SAS modes! Just when i start research on how to implement it by myself. Realy, I love you guys

This is 100% behavior of kspio on w10. LED turn on and off during loading and thus plugin start means your arduino recived handshake (like "hey, are you KSP Display?") but whatever reason on win10 even your display respond correctly ("yes I am KSP Display") plugin will ignore it. Sadly no permanent fix atm. Workaround 1: disable handshake and only recive data. Workaround 2: get ch340 usb-ttl convertor (1$ on ebay) Aaaah, sad to hear. I was interested more in your work. Realy cool stuff! About SAS mode and etc. Here is link to topic about "same" issue. Somebody try to make keybinds. I am not expert but i belive those exact commands could be impleneted and send in packet by ksoio. Looks simple enought

Didn`t Stibbons have some vectoring stuff for his navball? Maybe he can enlighten us about it. I would like to know more too Anyway, having more stuff is always nice (docking aid would be cool, but again, it only about target vectors. Damn vectors! ), but having more you need more compute power and also something to show that info. Not all the time you need all the info.

That is weird. Unmodifed Demo and without any more hardware should work and not lag behind. I am using Mega as "The Gateway" for whole control panel and main process unit and I fixed lag issue long before and far away. Try increase that buffer (mentioned in first post) and for testing purpose you can change refresh rate to something crazy like 1 second or more. 1sec is loooooots of time for any mCU to do stuff. My guess KSPDemo get executed like 10,000,000 per second I think increasing speed of Gateway mCU is kind of pointless atm for purpose faster data transfer PC <--> Arduino. EDIT: About that Test tool. I forgot that normaly you cant change bound rate within program itself. If you want change it, you must find config file in source files of tool, change value and recompile tool again

It looks like code desync to me as it happed several ppl (include me) here. In short term, arduino is taking to much time to do stuff and cant keep up with data input and thus it stop talk to KSPIo. What do you have connected to your Arduino? Only 3 leds as demo? You may try increase bound rate or lower refresh rate at least for test purpose. Also I recomend for this kind of testing awesome TOOL HERE by @KingLuxor

DEV version of KER for 1.2 is aviable. So far its working but watchout for bugs of course since it is dev version.

Yeah totaly. I should take my head of clouds and go back to ground, that means stop thinking about 17" touch lcds and fancy stuff and be more realistic with leds and analog meters. I think we are not here to build precise spaceship simulator I stick to DUE as best what i can achive to get it work one day. To all of you who can do 3D navballs and such stuff that is realy cool work, very nice Edit: Question for navball experts. How do you get data where ship points relative to any nav node? I know we have pitch/yaw/roll data of ship. I am asking bcs i got idea about very simplified linear "navball" (for us non experts ) that could tell you if you point to desired navpoint or not

Why not just then use raspberry pi or beaglebone if you need so much compute power? 1Ghz clock and tons of ram and storage space

I probably got what do you think. Adding more stuff to control panel means adding more compute power to it as well. It probably mostly depends on what type of CP you are building. And thinking of it we, have four styles of panels at moment 1. Apollo era - lots of buttons, switches, analog meters, almost none digital devices. 2. Early (1980) Shuttle - its kind of Apollo style with some more lcds and digital tech. 3. 2000+ Shuttles, Soyuz, other active spaceships - modern looking, many lcds, fewer switches and analog devices. 4. Future, sci-fi style - probably CP with touch lcds and other fancy stuff and eye candy. Here i found some very nice LCD screens from shuttle showing information of all kind. For inspiration That thing about data packet size and sram. I belive that suggestion was there few post back, but good way how to make it would be like do Lite version (one 255 packet) and Full version having 2x255 packets or so, for ppl with fancy powerful hardware able to handle it (Dueeeeee ) Or maybe be able to chose data what you want send in packet. For instance, i dont use like 40% of incoming information in packet atm (useless to me) . Suggestions? Edit: So I decided to use DUE as well. It will be more helpful here in KSPio CP then my other project. Lets call some kerbal engineers here and get to work, maybe Bill Kerman will know. Bill, hey Bill, how we control that sweet 9" 800x600 touch lcd ??.....

I can confirm fully fumctionality too. At least for my controler. Also with CH340 module no issues. I noticed way quicker KSPIo start when going to pad. We have somechanges in that matter or it's KSP itself? Regarding Due/Mega discussion. At what point is realy worth to use a Due insted of more common Arduino board? I mean what kind of hardware and how much of it can be run by Mega and when it stop to be enough horsepower?

Yeah true enought In past I did test 2,2" tft showing simple text and graphs fot fuel etc. and Mega handle it okay. Due is required for more fancy graphics or animation if we talk about lcd's. I wish that we can handle big lcds in smoth way. I have 15" panel from notebook here but 0.2 fps or less insn't good at all. Oh damn you! I start thinking about getting Due insted of Mega for my final version too

Isn't Due kind of overkill for such project? If you dont use things like lcd's, monitors and such things required high compute power then Uno/Mega should be fine, right? I have Due here sitting and waitng for my lcd to come for other project. Never think of using it for KSPIo. Too much horsepower

Now littla noob question from me since I am not expert on these communications, we cant just add another 255 bytes? like send two packets ot something like that? On that splitting data to diferent arduinos, I did and I am using kind of such thing. More hardware based. My Mega2560 is acting as main board and there is little instruction that take speed data, save it as unit_32 value and then send over RX1,TX1 to UNO board which is acting as control procesor for nixie tubes. I like that concept so much that Iy plan to create for each function (displays, nixies, controls) to have its own processor . Sound good.

Oh yes, its someting realy missing But isnt we running out of space in data packet? Edit: Anyone else already got CH340 module and test it? So we can finaly for 100% said where is issue with W10 and KSPIo

wait a minute, we have new ksp version, why nobody told me?:D Behold of more broken mods

None (or W10 found some on its own, not sure now). I didnt instal anything related to CH340. Plug n Play Yup, exactly as you said. I just dont used arduinos usb as power source. Idk what happen if both Atmega16U2 and CH340 will be present during handshake. For code, there are no modification at all. Technicaly this is only hardware change.

Okaaay. Just finished tests with my control panel + CH340. I had no issues so far, everything works as expected. Connection is fine. Recived and transmited data are okay too. I think we can say that problem is in Atmega16U2 chip or its drivers. That isn my expertise so I cant say why is that. If anyone strugling in Win10 with his or hers custom control panel and dont want wait for fix (or maybe it wont be even possible to fix) you can get same USB-TTL-Thing as me.

Just sit tight with me and have fingers crossed. I ordered from ebay that USB-TTL module with CH340 chip and REALY hoping it will work. I am guessing 10-14 days until it arrives so lets wait. EDIT: So today i got a little surprise from ebay. That USB-TTL module actualy come TODAY! unbeliveable. But sadly i am not home and cant do serious testing. Buuuut i made quick test (Uno with KSPIODemo13) and comunication was handled by CH340 convertor insted of Uno`s on board Atmega16U2. And guess what? IT WORKS ABSOLUTLY PERFECT! Yes, KSP IO pluggin is working under Win10 with no issues (kind of). I got communication both ways, in and out. I got throttle from uno board even when there werent any controler (probably getting false signals on unconnected analog input) and it was seen in game on actual throttle. From those few short test I didnt lost comunication with board and seem absolutly fine. I will get home tomorow and ll be able to run some full test, especialy connect my full control panel using CH340 and see how it goes. Probably run some quick Mun mission and see if it will held up whole time with no issues (I guess it will be ok). So long story short, Win10 have issues comunicate over Atmega16U2 but CH340 run fine. I hope it will some of you more experianced guys (or girls) some idea how to fix code insted of telling ppl to go buy CH340 TTL module.

Well that maybe it since I just disable HandShake in config file of pluggin itself and not bother with code at all. I ll try that. I can do some testing, I ll check it out and see it that will work, since it looks like some good solution is faaar away. Well it maybe go somewhere, since today when i was googling for issue i came over this video Windows USB Serial COM port driver bug and guy there did some tests where UNO r3 with its ATmega16U2 as USB-to-serial have issues but Duemilanove with FTDI USB-to-TTL works fine. Maybe WCH340 works too since its "hardware" convertor opposite ATmega16U2 "software" based convertor? I assume that basic USB-to-TTL convertor based on WCH340 or similar chip connected to arudino TX RX lines and bypassing its original ATmega16U2 in theory could do the trick. Thinking of buying it and testing it. Or Uno with WCH340, but its 3 week for something to come from ebay xD Edit: Found this thing on Ebay CH340G USB-TTL Convertor . Cheap too.

Hey guys and girls, any news on W10 issue? It realy sad not to use my control panel since even with handshake disabled it wont work (connect, disconnect, connect disconnect...). I Didnt found any solid information about usb win10 problems, only found out that MANY ppl with arduino and other custom hardware using usb for communication have big problems with connection.