Activity for SHillier
-
SHillier modified a comment on discussion General Discussion
The INDI driver for myDCP4ESP32 has been accepted and will be available in the nightly builds starting tonight. Or, you can download it from the github repository. The listing for the driver is also up on the indilib.org website at: MyDCP4ESP32 Dew Controller. I also updated the images of the driver tabs because I needed to make a couple changes to detect and display active temperature probes.
-
The INDI driver for myDCP4ESP32 has been accepted and will be available in the nightly builds starting tonight. Or, you can download it from the github repository. The listing for the driver is also up on the indilib.org website at: MyDCP4ESP32 Dew Controller. I also updated the images of the driver tabs because I needed to make a couple changes to detect and display active temperature probes.
-
The INDI driver for myDCP4ESP32 has been accepted and will be available in the nightly builds starting tonight. Or, you can download it from the github repository. The listing for the driver is also up on the indilib.org website at: MyDCP4ESP32 Dew Controller. I also updated the images of the driver tabs because I needed to make a couple changes to detect and display active temperature probes.
-
NP, you're welcome to use the images. I haven't created a pull request in the main INDI repo yet since I figured I'd wait for your new firmware. INDI just released V2.0.0 on Feb 1st so it will be April before the next release. A quick look at the protocol doc and it doesn't look like any of the commands I implemented we're impacted. At least by protocol changes. I only implemented the core dew heater functional commands so any changes to commands for RTC/NTP, the display or MQTT won't impact the...
-
Well then, I'm pretty much done for now. Serial is there but not tested. I also have a check for firmware version greater than 109. Greater than 109 enables tracking offset and the 100% boost buttons while with 109 they are removed. I set the firmware version of my copy to 110 after making the changes I mentioned. Screen captures attached. Three tabs. A "Main Control" tab to display temp, humidity and power that also allows tracking mode selection. A "Connection" tab and an "Options" tab. The Options...
-
Pretty well have the INDI driver working. At least for TCP. I don't have mine set up for serial connection. Found a couple other bugs. First is with overrides.I don't use override switches but when using the set override command I found the previously reported problem of all channels going to 100%. In dewchannels.h the getpwr proceedure there's a check for channel overide in each channel from lines 565 to 670. The channel isn't passed into the getpwr only temp and trackmode so if any channel is in...
-
Look forward to trying out the new firmware. Even though there will be lots of changes I hope you won't mind me reporting issues with the current version when I run into them. The set tracking offset command doesn't work for negative values. There's a cast to byte when the :19value# command is received. Its supposed to accept an int from -4 to 3 but the cast effectively forces to uint. In the comms.h line 410: case 19: // Set tracking offset value mySetupData->set_trackingoffset((byte)workString.toInt());...
-
I was playing with making a driver for Indi and was having weird results until I looked at the protocol document for the myFP2 comms protocol document since that Indi driver works well. The myFP2 protocol documentation mentions that all commands require a leading colon ":" and are terminated by an octothorp "#". The myDCP4ESP32 protocol document does not mention the leading colon but once added everything seems to be working. Quickly checking comms.h it is processing the command string assuming a...
-
Thanks and NP. I had read your firmware update postings under the Updates topic. I didn't expect immediate fixes just thought I'd put down any issues for when you have the chance to get to them.
-
Late to the party but mine is complete. I only needed 2 channels and was aiming for as small a box as possible. Also used silicone wires because they're way more flexible for stuffing in a small box.
-
I use the dual WiFi config from the wificonfig.json. The buffer size for reading the values is too small. I think this error was in the myFP2ESP code when you initially added this feature too. I changed the following line in myDCP4ESP32-109-b1.ino from: DynamicJsonDocument doc( (const size_t) (JSON_OBJECT_SIZE(1) + JSON_ARRAY_SIZE(2) + 120)); // allocate json buffer to (same is in the myFP2ESP code): DynamicJsonDocument doc( (const size_t) (JSON_OBJECT_SIZE(4) + 372)); // allocate json buffer This...
-
Robert, First, thanks for another great project. I've been using the myFP2ESP for quite a while now. Works great. This looks like another winner. In the documentation you've commented that the HYU21D has high accuracy. I've found that mine has a tendency for self heating. At first I thought maybe it was my enclosure for the sensor but I've tried it in various setups. Both enclosed, in the open air and in various orientations. Next question to ask, is it just my sample? Maybe, but I did look on the...
-
Thanks. Verified it compiles and also verified that all functions I have configured seem to work.
-
Typo in myBoards.cpp: sketch\myBoards.cpp: In member function 'void DriverBoard::initmove(bool, long unsigned int, byte, bool, bool)': myBoards.cpp:511:18: error: 'DebugPrintt' was not declared in this scope DebugPrintt(dir); Looks like another typo on the line previous to one indicated below. myFP2ESP.ino line 614 only has "myoled." on it. src\myFP2ESP\myFP2ESP.ino: In function 'void close_oledtextdisplay()': myFP2ESP:615:5: error: request for member 'mySetupData' in 'myoled', which is of pointer...
-
Ok, thanks. I had looked at github but it seemed it only went up to 132 so I used the 135 I previously grabbed from sourceforge. I just saw your other post so I'll move on over to github and grab a copy there.
-
Thanks. I wasn't able to find a ClearEEPROM.ino that seemd to work but I used the erase_flash option on esptool which did seem to work. I tried using the 135 version from sourceforge. 1. Deleted and replaced myDallasTemperature, myfp2eIRremoteESP8266, myHalfStepperESP32 and myOLED in the Arduino libraries folder. 2. Updated the focuserconfig.h, checked that myBoards.h was good and updated the irremotemappings.h. 3. Used esptool to clear the flash then I built and uploaded V135. 4. Then I uploaded...
-
Thanks Robert, great project! I was going to go the stripboard route but after seeing how easy it was to order PCBs I went for the ESP32-DRV8825 PCB instead. While waiting for the parts I designed and printed my own case as well as the stepper/focuser bracket. Finally got it all together by September and it has worked well for me since. Instead of a DB9 for the steppers I went with a GX12-6pin and combined the steppers and home position wires together to reduce connections. I used separate shielded...
-
Thanks Robert, great project! I was going to go the stripboard route but after seeing how easy it was to order PCBs I went for the ESP32-DRV8825 PCB instead. While waiting for the parts I designed and printed my own case as well as the stepper/focuser bracket. Finally got it all together by September and it has worked well for me since. Instead of a DB9 for the steppers I went with a GX12-6pin and combined the steppers and home position wires together to reduce connections. I used separate shielded...
-
Thanks Robert, great project! I was going to go the stripboard route but after seeing how easy it was to order PCBs I went for the ESP32-DRV8825 PCB instead. While waiting for the parts I designed and printed my own case as well as the stepper/focuser bracket. Finally got it all together by September and it has worked well for me since. Instead of a DB9 for the steppers I went with a GX12-6pin and combined the steppers and home position wires together to reduce connections. I used separate shielded...
-
NP. Although it looks like you already found them and modified the solder side view to disconnect those pins. I'll provide a link next tme. Thanks.
-
I was thinking of doing the stripboard version to try this out. Looking at the stripboard jpgs versus the schematic it looks like the EN, VP and VN pins need to be issolated but are currently showing to be connected to 12V, GND and 5V. Awaiting delivery of my parts from China and looking forward to starting on this... Thanks.
1