EHS6 Java application uses ELS6x remote debugging | Telit Cinterion IoT Developer Community
June 5, 2017 - 3:10pm, 3358 views
Hi !
I tested a modified HelloWorld that has been previously been run using the IMP_NG_ELSx_REMOTE1.
Now, I started the same with IMP_NG_EHSx_REMOTE1 after having used "repair" for the Toolkit to read the
EHS6 module information. I also chose IMP_NG_EHSx_REMOTE1 in the Netbeans user interface.
For some reason, I will get:
Starting emulator in execution **** <-ok
Using USB port COM20. <-ok
Connecting to module... <-ok
Initializing module for debugging...<-ok
Establishing "IP connection for remote debugging of ELSx"... <-how can I change this to EHSx?
The ****m (or other connecting device) has reported an error.
Establishment of TCP/IP connection failed!
Passing control to external device emulator...
*** Error ***
Check the COM connection and dial up network parameters!
Device "IMP_NG_EHSx_REMOTE1" not registered!
I am using Netbeans 7.2, the EHS6 module is 03.001 ARN50.
I also restarted the OJMEE Device Manager.
Best Regards,
Antero
Antero Markkula
Communication and Mechatronics
Enkom Active Oy – www.enkom-active.fi
Upseerinkatu 3 A, 02600 Espoo, Finland
Mobile: +358 400 411368
Office: +358 10 204 0000
Fax: +358 10 204 0010
E-mail: antero.markkula@enkom-active.fi
Hello,
So it was working fine with ELS61 module, then it was possible to integrate with EHS6 but the debugging session does not work. The error information suggests some problem with the COM port. Please check with SCFG command if the System.out is not redirected to this port.
Regards,
Bartłomiej
Hello,
The COM port for stdio is ^SCFG: "Userware/Stdout","usb1",,,,"off", that equals to COM23
I tried to use a different COM port COM4 that equals to usb4.
The error is still the same. For some reason the wrong debug connection still tries to launch:
"IP connection for remote debugging of ELSx"
I also tried the repair option of the Toolkit and IMPDbgConnectionSetup, with no success.
The sw responds:"No supported module found, the debug RAS-connetion has not been updated".
Using the EHSx module by Teraterm works fine. I can also copy the compiled Java files through MES and they are working properly. Both serial and USB ports are all working.
The main question is: why I will get "IP connection for remote debugging of ELSx" instead of
"IP connection for remote debugging of EHSx".
Best Regards,
Antero
Antero Markkula
Communication and Mechatronics
Enkom Active Oy – www.enkom-active.fi
Upseerinkatu 3 A, 02600 Espoo, Finland
Mobile: +358 400 411368
Office: +358 10 204 0000
Fax: +358 10 204 0010
E-mail: antero.markkula@enkom-active.fi
Hello,
Please restart the module, close OJMEE and try to install again. Make sure that all the drivers are installed and wait a bit if not before clicking OK to scan the ports.
If you get "IP connection for remote debugging of ELSx" you have probably not changed the runtime from ELS to EHS. Please open Application Descriptor and verify the runtime on Overview tab.
Regards,
Bartłomiej
Hello,
I found solution to the "IP connection for remote debugging of ELSx" problem. I chose the "IMP-NG EHS5 Wireless Toolkit by Cinterion" from the Application Descriptor -> Platform. Earlier I had the "IMP-NG M2M Wireless Toolkit by Cinterion" that supports also the ELSx family.
The debug problem still remains. We have isolated the problem to Windows 10 Dial-Up software which does not communicate with the Netbeans/module. When selecting "Run" from Netbeans, the "IP Connection for remote debugging of EHSx" will start but does not communicate with the modem.
In comparison, both Teraterm and MES communication are working properly in all relevant ports.
Here is the output of the test. The degug device registration fails.
Starting emulator in execution mode
Using USB port COM20.
Connecting to module...
Initializing module for debugging...
Establishing "IP connection for remote debugging of EHSx"...
Registering ip address "192.168.244.1" of remote debugging device...
Waiting for debug device registration of "IMP_NG_EHS5_REMOTE"...
Passing control to external device emulator...
*** Error ***
Failed to connect to device 0!
Reason:
Failed to connect remote debugging device!
Emulator 0 terminated while waiting for it to register!
End of debug session. Emulator is closed!
Please see Microsoft's link about the problem with their update 1703. This could make sense as before this update, we could debug normally, assuming the Windows Firewall was configured to pass information properly.
We tried Microsoft's workaround using the registry editor, with no success.
Please check if this can be solved as the majority of customers have upgraded to Windows 10 and cannot use old Windows 7 machines in their internal networks.
Best Regards,
Antero
Antero Markkula
Communication and Mechatronics
Enkom Active Oy – www.enkom-active.fi
Upseerinkatu 3 A, 02600 Espoo, Finland
Mobile: +358 400 411368
Office: +358 10 204 0000
Fax: +358 10 204 0010
E-mail: antero.markkula@enkom-active.fi
Hello,
Thank you for this information.
This output is also typical for the wrong device type configured for the project as I have written before - you can change it in Application Descriptor or project configuration from IMP_NG_*** to IMP_NG_***_REMOTE1. But here it is not the case as you have set the correct one.
The main problem here is that, as you probably know, the Windows 10 is not yet supported by our software. But thank you for your input and opinion - it may help to prepare the proper solution.
Regards,
Bartłomiej