MPDCenter - Inventory problem

[Marc Belanger]

Hello all,

I recently got a new computer (Windows 10), and after installing MPDCenter, I’m encountering an issue where it won't create an Inventory file. I receive the following error message:

"La conversion de la chaîne '1/426' en Integer n'est pas valide. Microsoft VisualBasic."
This translates to something like: "Conversion of the string '1/426' to Integer is not valid. Microsoft VisualBasic."

Even though MPDCenter generates the .bat, .html, and .pbg files, the .html file only contains the table headers:
Parts List for 40691_mythical_pegasus_bird.mpd (0 parts) and Part/Color/Quantity.

Any help would be appreciated.

Thanks,
Marc

[Manfred Schaefer]

Hello all,

I recently got a new computer (Windows 10), and after installing MPDCenter, I’m encountering an issue where it won't create an Inventory file. I receive the following error message:

"La conversion de la chaîne '1/426' en Integer n'est pas valide. Microsoft VisualBasic."
This translates to something like: "Conversion of the string '1/426' to Integer is not valid. Microsoft VisualBasic."

Even though MPDCenter generates the .bat, .html, and .pbg files, the .html file only contains the table headers:
Parts List for 40691_mythical_pegasus_bird.mpd (0 parts) and Part/Color/Quantity.

Any help would be appreciated.

Thanks,
Marc

Hello,

It could be related to the new structure of LDConfig.ldr.

Entry in LDconfig.ldr
0                              // LEGOID  1/426 - White
0 !COLOUR White
CODE    15  VALUE #F4F4F4  EDGE #333333

I can't tell you why “LEGOID  1 - White”  became “LEGOID  1/426 - White”. 

Best regards,

Manfred

[Marc Belanger]

[quote pid="58806" dateline="1760629380"]
It could be related to the new structure of LDConfig.ldr.

Entry in LDconfig.ldr
0                              // LEGOID  1/426 - White
0 !COLOUR White
CODE    15  VALUE #F4F4F4  EDGE #333333

I can't tell you why “LEGOID  1 - White”  became “LEGOID  1/426 - White”. 
[/quote]

I changed the parameters in my LDConfig.ldr file. The error messages stopped, but I still have blank inventory lists. My file is OMR compliant.
--
M.

EDIT: I tried creating an Inventory List on my old computer, and I also get empty lists. Strange... Could it be my file, even though it is compliant?

[Manfred Schaefer]

[quote pid="58806" dateline="1760629380"]
It could be related to the new structure of LDConfig.ldr.

Entry in LDconfig.ldr
0                              // LEGOID  1/426 - White
0 !COLOUR White
CODE    15  VALUE #F4F4F4  EDGE #333333

I can't tell you why “LEGOID  1 - White”  became “LEGOID  1/426 - White”. 

I changed the parameters in my LDConfig.ldr file. The error messages stopped, but I still have blank inventory lists. My file is OMR compliant.
--
M.

EDIT: I tried creating an Inventory List on my old computer, and I also get empty lists. Strange... Could it be my file, even though it is compliant?
[/quote]


----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hello,

can you upload your file here?

Greetings

Manfred

[Marc Belanger]

Hello,

It could be related to the new structure of LDConfig.ldr.

Entry in LDconfig.ldr
0                              // LEGOID  1/426 - White
0 !COLOUR White
CODE    15  VALUE #F4F4F4  EDGE #333333

I can't tell you why “LEGOID  1 - White”  became “LEGOID  1/426 - White”. 

Best regards,

Manfred

I changed the parameters in my LDConfig.ldr file. The error messages stopped, but I still have blank inventory lists. My file is OMR compliant.
--
M.

EDIT: I tried creating an Inventory List on my old computer, and I also get empty lists. Strange... Could it be my file, even though it is compliant?

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hello,

can you upload your file here?

Greetings

Manfred
[/quote]

Here you go.

[Chris Böhnke]

Hello,

as far as I know, the ldconfig entries with double numbers exist for a little longer now. This particular case likely since April 2025 (when Lego introduced "426 White V.3").

Can anyone confirm whether or not this causes the issue?

Certain colours had double entries far longer - Dark Pink for example used to be listed as " // LEGOID  22 / 221 - Medium Reddish Violet / Bright Purple". I am assuming that most of these never caused the problem because the colours are more rare than White?

Have you tried 226 Bright Light Yellow? This one has a similar entry due to the V.3 version.

[Manfred Schaefer]

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hello,
can you upload your file here?
Greetings
Manfred

Here you go.
[/quote]

------------------------------------------------------------------------------------------------------------------

Hello,
I can't find anything that could be wrong with your file.

Greetings

Manfred

[Marc Belanger]

I can't find anything that could be wrong with your file.

Thank you.

[Marc Belanger]

Have you tried 226 Bright Light Yellow? This one has a similar entry due to the V.3 version.

I've found a solution, but I'm not sure if it will last. In the LDConfig.ldr file, the problematic entry for White was written as '1/426.' I noticed similar entries written as '999 / 999,' with spaces between the numbers and the slash. So, I changed '1/426' to '1 / 426' and '226 / 427' for Cool Yellow, and now everything seems to be working as it should.
--
M.

[Marc Belanger]

Spoke too soon—it works with some MPD files, but not all of them. Again, any help would be appreciated.
--
M.

[Orion Pobursky]

I've found a solution, but I'm not sure if it will last. In the LDConfig.ldr file, the problematic entry for White was written as '1/426.' I noticed similar entries written as '999 / 999,' with spaces between the numbers and the slash. So, I changed '1/426' to '1 / 426' and '226 / 427' for Cool Yellow, and now everything seems to be working as it should.
--
M.

This is 100% an issue with MPDCenter improperly parsing comments for information. There is no issue with LDConfig and the "/" characters are allowed in comments.

[Marc Belanger]

This is 100% an issue with MPDCenter improperly parsing comments for information. There is no issue with LDConfig and the "/" characters are allowed in comments.

True. The problem seems to be the space characters between the numbers (1 and 426 in this case) and the slash character. Adding spaces worked for me.
--
M.

[Marc Belanger]

Anyway, I found the problem. The MPD files that MPDCenter couldn't generate the parts list for had empty main.ldr sections. Adding a part to the main.ldr section fixed the issue.

Thanks, everyone!
--
M.