|
It is currently Sun 24. Nov 2024 20:05:28
|
View unanswered posts | View active topics
|
Page 1 of 1
|
[ 7 posts ] |
|
Author |
Message |
rcarson
|
Posted: Fri 17. Apr 2020 18:21:30 |
|
Joined: Thu 01. Oct 2015 20:21:02 Posts: 6
|
I updated my spirit red to 3.0. Followed instructions to revert back to 2.8.
As a consequence, my spirit red will not bind any longer. (I selected DSM2/X in my PC computer software)
Why did this happen? How can I fix it.?????
|
|
Top |
|
|
Fortune7
|
Posted: Fri 17. Apr 2020 19:15:25 |
|
Joined: Tue 21. Jan 2020 11:28:04 Posts: 78
|
Hi Tomas,
Sorry to say I am having the same issue: reverting from v3.0 to v2.8 today and the receiver is not communicating with the μSpirit unit, with SRXL2 protocol.
My setup: μSpirit with Spektrum AR6610T, using the appropriate connection (signal to AIL pin, power via RUD port). The setup was working ok with V3.00, though not yet flown - it is a new TREX 300X heli and μSpirit unit setup. After several re-binding and re-initialisation attempts with v2.8 firmware and software, and checking the continuity of the SRXL2 signal wire between the unit and receiver with no improvement, I went back to v3.00 software and firmware and all functions work from transmitter. This does not appear to be a receiver binding problem but a Rx/unit communication issue. At every stage I made sure the Spirit settings were at 'SRXL2" option.
When I received my (2) new μSpirit units last week I didn't operate with 2.8 software / firmware, but chose to update to v3.0 immediately as it became available. It was working as expected (again setup only, not flying yet) until today when the advice was to revert to 2.8, so I can't confirm the setup worked on v2.8 with this unit.
I hope this helps with diagnosis, and with thanks to you as always for your excellent customer service here. Things go wrong, especially with new software, but it is the speed and openness of response which matters greatly. Keep up the good work!
Cheers, Andy UK
|
|
Top |
|
|
igloo
|
Posted: Fri 17. Apr 2020 21:12:04 |
|
Joined: Sun 03. May 2015 16:56:24 Posts: 45
|
I don't know for yours but when I went back from the 3.00 to the previous 2.80 release, I was firstly asked by the system to go back to the 1.3.2.4 release (and provided by the system) before to be able to flash back to the 2.80. Once done, the module did not work because was reset to the factory standard (no bus). After having reloaded the banks I saved from the 3.00 version before, the module works as expected.
|
|
Top |
|
|
rcarson
|
Posted: Fri 17. Apr 2020 21:54:54 |
|
Joined: Thu 01. Oct 2015 20:21:02 Posts: 6
|
I tried that also. However I only had the 3.0 firmware. The 3.0 Spirit Windows operating download is not available. (I should have saved it to my files.)
|
|
Top |
|
|
ZeXx86
|
Posted: Sat 18. Apr 2020 15:31:24 |
|
|
Site Admin |
Joined: Mon 29. Apr 2013 16:06:44 Posts: 12442
|
Full support for AR6610T was introduced in version 3, so it might not work with 2.8 unfortunately. You can use version 3 or wait for new update few days.
_________________ Spirit System developer
|
|
Top |
|
|
rcarson
|
Posted: Sat 18. Apr 2020 15:45:05 |
|
Joined: Thu 01. Oct 2015 20:21:02 Posts: 6
|
can you provide a link to 3.O for Windows? (I did not save it to my PC)
I have the 3.OV firmware.
|
|
Top |
|
|
igloo
|
Posted: Sat 18. Apr 2020 16:43:20 |
|
Joined: Sun 03. May 2015 16:56:24 Posts: 45
|
|
Top |
|
|
|
Page 1 of 1
|
[ 7 posts ] |
|
|
Who is online |
|
Users browsing this forum: No registered users and 51 guests |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|