SHillier

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...