BC
Bob Camp
Wed, Aug 18, 2010 11:22 PM
Hi
I sort of assumed this group was more likely to be brushing up on tech than on English Lit.
One other thing some outfits check - they will only email the activation codes to an account at the school you claim to attend.
Bob
On Aug 18, 2010, at 10:40 AM, jimlux jimlux@earthlink.net wrote:
Hi
Continuing education at the local community collage is your friend. Do it online and you don't even spend gas money.
Bob
Not always.. e.g. Matlab says: "The product is solely for use in connection with courses offered at degree-granting institutions, either by students working toward a degree, or by continuing education students." "They are not for personal, professional, or commercial use.
and they do "check ID"
Proof of student status is documentation that confirms that you are currently a student enrolled in a degree-granting institution. To successfully authenticate as a student, you must provide us with acceptable proof of student status by uploading a digital copy of any one of these documents:
I doubt that they'd call the school to see if you're taking a class that actually could use matlab ("Aha, we see you're taking 17th century English literature, how ARE you using Matlab in that?" "Why, I'm using it to do statistical analysis on the works allegedly written by Shakespeare to determine the actual author.")
So, you'd be splitting hairs a bit... (not likely that the mathworks police are coming after you)
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hi
I sort of assumed this group was more likely to be brushing up on tech than on English Lit.
One other thing some outfits check - they will only email the activation codes to an account at the school you claim to attend.
Bob
On Aug 18, 2010, at 10:40 AM, jimlux <jimlux@earthlink.net> wrote:
> Bob Camp wrote:
>> Hi
>> Continuing education at the local community collage is your friend. Do it online and you don't even spend gas money.
>> Bob
>
> Not always.. e.g. Matlab says: "The product is solely for use in connection with courses offered at degree-granting institutions, either by students working toward a degree, or by continuing education students." "They are not for personal, professional, or commercial use.
>
>
> and they do "check ID"
> Proof of student status is documentation that confirms that you are currently a student enrolled in a degree-granting institution. To successfully authenticate as a student, you must provide us with acceptable proof of student status by uploading a digital copy of any one of these documents:
>
>
> I doubt that they'd call the school to see if you're taking a class that actually could use matlab ("Aha, we see you're taking 17th century English literature, how ARE you using Matlab in that?" "Why, I'm using it to do statistical analysis on the works allegedly written by Shakespeare to determine the actual author.")
>
>
> So, you'd be splitting hairs a bit... (not likely that the mathworks police are coming after you)
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
DB
David Bobbett
Thu, Aug 19, 2010 7:22 AM
Hi Brooke,
I know what you are thinking! Sadly the supply is 12.1v so there's
plenty of regulator headroom, very interesting page though. I'm
beginning to think that Didier's suggestion of corrupted firmware in the
iCruse is the most probable explanation.
Best wishes,
David
On 18/08/2010 16:58, Brooke Clarke wrote:
Hi Didier,
No - the display reads "DAC V: 0.0000" on the iCruse LCD, all the
other data (including temperature) displays normally and correctly.
So it is only that part of the data which doesn't seem to be decoded
and displayed correctly. The really odd thing is that the DAC V value
can be seen in Tboltmon.exe, although I realise that that particular
program also sends data to the Tbolt, which the iCruse does not.
The reference to the RS232 resistors was in the context of the
discussions regarding whether the values in the iCruse are correct -
but of course if all the other data is being received correctly,
there doesn't seem to be any logical reason why the DAC data would be
any different.
Thanks for the reply, but I'm still puzzled!
David, G4IRQ
On 18/08/2010 12:33, Didier Juges wrote:
When you say "will not display the DAC V value", do you mean the
display is
blank, or it displays garbage?
Interestingly, the code that displays temperature and DAC voltage is
essentially the same, the only difference being which part of the data
string received from the Thunderbolt is processed, so it is hard to
imagine
why one would work and not the other, unless the data received from
the TB
is corrupted in the part that should contain the DAV value, and the
conversion routine fails.
If you have doubts that the serial interface may not be working (I
am not
sure about what missing resistor you are talking about), fix that
first and
try again.
Looking at the serial stream with a scope may help diagnose such
problem.
Didier KO4BB
-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of David Bobbett
Sent: Wednesday, August 18, 2010 4:23 AM
To: time-nuts@febo.com
Subject: [time-nuts] Tbolt and iCruse readout problem - any ideas?
Hi all,
Having struggled in vain to solve this problem, I thought I would
make a
plea for help as my first posting to Time Nuts . . . so here goes!
I have a Tbolt with v3.00 firmware which works fine with the
Tboltmon.exe
V2.60 and Lady Heather software. It also works fine with the iCruse
Tbolt
LCD monitor - except that the monitor will not display the "DAC V"
value,
all the other values are displayed without a problem.
The iCruse is the later version which has had the PIC voltage
conversion
done, but not the RS232 input resistor mods.
I have two questions really:
-
Is there a setting which I need to change in my Tbolt using
Tboltmon.exe
to get this to work?
-
Does anybody on Time Nuts have an iCruse which shows a negative
value for
the "DAC V"?
As far as I can see, there are 3 options: a) there is a configuration
problem, b) the iCruse doesn't display negative values for DAC V, c) my
iCruse is faulty. I've pretty much run out of ideas on this one, so any
suggestions would be greatly appreciated!
Regards,
David Bobbett, Milton Keynes, UK.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hi Brooke,
I know what you are thinking! Sadly the supply is 12.1v so there's
plenty of regulator headroom, very interesting page though. I'm
beginning to think that Didier's suggestion of corrupted firmware in the
iCruse is the most probable explanation.
Best wishes,
David
On 18/08/2010 16:58, Brooke Clarke wrote:
> Hi David:
>
> What power supply voltage are you using?
> http://www.prc68.com/I/ThunderBolt.shtml#iCruze
>
> Have Fun,
>
> Brooke Clarke
> http://www.PRC68.com
>
>
> David Bobbett wrote:
>> Hi Didier,
>>
>> No - the display reads "DAC V: 0.0000" on the iCruse LCD, all the
>> other data (including temperature) displays normally and correctly.
>> So it is only that part of the data which doesn't seem to be decoded
>> and displayed correctly. The really odd thing is that the DAC V value
>> can be seen in Tboltmon.exe, although I realise that that particular
>> program also sends data to the Tbolt, which the iCruse does not.
>>
>> The reference to the RS232 resistors was in the context of the
>> discussions regarding whether the values in the iCruse are correct -
>> but of course if all the other data is being received correctly,
>> there doesn't seem to be any logical reason why the DAC data would be
>> any different.
>>
>>
>> Thanks for the reply, but I'm still puzzled!
>>
>>
>> David, G4IRQ
>>
>>
>>
>>
>>
>> On 18/08/2010 12:33, Didier Juges wrote:
>>> When you say "will not display the DAC V value", do you mean the
>>> display is
>>> blank, or it displays garbage?
>>>
>>> Interestingly, the code that displays temperature and DAC voltage is
>>> essentially the same, the only difference being which part of the data
>>> string received from the Thunderbolt is processed, so it is hard to
>>> imagine
>>> why one would work and not the other, unless the data received from
>>> the TB
>>> is corrupted in the part that should contain the DAV value, and the
>>> conversion routine fails.
>>>
>>> If you have doubts that the serial interface may not be working (I
>>> am not
>>> sure about what missing resistor you are talking about), fix that
>>> first and
>>> try again.
>>>
>>> Looking at the serial stream with a scope may help diagnose such
>>> problem.
>>>
>>> Didier KO4BB
>>>
>>> -----Original Message-----
>>> From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
>>> Behalf Of David Bobbett
>>> Sent: Wednesday, August 18, 2010 4:23 AM
>>> To: time-nuts@febo.com
>>> Subject: [time-nuts] Tbolt and iCruse readout problem - any ideas?
>>>
>>> Hi all,
>>>
>>> Having struggled in vain to solve this problem, I thought I would
>>> make a
>>> plea for help as my first posting to Time Nuts . . . so here goes!
>>>
>>> I have a Tbolt with v3.00 firmware which works fine with the
>>> Tboltmon.exe
>>> V2.60 and Lady Heather software. It also works fine with the iCruse
>>> Tbolt
>>> LCD monitor - except that the monitor will not display the "DAC V"
>>> value,
>>> all the other values are displayed without a problem.
>>> The iCruse is the later version which has had the PIC voltage
>>> conversion
>>> done, but not the RS232 input resistor mods.
>>>
>>>
>>> I have two questions really:
>>>
>>> 1) Is there a setting which I need to change in my Tbolt using
>>> Tboltmon.exe
>>> to get this to work?
>>>
>>> 2) Does anybody on Time Nuts have an iCruse which shows a negative
>>> value for
>>> the "DAC V"?
>>>
>>>
>>> As far as I can see, there are 3 options: a) there is a configuration
>>> problem, b) the iCruse doesn't display negative values for DAC V, c) my
>>> iCruse is faulty. I've pretty much run out of ideas on this one, so any
>>> suggestions would be greatly appreciated!
>>>
>>> Regards,
>>>
>>> David Bobbett, Milton Keynes, UK.
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> time-nuts mailing list -- time-nuts@febo.com
>>> To unsubscribe, go to
>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>>> and follow the instructions there.
>>>
>>>
>>> _______________________________________________
>>> time-nuts mailing list -- time-nuts@febo.com
>>> To unsubscribe, go to
>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>>> and follow the instructions there.
>>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts@febo.com
>> To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
DB
David Bobbett
Thu, Aug 19, 2010 9:20 AM
Further to my messages regarding this problem, I contacted Bob (aka
fluke.l) who replied almost immediately, saying that this has happened
to around 1 in 400 iCruse units and he is working on a fix. Sort of a
relief that there really is a problem and not some strange combination
of events.
On 19/08/2010 08:22, David Bobbett wrote:
Hi Brooke,
I know what you are thinking! Sadly the supply is 12.1v so there's
plenty of regulator headroom, very interesting page though. I'm
beginning to think that Didier's suggestion of corrupted firmware in
the iCruse is the most probable explanation.
Best wishes,
David
On 18/08/2010 16:58, Brooke Clarke wrote:
Hi Didier,
No - the display reads "DAC V: 0.0000" on the iCruse LCD, all the
other data (including temperature) displays normally and correctly.
So it is only that part of the data which doesn't seem to be decoded
and displayed correctly. The really odd thing is that the DAC V
value can be seen in Tboltmon.exe, although I realise that that
particular program also sends data to the Tbolt, which the iCruse
does not.
The reference to the RS232 resistors was in the context of the
discussions regarding whether the values in the iCruse are correct
- but of course if all the other data is being received correctly,
there doesn't seem to be any logical reason why the DAC data would
be any different.
Thanks for the reply, but I'm still puzzled!
David, G4IRQ
On 18/08/2010 12:33, Didier Juges wrote:
When you say "will not display the DAC V value", do you mean the
display is
blank, or it displays garbage?
Interestingly, the code that displays temperature and DAC voltage is
essentially the same, the only difference being which part of the data
string received from the Thunderbolt is processed, so it is hard to
imagine
why one would work and not the other, unless the data received from
the TB
is corrupted in the part that should contain the DAV value, and the
conversion routine fails.
If you have doubts that the serial interface may not be working (I
am not
sure about what missing resistor you are talking about), fix that
first and
try again.
Looking at the serial stream with a scope may help diagnose such
problem.
Didier KO4BB
-----Original Message-----
From: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] On
Behalf Of David Bobbett
Sent: Wednesday, August 18, 2010 4:23 AM
To: time-nuts@febo.com
Subject: [time-nuts] Tbolt and iCruse readout problem - any ideas?
Hi all,
Having struggled in vain to solve this problem, I thought I would
make a
plea for help as my first posting to Time Nuts . . . so here goes!
I have a Tbolt with v3.00 firmware which works fine with the
Tboltmon.exe
V2.60 and Lady Heather software. It also works fine with the iCruse
Tbolt
LCD monitor - except that the monitor will not display the "DAC V"
value,
all the other values are displayed without a problem.
The iCruse is the later version which has had the PIC voltage
conversion
done, but not the RS232 input resistor mods.
I have two questions really:
-
Is there a setting which I need to change in my Tbolt using
Tboltmon.exe
to get this to work?
-
Does anybody on Time Nuts have an iCruse which shows a negative
value for
the "DAC V"?
As far as I can see, there are 3 options: a) there is a configuration
problem, b) the iCruse doesn't display negative values for DAC V,
c) my
iCruse is faulty. I've pretty much run out of ideas on this one, so
any
suggestions would be greatly appreciated!
Regards,
David Bobbett, Milton Keynes, UK.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Further to my messages regarding this problem, I contacted Bob (aka
fluke.l) who replied almost immediately, saying that this has happened
to around 1 in 400 iCruse units and he is working on a fix. Sort of a
relief that there really is a problem and not some strange combination
of events.
On 19/08/2010 08:22, David Bobbett wrote:
> Hi Brooke,
>
> I know what you are thinking! Sadly the supply is 12.1v so there's
> plenty of regulator headroom, very interesting page though. I'm
> beginning to think that Didier's suggestion of corrupted firmware in
> the iCruse is the most probable explanation.
>
> Best wishes,
>
> David
>
>
>
> On 18/08/2010 16:58, Brooke Clarke wrote:
>> Hi David:
>>
>> What power supply voltage are you using?
>> http://www.prc68.com/I/ThunderBolt.shtml#iCruze
>>
>> Have Fun,
>>
>> Brooke Clarke
>> http://www.PRC68.com
>>
>>
>> David Bobbett wrote:
>>> Hi Didier,
>>>
>>> No - the display reads "DAC V: 0.0000" on the iCruse LCD, all the
>>> other data (including temperature) displays normally and correctly.
>>> So it is only that part of the data which doesn't seem to be decoded
>>> and displayed correctly. The really odd thing is that the DAC V
>>> value can be seen in Tboltmon.exe, although I realise that that
>>> particular program also sends data to the Tbolt, which the iCruse
>>> does not.
>>>
>>> The reference to the RS232 resistors was in the context of the
>>> discussions regarding whether the values in the iCruse are correct
>>> - but of course if all the other data is being received correctly,
>>> there doesn't seem to be any logical reason why the DAC data would
>>> be any different.
>>>
>>>
>>> Thanks for the reply, but I'm still puzzled!
>>>
>>>
>>> David, G4IRQ
>>>
>>>
>>>
>>>
>>>
>>> On 18/08/2010 12:33, Didier Juges wrote:
>>>> When you say "will not display the DAC V value", do you mean the
>>>> display is
>>>> blank, or it displays garbage?
>>>>
>>>> Interestingly, the code that displays temperature and DAC voltage is
>>>> essentially the same, the only difference being which part of the data
>>>> string received from the Thunderbolt is processed, so it is hard to
>>>> imagine
>>>> why one would work and not the other, unless the data received from
>>>> the TB
>>>> is corrupted in the part that should contain the DAV value, and the
>>>> conversion routine fails.
>>>>
>>>> If you have doubts that the serial interface may not be working (I
>>>> am not
>>>> sure about what missing resistor you are talking about), fix that
>>>> first and
>>>> try again.
>>>>
>>>> Looking at the serial stream with a scope may help diagnose such
>>>> problem.
>>>>
>>>> Didier KO4BB
>>>>
>>>> -----Original Message-----
>>>> From: time-nuts-bounces@febo.com
>>>> [mailto:time-nuts-bounces@febo.com] On
>>>> Behalf Of David Bobbett
>>>> Sent: Wednesday, August 18, 2010 4:23 AM
>>>> To: time-nuts@febo.com
>>>> Subject: [time-nuts] Tbolt and iCruse readout problem - any ideas?
>>>>
>>>> Hi all,
>>>>
>>>> Having struggled in vain to solve this problem, I thought I would
>>>> make a
>>>> plea for help as my first posting to Time Nuts . . . so here goes!
>>>>
>>>> I have a Tbolt with v3.00 firmware which works fine with the
>>>> Tboltmon.exe
>>>> V2.60 and Lady Heather software. It also works fine with the iCruse
>>>> Tbolt
>>>> LCD monitor - except that the monitor will not display the "DAC V"
>>>> value,
>>>> all the other values are displayed without a problem.
>>>> The iCruse is the later version which has had the PIC voltage
>>>> conversion
>>>> done, but not the RS232 input resistor mods.
>>>>
>>>>
>>>> I have two questions really:
>>>>
>>>> 1) Is there a setting which I need to change in my Tbolt using
>>>> Tboltmon.exe
>>>> to get this to work?
>>>>
>>>> 2) Does anybody on Time Nuts have an iCruse which shows a negative
>>>> value for
>>>> the "DAC V"?
>>>>
>>>>
>>>> As far as I can see, there are 3 options: a) there is a configuration
>>>> problem, b) the iCruse doesn't display negative values for DAC V,
>>>> c) my
>>>> iCruse is faulty. I've pretty much run out of ideas on this one, so
>>>> any
>>>> suggestions would be greatly appreciated!
>>>>
>>>> Regards,
>>>>
>>>> David Bobbett, Milton Keynes, UK.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> time-nuts mailing list -- time-nuts@febo.com
>>>> To unsubscribe, go to
>>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>>>> and follow the instructions there.
>>>>
>>>>
>>>> _______________________________________________
>>>> time-nuts mailing list -- time-nuts@febo.com
>>>> To unsubscribe, go to
>>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>>>> and follow the instructions there.
>>>>
>>>
>>> _______________________________________________
>>> time-nuts mailing list -- time-nuts@febo.com
>>> To unsubscribe, go to
>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>>> and follow the instructions there.
>>>
>>>
>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts@febo.com
>> To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
DJ
Didier Juges
Thu, Aug 19, 2010 12:28 PM
1 in 400 have a problem, so assuming that he had at least one other complaint would seem to imply that he sold as many as 800 units at least? That sounds somewhat high, but if true, good for him :)
Didier
Sent from my BlackBerry Wireless thingy while I do other things...
-----Original Message-----
From: David Bobbett d.bobbett@tiscali.co.uk
Sender: time-nuts-bounces@febo.com
Date: Thu, 19 Aug 2010 10:20:17
To: Discussion of precise time and frequency measurementtime-nuts@febo.com
Reply-To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Subject: Re: [time-nuts] Tbolt and iCruse readout problem - any ideas?
Further to my messages regarding this problem, I contacted Bob (aka
fluke.l) who replied almost immediately, saying that this has happened
to around 1 in 400 iCruse units and he is working on a fix. Sort of a
relief that there really is a problem and not some strange combination
of events.
On 19/08/2010 08:22, David Bobbett wrote:
Hi Brooke,
I know what you are thinking! Sadly the supply is 12.1v so there's
plenty of regulator headroom, very interesting page though. I'm
beginning to think that Didier's suggestion of corrupted firmware in
the iCruse is the most probable explanation.
Best wishes,
David
On 18/08/2010 16:58, Brooke Clarke wrote:
Hi Didier,
No - the display reads "DAC V: 0.0000" on the iCruse LCD, all the
other data (including temperature) displays normally and correctly.
So it is only that part of the data which doesn't seem to be decoded
and displayed correctly. The really odd thing is that the DAC V
value can be seen in Tboltmon.exe, although I realise that that
particular program also sends data to the Tbolt, which the iCruse
does not.
The reference to the RS232 resistors was in the context of the
discussions regarding whether the values in the iCruse are correct
- but of course if all the other data is being received correctly,
there doesn't seem to be any logical reason why the DAC data would
be any different.
Thanks for the reply, but I'm still puzzled!
David, G4IRQ
On 18/08/2010 12:33, Didier Juges wrote:
When you say "will not display the DAC V value", do you mean the
display is
blank, or it displays garbage?
Interestingly, the code that displays temperature and DAC voltage is
essentially the same, the only difference being which part of the data
string received from the Thunderbolt is processed, so it is hard to
imagine
why one would work and not the other, unless the data received from
the TB
is corrupted in the part that should contain the DAV value, and the
conversion routine fails.
If you have doubts that the serial interface may not be working (I
am not
sure about what missing resistor you are talking about), fix that
first and
try again.
Looking at the serial stream with a scope may help diagnose such
problem.
Didier KO4BB
-----Original Message-----
From: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] On
Behalf Of David Bobbett
Sent: Wednesday, August 18, 2010 4:23 AM
To: time-nuts@febo.com
Subject: [time-nuts] Tbolt and iCruse readout problem - any ideas?
Hi all,
Having struggled in vain to solve this problem, I thought I would
make a
plea for help as my first posting to Time Nuts . . . so here goes!
I have a Tbolt with v3.00 firmware which works fine with the
Tboltmon.exe
V2.60 and Lady Heather software. It also works fine with the iCruse
Tbolt
LCD monitor - except that the monitor will not display the "DAC V"
value,
all the other values are displayed without a problem.
The iCruse is the later version which has had the PIC voltage
conversion
done, but not the RS232 input resistor mods.
I have two questions really:
-
Is there a setting which I need to change in my Tbolt using
Tboltmon.exe
to get this to work?
-
Does anybody on Time Nuts have an iCruse which shows a negative
value for
the "DAC V"?
As far as I can see, there are 3 options: a) there is a configuration
problem, b) the iCruse doesn't display negative values for DAC V,
c) my
iCruse is faulty. I've pretty much run out of ideas on this one, so
any
suggestions would be greatly appreciated!
Regards,
David Bobbett, Milton Keynes, UK.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
1 in 400 have a problem, so assuming that he had at least one other complaint would seem to imply that he sold as many as 800 units at least? That sounds somewhat high, but if true, good for him :)
Didier
------------------------
Sent from my BlackBerry Wireless thingy while I do other things...
-----Original Message-----
From: David Bobbett <d.bobbett@tiscali.co.uk>
Sender: time-nuts-bounces@febo.com
Date: Thu, 19 Aug 2010 10:20:17
To: Discussion of precise time and frequency measurement<time-nuts@febo.com>
Reply-To: Discussion of precise time and frequency measurement
<time-nuts@febo.com>
Subject: Re: [time-nuts] Tbolt and iCruse readout problem - any ideas?
Further to my messages regarding this problem, I contacted Bob (aka
fluke.l) who replied almost immediately, saying that this has happened
to around 1 in 400 iCruse units and he is working on a fix. Sort of a
relief that there really is a problem and not some strange combination
of events.
On 19/08/2010 08:22, David Bobbett wrote:
> Hi Brooke,
>
> I know what you are thinking! Sadly the supply is 12.1v so there's
> plenty of regulator headroom, very interesting page though. I'm
> beginning to think that Didier's suggestion of corrupted firmware in
> the iCruse is the most probable explanation.
>
> Best wishes,
>
> David
>
>
>
> On 18/08/2010 16:58, Brooke Clarke wrote:
>> Hi David:
>>
>> What power supply voltage are you using?
>> http://www.prc68.com/I/ThunderBolt.shtml#iCruze
>>
>> Have Fun,
>>
>> Brooke Clarke
>> http://www.PRC68.com
>>
>>
>> David Bobbett wrote:
>>> Hi Didier,
>>>
>>> No - the display reads "DAC V: 0.0000" on the iCruse LCD, all the
>>> other data (including temperature) displays normally and correctly.
>>> So it is only that part of the data which doesn't seem to be decoded
>>> and displayed correctly. The really odd thing is that the DAC V
>>> value can be seen in Tboltmon.exe, although I realise that that
>>> particular program also sends data to the Tbolt, which the iCruse
>>> does not.
>>>
>>> The reference to the RS232 resistors was in the context of the
>>> discussions regarding whether the values in the iCruse are correct
>>> - but of course if all the other data is being received correctly,
>>> there doesn't seem to be any logical reason why the DAC data would
>>> be any different.
>>>
>>>
>>> Thanks for the reply, but I'm still puzzled!
>>>
>>>
>>> David, G4IRQ
>>>
>>>
>>>
>>>
>>>
>>> On 18/08/2010 12:33, Didier Juges wrote:
>>>> When you say "will not display the DAC V value", do you mean the
>>>> display is
>>>> blank, or it displays garbage?
>>>>
>>>> Interestingly, the code that displays temperature and DAC voltage is
>>>> essentially the same, the only difference being which part of the data
>>>> string received from the Thunderbolt is processed, so it is hard to
>>>> imagine
>>>> why one would work and not the other, unless the data received from
>>>> the TB
>>>> is corrupted in the part that should contain the DAV value, and the
>>>> conversion routine fails.
>>>>
>>>> If you have doubts that the serial interface may not be working (I
>>>> am not
>>>> sure about what missing resistor you are talking about), fix that
>>>> first and
>>>> try again.
>>>>
>>>> Looking at the serial stream with a scope may help diagnose such
>>>> problem.
>>>>
>>>> Didier KO4BB
>>>>
>>>> -----Original Message-----
>>>> From: time-nuts-bounces@febo.com
>>>> [mailto:time-nuts-bounces@febo.com] On
>>>> Behalf Of David Bobbett
>>>> Sent: Wednesday, August 18, 2010 4:23 AM
>>>> To: time-nuts@febo.com
>>>> Subject: [time-nuts] Tbolt and iCruse readout problem - any ideas?
>>>>
>>>> Hi all,
>>>>
>>>> Having struggled in vain to solve this problem, I thought I would
>>>> make a
>>>> plea for help as my first posting to Time Nuts . . . so here goes!
>>>>
>>>> I have a Tbolt with v3.00 firmware which works fine with the
>>>> Tboltmon.exe
>>>> V2.60 and Lady Heather software. It also works fine with the iCruse
>>>> Tbolt
>>>> LCD monitor - except that the monitor will not display the "DAC V"
>>>> value,
>>>> all the other values are displayed without a problem.
>>>> The iCruse is the later version which has had the PIC voltage
>>>> conversion
>>>> done, but not the RS232 input resistor mods.
>>>>
>>>>
>>>> I have two questions really:
>>>>
>>>> 1) Is there a setting which I need to change in my Tbolt using
>>>> Tboltmon.exe
>>>> to get this to work?
>>>>
>>>> 2) Does anybody on Time Nuts have an iCruse which shows a negative
>>>> value for
>>>> the "DAC V"?
>>>>
>>>>
>>>> As far as I can see, there are 3 options: a) there is a configuration
>>>> problem, b) the iCruse doesn't display negative values for DAC V,
>>>> c) my
>>>> iCruse is faulty. I've pretty much run out of ideas on this one, so
>>>> any
>>>> suggestions would be greatly appreciated!
>>>>
>>>> Regards,
>>>>
>>>> David Bobbett, Milton Keynes, UK.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> time-nuts mailing list -- time-nuts@febo.com
>>>> To unsubscribe, go to
>>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>>>> and follow the instructions there.
>>>>
>>>>
>>>> _______________________________________________
>>>> time-nuts mailing list -- time-nuts@febo.com
>>>> To unsubscribe, go to
>>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>>>> and follow the instructions there.
>>>>
>>>
>>> _______________________________________________
>>> time-nuts mailing list -- time-nuts@febo.com
>>> To unsubscribe, go to
>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>>> and follow the instructions there.
>>>
>>>
>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts@febo.com
>> To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
_______________________________________________
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
E
ernieperes@aol.com
Thu, Aug 19, 2010 1:27 PM
Hi David,
did you chked the PIC 3.3 voltage?????? because it is the key point if you have garbled msg.
Rgds, Ernie.
-----Original Message-----
From: Didier Juges didier@cox.net
To: Time-Nuts time-nuts@febo.com
Sent: Thu, Aug 19, 2010 2:28 pm
Subject: Re: [time-nuts] Tbolt and iCruse readout problem - any ideas?
1 in 400 have a problem, so assuming that he had at least one other complaint
ould seem to imply that he sold as many as 800 units at least? That sounds
omewhat high, but if true, good for him :)
Didier
ent from my BlackBerry Wireless thingy while I do other things...
-----Original Message-----
rom: David Bobbett d.bobbett@tiscali.co.uk
ender: time-nuts-bounces@febo.com
ate: Thu, 19 Aug 2010 10:20:17
o: Discussion of precise time and frequency measurementtime-nuts@febo.com
eply-To: Discussion of precise time and frequency measurement
time-nuts@febo.com
ubject: Re: [time-nuts] Tbolt and iCruse readout problem - any ideas?
Further to my messages regarding this problem, I contacted Bob (aka
luke.l) who replied almost immediately, saying that this has happened
o around 1 in 400 iCruse units and he is working on a fix. Sort of a
elief that there really is a problem and not some strange combination
f events.
n 19/08/2010 08:22, David Bobbett wrote:
Hi Brooke,
I know what you are thinking! Sadly the supply is 12.1v so there's
plenty of regulator headroom, very interesting page though. I'm
beginning to think that Didier's suggestion of corrupted firmware in
the iCruse is the most probable explanation.
Best wishes,
David
On 18/08/2010 16:58, Brooke Clarke wrote:
Hi Didier,
No - the display reads "DAC V: 0.0000" on the iCruse LCD, all the
other data (including temperature) displays normally and correctly.
So it is only that part of the data which doesn't seem to be decoded
and displayed correctly. The really odd thing is that the DAC V
value can be seen in Tboltmon.exe, although I realise that that
particular program also sends data to the Tbolt, which the iCruse
does not.
The reference to the RS232 resistors was in the context of the
discussions regarding whether the values in the iCruse are correct
- but of course if all the other data is being received correctly,
there doesn't seem to be any logical reason why the DAC data would
be any different.
Thanks for the reply, but I'm still puzzled!
David, G4IRQ
On 18/08/2010 12:33, Didier Juges wrote:
When you say "will not display the DAC V value", do you mean the
display is
blank, or it displays garbage?
Interestingly, the code that displays temperature and DAC voltage is
essentially the same, the only difference being which part of the data
string received from the Thunderbolt is processed, so it is hard to
imagine
why one would work and not the other, unless the data received from
the TB
is corrupted in the part that should contain the DAV value, and the
conversion routine fails.
If you have doubts that the serial interface may not be working (I
am not
sure about what missing resistor you are talking about), fix that
first and
try again.
Looking at the serial stream with a scope may help diagnose such
problem.
Didier KO4BB
-----Original Message-----
From: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] On
Behalf Of David Bobbett
Sent: Wednesday, August 18, 2010 4:23 AM
To: time-nuts@febo.com
Subject: [time-nuts] Tbolt and iCruse readout problem - any ideas?
Hi all,
Having struggled in vain to solve this problem, I thought I would
make a
plea for help as my first posting to Time Nuts . . . so here goes!
I have a Tbolt with v3.00 firmware which works fine with the
Tboltmon.exe
V2.60 and Lady Heather software. It also works fine with the iCruse
Tbolt
LCD monitor - except that the monitor will not display the "DAC V"
value,
all the other values are displayed without a problem.
The iCruse is the later version which has had the PIC voltage
conversion
done, but not the RS232 input resistor mods.
I have two questions really:
-
Is there a setting which I need to change in my Tbolt using
Tboltmon.exe
to get this to work?
-
Does anybody on Time Nuts have an iCruse which shows a negative
value for
the "DAC V"?
As far as I can see, there are 3 options: a) there is a configuration
problem, b) the iCruse doesn't display negative values for DAC V,
c) my
iCruse is faulty. I've pretty much run out of ideas on this one, so
any
suggestions would be greatly appreciated!
Regards,
David Bobbett, Milton Keynes, UK.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hi David,
did you chked the PIC 3.3 voltage?????? because it is the key point if you have garbled msg.
Rgds, Ernie.
-----Original Message-----
From: Didier Juges <didier@cox.net>
To: Time-Nuts <time-nuts@febo.com>
Sent: Thu, Aug 19, 2010 2:28 pm
Subject: Re: [time-nuts] Tbolt and iCruse readout problem - any ideas?
1 in 400 have a problem, so assuming that he had at least one other complaint
ould seem to imply that he sold as many as 800 units at least? That sounds
omewhat high, but if true, good for him :)
Didier
------------------------
ent from my BlackBerry Wireless thingy while I do other things...
-----Original Message-----
rom: David Bobbett <d.bobbett@tiscali.co.uk>
ender: time-nuts-bounces@febo.com
ate: Thu, 19 Aug 2010 10:20:17
o: Discussion of precise time and frequency measurement<time-nuts@febo.com>
eply-To: Discussion of precise time and frequency measurement
<time-nuts@febo.com>
ubject: Re: [time-nuts] Tbolt and iCruse readout problem - any ideas?
Further to my messages regarding this problem, I contacted Bob (aka
luke.l) who replied almost immediately, saying that this has happened
o around 1 in 400 iCruse units and he is working on a fix. Sort of a
elief that there really is a problem and not some strange combination
f events.
n 19/08/2010 08:22, David Bobbett wrote:
Hi Brooke,
I know what you are thinking! Sadly the supply is 12.1v so there's
plenty of regulator headroom, very interesting page though. I'm
beginning to think that Didier's suggestion of corrupted firmware in
the iCruse is the most probable explanation.
Best wishes,
David
On 18/08/2010 16:58, Brooke Clarke wrote:
> Hi David:
>
> What power supply voltage are you using?
> http://www.prc68.com/I/ThunderBolt.shtml#iCruze
>
> Have Fun,
>
> Brooke Clarke
> http://www.PRC68.com
>
>
> David Bobbett wrote:
>> Hi Didier,
>>
>> No - the display reads "DAC V: 0.0000" on the iCruse LCD, all the
>> other data (including temperature) displays normally and correctly.
>> So it is only that part of the data which doesn't seem to be decoded
>> and displayed correctly. The really odd thing is that the DAC V
>> value can be seen in Tboltmon.exe, although I realise that that
>> particular program also sends data to the Tbolt, which the iCruse
>> does not.
>>
>> The reference to the RS232 resistors was in the context of the
>> discussions regarding whether the values in the iCruse are correct
>> - but of course if all the other data is being received correctly,
>> there doesn't seem to be any logical reason why the DAC data would
>> be any different.
>>
>>
>> Thanks for the reply, but I'm still puzzled!
>>
>>
>> David, G4IRQ
>>
>>
>>
>>
>>
>> On 18/08/2010 12:33, Didier Juges wrote:
>>> When you say "will not display the DAC V value", do you mean the
>>> display is
>>> blank, or it displays garbage?
>>>
>>> Interestingly, the code that displays temperature and DAC voltage is
>>> essentially the same, the only difference being which part of the data
>>> string received from the Thunderbolt is processed, so it is hard to
>>> imagine
>>> why one would work and not the other, unless the data received from
>>> the TB
>>> is corrupted in the part that should contain the DAV value, and the
>>> conversion routine fails.
>>>
>>> If you have doubts that the serial interface may not be working (I
>>> am not
>>> sure about what missing resistor you are talking about), fix that
>>> first and
>>> try again.
>>>
>>> Looking at the serial stream with a scope may help diagnose such
>>> problem.
>>>
>>> Didier KO4BB
>>>
>>> -----Original Message-----
>>> From: time-nuts-bounces@febo.com
>>> [mailto:time-nuts-bounces@febo.com] On
>>> Behalf Of David Bobbett
>>> Sent: Wednesday, August 18, 2010 4:23 AM
>>> To: time-nuts@febo.com
>>> Subject: [time-nuts] Tbolt and iCruse readout problem - any ideas?
>>>
>>> Hi all,
>>>
>>> Having struggled in vain to solve this problem, I thought I would
>>> make a
>>> plea for help as my first posting to Time Nuts . . . so here goes!
>>>
>>> I have a Tbolt with v3.00 firmware which works fine with the
>>> Tboltmon.exe
>>> V2.60 and Lady Heather software. It also works fine with the iCruse
>>> Tbolt
>>> LCD monitor - except that the monitor will not display the "DAC V"
>>> value,
>>> all the other values are displayed without a problem.
>>> The iCruse is the later version which has had the PIC voltage
>>> conversion
>>> done, but not the RS232 input resistor mods.
>>>
>>>
>>> I have two questions really:
>>>
>>> 1) Is there a setting which I need to change in my Tbolt using
>>> Tboltmon.exe
>>> to get this to work?
>>>
>>> 2) Does anybody on Time Nuts have an iCruse which shows a negative
>>> value for
>>> the "DAC V"?
>>>
>>>
>>> As far as I can see, there are 3 options: a) there is a configuration
>>> problem, b) the iCruse doesn't display negative values for DAC V,
>>> c) my
>>> iCruse is faulty. I've pretty much run out of ideas on this one, so
>>> any
>>> suggestions would be greatly appreciated!
>>>
>>> Regards,
>>>
>>> David Bobbett, Milton Keynes, UK.
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> time-nuts mailing list -- time-nuts@febo.com
>>> To unsubscribe, go to
>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>>> and follow the instructions there.
>>>
>>>
>>> _______________________________________________
>>> time-nuts mailing list -- time-nuts@febo.com
>>> To unsubscribe, go to
>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>>> and follow the instructions there.
>>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts@febo.com
>> To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
_______________________________________________
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
_______________________________________________
ime-nuts mailing list -- time-nuts@febo.com
o unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
nd follow the instructions there.
______________________________________________
ime-nuts mailing list -- time-nuts@febo.com
o unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
nd follow the instructions there.