-
Posts
692 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Everything posted by zitronen
-
@ajden It seems like all you need to do is send serial packets to the screen so not sure why it's not working. Do you have the source code so you can see what is actually happening in "genie.WriteObject()"? If it really is taking too long you can try reducing the refresh rate in the plugin cfg file. You can also use another arduino to handle the display and just send simple serial data from your main arduino to it.
-
@Scout1218 if you go to a electronics distributor like Farnell, Mouser or Digikey, you can find 7 segment LEDs of all kinds of colours. Also try "orange" instead of "amber".
-
[1.4] Wheels Collection (formerly rollkage & better wheels)
zitronen replied to zitronen's topic in KSP1 Mod Releases
This still works fine for 1.3, the original rollkage stuff might need some cfg updates. -
Just to confirm you are using COM9 for your arduino and you are using the demo16 arduino code? Do you see any serial rx tx lights flash on your arduino when you go to launch? I could be either your arduino is not receiving anything from the plugin or for some reason it's not sending the handshake packet. Maybe increase handshake from 2500 to 5000 in the settings file? "KSP Display" is just referring to your arduino. I called it a "display" because originally I made a display with mine. Maybe I should change it to something generic. Oh I just checked the first post, the "tutorial" still linked to the older demo13 version of the arduino code, you need demo16 for the current 0.19 plugin. No sure if this is the problem but I fixed the link now.
-
Hi Changine IDLETIMER is fine, it needs to be at least more than refresh time. Increasing handshake delay is also fine, the only downside is if you have lots of serial ports, the plugin can wait up to the delay for each port as it checks for a connection, so it can increase KSP load time by a lot. I don't know which screen you are using, but you also might try some of the fast tft libraries. Oh and ideally, you should put your code between case 1: // your code here break; you can also add something like case 0: //Handshake packet Handshake(); tft.print("connecting"); break; if you want
-
OK cool, but without seeing your whole code it's hard to say if you put it in the right place. Ideally you should put it in the outputs() function, which is run every 25ms by default if you want fast updates from axes controls: controlTime = now - controlTimeOld; if (controlTime > CONTROLREFRESH){ controlTimeOld = now; controls(); Serial1.println((long)VData.ECharge); } or in inputs() which is ran whenever a packet is received from KSP if (KSPBoardReceiveData()){ deadtimeOld = now; returnValue = id; switch(id) { case 0: //Handshake packet Handshake(); break; case 1: Indicators(); Serial1.println((long)VData.ECharge); break; }
-
You mean on a mega? You can't do it without software serial on a normal arduino. On a mega you can use Serial.print(), Serial1.print(), and so on. It will be much faster because they are hardware serial ports. There are also other arduino or teensy boards with more than 1 serial ports. But this is assuming your problem is caused by software serial.
-
Update 0.19.0: Changes: Fixed broken axis/SAS control issues reported by @Freshmeat and @#Pseudo Rebuilt against KSP 1.3 (previous version seem to work still, so this is just in case something changed) Download link: https://sites.google.com/site/zitronfiles/KSPSerialIO_019_0.zip This now becomes the recommended version.
-
If TT is smart, they should hire back the all the actual devs that quit squad after 1.2, and pay them properly. I would happily pay money for whatever DLC Harvester, Mu, Taniwha, NathanKell, Sarbian, Romfarer, Arsonide, Porkjet, and Claw comes up with.
- 772 replies
-
- 14
-
- kerbal space program
- take-two
-
(and 1 more)
Tagged with: