NEED HELP HAVE BRAND NEW 0.6.0 FIRMWARE

[TeakRaindrop138]

2 yellow one red one green

 

[CharlieKeck]

2 yellow one red one green

That is exactly what you want on the Solo. The two yellow go blue when GPS locks and that means it's armed and ready...did the controller update?

 

[TeakRaindrop138]

No to the controller

 

[CharlieKeck]

No to the controller

Crap - so the SCP to upload the controller failed? Did you do the secondary step involving using PUTTY to issue those "sololink ..." commands?

 

[CharlieKeck]

Crap - so the SCP to upload the controller failed? Did you do the secondary step involving using PUTTY to issue those "sololink ..." commands?

So close now...the Solo is clearly correctly updated.

 

[TeakRaindrop138]

That is exactly what you want on the Solo. The two yellow go blue when GPS locks and that means it's armed and ready...did the controller update?

It will say paired

Crap - so the SCP to upload the controller failed? Did you do the secondary step involving using PUTTY to issue those "sololink ..." commands?

I'm good but not putty good I gave up yesterday I've been on this for 4 days now my adhd I'd gone through the roof lolz

 

[CharlieKeck]

It will say paired

I'm good but not putty good I gave up yesterday I've been on this for 4 days now my adhd I'd gone through the roof lolz

LOL!! You're really close - I'm reviewing those UPDATE VIA SCP commands now - I've literally done this at least 20 times with no issues...let me review them...BRB. If you want to stick with this I'm totally with you here.

 

[CharlieKeck]

LOL!! You're really close - I'm reviewing those UPDATE VIA SCP commands now - I've literally done this at least 20 times with no issues...let me review them...BRB. If you want to stick with this I'm totally with you here.

1. SSH into the controller with IP 10.1.1.1, username root, password TjSDBkAu
2. # sololink_config --update-prepare sololink cleans up and prepares the directories.
3. Copy 3dr-controller.tar.gz and 3dr-controller.tar.gz.md5 to the /log/updates directory on the controller.
4. # sololink_config --update-apply sololink --reset executes the update and reboots.

This should just work.

 

[TeakRaindrop138]

LOL!! You're really close - I'm reviewing those UPDATE VIA SCP commands now - I've literally done this at least 20 times with no issues...let me review them...BRB. If you want to stick with this I'm totally with you here.

Brother if keen to help this slow fucker how to get her done I'm keen aa mustard

 

[CharlieKeck]

Trust me - that sequence works...you did it on the Solo!

 

[CharlieKeck]

Trust me - that sequence works...you did it on the Solo!

When in PUTTY, does it accept the sololink commands? No funky error messages or shit like that?

 

[TeakRaindrop138]

When in PUTTY, does it accept the sololink commands? No funky error messages or shit like that?

Not there yet had to make some concentration juice just turned her on

 

[CharlieKeck]

Not there yet had to make some concentration juice just turned her on

Gotcha - stupid question, but you know that you don't enter that '#' they show before the sololink command? That has screwed many and I don't know why they haven't fixed that in github!

So the first PUTTY command is : sololink_config --update-prepare sololink

 

[TeakRaindrop138]

1. SSH into the controller with IP 10.1.1.1, username root, password TjSDBkAu
2. # sololink_config --update-prepare sololink cleans up and prepares the directories.
3. Copy 3dr-controller.tar.gz and 3dr-controller.tar.gz.md5 to the /log/updates directory on the controller.
4. # sololink_config --update-apply sololink --reset executes the update and reboots.

This should just work.

So trying to get into 10.1.1.1.1via my laptop but I can't seem to find it or anything

 

[CharlieKeck]

So trying to get into 10.1.1.1.1via my laptop but I can't seem to find it or anything

The laptop WiFi must be connected to the controller. You run WINSCP, that's where you get into 10.1.1.1. That will give you access to the file structure in the controller.

The sololink commands are issued from PUTTY, accessed in the top row of WINSCP icons. You have to log in to PUTTY the same way as logging into WINSCP.

 

[TeakRaindrop138]

The laptop WiFi must be connected to the controller. You run WINSCP, that's where you get into 10.1.1.1. That will give you access to the file structure in the controller.

The sololink commands are issued from PUTTY, accessed in the top row of WINSCP icons. You have to log in to PUTTY the same way as logging into WINSCP.

Do I need to download this WINCSP

 

[CharlieKeck]

Do I need to download this WINCSP

Yes - WINSCP is a Windows app required for all this. PUTTY is embedded within.
---------------------------
We may be going down a rat hole now. Let me ask if you ever got SOLEX and the controller linked up? It's so much easier to do from SOLEX. Let's do that SOLEX should see the controller's WiFi hotspot.

 

[TeakRaindrop138]

Yes - WINSCP is a Windows app required for all this. PUTTY is embedded within.
---------------------------
We may be going down a rat hole now. Let me ask if you ever got SOLEX and the controller linked up? It's so much easier to do from SOLEX. Let's do that SOLEX should see the controller's WiFi hotspot.

Have solex app WiFi works in it bit doesnt connect the vehicle to the app connects to the controller iv got it all downloaded and ready to go

 

[CharlieKeck]

Have solex app WiFi works in it bit doesnt connect the vehicle to the app connects to the controller iv got it all downloaded and ready to go

OK, if SOLEX and the controller are talking, have you previously downloaded the Open Solo for controller file, using your home WiFi, as you have to switch back and forth between home and the controller wifi.

 

[CharlieKeck]

OK, if SOLEX and the controller are talking, have you previously downloaded the Open Solo for controller file, using your home WiFi, as you have to switch back and forth between home and the controller wifi.

Here's the 64K question: where do you live?