Flexy 205 with serial card connecting to Mitsubishi A1S

Hi Tim,

This is what I see. I just updated the firmware so it may have changed from yesterday.


I’ll need to check with a colleague in Belgium tomorrow morning and see what I can find out about adding gateways without a Pro account.

Can you go onto eBuddy and go to the firmware upgrade section and change your firmware to 14.0s2 and see if that makes a difference? My colleague said there seems to be some kind of issue with USB connections in the 14.1 firmware. He was saying that you shouldn’t need to do anything on eCatcher though and it should show up automatically.

I’m on it…

Oh sorry about that, my colleague that mentioned this thought was currently possible. If it’s getting that error, the only way to downgrade the firmware is the recovery procedure described in the post below.

Just in case you may also want to take a backup of the device before you do this.

Thank you Tim. Unfortunately I have to send this unit to a customer today so we will have to pick this back up when I get the unit returned. Thank you for your help so far and I’ll let you know when I get it back.


Ok sounds good. I’ll leave the ticket open for now then until you get back to work on this ticket

Hi Tim,

We sent the Flexy to a customer. I set up the wifi network to connect to theirs when it got there. Now when they plug it in there are not light lit on the wifi card. What do you think is wrong? Is there anything we can do without being


If it’s setup to connect on their wifi network the only thing I can think might be wrong would be if they’re blocking UDP port 1194, TCP port 443, or blocking openVPN with a firewall such as sonicwall.

Was the device setup for static or DCHP WI-FI connection? If you know the IP address it should be getting you could have their IT team take a wireshark capture and look if there’s anything blocking the device.

kb-0209-00-en-adresses-and-ports-used-by-talk2m.pdf (290.9 KB)

This is way above my level. I set up an old router in my home to have the same wifi network name as they have and used it to configure it. It is a guest network with no password.

They say that no lights are lit on the wifi card. This that normal to have no lights on the wifi card??

Is there anybody with a computer at the location so that we could take a look at this over Teamviewer? If there’s no lights on, I believe that means that there’s no signal

I’m trying. There is a skeleton crew there with no IT people and it is very discouraging. I’m also trying to get them to hardwire it into the wall but I don’t know if that will work.

As long as they have a PC and an Ethernet cable, I think I can help them get the device back online

OK. Can you send me what you to do or do you need to talk to them directly? They are getting it set up now.

I can just try and talk with them directly. Can you send me their contact info?

[customer info hidden]

Thank you!!

Can you tell me what the login info for that device is? it looks like the default:

User: adm
Pwd: adm

doesn’t seem to work

Tim, this is from another employee there who sent the document to IT:

Thanks Frank for the information.

Our IT dept indicates that we have another vendor using type of solution, therefore it should work. TCP port 443 should be open. He did not see the device on the network, but Rex might have taken it back to
his desk by that time. He is thinking he will go into the office tomorrow and make the hardwire connections live that are near the lappers and first verify that he can see the router on our network, then we can proceed from there.

It does look like the TCP port 443 is open, UDP 1194 is definitely closed, but I think the issue might be that they either don’t have our servers whitelisted or that their network might be blocking openvpn