![](https://forum.kerbalspaceprogram.com/uploads/set_resources_17/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
![](https://forum.kerbalspaceprogram.com/uploads/set_resources_17/84c1e40ea0e759e3f1505eb1788ddf3c_default_photo.png)
brndonaut
Members-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Everything posted by brndonaut
-
That was exactly it. Actually i re-downloaded, but i still had the previous version in my download folder and extracted that instead. So a big pebcak there from me In addition: when i refactored my arduino code, i moved the initTxPackets() function, still with CPacket.id = 1; instead of = 101; So there were two mismatches. It's working now and i can go back to further implement my buttons. Thanks for the quick help, everyone
-
Big thanks for pointing that out. Looks like something is wrong with my arduino code. Though i can not figure out what right now. With Demo8-Code, my controls are working, with my code, the indicators are working. Guess i have to merge that now somehow... Back to the drawing board for me Thank you, for your help.
-
Thanks for your reply. It's greatly appreciated. I've downloaded the version 0.15.3 from your first post (recommended stable), with the corresponding demo8 arduino code, that i used as a base for my code. I am using the same version with my 0.23.5 setup, where everything works fine. Is it possible, that another mod causes this behaviour? If so, how do i check? What can i do to help you helping me?
-
Hello, First of all: Thanks for your plugin. It really brought me into tinkering with microcontrollers and serial communication. Now to my problem: Is your mod working with 0.24.2? I experience the same issue Mulbin had. With 0.23.5 Everything works as intended, as soon as i fire up my 0.24.2 i get the "RX constantly flashing, TX dead" behaviour that is described earlier in this thread. I tried the following: Removing all mods except KSPSerialIO Changed the delay in the config (up to 40 seconds, confirmed new value via debug-console in main-screen) Changed baud-rate Changed value of #define IDLETIMER Changed value of #define CONTROLREFRESH Tried 0.24.2 32bit and 64bit I receive the message, that the COM5-port is used (correct port), as soon as the scene is loaded and then the RX-flashery starts. Here is the KSP-Log of my (unmodded) 0.24.2 Game: http://pastebin.com/hFqVR3Tk Any hints on what this may cause? Any help is really appreciated