Many thanks for this great project and the Motor focuser that I am also using. Both projects are very professional and work very well in the INDI EKOS system that we are using with Raspberry Pi.
I am having some problems getting the Bluetooth to work on the Dew Controller. The Bluetooth testing program works normally and the device pairs normally with the laptop but when I try to connect through the Windows application the port closes after a few seconds while waiting for the firmware version. I have tried everything that I can think of to remedy this issue but nothing works.
Given that the Bluetooth pairs and the testing with the serial monitor works perfectly can I assume that the module is working? Obviously we can leave this as a standalone or use USB connection to the app but we are trying to keep cabling to a minimum and would like to make this able to be remotely controlled as much as possible.
Have you come across this problem before?
I am running the Windows app on a brand new Asus laptop with Bluetooth 4.1 ( I have tried others too). The coding version is v324 with a Nano and version 309 stripboard with MOSFETs etc. Is there any other info that you need?
I feel that it is probably something really simple that I am missing.
Thanks for the assistance. I updated to v328 uncommented the add bluetooth line. Also added the libraries to the arduino libraries folder.
Unfortunately the problem persists. The HC05 appears as paired in my Windows bluetooth settings. I connect through USB (com5) and establish logging then disconnect and unplug the USB then try to connect using com3 (bluetooth) It appears to connect and then says that it is finding the firmware but this never comes over and an exception error occurs and the port is closed. I dont think that the datalog will be terribly helpful but I have attached it and a few others. When you say you need the logfile do you mean the datalog created in the Windows application or event log created in Windows related to the bluetooth connection. If you do mean the event log you will need to give me instructions how to find it. I really appreciate the help.
Hi Robert,
I tried resetting the arduino code BT to 9600 and the windows connection. Unfortunately with the same result. I have attached the log files from yesterday and today.
An interesting observation was that when I monitored the HC05 during the connection and getting firmware the status changed to "setting up device" but this then disappeared when the exception message "myDewController did not respond to request for firmware version. An exceptionerror has occurred and the serial port has been closed"
When I use the Bluetooth testing program and serial monitor program it all checks out as expected.
Are there any other ways that I can check the connection and that the HC05 module is working?
Hi Micheal
Can you please try attached - specify 9600 in drop down box when connecting to BT and 57600 when using USB cable. If using BT make sure USB cable disconnected.
I am in process of rebuilding my dew controller and just waiting for some parts so cannot test this at present, but hope new parts arrive in a few days.
Hi Micheal
Can you please try attached - specify 9600 in drop down box when
connecting to BT and 57600 when using USB cable. If using BT make sure USB
cable disconnected.
I am in process of rebuilding my dew controller and just waiting for some
parts so cannot test this at present, but hope new parts arrive in a few
days.
Hi Robert,
Still no joy with the suggested changes unfortunately. Nice additions to the Windows app though. Works perfectly through USB. I have another bluetooth module 4.0 Z6365. Would this work in this application? Do you need any more logfiles?
I tried using the bluetooth testing app again just in case there was a new fault with the module but again this works fine. It just does not make sense. I'm grateful for any advice but it strikes me that it is likely to be a hardware issue if no one else has reported this issue with the software/coding. What do you think?
Have a good Easter.
Regards,
Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
BT com is com3 and USB is com5.
Please don't spend a lot of time on this Robert. If you think that it could
be hardware I will just go out and get a new module. Has anyone else had
these problems?
Hi Robert,
No joy. It still times out waiting for the firmware version then closes the
port. Just a thought, I notice that the red light on the HC-05 is
continually flashing rapidly even though the laptop says that it is paired.
Does this mean that it is not connected? Also the default mode for this
module is to be a slave, would it make any difference to configure it as a
master?
I am scraping the barrel for ideas now. I am going to get a replacement
module if I can find one as they seem to be being superceeded now by the
BT4.0 modules.
the red light should be flashing, mine does - not flashing indicates an issue
configuring as a master should prevent it from working
I can verify firmware 329 is working with BT/HC05 with no USB cable.
You have enabled BT in the firmware? If not reprogram controller
Try power off controller (no usb cable), uninstall/remove HC05 device, disable bluetooh on computer, restart, enable bluetooth, power on controller with 12VDC (no usb cable) and let windows reinstall HC05 device
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert,
No luck with any of those methods. When I connect and look in the windows
settings there are 2 com ports associated with the HC-05. Com 4 incoming
HC-05 and Com 3 outoing HC-05 'Spp Dev'. I have been using com 3 as this
is for the spp dev as in your documentation. I have tried com 4 also with
no effect. However your documentation does not show 2 com ports. I am
concerned that the request for firmware is not being answered so is the BT
not transmitting this data from the arduino? Also the text about the BT in
the latest documentation suggests using a 100 ohm resistor (in the section
about BT) but the stripboard layout uses 1k ohm resistors. I am using 1k as
per v309 stripboard diagram should this be changed?
the red light should be flashing, mine does - not flashing
indicates an issue
configuring as a master should prevent it from working
I can verify firmware 329 is working with BT/HC05 with no USB
cable.
You have enabled BT in the firmware? If not reprogram controller
Try power off controller (no usb cable), uninstall/remove HC05
device, disable bluetooh on computer, restart, enable bluetooth, power on
controller with 12VDC (no usb cable) and let windows reinstall HC05 device
Connections:
VCC=5V
GND=GND
TXD = D12
RXD = A resistor dividor pair - The join of a 1K and 2.2K resistor. The other end of the 1K resistor goes to D13. The other end of the 2.2K resistor goes to GND
I noticed an error in the stripboard circuit - am uploading revised diagram.
I have also corrected the PDF. I had assumed you were using the PCB , I can't remember the last time I dealt with a stripboard, so apologies that it has taken some time to get a resolution, The wiring for the BT I have also uploaded. The PDF now has the correct info in the BT appendix, with the corrected circuits and stripboard layouts. Apologies for the errors.
Last edit: brownrb 2018-03-31
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My BT connections are the same. I pulled the controller to pieces and
carefully examined the stripboard for dry joints etc and checked it all
over with a multimeter to ensure that there were no shorts on the board.
Tried another BT module but same results. I am pretty much out of ideas.
The windows app just does not get a reply from the controller when asking
for the firmware version and times out thus closing the port.
Thanks for all your help Robert but I think I will call it a day and just
use it from USB. It's still a great piece of kit!
Connections:
VCC=5V
GND=GND
TXD = D12
RXD = A resistor dividor pair - The join of a 1K and 2.2K resistor. The
other end of the 1K resistor goes to D13. The other end of the 2.2K
resistor goes to GND
Sorry to hear that it is still not working, I did correct the error on the stripboard as this would certainly have prevented it from working.
If you had a spare nano or uno lying around it would be easy just to breadboard that with two resistors and an HC05. You could then load the firmware and see if there was a response. Ensure there is no resistor in the TXD line from the BT to the Nano, only the RXD line.
Ensure that you have BLUETOOTH defined in the firmware before programming the controller. It should read with the two leading //
#define ADDBLUETOOTH 1
Last edit: brownrb 2018-03-31
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sure that I will keep working on it and eventually get there. I hate to
be beaten by a problem. I will keep at it and let you know if I fix it.
Out of interest (and off topic) we are currently working on an arduino
controlled servo operated telescope lens cap a bit like Flip Flat with
integrated heater band. Done the prototype using a 270 degree servo so that
it folds back against the scope when open. We want to use it with EKOS so
now working on the coding to automate opening at the start of a session and
closing at the end. I'll send some pictures when it's done.
Best regards
Mike
Sorry to hear that it is still not working, I did correct the error on the
stripboard as this would certainly have prevented it from working.
If you had a spare nano or uno lying around it would be easy just to
breadboard that with two resistors and an HC05. You could then load the
firmware and see if there was a response. Ensure there is no resistor in
the TXD line from the BT to the Nano, only the RXD line.
Hi Robert,
So I breadboarded with a old Nano and BT (HC-06 same as HC-05 but only
operates in slave mode) using the v329 firmware and the resistors on the
RXD as you instructed. Curiously it still would not connect but kept
telling me that it was version pro 2 and would be closing the port. After
OK'ing the exception info boxes the Windows desktop app showed that it was
still connected but would not let me send any commands as the port was
closed. Very odd but different. As I said I will come back to this later
when I have more time, I won't admit defeat but will pause to think a bit
laterally on the problem.
If I crack it I will let you know.
All the best
Mike
I'm sure that I will keep working on it and eventually get there. I hate to
be beaten by a problem. I will keep at it and let you know if I fix it.
Out of interest (and off topic) we are currently working on an arduino
controlled servo operated telescope lens cap a bit like Flip Flat with
integrated heater band. Done the prototype using a 270 degree servo so that
it folds back against the scope when open. We want to use it with EKOS so
now working on the coding to automate opening at the start of a session and
closing at the end. I'll send some pictures when it's done.
Best regards
Mike
On Sun, Apr 1, 2018 at 4:00 AM, brownrb brownrb@users.sourceforge.net
wrote:
Hi Michael
Sorry to hear that it is still not working, I did correct the error on the
stripboard as this would certainly have prevented it from working.
If you had a spare nano or uno lying around it would be easy just to
breadboard that with two resistors and an HC05. You could then load the
firmware and see if there was a response. Ensure there is no resistor in
the TXD line from the BT to the Nano, only the RXD line.
Hi Robert,
I was trying to think of what may be different in your setup to mine. I don't have an on board PCB temp sensor controlling the fan. When I breadboarded the nano the Windows app kept telling me that I had version 2 and closed the port. I note that the fan PCB sensor is available on revision 2 of the PCB. I am just guessing here but could this be an issue.
All the best,
Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A version2 controller returns Version=(c)RBB v2.98loc
Generally it only says version 2 if you have loaded the version 2 firmware on the controller.
It is easy to check the firmware version in the controller, by using the arduino serial port monitor by sending the code v# to the controller, which should respond with v329$
If it returns this but the windows app 3052 is saying it is a version 2 controller then there is an issue with the app I will need to look at. If this is the case, let me know and also send the errorlog file.
Regards
Robert
Last edit: brownrb 2018-04-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I set up the Nano on the breadboard with the BT as instructed, flashed the
v329 firmware, disconnected the USB. Connected the power paired the BT with
the laptop (comport 4). Checked the port settings and baud rate were OK
(9600). Started up the Windows program. Changed to com 4 and pressed
connect.
The dialogue box said "attempting to connect to com 4" then getting
firmware version"
Then "error - version". Windows pop dialogue box said exception timeout
error I OK'd it out and the next box said I had version 2 and the port was
closed"
Here is the log file. (using Windows app 3052)
Best regards
Generally it only says version 2 if you have loaded the version 2 firmware
on the controller.
It is easy to check the firmware version in the controller, by using the
arduino serial port monitor by sending the code v# to the controller, which
should respond with v329#
If it returns this but the windows app 3052 is saying it is a version 2
controller then there is an issue with the app I will need to look at. If
this is the case, let me know and also send the errorlog file.
Hi Robert,
Many thanks for this great project and the Motor focuser that I am also using. Both projects are very professional and work very well in the INDI EKOS system that we are using with Raspberry Pi.
I am having some problems getting the Bluetooth to work on the Dew Controller. The Bluetooth testing program works normally and the device pairs normally with the laptop but when I try to connect through the Windows application the port closes after a few seconds while waiting for the firmware version. I have tried everything that I can think of to remedy this issue but nothing works.
Given that the Bluetooth pairs and the testing with the serial monitor works perfectly can I assume that the module is working? Obviously we can leave this as a standalone or use USB connection to the app but we are trying to keep cabling to a minimum and would like to make this able to be remotely controlled as much as possible.
Have you come across this problem before?
I am running the Windows app on a brand new Asus laptop with Bluetooth 4.1 ( I have tried others too). The coding version is v324 with a Nano and version 309 stripboard with MOSFETs etc. Is there any other info that you need?
I feel that it is probably something really simple that I am missing.
Best regards,
Mike Hamilton
Sent from Mail for Windows 10
Please update firmware to 328 with latest windows app 3051.
Rememeber to uncomment this line in the firmware before programming the controller
//#define ADDBLUETOOTH 1
Last edit: brownrb 2018-03-27
Hi Robert,
Thanks for the assistance. I updated to v328 uncommented the add bluetooth line. Also added the libraries to the arduino libraries folder.
Unfortunately the problem persists. The HC05 appears as paired in my Windows bluetooth settings. I connect through USB (com5) and establish logging then disconnect and unplug the USB then try to connect using com3 (bluetooth) It appears to connect and then says that it is finding the firmware but this never comes over and an exception error occurs and the port is closed. I dont think that the datalog will be terribly helpful but I have attached it and a few others. When you say you need the logfile do you mean the datalog created in the Windows application or event log created in Windows related to the bluetooth connection. If you do mean the event log you will need to give me instructions how to find it. I really appreciate the help.
Mike
The csv file is no good.
I am looking for the logfile txt file generated by the windows mydewcontrollerpro2 app.
Last edit: brownrb 2018-03-27
Be sure to use 9600 when connecting to the BT device
Hi Robert,
I tried resetting the arduino code BT to 9600 and the windows connection. Unfortunately with the same result. I have attached the log files from yesterday and today.
An interesting observation was that when I monitored the HC05 during the connection and getting firmware the status changed to "setting up device" but this then disappeared when the exception message "myDewController did not respond to request for firmware version. An exceptionerror has occurred and the serial port has been closed"
When I use the Bluetooth testing program and serial monitor program it all checks out as expected.
Are there any other ways that I can check the connection and that the HC05 module is working?
Mike
Hi Micheal
Can you please try attached - specify 9600 in drop down box when connecting to BT and 57600 when using USB cable. If using BT make sure USB cable disconnected.
I am in process of rebuilding my dew controller and just waiting for some parts so cannot test this at present, but hope new parts arrive in a few days.
Regards
Robert
Hi Robert
Here is latest logfile. Sorry I forgot to include it.
Mike
On Thu, Mar 29, 2018 at 4:09 AM, brownrb brownrb@users.sourceforge.net
wrote:
Hi Robert,
Still no joy with the suggested changes unfortunately. Nice additions to the Windows app though. Works perfectly through USB. I have another bluetooth module 4.0 Z6365. Would this work in this application? Do you need any more logfiles?
I tried using the bluetooth testing app again just in case there was a new fault with the module but again this works fine. It just does not make sense. I'm grateful for any advice but it strikes me that it is likely to be a hardware issue if no one else has reported this issue with the software/coding. What do you think?
Have a good Easter.
Regards,
Mike
Hi Mike
I have uploaded firmware v329. Please use this
Regards
Robert
Last edit: brownrb 2018-03-29
Hi Robert,
BT com is com3 and USB is com5.
Please don't spend a lot of time on this Robert. If you think that it could
be hardware I will just go out and get a new module. Has anyone else had
these problems?
Regards,
Mike
On Fri, Mar 30, 2018 at 5:45 AM, brownrb brownrb@users.sourceforge.net
wrote:
Hi Robert
Com 3 for BT and Com 5 for USB
I have tested 329 and it works for me. 328 did not. It was broken,.
Thanks, I'll check it out.
On Fri., 30 Mar. 2018, 1:50 pm brownrb, brownrb@users.sourceforge.net
wrote:
Hi Robert,
No joy. It still times out waiting for the firmware version then closes the
port. Just a thought, I notice that the red light on the HC-05 is
continually flashing rapidly even though the laptop says that it is paired.
Does this mean that it is not connected? Also the default mode for this
module is to be a slave, would it make any difference to configure it as a
master?
I am scraping the barrel for ideas now. I am going to get a replacement
module if I can find one as they seem to be being superceeded now by the
BT4.0 modules.
Regards,
Mike
On Fri, Mar 30, 2018 at 4:22 PM, Michael Hamilton mike1491@users.sourceforge.net wrote:
Hi Robert,
No luck with any of those methods. When I connect and look in the windows
settings there are 2 com ports associated with the HC-05. Com 4 incoming
HC-05 and Com 3 outoing HC-05 'Spp Dev'. I have been using com 3 as this
is for the spp dev as in your documentation. I have tried com 4 also with
no effect. However your documentation does not show 2 com ports. I am
concerned that the request for firmware is not being answered so is the BT
not transmitting this data from the arduino? Also the text about the BT in
the latest documentation suggests using a 100 ohm resistor (in the section
about BT) but the stripboard layout uses 1k ohm resistors. I am using 1k as
per v309 stripboard diagram should this be changed?
Thx
Mike
On Sat, Mar 31, 2018 at 7:44 AM, brownrb brownrb@users.sourceforge.net
wrote:
I am using the outgoing com port
Connections:
VCC=5V
GND=GND
TXD = D12
RXD = A resistor dividor pair - The join of a 1K and 2.2K resistor. The other end of the 1K resistor goes to D13. The other end of the 2.2K resistor goes to GND
I noticed an error in the stripboard circuit - am uploading revised diagram.
I have also corrected the PDF. I had assumed you were using the PCB , I can't remember the last time I dealt with a stripboard, so apologies that it has taken some time to get a resolution, The wiring for the BT I have also uploaded. The PDF now has the correct info in the BT appendix, with the corrected circuits and stripboard layouts. Apologies for the errors.
Last edit: brownrb 2018-03-31
Hi Robert,
My BT connections are the same. I pulled the controller to pieces and
carefully examined the stripboard for dry joints etc and checked it all
over with a multimeter to ensure that there were no shorts on the board.
Tried another BT module but same results. I am pretty much out of ideas.
The windows app just does not get a reply from the controller when asking
for the firmware version and times out thus closing the port.
Thanks for all your help Robert but I think I will call it a day and just
use it from USB. It's still a great piece of kit!
Mike
On Sat, Mar 31, 2018 at 12:36 PM, brownrb brownrb@users.sourceforge.net
wrote:
Hi Michael
Sorry to hear that it is still not working, I did correct the error on the stripboard as this would certainly have prevented it from working.
If you had a spare nano or uno lying around it would be easy just to breadboard that with two resistors and an HC05. You could then load the firmware and see if there was a response. Ensure there is no resistor in the TXD line from the BT to the Nano, only the RXD line.
Ensure that you have BLUETOOTH defined in the firmware before programming the controller. It should read with the two leading //
#define ADDBLUETOOTH 1
Last edit: brownrb 2018-03-31
Hi Robert,
I'm sure that I will keep working on it and eventually get there. I hate to
be beaten by a problem. I will keep at it and let you know if I fix it.
Out of interest (and off topic) we are currently working on an arduino
controlled servo operated telescope lens cap a bit like Flip Flat with
integrated heater band. Done the prototype using a 270 degree servo so that
it folds back against the scope when open. We want to use it with EKOS so
now working on the coding to automate opening at the start of a session and
closing at the end. I'll send some pictures when it's done.
Best regards
Mike
On Sun, Apr 1, 2018 at 4:00 AM, brownrb brownrb@users.sourceforge.net
wrote:
Hi Robert,
So I breadboarded with a old Nano and BT (HC-06 same as HC-05 but only
operates in slave mode) using the v329 firmware and the resistors on the
RXD as you instructed. Curiously it still would not connect but kept
telling me that it was version pro 2 and would be closing the port. After
OK'ing the exception info boxes the Windows desktop app showed that it was
still connected but would not let me send any commands as the port was
closed. Very odd but different. As I said I will come back to this later
when I have more time, I won't admit defeat but will pause to think a bit
laterally on the problem.
If I crack it I will let you know.
All the best
Mike
On Sun, Apr 1, 2018 at 9:49 AM, Michael Hamilton mike1491@users.sourceforge.net wrote:
Hi Robert,
I was trying to think of what may be different in your setup to mine. I don't have an on board PCB temp sensor controlling the fan. When I breadboarded the nano the Windows app kept telling me that I had version 2 and closed the port. I note that the fan PCB sensor is available on revision 2 of the PCB. I am just guessing here but could this be an issue.
All the best,
Mike
A version2 controller returns Version=(c)RBB v2.98loc
Generally it only says version 2 if you have loaded the version 2 firmware on the controller.
It is easy to check the firmware version in the controller, by using the arduino serial port monitor by sending the code v# to the controller, which should respond with v329$
If it returns this but the windows app 3052 is saying it is a version 2 controller then there is an issue with the app I will need to look at. If this is the case, let me know and also send the errorlog file.
Regards
Robert
Last edit: brownrb 2018-04-02
Hi Robert,
I set up the Nano on the breadboard with the BT as instructed, flashed the
v329 firmware, disconnected the USB. Connected the power paired the BT with
the laptop (comport 4). Checked the port settings and baud rate were OK
(9600). Started up the Windows program. Changed to com 4 and pressed
connect.
The dialogue box said "attempting to connect to com 4" then getting
firmware version"
Then "error - version". Windows pop dialogue box said exception timeout
error I OK'd it out and the next box said I had version 2 and the port was
closed"
Here is the log file. (using Windows app 3052)
Best regards
Mike
On Mon, Apr 2, 2018 at 1:53 PM, brownrb brownrb@users.sourceforge.net
wrote: