开云体育

  1. LTspice
  2. Topics

Error when loading LTC6258_LTC6992-1_F04A_Oscillator.asc file SOLVED tnx to Andy !

 

开云体育

Andy,

BINGO !

I followed your instructions and the simulation in LTspice IV is running 100% OK !

After renaming the original LTC3.lib as LTC3.ori, i've copied the LTspice XVII's LTC3.lib in the LTspice IV \sub folder.

No more error and i get the same simulation result as with LTspice XVII.

I'ts the best solution for me because i prefer to continue my occasional simulations with LTspice IV. (i've a lot of *.asc files...)

If necessary for a new component, i will do your Unicode => ANSI modif. via Bloc-notes and importation of *.lib too.

Thank you very much for your help.

Best regards,

Rudi

PS i will upload a screen-shot into "Photos"


Le 23.05.2018 à 06:21, ai.egrps@... [LTspice] a écrit?:
?

Rudi, it's hard to read the error text in the screenshot photo you uploaded, but I think it points to the LTC6258.

I think the problem is that the LTC6258 model is too recent for LTspice IV. The standard LTspice IV installation did not come with the LTC6258 SPICE model. In my LTspice IV, it has the models for LTC6252, 6253, 6254, and 6255 -- and then there is a gap until 6268. I guess this means that the 6258 model did not exist until after LTspice XVII was introduced. Linear Tech decided there will be no further upgrades to LTspice IV. Therefore newer models, such as the LTC6258, will not be added to LTspice IV by Linear Tech / Analog Devices.

But there is a work-around, if you need to use LTspice IV. You can copy the SPICE model for the LTC6258 from LTspice XVII (which is contained within Documents\LTspiceXVII\lib\sub\LTC3.lib) to the lib\sub folder where you have LTspice IV installed. It would overwrite the LTC3.lib file that's already there, so it would be a good idea to rename the old file first, just in case.

Actually, I'm surprised that you could even open the schematic in LTspice IV, because LTspice IV doesn't have a schematic symbol for the LTC6258. But your picture shows one. Where did it come from?

Regards,
Andy




L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.


 

All of your *.asc files should open and simulate fine in LTspice XVII; at least mine do.

If you've modified the distributed libraries from LTspice IV, that is a different problem that is readily solved by keeping the non-LT models, subcircuits, and symbols in the directory of the project. That way, one never has to guess which models/libs/... are from outside sources and which are from the LTspice installation. (I figure everything from LTspice belongs to LTspice and is for it to manage; everything else is mine.)

Donald.
--
*Plain Text* email -- it's an accessibility issue
() no proprietary attachments; no html mail
/&#92; <>

On 23-May-2018 03:11, Rudolf Schaffer rudolf.schaffer@... [LTspice] wrote:
Andy,
BINGO !
I followed your instructions and the simulation in LTspice IV is running 100% OK !
After renaming the original LTC3.lib as LTC3.ori, i've copied the LTspice XVII's LTC3.lib in the LTspice IV &#92;sub folder.
No more error and i get the same simulation result as with LTspice XVII.
I'ts the best solution for me because i prefer to continue my occasional simulations with LTspice IV. (i've a lot of *.asc files...)
If necessary for a new component, i will do your Unicode => ANSI modif. via Bloc-notes and importation of *.lib too.
Thank you very much for your help.
Best regards,
Rudi
PS i will upload a screen-shot into "Photos"
Le 23.05.2018 à 06:21, ai.egrps@... [LTspice] a écrit?:

Rudi, it's hard to read the error text in the screenshot photo you uploaded, but I think it points to the LTC6258.

I think the problem is that the LTC6258 model is too recent for LTspice IV. The standard LTspice IV installation did not come with the LTC6258 SPICE model. In my LTspice IV, it has the models for LTC6252, 6253, 6254, and 6255 -- and then there is a gap until 6268. I guess this means that the 6258 model did not exist until after LTspice XVII was introduced. Linear Tech decided there will be no further upgrades to LTspice IV. Therefore newer models, such as the LTC6258, will not be added to LTspice IV by Linear Tech / Analog Devices.

But there is a work-around, if you need to use LTspice IV. You can copy the SPICE model for the LTC6258 from LTspice XVII (which is contained within Documents&#92;LTspiceXVII&#92;lib&#92;sub&#92;LTC3.lib) to the lib&#92;sub folder where you have LTspice IV installed. It would overwrite the LTC3.lib file that's already there, so it would be a good idea to rename the old file first, just in case.

Actually, I'm surprised that you could even open the schematic in LTspice IV, because LTspice IV doesn't have a schematic symbol for the LTC6258. But your picture shows one. Where did it come from?

Regards,
Andy
---------------------------------------------------------------------------
Avast logo <>
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com <>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
 

开云体育

Hi Donald,

Thank you for your reply and information.

May be something is not correct in my set-up, but i'm obliged to convert my .asc files from ANSI to Unicode as Andy wrote.

In a near future, i will try again to load directly my .asc files into LTspice XVII; for the moment i must continue with my current

project. A good idea to have the non LT files in the project directory ! I will follow your recommendation, sure !

Best regards,

Rudi


Le 23.05.2018 à 12:55, Donald H Locker dhlocker@... [LTspice] a écrit?:

?

All of your *.asc files should open and simulate fine in LTspice XVII; at
least mine do.

If you've modified the distributed libraries from LTspice IV, that is a
different problem that is readily solved by keeping the non-LT models,
subcircuits, and symbols in the directory of the project. That way, one
never has to guess which models/libs/... are from outside sources and which
are from the LTspice installation. (I figure everything from LTspice
belongs to LTspice and is for it to manage; everything else is mine.)

Donald.
--
*Plain Text* email -- it's an accessibility issue
() no proprietary attachments; no html mail
/\

On 23-May-2018 03:11, Rudolf Schaffer rudolf.schaffer@... [LTspice]
wrote:
>
>
> Andy,
>
> BINGO !
>
> I followed your instructions and the simulation in LTspice IV is running
> 100% OK !
>
> After renaming the original LTC3.lib as LTC3.ori, i've copied the LTspice
> XVII's LTC3.lib in the LTspice IV \sub folder.
>
> No more error and i get the same simulation result as with LTspice XVII.
>
> I'ts the best solution for me because i prefer to continue my occasional
> simulations with LTspice IV. (i've a lot of *.asc files...)
>
> If necessary for a new component, i will do your Unicode => ANSI modif. via
> Bloc-notes and importation of *.lib too.
>
> Thank you very much for your help.
>
> Best regards,
>
> Rudi
>
> PS i will upload a screen-shot into "Photos"
>
>
> Le 23.05.2018 à 06:21, ai.egrps@... [LTspice] a écrit?:
>>
>> Rudi, it's hard to read the error text in the screenshot photo you
>> uploaded, but I think it points to the LTC6258.
>>
>> I think the problem is that the LTC6258 model is too recent for LTspice
>> IV. The standard LTspice IV installation did not come with the LTC6258
>> SPICE model. In my LTspice IV, it has the models for LTC6252, 6253, 6254,
>> and 6255 -- and then there is a gap until 6268. I guess this means that
>> the 6258 model did not exist until after LTspice XVII was introduced.
>> Linear Tech decided there will be no further upgrades to LTspice IV.
>> Therefore newer models, such as the LTC6258, will not be added to LTspice
>> IV by Linear Tech / Analog Devices.
>>
>> But there is a work-around, if you need to use LTspice IV. You can copy
>> the SPICE model for the LTC6258 from LTspice XVII (which is contained
>> within Documents\LTspiceXVII\lib\sub\LTC3.lib) to the lib\sub folder
>> where you have LTspice IV installed. It would overwrite the LTC3.lib file
>> that's already there, so it would be a good idea to rename the old file
>> first, just in case.
>>
>> Actually, I'm surprised that you could even open the schematic in LTspice
>> IV, because LTspice IV doesn't have a schematic symbol for the LTC6258.
>> But your picture shows one. Where did it come from?
>>
>> Regards,
>> Andy
>>
>
>
>
> ----------------------------------------------------------
> Avast logo
>
> L'absence de virus dans ce courrier électronique a été vérifiée par le
> logiciel antivirus Avast.
>
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
>


 

Rudi wrote:

"May be something is not correct in my set-up, but i'm obliged to convert my .asc files from ANSI to Unicode as Andy wrote."

You might have misunderstood me. You do not need to convert your old .asc files from ANSI to Unicode! LTspice XVII is OK with both Unicode and ANSI (non-Unicode) .asc files.

LTspice XVII usually saves new .asc files without Unicode. But if there is a character on your schematic that requires Unicode, then it changes to Unicode and THEN it's a problem for LTspice IV. (And when that happens, it seems to set a flag in LTspice to save with Unicode, and you must exit from LTspice to reset that flag.)

Almost all (if not all) .asc files from LTspice IV should open directly in LTspice XVII -- unless you customized your LTspice IV libraries, as Donald noted.

One of the only reasons for keeping LTspice IV, is if you have a computer running Windows XP.

Regards,
Andy

1 - 4 of 4