Author Topic: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137  (Read 5652 times)

0 Members and 1 Guest are viewing this topic.

JayE

  • Been Here a Bit
  • **
  • Posts: 11
    • View Profile
Smartsensor utility can connect to and control the smartsensor fine. After the upgrade to .137 rcs64 is unable to the smartsensor. I Think I have tried just about anything but With no Luck. I have reset rcs64 to factory defaults on all values and still nothing. Any help would be welcome.

martin

  • Administrator
  • Here a Real Lot!
  • *****
  • Posts: 275
  • RCS64 Programmer
    • View Profile
Re: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137
« Reply #1 on: October 12, 2016, 07:41:35 PM »
Have you updated the Smartsensor firmware?

JayE

  • Been Here a Bit
  • **
  • Posts: 11
    • View Profile
Re: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137
« Reply #2 on: October 12, 2016, 08:02:56 PM »
Rcs64 is not able to Update the firmware. It detects the smartsensor AS nano. Setting the Update to Uno allows the Update but Reads version0 afterwards.



JayE

  • Been Here a Bit
  • **
  • Posts: 11
    • View Profile
Re: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137
« Reply #3 on: October 12, 2016, 08:05:11 PM »
Firmware version in smartsensor utility says 14

martin

  • Administrator
  • Here a Real Lot!
  • *****
  • Posts: 275
  • RCS64 Programmer
    • View Profile
Re: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137
« Reply #4 on: October 12, 2016, 08:46:05 PM »
version 14 should be the correct one. Make sure to the Smartsensor utility isent connected to Smartsensor, then RCS64 cant conect to it.

Its very strange that RCS64 cant update it, First time I have heard about that issue.

It sounds to me that the smart sensor utility mess up the comports.

Martin

JayE

  • Been Here a Bit
  • **
  • Posts: 11
    • View Profile
Re: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137
« Reply #5 on: October 12, 2016, 09:26:19 PM »
The utility is not open when I start rcs64. Starting only rcs64 after reboot of Windows does not help either. I Will try to reinstall rcs64 from scratch tomorrow.

martin

  • Administrator
  • Here a Real Lot!
  • *****
  • Posts: 275
  • RCS64 Programmer
    • View Profile
Re: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137
« Reply #6 on: October 12, 2016, 09:29:26 PM »
I dont think reinstallation off RCS64 will help. I think its a comport issue. Somehow is there a (Fake comport) that RCS think is the Smartsensor. Can you make a screendumb off your device setting for comports?

JayE

  • Been Here a Bit
  • **
  • Posts: 11
    • View Profile
Re: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137
« Reply #7 on: October 14, 2016, 05:27:18 PM »
Correct reinstallation didn't fix the problem. Finally I got it. Looking under the advanced settings of the com port for the smart sensor I found that lowering the values transmit and receive buffers from high performance to low did the trick. Any advice on the recommended settings would be appreciated.


martin

  • Administrator
  • Here a Real Lot!
  • *****
  • Posts: 275
  • RCS64 Programmer
    • View Profile
Re: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137
« Reply #8 on: October 14, 2016, 05:29:33 PM »
Do you use smart system. Normal this should work out off the box

JayE

  • Been Here a Bit
  • **
  • Posts: 11
    • View Profile
Re: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137
« Reply #9 on: October 14, 2016, 05:42:36 PM »
I use the smart sensor. Dont know what you mean by smart system. Issue was with connectivity in rcs64. It detected the sensor but couldnt connect to it or couldnt keep the connection. Lowering the values fixed the problem.

martin

  • Administrator
  • Here a Real Lot!
  • *****
  • Posts: 275
  • RCS64 Programmer
    • View Profile
Re: Unable to connect smart sensor after upgrade from 4.1.0.105 to .137
« Reply #10 on: October 14, 2016, 05:45:56 PM »
Ok this sounds very strange, maybe also give it a try to change the latency to 5ms.