Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GC closes unexpectedly after connecting to arduino in Win8 64 bit #750

Closed
raynerzed opened this issue Aug 11, 2018 · 9 comments
Closed

GC closes unexpectedly after connecting to arduino in Win8 64 bit #750

raynerzed opened this issue Aug 11, 2018 · 9 comments

Comments

@raynerzed
Copy link

GC 1.19 closes immediately upon connection to the arduino. Everything was setup correctly. Doesn't happen when changed version to GC 1.18

Linking the forum thread where everything is documented - https://forums.maslowcnc.com/t/groundcontrol-closes-unexpectedly-upon-connecting-to-arduino/5636/9

@blurfl
Copy link
Collaborator

blurfl commented Aug 11, 2018

Thanks for opening an issue on this. In the GroundControl folder within the GroundControl-Windows.Portable.v.1.19 folder you'll find a file log.txt. It would greatly aid troubleshooting if you could zip that and attach it to a post here. It should contain information about the cause of the crash.

@raynerzed
Copy link
Author

log.txt
Here you go :)

@blurfl
Copy link
Collaborator

blurfl commented Aug 11, 2018

Well_that's_ disappointing 🙁, no smoking guns... Here's something to try - disconnect the Arduino and start GC1.19 - does it stay running until the Arduino is connected, or crash before then?

@blurfl
Copy link
Collaborator

blurfl commented Aug 11, 2018

Good news, kind of - I'm able to reproduce this problem by flashing 'Blink.ino' and then the current firmware and removing groundcontrol.ini before starting GC.
This looks like the same issue as Issue #749 . When the new groundcontrol.ini file is created, the section for propweightz in [Computed Settings] is not created.

The quick-and-dirty workaround is to add this line to groundcontrol.ini at the end of the [Computed Settings] section.
'''
propweightz = 1

'''

@BarbourSmith
Copy link
Member

BarbourSmith commented Aug 13, 2018

Darn, sorry for really causing a mess here! I'll start looking into why this is happening right now. Any thoughts on what I did differently with this setting than the others?

Edit: I can reproduce the issue with traceback:

 Traceback (most recent call last):
   File "main.py", line 502, in <module>
     GroundControlApp().run()
   File "C:\Python27\lib\site-packages\kivy\app.py", line 828, in run
     runTouchApp()
   File "C:\Python27\lib\site-packages\kivy\base.py", line 504, in runTouchApp
     EventLoop.window.mainloop()
   File "C:\Python27\lib\site-packages\kivy\core\window\window_sdl2.py", line 663, in mainloop
     self._mainloop()
   File "C:\Python27\lib\site-packages\kivy\core\window\window_sdl2.py", line 405, in _mainloop
     EventLoop.idle()
   File "C:\Python27\lib\site-packages\kivy\base.py", line 339, in idle
     Clock.tick()
   File "C:\Python27\lib\site-packages\kivy\clock.py", line 581, in tick
     self._process_events()
   File "kivy\_clock.pyx", line 367, in kivy._clock.CyClockBase._process_events (kivy\_clock.c:7700)
   File "kivy\_clock.pyx", line 397, in kivy._clock.CyClockBase._process_events (kivy\_clock.c:7577)
   File "kivy\_clock.pyx", line 395, in kivy._clock.CyClockBase._process_events (kivy\_clock.c:7498)
   File "kivy\_clock.pyx", line 167, in kivy._clock.ClockEvent.tick (kivy\_clock.c:3490)
   File "main.py", line 341, in runPeriodically
     self.receivedSetting(message)
   File "main.py", line 301, in receivedSetting
     maslowSettings.syncFirmwareKey(int(parameter), value, self.data)
   File "C:\Users\Bar\Git\GroundControl\Settings\maslowSettings.py", line 628, in syncFirmwareKey
     storedValue = data.config.get(section, option['key'])
   File "C:\Python27\lib\site-packages\kivy\config.py", line 474, in get
     value = PythonConfigParser.get(self, section, option, **kwargs)
   File "C:\Python27\lib\ConfigParser.py", line 618, in get
     raise NoOptionError(option, section)
 ConfigParser.NoOptionError: No option 'propweightz' in section: 'Computed Settings'

@blurfl
Copy link
Collaborator

blurfl commented Aug 13, 2018

That PR looks like it is 'reversed' - the variable should not be deleted?

@BarbourSmith
Copy link
Member

I'm not sure I understand, which variable is it that is deleted?

@blurfl
Copy link
Collaborator

blurfl commented Aug 13, 2018

Sory, shouldn't be responding from up onm a ladder 😁
PR#747 changed main.py:199 to remove the propWeightZ. Could this be the cause of this issue?

@BarbourSmith
Copy link
Member

Directing software development from up on a ladder 😁

I think you are 100% correct. I've opened #753 to put the missing variable back in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants