REDMOTE - update can't connect to Redmote to update

[roryhinds]

I'm trying to update my Redmote's but can't seem to connect to them anymore. I have connected to them many times in the past and updated their firmware with no problems but now am unable to make a connection on my Macbook Pro.

Redmote is running 4.0.4
Redmote upgrade software is 24
MacBook wireless airport is turned off. Redlink is turned off on Redmote.
I can see the RNDIS Gadget in the Network and the IP is Self Assigned and when I open the Redmote Upgrade application and try connect I get nothing.

This is happening on both my Redmote's

I tried installing the Redmote upgrade app on Window 7 but can't install as it has "Error opening file from writing" linux.inf

 

[Mark Britton]

When installing REDmote_upgrade_setup.exe on Windows 7, right click the installation executable and choose "Run as administrator".

 

[Michael Lindsay]

Are you using the latest MacBook pro with usb3? I had a problem and had to switch to a 17inch Macbookpro fe the redmote..

 

[roryhinds]

Cool, thanks for the Window7 tip, I'll give that a try.

No I'm not on a USB3 Macbook Pro and am using my old 2007 MacBookPro that I have been using all along and never had any issues updating the firmware on the Redmote.

 

[roryhinds]

Well I got the update installed on Window 7 but still am unable to connect to my RedMote's.

Frustrating as its stopping me from getting on the latest Epic firmware

 

[Trent Lillehaugen]

Well I got the update installed on Window 7 but still am unable to connect to my RedMote's.

Frustrating as its stopping me from getting on the latest Epic firmware

Did you download the latest REDmote upgrade utility from the RED website?

Do the REDmotes charge when you plug them in via USB?

Did you disable all networks? The REDmote sets up a 192.168.0.xxx network wich will conflict with many home networks.

You said your REDmotes are running 4.0.4? That is compatible with Epic version 3.3.x

 

[Richard Andrewski]

I have the same problem. Was going to report it then saw this thread. Update utility is the latest (V 33) from DSMC utilities download. Installed fine on Windows 7 on two different computers and I even uninstalled, redownloaded and re-installed again and still doesn't work. Tried different USB cable, etc. The current version of the Redmote is 4.04 and I have updated the redmote at least two times prior so it was working. When plugged into the USB, it is recognized by Win 7 computer (device drivers load for "linux device" or something like that) and also the battery does charge on the redmote when plugged into USB.

Tried on both computers to connect and it never does connect, just sits there waiting and waiting. Tried multiple times on both computers and nothing. Redmote appears not to work wirelessly anymore either but does work when plugged in to back of Epic. When using the pairing function of the EPIC, I can get the Epic to see the Redmote but the Redmote won't do its part to connect with the Epic.

 

[roryhinds]

Did you download the latest REDmote upgrade utility from the RED website?

Do the REDmotes charge when you plug them in via USB?

Did you disable all networks? The REDmote sets up a 192.168.0.xxx network wich will conflict with many home networks.

You said your REDmotes are running 4.0.4? That is compatible with Epic version 3.3.x

Hi Trent

Yes I downloaded the latest version of the upgrade utility.
Yes the Redmotes charge when plugged in.
Yes I disable all networks, as mentioned I have upgraded the Redmotes many times before and thought I know what I was doing as it worked with no trouble before.

With the new Epic firmware there is new firmware for the Redmote so I like too keep them both uptodate to avoid any issues.

Seems I'm not the only one having this issue as Richard reported.
I'll check the Redmotes still work with my cameras in the morning.
I had issues with them loosing connection on my last shoot and I was standing right by the camera so I do hope the new firmware fixes this.

 

[alexx_hg]

Same problem here. updated first and it worked. After having some hiccups with redmote after update (RM freezes and I have to restart redmote, than it worked) I wanted to reinstall the update, but can´t connect anymore to my win7pc.
The linux drivers USBEthernetRNDIS is activated in the network panel, Redmote charges, latest RedMote upgrade.
(network is 192.168.1.xxx, never had to disable, but tried, no success)

please

bg
alex

 

[roryhinds]

As both my Redmotes are behaving the same problem with the inability to connect and update and others are reporting the issue it makes me think that perhaps something broke the linking connection to the Redmote with the last update 4.0.4.
My question would be if that is the case and we have no way of connecting to the Redmote for updates then we're kind of screwed, yeah?

 

[Trent Lillehaugen]

As both my Redmotes are behaving the same problem with the inability to connect and update and others are reporting the issue it makes me think that perhaps something broke the linking connection to the Redmote with the last update 4.0.4.
My question would be if that is the case and we have no way of connecting to the Redmote for updates then we're kind of screwed, yeah?

I have not seen this problem with any of the REDmotes here - it does not appear to be a systemic problem with 4.0.4

To answer your second concern you will be able to upgrade REDmotes through the camera instead of USB with future camera builds (it will just take much longer).

 

[roryhinds]

Thanks Trent, its great to know you'll be able to update the Redmote directly on the camera.
Do you know when this feature will be available?

Is there anything I can do to help to get this issue of not being able to connect resolved?

 

[Trent Lillehaugen]

Thanks Trent, its great to know you'll be able to update the Redmote directly on the camera.
Do you know when this feature will be available?

Is there anything I can do to help to get this issue of not being able to connect resolved?

This feature should be available with the next major release after 3.3

If you haven't already, please open a support ticket.

 

[roryhinds]

Thanks Trent I'll do that now.
Can Support refer to this thread as I try avoid repeating myself as much as I can

 

[Philip Lima]

I was having similar issues. I have used my same laptop for months up update our REDMOTE and has always worked perfectly until today. I did also just upgrade to 10.8 though, so maybe the updater isn't fully compatible with mt lion yet?

 

[Russ Fill]

Have any of you updated any OS on your computers lately.

 

[roryhinds]

No no updates here. As mentioned before I have been using the same MacBookPro 17" to do all my updates to my Redmote's and not had issues with it in the past and have done it many times before.

 

[Mark Britton]

I actually can't get my REDmote to connect with my Windows 7 workstation either. Installing on my Windows Vista laptop (never mind why I still keep the old dog around) worked fine when I last updated. Soo...I did some poking around.

Looking closer after installing REDmote Upugrade Utility from DSMC Resources v3.2 on Windows 7...when I look at the "Show Details" option at the "installation complete" dialog, there is an error message in the log:

Output folder: C:\Program Files (x86)\REDmote
Extract: linux.inf... 100%
Extract: libgcc_s_dw2-1.dll... 100%
Extract: mingwm10.dll... 100%
Extract: QtCore4.dll... 100%
Extract: QtGui4.dll... 100%
Extract: QtNetwork4.dll... 100%
Extract: Redmote.exe... 100%
Extract: red.ico... 100%
Output folder: C:\Program Files (x86)\REDmote\imageformats
Extract: qico4.dll... 100%
Windows Version: 7
Updating the driver...
Driver update has failed. (7:0,-536870347)
Installing the driver... (C:\Program Files (x86)\REDmote\linux.inf, C:\Program Files (x86)\REDmote)
Created uninstaller: C:\Program Files (x86)\REDmote\Uninstall.exe
Create folder: C:\Users\Mark\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\REDmote update
Create shortcut: C:\Users\Mark\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\REDmote update\REDmote_update.lnk
Create shortcut: C:\Users\Mark\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\REDmote update\Uninstall.lnk
Completed

I'm not certain that is a cause or a symptom, but perhaps that is of interest for debugging.

Poking around further with the USB Etherenet/RNDIS Gadget installed (and my NIC ports disabled), I noted that it was NOT actually using an address in 192.168.0.xxx range:

Windows IP Configuration




Ethernet adapter Local Area Connection 4:


Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::65a9:3779:42d2:f951%18
Autoconfiguration IPv4 Address. . : 169.254.249.81
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :


So...I poked further. Dug into the network properties for the RNDIS device. Brought up Internet Protocol Version 4 (TCP/IPv4) properties window that corresponded with the RNDIS device as installed on my PC. Selected "Use the following IP address" entry and manually entered 192.168.0.1 for IP and 255.255.255.0 for subnet mask.

Bam. REDmote connected to my Windows 7 workstation in an eyeblink when I clicked the Connect button on restarted REDmote Upgrade Utility instance.

Apologies if this is a bit of a rambling mess, but there might be something of use to someone at RED or other people experiencing difficulties, so, post it I shall.

 

[George Tsai]

I actually can't get my REDmote to connect with my Windows 7 workstation either. Installing on my Windows Vista laptop (never mind why I still keep the old dog around) worked fine when I last updated. Soo...I did some poking around.

Looking closer after installing REDmote Upugrade Utility from DSMC Resources v3.2 on Windows 7...when I look at the "Show Details" option at the "installation complete" dialog, there is an error message in the log:

Output folder: C:\Program Files (x86)\REDmote
Extract: linux.inf... 100%
Extract: libgcc_s_dw2-1.dll... 100%
Extract: mingwm10.dll... 100%
Extract: QtCore4.dll... 100%
Extract: QtGui4.dll... 100%
Extract: QtNetwork4.dll... 100%
Extract: Redmote.exe... 100%
Extract: red.ico... 100%
Output folder: C:\Program Files (x86)\REDmote\imageformats
Extract: qico4.dll... 100%
Windows Version: 7
Updating the driver...
Driver update has failed. (7:0,-536870347)
Installing the driver... (C:\Program Files (x86)\REDmote\linux.inf, C:\Program Files (x86)\REDmote)
Created uninstaller: C:\Program Files (x86)\REDmote\Uninstall.exe
Create folder: C:\Users\Mark\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\REDmote update
Create shortcut: C:\Users\Mark\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\REDmote update\REDmote_update.lnk
Create shortcut: C:\Users\Mark\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\REDmote update\Uninstall.lnk
Completed

I'm not certain that is a cause or a symptom, but perhaps that is of interest for debugging.

Poking around further with the USB Etherenet/RNDIS Gadget installed (and my NIC ports disabled), I noted that it was NOT actually using an address in 192.168.0.xxx range:

Windows IP Configuration




Ethernet adapter Local Area Connection 4:


Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::65a9:3779:42d2:f951%18
Autoconfiguration IPv4 Address. . : 169.254.249.81
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :


So...I poked further. Dug into the network properties for the RNDIS device. Brought up Internet Protocol Version 4 (TCP/IPv4) properties window that corresponded with the RNDIS device as installed on my PC. Selected "Use the following IP address" entry and manually entered 192.168.0.1 for IP and 255.255.255.0 for subnet mask.

Bam. REDmote connected to my Windows 7 workstation in an eyeblink when I clicked the Connect button on restarted REDmote Upgrade Utility instance.

Apologies if this is a bit of a rambling mess, but there might be something of use to someone at RED or other people experiencing difficulties, so, post it I shall.

Awesome thanks for pointing this out! I was having problems connecting in my windows 7 where prior upgrades worked without a hitch. After reading your post I manually changed the IP too and it instantly picked it up and upgraded without a problem

 

[Trent Lillehaugen]

Mark, thanks for posting your work-around, we are in the process of preparing official work-around instructions along with a new REDmote build that won't require the work around any more. I would like to stress that if anyone follows these instructions they should return the network setting back to DHCP after we release a fixed REDmote build.