Error Connecting to OpenSignals Fail

For problems with the OpenSignals software
akumiro
Posts: 11
Joined: Wed Apr 27, 2016 9:15 am

Error Connecting to OpenSignals Fail

Postby akumiro » Fri Apr 29, 2016 9:36 am

I have a bitalino Freestyle Kit that I have mounted to a breadboard. Basically, I want to be able to rapidly expriment with different sensors without having to solder everything together. This is how the error occurs:I connect the board, the LED on the MCU blinks slows as expected, the power supply provide the expected voltages (I have measured each pins and voltages seem to be okay.I then run opensignal (Win 64-bit(beta v.2016). It finds the mac of my Bluetooth but then display this error message that the communication with the device was lost, followed by yet another confusing message that the communication port does not exist. Please refer to the attached image.
Error Message.PNG
Error Message.PNG (55.68 KiB) Viewed 3026 times

Things to consider"
1. I have tried to use both a an internal bluetooth of my Macbook Pro and of another Sonny Computer. It didn't work.
2. I have also used a third party Bluetooth adapter, still it didn't work.
3. During the troubleshooting, I had connected an LED to the STAT pin of the Bluetooth module. Sometimes it blinks and stays on when connecting to the computer. Sometime it is just completely off. I don't know why. For now, I have connected the STAT pin to HIGH. i suspect I am doing something wrong here.
3. This is how I have connected the different pieces of the kit:
- All pins are connected as expected (GND to GND of the power supply, VCC, AGND also connected as labeled.
- I have connected all VSS to the VSS of the Power supply (Should it be VCC/2)
- All STAT pins are connected to VSS (Is this correct?)
- All NC pins are not connected.
- The RST pin is connected to VCC as well
- On the MCU, only pins I believe I need are connected. This are DGNS, STAT, DVCC, RX, TX, RST, AGND, VSS, AVCC
- I have also connected the A2 pin to the EDA sensor

I have troubleshooted this thing for too long that I need some help for experts! Thanks for any help you can provide.
Last edited by akumiro on Mon May 02, 2016 3:40 am, edited 1 time in total.

BITalino
Site Admin
Posts: 567
Joined: Tue Aug 27, 2013 3:47 pm

Re: Error Connecting to OpenSignals Fail

Postby BITalino » Fri Apr 29, 2016 10:04 am

Hi there,

Sorry to hear about the issues you are experiencing; from the information available there are a few good signs... the device is listed on OpenSignals, which means that the Bluetooth is powered and should be working.

The messages that you are obtaining are usually related with the inability for the OpenSignals software to send / receive commands to the device. This may happen for a number of reasons, chief amongst which are:

A) The RX & TX lines are not correctly wired
B) You have another application connected (and blocking the access) to the device
C) BITalino is detected but not correctly paired on the computer's Bluetooth device manager


As for the considerations you've highlighted:

1) & 2) Problems related with the performance of the Bluetooth interface on the computer are usually expressed as noticeable delays in the signal response or loss of communication after a few seconds, but you'd be able to see the device entering acquisition mode (white LED blinking instead of fading)

3) The STAT pin should be connected to its counterpart on the Bluetooth module

4)
- VSS is indeed VCC/2 and I don't think STAT is supposed to be connected to VSS so please confirm that you haven't accidentally made any shunt on your assembly that shouldn't be there
- RST should not be connected to anything


Please refer to the following videos for additional information on how to wire a BITalino Freestyle:
https://www.youtube.com/watch?v=UG8byfWQOuo
https://www.youtube.com/watch?v=GvwMtHKWxgI


Note that on the video regarding the FTDI interface you should avoid connecting the FTDI & the BITalino PWR block simultaneously as it will lead to failure.

Hope you find this information helpful for your troubleshooting... in case you continue to experience any issues just let us know and we'll do our best to support. You can also e-mail us to bitalino@plux.info and we'll try to find a way of further helping out ;)

Best regards,
The BITalino Team

akumiro
Posts: 11
Joined: Wed Apr 27, 2016 9:15 am

Re: Error Connecting to OpenSignals Fail

Postby akumiro » Mon May 02, 2016 2:38 am

Thanks a lot for your support. I have done as exactly as you said. I now can connect to the device via Open Signals (r)evolution. For quick testing, I simply tried to use the LUX sensor by connecting the device and its output to A5 of the MCU. However, I am not getting any output displayed on Open Signals (r)evolution. I get this blank screen and the MCU LED is just blinking slow. No indication that something is being received. Of course when I try to use the visualization tool, it tells me that it cannot access the file specified. Is it maybe the problem with the bluetooth module which may not be working as expected?
After investigating the output in the command window, I get the following exceptions

Code: Select all

exception creating base dev : could not open device
> FIND_DEVICES
> CHECK_DEVICE  98:D3:31:80:48:17
BITalino.open: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because
 connected host has failed to respond.

exception creating base dev : could not open device
> FIND_DEVICES
> CHECK_DEVICE  98:D3:31:80:48:17
Exception @connect_database:  (2003, "Can't connect to MySQL server on 'mysql.plux.info' (10060)")

Also, in my previous post, I forgot to mention that I am not connecting the following MCU pins: GP, SCL and SDA. Should this be a problem?
Thanks for the support you can provide.
Regards,
Attachments
Capture.PNG
Capture.PNG (124.01 KiB) Viewed 3013 times

BITalino
Site Admin
Posts: 567
Joined: Tue Aug 27, 2013 3:47 pm

Re: Error Connecting to OpenSignals Fail

Postby BITalino » Mon May 02, 2016 8:44 am

Hi,

The blinking status LED is already a significant progress as it means that the MCU is receiving the command to start acquisition ;)

From the screenshot you've posted it seems that you are using a legacy version of OpenSignals, which we are not developing anymore.

Please try to use the latest OpenSignals (r)evolution version available for download on our website and let us know how it goes:
http://bitalino.com/index.php/software

Best regards,
The BITalino Team

akumiro
Posts: 11
Joined: Wed Apr 27, 2016 9:15 am

Re: Error Connecting to OpenSignals Fail

Postby akumiro » Thu May 05, 2016 1:34 am

Dear Bitalino Team,
Thanks a lot again for your support.
I have finally been able to connect and acquired sensor data on the OpenSignal. However, what I am getting is completely off. The output is all at 1023. And I believe the problem isn't my sensors because the sensor work independently and give me good data. I have even tried to connect the inputs analog pins (A1 and A5) to VSS and I am still getting the same output of 1023. Of course I expected to get in this case just 512. What's going wrong? I wrote a C# application to read the different sensors, and my programs gives me exactly what opensignal was giving. Here is a sample output

Code: Select all

Searching for devices. Please Wait...
1 devices have been found:
98:D3:31:80:48:17 - bitalino
Connecting to device 98:D3:31:80:48:17
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
A1: 1023 A2: 1023 A3:1023 A4:1023 A5:63 A6:63
BITalino exception: The computer lost communication with the device.
Press any key to continue . . .

Can please some suggest why this may happen?
I appreciate your help

BITalino
Site Admin
Posts: 567
Joined: Tue Aug 27, 2013 3:47 pm

Re: Error Connecting to OpenSignals Fail

Postby BITalino » Thu May 05, 2016 10:36 am

Great to hear that you have made some progress... hopefully you're reaching the final stage of obtaining your desired setup.

If we understood correctly, the current status of your build is that:

1) When the device is powered on there's a white LED fading (standby / idle mode)

2) The device successfully pairs with the receiver and appears in OpenSignals / C# API

3) When you record on OpenSignals / C# API the white LED starts blinking (streaming mode) and samples arrive at a steady rate


Under these conditions, the device appears to be communicating and changing state correctly, in which case, when streaming, all channels but A6 (depending on whether it is connected to the corresponding pin on the PWR block should be at zero.

For the values to be 1023 on A1-A4 and 63 on A5 & A6, all channels would have to be connected to VCC, which may be indicative of a shunt or short circuit in the connections.

As such we'd advise you to use a multimeter to confirm whether the input voltage at the analog input pins is indeed (VCC=3.3V) or not, and re-check your assembly for shunts and short circuits.

Best regards,
The BITalino Team

akumiro
Posts: 11
Joined: Wed Apr 27, 2016 9:15 am

Re: Error Connecting to OpenSignals Fail

Postby akumiro » Fri May 06, 2016 6:57 am

Dear Bitalino Team-
Thanks again for your support. I have done as you suggested. I rechecked every pin on the MCU for a short or a shunt but nothing was found. I have measured the voltage on the analog pin (A5 in this case) and the voltage is changing as expected when light is light on the LUX sensor. The voltage is no where to VCC. It is around 0.4 to 0.6V depending on the amount of light on the LUX sensor. To make sure the problem does not reside in my faulty soldering, I have used a new MCU, reconnected all the pins but I get the same exact bug: The output is constantly at 1023 as if the analog input was at VCC. I cannot fully understand why two MCU would behave exactly the same way. Again, would you please confirm if pin GP, SDA and SCL of the MCU should not be connected to anything? As of now, I have left them floating!
For the record, I am using BITalino version: BITalino_v3.3a_18032014. I tried to update to the latest version using the tools you provide (http://plux.info/index.php/en/18-software) but I was not been able too. The firmware updater keeps loosing connection to the device. I don't why this is the case..
Regards,

BITalino
Site Admin
Posts: 567
Joined: Tue Aug 27, 2013 3:47 pm

Re: Error Connecting to OpenSignals Fail

Postby BITalino » Fri May 06, 2016 1:02 pm

Hi,

We'll try to provide you with additional support soon. As for the firmware update, we have a toolset available online but it only works with our biosignalsplux professional product line. For BITalino you need to follow these instructions herein:
https://github.com/BITalinoWorld/firmware-bitalino

Best regards,
The BITalino Team

akumiro
Posts: 11
Joined: Wed Apr 27, 2016 9:15 am

Re: Error Connecting to OpenSignals Fail

Postby akumiro » Sat May 07, 2016 6:31 am

Dear Bitalino Team,
As an update to my previous post, I forgot to mention that I have also tried to ground the analog input (A5) but I still get the same output of 1023. It seems as if the analog pin isn't connected at all! I have made all the verification possible and I believe there is no problem with my wiring.
Thanks a lot again. I will wait for your further support.
Regards,

BITalino
Site Admin
Posts: 567
Joined: Tue Aug 27, 2013 3:47 pm

Re: Error Connecting to OpenSignals Fail

Postby BITalino » Sun May 08, 2016 1:38 pm

Hi,

Your inquiry has been forwarded to our colleagues from software engineering.

They should get back to you tomorrow with some additional information.

Best regards,
The BITalino Team


Return to “Troubleshooting”