Jump to content

Error: Object reference not set to an instance of an object


Recommended Posts

Posted

Hi,

I got the following error and do not know what it means nor how to solve it:

 

image.png.e5341a6644f963a134d77624f55e9ef6.png

 

I was working on a project and saved it successfully, then went on to create more buildings in the 3D Design area. When I did, PV SOL asked whether it was OK to delete the shading simulation, which I accepted. I then tried to exit the 3D Design and was prompted to simulate shading, which I declined, as I was not done yet (I had already configured some modules with their inverters).

 

And then when I tried to save my project that error popped up. Am I doing something wrong? I had previously created other buildings and it was not a problem.

 

Thanks for your support.

 

Posted

So, just for the record, and in case that other users have a similar problem:

In PV*SOL premium 2019 R2 there is a bug that can occur when you have the following setup:

  • you edit a 3D project were shadows have already been calculated
  • You add more objects in 3D so that the shading calculations are deleted
  • Then you leave 3D, adopt the data to PV*SOL, but you don't recalculate the shadows
  • When you then try to save the file, an error might occur, depending on the inverter configuration you have

We will fix this bug in the next release. For now you can save the projects when you calculate the shadows again.

Sorry for the inconvenience,

Martin

Posted (edited)

Dear Martin,

I have another bug in the R2 version; It is not possible to select single modules in the mounted version. You can only select entire rows so it is not possible to just use 10 of the 100 modules to connect to a inverter.

 

Is the new release coming soon? I really need this function...

(for now, is it possible to download the older version of the program?)

Kind regards

 

Yvar

Edited by developer_mh
full quote removed
Posted (edited)

haha o, yes, that helps xD. It was always on in the previous version, so I never thought of trying the buttons. Thank you!

Edited by developer_mh
full quote removed
Posted

thanks, I had the same problem. good to know what the cause is. the workaround is just to recalculate the shadow when annotating from 3d to calculation and the saving works !

Posted

Hi Martin and everyone,

Is the bug I mentioned fixed in the new release to be downloaded today? I mean the one causing "Error: Object reference not set to an instance of an object" that originated this post.

Thanks!!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...