Issue selecting temperature probe funstion
Version 2 of the myFocuser Project
Brought to you by:
brownrb
Menu
▾
▴
Hi,
I’m having issues running the temperature probe and I’m hoping to get assistance.
I am compiling myFP2F_DRV8825_328 on a Rev 13 board in Arduino 2.1.1. When I comment out the temperature probe function in focuserconfig.h , everything compiles well and the board operates as expected – lights, buzzer, OLED display and stepper motor function as expected. Software connects and all is OK.
When I include the temperature probe function, everything compiles and uploads well with no warnings or errors. But, when the controller turns on, the buzzer and LEDs turn on and stay on and the OLED display does not turn on at all. It appears that the controller locks up. The software no longer connects either. Connecting/disconnecting the temperature probe makes no difference (turning off in between). When I remove the temperature configuration and recompile the controller works again.
I have:
OneWire.h Ver 2.3?
myDallasTemperature.h ver 3.7.3A
I have tested with:
DS18B20Probe.ino
LEDandBuzzer.ino
OLED.ino
All tests are OK.
I’ve also used different Nano boards with no difference. I can only assume it is a library issue or a setting issue but any guidance is appreciated.
Thank you
Hi Andrew
First, thanks for including good detail - it does save me time and so I appreciate that
You indicated that
myFP2FDRV8825328 on a Rev 13 board \
Is that a typo error? is it Rev12?
When I include the temperature probe function, everything compiles and uploads well with no warnings or errors. But, when the controller turns on, the buzzer and LEDs turn on and stay on and the OLED display does not turn on at all. It appears that the controller locks up.
The buzzer and leds form what is known as POST - Power On Self Test
When setup() starts, it turns on LEDs and Buzzer, to indicate controller is starting.
When setup() ends, it turns off LEDs and Buzzer to indicate the controller has successfully booted.
The fact that the LEDs and Buzzer remain ON is an indication that the setup() failed somewhere and the Controller is "hung" or stopped around a certain method.
In the boot sequence -
start serial
start leds and buzzer
check stepper power
read controller settings from eeprom
start temperature probe
start driver board
start motor timer
start display
start rotary encoder
read temperature
stop leds and buzzer
ready
Sometimes the eeprom can get corrupted a little, so its best to start from the beginning
That is caused by uploading a number of times with different versions etc
I would suggest the next step is
1. use the test program ClearEEPROM (in the tests folder
2. after the eeprom is erased,
3. load the firmware file into the arduino IDE
4. emanle the temperature probe
5. Compile - upload the firmware to the controller
If that does not solve it, then the next approach would be to enable debugging
then upload again
Open the serial port monitor and set speed to 9600
Then press the result button on the nanao chip so you can view the debug output in the serial monitor window.
The last serial.print will show where the issue is - you can highlight and copy the text output in the serial monitor window and paste it in a reply
NOW
remember to go back and turn the debug off in myDefines.h and then reprogram the controller again. If you do not do that then the apps and drivers will fail - because the debug goes to the serial port, and the drivers/apps read from the serial port - the debug messages get read by the apps/drivers and decoded as commands - which the messages are not - and then things go from bad to worse.
regards
Robert
Hi Robert,
You've got me worried with the board revision but it definitely says Rev 13 - as per attached image.
I cleared the EEPROM, enabled the temperature probe and then setup the debug. I received this:
LED001
TM (followed by a single square ASCII character that did not copy over)
To check, I disabled the temperature probe function and ran debug again and got this:
LED001
TMP001
BRD001
BRD002
fcurrentposition=5000, ftargetposition=5000
BRD005
MAS013MAS010BRD005
DIS001
TMP006
Setup end
STP001
STP001
STP001...
Thanks again for your assistance with this.
Regards,
Andrew
Ok so there was an issue with
TMP001 as it did not get to complete the action - only got TM
so thats an issue with the temperature probe.
Opps
Maybe not. I was puzzled when you said rev 13, cause I looked at the myFP2 PCB and could only find rev12.
What you have is a myFP2M board, so it means the myFP2 software won't run properly.
It has to be the myFP2M firware, not myFP2
yes, I know, I did not expect you to know about this and all the stuff below, so applogies, let me try and get you on the right path,
myFP2M - ready made controller using myFP2M firmware
myFP2N - nextion touch screen using myFP2N firmware
so, on the front page of the myfp2 project, scrolling down it says
myFP2M - Ready made Controllers
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/myFocuserPro2M/
The myFP2M boards have a small footprint, and some pins were changed etc.
Navigating the new link to
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/myFocuserPro2M/Arduino%20Firmware%20for%20myFP2M%20Prebuilt%20Controllers%20Only/Firmware_myFP2M_328.zip/download
Unzipping the Firmware_myFP2M_328.zip, then this folder has the correct myFP2M firmware for drv8825 model
myFP2M_DRV8825_328
Let me know how it goes.
Regards
Robert
Hi Andrew
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/myFocuserPro2M/
is where you will find all the myFP2M files, users-guide pdf, boards, firmware, wiring diagrams,
test progams and more
Can you can use the myFP2 ASCOM driver, Windows app with myFP2M boards.
Yes
Can use myfp2 firmware with myfp2M
No
Hi Robert,
Thank you so much for your help, it was the firmware version.
The sad thing is that I did download the correct firmware a while ago but because I have stopped and started so often I have lost continuity. I picked up the wrong file and didn't know it. It would have taken a long time to see this error on my own. Thanks again.
Regards,
Andrew