EHS6T LAN | Thales IoT Developer Community
August 18, 2016 - 4:00pm, 9395 views
As I understand the EHS6T LAN is unavailible at the moment however it is important for me to know now if the module can act as a client on a network. We are going to be using an external router and will not be using the 3G in the module. I understand the module has a full TCP/IP stack but we want to be absolutely sure that we can set the module with a static IP and it will be able to reach the internet via our external router (gateway).
Thanks for the help.
I am not from Gemalto, but I got a hand on one of LAN modules, a few months ago. And as I understood at that time, you still had to have SIM card to access the internet.
LAN enabled you to remote access EHS6 to send some AT commands, or update MIDlet, but not to use device ethernet to access the internet.
But I don't know if this information is still true.
Hi, EHS6T LAN is designed to be a gate way, enabling 3G connection via Ethernet. Therefor it can't work as a client. It will work like to standard router, but instead of WAN port it has APN and it's cellurar connection. Ethernet port in this case acts like a LAN ports in standard router, so they are enable only for clients.
The question is why do you want to use 3G terminal and not use 3G? Is it because of embedded processing? Or something else?
The problem is with our cliente´s specification. They want to use a 4G connection so we were thinking of using a 4G router as the gateway and using LAN for passing the connection to the module.
If I have devices connected via a switch to the module won't I still be able to communicate via the module and the device via IP? I mean if the module acts as a router then devices should be able to connect to it via IP and the module should be able to connect to the devices via IP as well, right?
You will be using some other 4G router as internet gateway for your LAN but still want EHS6T to be connected to the LAN. I'm not sure if I understand the idea - what's the reason for EHS6T here - is some logic going to be implemented on it?
Yes, the module has logic going on and will be gathering data from various sensors. Our cliente specified a 4G connection and in order to comply we need an external 4G router and the module ***** to communicate via lan to the router. It really is a silly requirement and we are trying to find out if there is a reason for requiring 4G or if they just meant "wireless mobile".
I hope this makes more sense.
Thank you for the clarification. I think that I've got your idea now.
As Michal has written before the EHS6 LAN terminal is designed to a gateway to the internet for LAN devices. In that scenario there is a separate processor running Linux which controls the LAN interface and only uses EHS6 module as a modem. EHS6 is connected to the processor via USB interface and is only a slave here used for establishing a ppp connection.
So I don't think that your scenario would be possiblein such variant - MIDlet application on the module would not be able to use LAN interface for communication with other hosts connected to the LAN interface. The MIDlet would only be able to communicate with the internet with it's own 3G connection. For your case there would need to be additional software implemented in the embedded Linux host and some firmware or software on the module - which is in the contrary to the main use case of the LAN terminal. Additionally even if you would use the terminal's 3G connection as a gateway the problem of direct communication of the application on the module with LAN devices would still exist.
We have an industrial monitoring application which polls multiple sensors using RS485 MODBUS RTU (via serial to rs485 converter). The information is collected up and delivered to our monitoring system via 3G.
Our customers now have a significant number of sensors and consoles that only have Ethernet ports and use TCP MODBUS. The entire industry is moving to ethernet as a standard. This forces us to find a new soluton. It would be great if the EHS6T LAN were able to (from JAVA as a client TCP) connect to each device in my ethernet subnet, collect the data and then deliver the processed data via 3G.
The EHS6 is such a powerful solution, our alternate solution is to use a EHS6T and integrate a linux based ethernet to serial converter to allow the EHS6 to collect the data from multiple TCP devices and then deliver it via 3G to our servers. It stikes me that the EHS6T LAN already has both linux, ethernet and is physically connected to the rest of the stack - If we can get it to connect to my devices as a TCP client (for devices on the same subnet), I get to reduce the number of devices to 1 (the EHS6T LAN).
Is there any way to allow the JAVA o EHS6T LAN to access the ethernet subnet? Once it got out the EHS6T LAN's ethernet port into the network switch, the switch would do the rest. Can the linux routing be altered to allow this to work, perhaps even tricking it with NAT'ing or port forwarding?
This would be a significant win for us and our clients. If we had to write a tunnel/gateway program that ran on the linux server to communicate between a Java thread or socket in order to achieve the desired communication and outbound TCP client connections into the Ethernet network, we'd be keen to proceed and wouldnt mind sharing the code. We would appreciate Cinterion support for this. (Digital Telemetry Limited, New Zealand)
Thank you for additional explanation. It creates the complete view of the solution now.
It would not be a problem to communicate the LAN devices directly with the remote server via EHS6T LAN, because that's what it has been created for.
But the functionality that you have described formulates a change request for the product's features in my opinion. So I think that you should contact the technical sales person for your region to talk about technical and business possibilities of such changes.
You can find the contact here: http://www.gemalto.com/m2m/where-to-buy?country=New%20zealand
We have successfully written the C & Java code to connect the Java module with the Ethernet Linux module (with Gemalto's help) which has allowed me to drive the outbound Ethernet connection from JAVA.
We can now use our data collection and control applications (from JAVA) to communicate with local TCP based equipment, interogate, manage and monitor them and feed back results to our Data Collection Hub over 3g. We can even use the EHS6T to tunnel web traffic to allow our customers to manage their own equipment which have http services.
This terminal (EHS6T-LAN) has some huge potential :) Looking forward to 4g.