|
|
Post by bikash504861 on Oct 17, 2017 1:10:33 GMT -5
Lakeshore transmitter 240-8p not responding through USB cable, but it is communicating through profibus cable. When we connect USB cable to lakeshore transmitter through measurelink software, it shows error, and communication is not possible through USB cable. But when we check the temperature values in SCADA( through profibus ), it shows actual temperature values.
This is the problem, i need your help to resolve the problem.
Thanks in advance
|
|
|
|
Post by Lake Shore Jeff M on Oct 17, 2017 6:58:43 GMT -5
Please confirm that the Model 240 is assigned a COM Port by looking in the Device Manager Ports (COM & LPT) and make sure that is the port you are selecting in MeasureLINK.
If the COM port is assigned and correctly selected, please provide the exact error message MeasureLINK is showing.
|
|
|
|
Post by bikash504861 on Oct 18, 2017 7:25:55 GMT -5
First of all thanks for reply.
As far as COMM port is concern, YES port is configured in device manager and same is reflected in measure link software.
But still it shows error message after few seconds "device is disconnected try again later".
Thanks in advance
|
|
|
|
Post by Lake Shore Jeff M on Oct 18, 2017 7:36:00 GMT -5
Thanks for the verification and error message. Can you send a screen shot of the error to me at service@lakeshore.com so I can show my engineering team what you are seeing?
|
|
|
|
Post by bikash504861 on Oct 23, 2017 1:22:21 GMT -5
Thanks for reply. Here I am attaching the screen shot of error message.  |
|
|
|
Post by Lake Shore Jeff M on Oct 23, 2017 11:52:30 GMT -5
Thank you for sending the screen shot showing the error. I will assume that clicking on the connect button will not reconnect MeasureLINK to the Model 240. If that is the case, I would like for you to try connecting to the Model 240 using an external Terminal Emulation program like Hyper Terminal or Tera Term. If you can send an email to service@lakeshore.com, I can send you the configuration information for Tera Term or Hyper Term if you can use either of these programs.
|
|
|
|
Post by Lake Shore Jeff M on Oct 23, 2017 11:58:35 GMT -5
Actually, you do not need to send the email as I have added the Tera Term document to this post. I suggested Tera Term as it is a free program that you can download and install.
If you need a Hyper Terminal document, please let me know. |
|
|
|
Post by bikash504861 on Oct 24, 2017 7:37:56 GMT -5
I followed the step as per guideline given in your document. But still issue is not yet resolved. however, communication has been established through tera term . Serial no. info as per doc was displayed as we write *IDN? (as per   attached screenshot) Three screenshot are attached 1. baud rate setting (device manager) 2. successful serial information displayed through tera term 3. error pop up message when tera term software was open in PC when we close tera term software, if we try to connect measure link software then it connects for few second and automatically disconnect and same error pop up message (disconnect) comes which we have told you earlier In this way, we can receive information through tera term but issue with measurelink software is not resolved so far. We kindly request you to needful to resolve this issue. Attachments:
|
|
|
|
Post by bikash504861 on Oct 27, 2017 0:25:42 GMT -5
I am waiting for your reply.
|
|
|
|
Post by Lake Shore Jeff M on Oct 27, 2017 6:14:07 GMT -5
Have you tried to uninstall and reinstall the MeasureLINK Application? Communicating with the Model 240 using Tera Term confirms that the USB Port is operating correctly so the issue seems to be between the MeasureLINK application and the Model 240. Also, please confirm what COM Port you have assigned as I see two different ports in the screen shots you have provided.
|
|
|
|
Post by burchsung on Jun 12, 2018 12:15:20 GMT -5
Hi...as per my knowledge Bad or defective Thunderbolt data cables can cause many issues with Apollo / UAD devices. If your problem persists after performing the procedures listed above, we recommend replacing your data cable Thunderbolt to eliminate that as the cause of the problem. turnkey pcb assembly |
|
|
|
Post by bikash504861 on Feb 12, 2020 1:04:35 GMT -5
I followed the procedure suggest by you and now the communication is successful between 240 module and measure_link_software. Issue is with the older version of measure_link_software.
In steed of using older version of measure_link software, I used new version of measure_link software (i.e. measure_link_for_240series_V10.0 prototype) in which successful communication is established.
Thanks for your kind-support and co-operation.
|
|
|
|
Post by Lake Shore Jeff M on Feb 24, 2020 14:54:22 GMT -5
Thanks for letting us know the application is working
|
|
|
|
Post by debbysherr on Oct 14, 2020 10:36:57 GMT -5
Hello...I had precisely the same issue. For reasons unknown changing the USB link to the one that accompanied my telephone fixed it. Some work and some don't, I figure it may be on the grounds that a portion of the links squirm around in the port. I have no clue about why the separation issue would occur for an explanation other than this since they are utilizing an advanced norm, yet mine doesn't detach with specific links and does with others. This additionally shouldn't be the case since it doesn't appear to squirm enough to disconnnect, however the link that accompanied my Phantom stood out more than the one I am currently utilizing. It may not be the link, yet it works with specific ones and I am tolerating it. pcb quote |
|
|
|
Post by michaeljohnbelta on Aug 29, 2023 0:28:34 GMT -5
It's interesting that communication is successful through the profibus cable but not through the USB cable and Measurelink software. This could point to a spotify blend potential issue with the USB connection or software configuration. To assist you further, I would need some additional information: Have you tried different USB cables and ports to rule out a hardware issue? Are there any specific error messages displayed when attempting communication through Measurelink software? Have you checked the device manager to ensure that the USB driver is properly installed and recognized? |
|
