Not sure whether this thread should be in microcontrollers or RF communications.
In an earlier blog, I describe serial communications between an accelerometer and a 2X16 LCD (https://www.electro-tech-online.com/blog-entries/memsic-inclinometer-assembly-language.254/ ). Eventually, I will be using a wireless link to connect the sensor to the readout/control unit. Two years ago, I got a pair of XBee S1's, played with them briefly, then set them aside. In the interim, I have switched homes, computers, OS's, doctors, etc. When I plugged them in two days ago, they did not work.
I downloaded the most recent versions of X-CTU and drivers. I am using an adapter board and FTDI cable from Ladyada. After a day and a half of fiddling, I was able to establish communication with them. They are working now and, much to my surprise and joy, communicate well. One XBee accepts the serial data form the accelerometer, and the other sends it to the display.
The problem I am having is that X-CTU will periodically shut down/stop working. It restarts and works fine. I am using Windows 7, and as mentioned the Adalady accessory board and FTDI cable. X-CTU is installed in the program files folder, x86. The security permissions panel for X-CTU is a bit odd, compared to other programs:
There is also an "Interactive" permission. All of the other programs I checked, except MPLab, have a very simple security panel like this:
But, MPLab, which works fine, is similar to X-CTU's.
1) Does anyone have experience with X-CTU and Win7? Any problems?
2) Is anyone familiar enough with the security on Win7 to explain such entries as Administrator (singular), Unknown Account, and Interactive account with "inherited" permissions?
John
In an earlier blog, I describe serial communications between an accelerometer and a 2X16 LCD (https://www.electro-tech-online.com/blog-entries/memsic-inclinometer-assembly-language.254/ ). Eventually, I will be using a wireless link to connect the sensor to the readout/control unit. Two years ago, I got a pair of XBee S1's, played with them briefly, then set them aside. In the interim, I have switched homes, computers, OS's, doctors, etc. When I plugged them in two days ago, they did not work.
I downloaded the most recent versions of X-CTU and drivers. I am using an adapter board and FTDI cable from Ladyada. After a day and a half of fiddling, I was able to establish communication with them. They are working now and, much to my surprise and joy, communicate well. One XBee accepts the serial data form the accelerometer, and the other sends it to the display.
The problem I am having is that X-CTU will periodically shut down/stop working. It restarts and works fine. I am using Windows 7, and as mentioned the Adalady accessory board and FTDI cable. X-CTU is installed in the program files folder, x86. The security permissions panel for X-CTU is a bit odd, compared to other programs:
There is also an "Interactive" permission. All of the other programs I checked, except MPLab, have a very simple security panel like this:
But, MPLab, which works fine, is similar to X-CTU's.
1) Does anyone have experience with X-CTU and Win7? Any problems?
2) Is anyone familiar enough with the security on Win7 to explain such entries as Administrator (singular), Unknown Account, and Interactive account with "inherited" permissions?
John
