Hi I have a working unit using the uln2003 driver on version 301 firmware but if i update to vers 309 it will upload ok reporting no errors but will fail to connect via bluetooth.
i ran the clear eprom ino sevral times and rebooted etc but it doees not connect
revert back to 301 and all is good!
see attached ascom logfile
fails to connect with indi as well as the windows app
all settings look identical to me in the firmware sketches!
You said it failed on Bluetooth - did it connect okay just using the USB cable? that might change my advice.
but I have a question for you first
22:05:45.170 Connected Get baudrate: 14400
22:05:45.170 Connected Setting baudrate to 14400
You set the baud rate to 14400? Mine all run at 9600
So my suggestion is try 9600 first
When using BT I like to also do the following as there are inherent delays in using BT that are a bit longer than using USB
On the windows app
undo reset controller on connect
on delays tab of windows app
set delay on connect to 5 or 8
set delay serial read timeout to 8
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert thanks for the reply.
yes it is only BT the serial via USB works fine
changing to 9600 and the time outs made no difference.
so I looked at the serialcomms.h on both sketches and found a difference.
on the 309 and 308 versions I had tried the start section appeared different to the vers 301 so I coppied the start from the 301 to 309 and its now working.
not sure if i am bypassing something that you have modified before but let me know if I have doen the wrong thing?
the part at the begining that works is here:
{
DebugPrint("-Send:");
DebugPrintln(str);
// for serial mode
Serial.print(str);
ifdef BLUETOOTH
// for bluetooth
btSerial.print(str);
endif
}
what was listed in vers 308 and 309 is here:
{
Serial.print(str);
}
should this be missing?
many thanks for your time looking at this
Dave W
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi I have a working unit using the uln2003 driver on version 301 firmware but if i update to vers 309 it will upload ok reporting no errors but will fail to connect via bluetooth.
i ran the clear eprom ino sevral times and rebooted etc but it doees not connect
revert back to 301 and all is good!
see attached ascom logfile
fails to connect with indi as well as the windows app
all settings look identical to me in the firmware sketches!
have I missed a reset somewhere?
many thanks
You said it failed on Bluetooth - did it connect okay just using the USB cable? that might change my advice.
but I have a question for you first
22:05:45.170 Connected Get baudrate: 14400
22:05:45.170 Connected Setting baudrate to 14400
You set the baud rate to 14400? Mine all run at 9600
So my suggestion is try 9600 first
When using BT I like to also do the following as there are inherent delays in using BT that are a bit longer than using USB
On the windows app
undo reset controller on connect
on delays tab of windows app
set delay on connect to 5 or 8
set delay serial read timeout to 8
Hi Robert thanks for the reply.
yes it is only BT the serial via USB works fine
changing to 9600 and the time outs made no difference.
so I looked at the serialcomms.h on both sketches and found a difference.
on the 309 and 308 versions I had tried the start section appeared different to the vers 301 so I coppied the start from the 301 to 309 and its now working.
not sure if i am bypassing something that you have modified before but let me know if I have doen the wrong thing?
the part at the begining that works is here:
{
DebugPrint("-Send:");
DebugPrintln(str);
// for serial mode
Serial.print(str);
ifdef BLUETOOTH
// for bluetooth
btSerial.print(str);
endif
}
what was listed in vers 308 and 309 is here:
{
Serial.print(str);
}
should this be missing?
many thanks for your time looking at this
Dave W
Hi Dave
Well that is a bit of a major stuff up.
Not sure when that code change happened but clearly it is wrong
Will post firmware 310 with it fixed shortly
R
ah well
glad i helped
cheers Robert