[argyllcms] Re: DTP41 transmittance help
- From: Doug Private <doug17r@xxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Thu, 3 Sep 2009 23:40:47 +1000
Thank you for the detailed response.
The '36OD' and '1422OD' are the same command, just with different parameters
so please try again and double check that the 'OD' command suffix is the
same. '36OD' is very useful as it shows the frequency read even upon
failure; try it after '0119CF' which should flash the light and only appear
to probe the frequency.
The m_bTransmissionEnabled flag is set after a successful '01CT'. You may
need to run a black calibration too, '00CT'.
I notice that your DTP41 is running old firmware, and perhaps this could be
making a difference. Your DTP41/T is running the same firmware as the DTP41
I am using for this hack.
Applying a 30kHz 5V signal to pin 3 allowed a calibration to continue and
with a little experimentation with the light placement and the diffuser it
succeeded. Got a chart read and the transmission profile made, thank you
for all your help. I'll order a light to frequency detector to help improve
the results, shall try something in the 20kHz to 450kHz range, and many have
adjustable scaling.
Douglas
On Thu, Sep 3, 2009 at 1:32 PM, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote:
> Doug Private wrote:
>
>> Thank you again. Your negative result is a little surprising. If the
>> 0119CF
>> command is failing then perhaps the frequency check is off. You can see
>> if
>> the transmission light frequency counter is running using:
>>
>> DEVELOPERPW
>> 36OD
>>
>> If this is running then you can compare the frequency to the upper and
>> lower
>> limits which are in the data store, see the output of '1422OD' and check
>> m_fUpperFrequencyLimit and m_fLowerFrequencyLimit. If the counter is not
>> running then it would seem your DTP41 is not compatible with your DTP41T
>> base.
>>
>
> For the DTP41, the firmware version is v9B11
>
> DEVELOPERPW returns 00
>
> 36OD returns 11, BAD_COMMAND
>
> 14220D returns
>
> Section 14
> CDSTransmission.cpp
> m_uiSectionDataSize = 856
> m_pbySectionData = 1033224
> m_bDirty = 1
> m_bLoadedDefaults = 0
> m_uiLastSetDirtyTime = 126
> m_uiLastClrDirtyTime = 0
> m_uiSectionDataSize = 856
> m_pbySectionData = 1033224
> m_uiLastClrDirtyTime = 0
> m_eLoadableMode = 1
> m_eStoreType = 2
> s_byRamSectionNumber = 1
> s_byBatteryRamSectionNumber = 0
> s_byCodeFlashSectionNumber = 16
> s_bySerialEESectionNumber = 0
> m_bMakePermanent = 0
> m_bSectionDataChanged = 0
> m_fCalibrationTemp = 25.0000
> m_bTransmissionEnabled = 0
> m_fUpperFrequencyLimit = 450000
> m_fLowerFrequencyLimit = 20000
> m_fMaxTransmission = 110.00
> m_fPostLampFailure = 0.25
> m_fNonLagrangeLowPoint = 0.10
> m_fFilterLimits[0] = 2000.00
> m_fFilterLimits[1] = 1300.00
> m_fFilterLimits[2] = 160.00
> m_fChannel0OffsetLimit = 80.00
> m_fChannel3OffsetLimit = 250.00
> m_uiTransmissionLampDelay = 400
> m_bUseESRFactors = 0
> m_bUseLagrangeLowPoint = 1
> m_bUse590Filter = 1
> m_bUse610Filter = 1
> m_bUsePostLampAdjust = 1...
>
>
> I would guess that m_bTransmissionEnabled = 0 is the problem.
>
> For the DTP41T, the firmware version is vD421
>
> DEVELOPERPW returns 00
>
> 36OD returns 11, BAD_COMMAND
>
> 14220D returns
>
> Section 14
> CDSTransmission.cpp
> m_uiSectionDataSize = 856
> m_pbySectionData = 1557500
> m_bDirty = 1
> m_bLoadedDefaults = 0
> m_uiLastSetDirtyTime = 125
> m_uiLastClrDirtyTime = 0
> m_uiSectionDataSize = 856
> m_pbySectionData = 1557500
> m_uiLastClrDirtyTime = 0
> m_eLoadableMode = 1
> m_eStoreType = 2
> s_byRamSectionNumber = 1
> s_byBatteryRamSectionNumber = 0
> s_byCodeFlashSectionNumber = 16
> s_bySerialEESectionNumber = 0
> m_bMakePermanent = 0
> m_bSectionDataChanged = 0
> m_fCalibrationTemp = 31.6650
> m_bTransmissionEnabled = 1
> m_fUpperFrequencyLimit = 450000
> m_fLowerFrequencyLimit = 20000
> m_fMaxTransmission = 110.00
> m_fPostLampFailure = 0.25
> m_fNonLagrangeLowPoint = 0.10
> m_fFilterLimits[0] = 2000.00
> m_fFilterLimits[1] = 1300.00
> m_fFilterLimits[2] = 160.00
> m_fChannel0OffsetLimit = 80.00
> m_fChannel3OffsetLimit = 250.00
> m_uiTransmissionLampDelay = 400
> m_bUseESRFactors = 0
> m_bUseLagrangeLowPoint = 1
> m_bUse590Filter = 1
> m_bUse610Filter = 1
> m_bUsePostLampAdjust = 1...
>
> It would be nice to know how the pulses are generated. Seems that pulses
>> are passed in pin 3, must be an oscillator in the base? Also it would be
>> interesting to know if the base has a light sensor or is it sensing the
>> current or a voltage.
>>
>
> The base unit has a light, a sensor and a chip. The chip is marked
> 2931A PYX05, so perhaps it is a low dropout 5V regulator.
> The sensor has 3 pins and is probably a light to frequency type. Pin 3 of
> the sensor goes to the connector pin 3. Connector pin 2 goes to the light
> and pin 1 of the sensor and pin 2, 6 & 7 of the chip. Connector
> pin 1 goes to the light and pin 8 of the chip. Chip pin 1 goes to pin 2 of
> the sensor. There is a 10 uF tantalum between pins 1 and 2 of the sensor,
> +ve to pin 2. There is a smaller non-polarized cap across the lamp.
> The sensor pins are labeled 1 - GND, 2 - Vdd, 3 - OUT.
> There don't seem to be any markings that identify the lamp or the sensor.
>
> cheers,
> Graeme Gill.
>
>
Other related posts:
