mkovalcson
1 September 2016 12:4301.09.2016 12:43
The issue I started with was that I couldn't get my NEO to drive my servos.
I saw the earlier issue suggesting that I start a configuration from scratch through to Finish.
I loaded a fresh configuration and configured it from scratch rather than using a preset.
I've tried that a few times now.
Now I see 2 additional issues.
1. It no longer sees the UDI input from the Jeti R3 which was working for the last few days.
2. It doesn't remember the configuration I gave it.
When I hit the finish button in the software I exit the software and unplug power from the NEO.
When I power it back up it no longer has the last configuration I gave it.
I have the same problem now if I load a preset. I can see all the configuration changes until I power the NEO down, then it forgets the new configuration.
Eddi E. aus G.
1 September 2016 13:2001.09.2016 13:20
Hi,
very strange. Did the NEO have a mishap in the past?
I guess it's better to have it checked at our service shop, please open a service case at www.vstabi.info/devices, the button in the column 'Service'.
Kind regards
Eddi
Born to fly ...
forced to work.
mkovalcson
1 September 2016 14:0801.09.2016 14:08
This NEO is brand new and just came out of the shrink wrap last week and has only been on the bench.
I registered it last Saturday September 27, 2016 and updated it to Pro + Rescue a few days ago.
I have a keyed JST to Servo connector so the 2S battery can't be plugged in a way to hurt the NEO.
To my best knowledge nothing has been done that could hurt it.
I created a Ticket and received an RMA email with attached PDF
Am I shipping this to Germany or Mikado USA ?
1 mal bearbeitet. Zuletzt am 01.09.2016 14:24 von mkovalcson.
mkovalcson
3 September 2016 12:2903.09.2016 12:29
I thought I had this figured out.
I reset my NEO to Express
Configured it from scratch to Finish
Updated it to Pro + Rescue
Finished configuring it.
It talked to my R3 again and it controlled the servos.
Then I had issues with the software recognizing the configuration on the NEO.
I found the following seemed to work.
I powered up the heli.
I connected the USB to the laptop
I started up the software and it recognized the configuration reliable.
So far so good...
Then I configured it to map the pitch to the throttle.
That worked.
I got my Kosmik configured.
From that point on I can no longer change the configuration on the NEO with the configuration software.
How do I get the Configuration software to recognize my NEO again?
1 mal bearbeitet. Zuletzt am 03.09.2016 12:58 von mkovalcson.
ulrich
3 September 2016 15:1203.09.2016 15:12
This sounds like a random effect. No idea why it shall happen at this point.
Maybe t has some serious defective USB, or there may be some software on your PC intefereing with the USB. Do you have the possibility to try on a different PC? Maybe some Anti Virus Software?
so long ... Uli
http://www.vstabi.de
mkovalcson
3 September 2016 19:4003.09.2016 19:40
Interestingly enough I thought the same thing when I was out hiking this morning :-)
My laptop is getting old and has very little installed on it, and I did turn off the anti-virus software on it.
However the left port I was using was a USB 1.1 port. On the back of the laptop are USB 2.0 ports.
I just plugged it into the USB 2.0 port on top of my development system and it has been connecting reliably so far.
I think I let frustration get the best of me on this issue!
Fingers crossed it will be smooth sailing going forward!