Add Sensor Driver of SPL07-003

[baiyang1990]

Hello Guys,
Since DPS310 has been discontinued, is it possible to add the driver code for its replacement SPL07-003? I can provide the reference driver code. Together we can add the driver code of the SPL07-003 sensor to the betaflight project to adapt to more user needs. If you want to know more information about SPL07-003, let me know, Thanks.
Looking forward to your reply.

[haslinghuis]

@baiyang1990 yes we are looking at it - any info is appreciated.

[baiyang1990]

SPA06-003 datasheet Ver02.pdf
barometer_dps310_SPL07-003.txt

Glad to get your reply,actually,SPL07-003 is very similar to DPS310,and we have modified barometer_dps310.c to support SPL07-003/SPA06-003,also it can support DPS310,if possible, you guys can update it to the betaflight project. and I will provide the datasheet to you used to review driver code
（barometer_dps310_SPL07-003.txt is barometer_dps310_SPL07-003.c）

[haslinghuis]

Thanks already got the sheet and made some adjustments locally - happy to compare.

    // 0x22 c31 [11:4] + 0x23 c31 [3:0]
    // 0x23 c40 [11:8] + 0x24 c40 [7:0]

[haslinghuis]

@baiyang1990 can not see the c file here - but my initial version can be found here: #13427

[baiyang1990]

Can not upload c file. I rename the barometer_dps310_SPL07-003.c to barometer_dps310_SPL07-003.txt

[haslinghuis]

considered this in the first place - as this would remove the extra define

if (ack && ((chipId[0] == DPS310_ID_REV_AND_PROD_ID) || (chipId[0] == SPL07_003_CHIP_ID))) {
            return true;
        }

Appreciate

if (chipId[0] == SPL07_003_CHIP_ID) {
		// 0x23 c31 [3:0] + 0x22 c31 [11:4]
		baroState.calib.c31 = getTwosComplement(((uint32_t)coef[18] << 4) | (((uint32_t)coef[19] >> 4) & 0x0F), 12);
	
		// 0x23 c40 [11:8] + 0x24 c40 [7:0]
		baroState.calib.c40 = getTwosComplement((((uint32_t)coef[19] & 0x0F) << 8) | (uint32_t)coef[20], 12);
	}
	else {
		baroState.calib.c31 = 0;
		baroState.calib.c40 = 0;
	}

will check more tomorrow

[baiyang1990]

Thanks for your attention,I think no problem,I am engineer of goertek, we found many customers use SPA06-003 on betaflight project, very much looking forward to the driver code can be pulled up to the betaflght project. Is there anything we can do for the code submission? such as provide the SPA06-003 samples for verification or ohter things?
By the way, I would also like to ask how long you estimate it will take to complete the verification of SPA06-003 and complete the code submission?

BR

[haslinghuis]

See #13427

For samples please contact BF using hardware at betaflight dot com.

[ctzsnooze]

It would be much better to use the real infineon DPS368, the direct replacement for the 310. That unit is individually temperature and pressure calibrated, piece by piece, and has very good characteristics.

We have had issues with some Baro units, I think SPA06, which report incorrect temperature values, so the temperature compensation doesn't work very well. This is some thing we can check. If you supply test FC's, please also include one with a real DPS-368 for comparison checks.

[SteveCEvans]

If you have any eval cards I can wire them up to an FC and write/test the drivers as I have done for other sensors such as the new STmicro devices.

For example the first gyro proven with an AT32F435 processor used

[SteveCEvans]

DM me on Discord (MrSteve).

[haslinghuis]

Provided code did not work on original DPS310. Fixed here #13427