Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

What does this log error mean?


catherineryanhyde
 Share

Question

I'm using BYN 2.1.2, premium. I've posted a couple of times lately about various errors that ended the imaging session with my older D810A. I believed, and still do, that the problem was the data cable port on the camera, due to minor cable snags and age. I emailed in a log (with a link to my forum post), but have not heard back. I recently replaced the older camera with a brand new D850, which I had astro-modified. Over the course of an hour or two of imaging, a "camera shutdown" will disconnect the camera and end the imaging session more than once. I initially thought the camera might be set to put itself to sleep, but that makes no sense in light of the fact that it's on AC power and is actively imaging. Also I can immediately reconnect without going out to do anything with the camera. The log is giving me this error, which I don't understand:  "Object reference not set to an instance of an object." Can anyone help me make sense of this?  

Link to comment
Share on other sites

  • Answers 32
  • Created
  • Last Reply

Top Posters For This Question

Recommended Posts

  • 0

This is not BYN related, it's a physical issue in the connection path IMO, so I can't really help from a software perspective :(

In power settings, you should have an option to prevent the USB from going to sleep.

What brand is the cable, is it USB2 or USB3?

image.png

Link to comment
Share on other sites

  • 0
15 minutes ago, astroman133 said:

You should follow the HOW-TO instructions on submitting a log file to Guylain. It is preferred that it NOT be posted to the forum.

The "Object reference..." entry indicates some kind of unexpected response or a  programming error.

 

I did not post the log to the forum. As I stated above "I emailed in a log (with a link to my forum post)" based on the directions he gave me.

Link to comment
Share on other sites

  • 0
2 minutes ago, astroman133 said:

I did not mean to suggest that you did post a log to the forum. My comment was more for other users who may have an issue.

You have a new issue with a new camera and should provide a log file that contains that issue.

 

Okay. Still haven't heard back about the last one, though.

Link to comment
Share on other sites

  • 0

I know that what you have posted will prompt Guylain to look back to what you sent earlier this month, but I got the impression that you had diagnosed your issue with the D810A as being a faulty USB jack on the one camera.

So do you still plan to use both cameras with BYN?

Link to comment
Share on other sites

  • 0
48 minutes ago, astroman133 said:

I know that what you have posted will prompt Guylain to look back to what you sent earlier this month, but I got the impression that you had diagnosed your issue with the D810A as being a faulty USB jack on the one camera.

So do you still plan to use both cameras with BYN?

I'm not going to use the old D810A anymore (I also bought a brand new D810A from Japan, as I have two setups), but it does concern me that I still get session-ending errors with a brand new camera. I'll try the new D810A tonight and see if I have similar issues.

Link to comment
Share on other sites

  • 0

Hi Catherine,

I found the log file in my spam folder.

I think you have a power source issue and/or cable snag. You have several StateEvent_Shutdown events in your logfile and I don't see evidence that you click disconnects. How are you providing power to the camera?  Battery or AC adapter?

2022-01-02 13:44:26,195 [OnStateEventHandler] INFO  - StateEvent_Shutdown Fired! (inParameter=0)
2022-01-02 13:44:26,548 [OnStateEventHandler] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2022-01-02 13:44:26,573 [OnStateEventHandler] DEBUG - ERROR EDS_ERR_INVALID_HANDLE : EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2022-01-02 13:44:26,573 [OnStateEventHandler] DEBUG -    at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.RunAndThrow(Func`1 function, String info)
   at BinaryRivers.Camera.Canon.PropertyBaseUint.UploadPropertyValueToCamera(UInt32 propertyid, Int32 param, UInt32 value)

 

Link to comment
Share on other sites

  • 0
2 minutes ago, admin said:

Hi Catherine,

I found the log file in my spam folder.

I think you have a power source issue and/or cable snag. You have several StateEvent_Shutdown events in your logfile and I don't see evidence that you click disconnects. How are you providing power to the camera?  Battery or AC adapter?


2022-01-02 13:44:26,195 [OnStateEventHandler] INFO  - StateEvent_Shutdown Fired! (inParameter=0)
2022-01-02 13:44:26,548 [OnStateEventHandler] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2022-01-02 13:44:26,573 [OnStateEventHandler] DEBUG - ERROR EDS_ERR_INVALID_HANDLE : EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2022-01-02 13:44:26,573 [OnStateEventHandler] DEBUG -    at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.RunAndThrow(Func`1 function, String info)
   at BinaryRivers.Camera.Canon.PropertyBaseUint.UploadPropertyValueToCamera(UInt32 propertyid, Int32 param, UInt32 value)

 

AC adapter. And it happened in the absence of any slewing, often more than once, so a cable snag seems unlikely. However, this was with the old camera. Still, it could be a very brief interruption to power. I have solar that switches to the grid when the sun is not out, rather than storing to a battery. However, this does not seem to explain why it would happen several times in the middle of the night. Still, it's an avenue to explore. I'll try running the camera on a battery, or plugging my camera AC adapter into a big field power pack and see if that makes a difference.

Link to comment
Share on other sites

  • 0
18 hours ago, admin said:

Hi Catherine,

I found the log file in my spam folder.

I think you have a power source issue and/or cable snag. You have several StateEvent_Shutdown events in your logfile and I don't see evidence that you click disconnects. How are you providing power to the camera?  Battery or AC adapter?



2022-01-02 13:44:26,195 [OnStateEventHandler] INFO  - StateEvent_Shutdown Fired! (inParameter=0)
2022-01-02 13:44:26,548 [OnStateEventHandler] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2022-01-02 13:44:26,573 [OnStateEventHandler] DEBUG - ERROR EDS_ERR_INVALID_HANDLE : EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2022-01-02 13:44:26,573 [OnStateEventHandler] DEBUG -    at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.RunAndThrow(Func`1 function, String info)
   at BinaryRivers.Camera.Canon.PropertyBaseUint.UploadPropertyValueToCamera(UInt32 propertyid, Int32 param, UInt32 value)

 

I wanted very much to be able to say it was a power source issue. But last night I ran the camera on a battery. And yes, I was very careful to be sure the battery was never exhausted. I even switched batteries once in only about a 4-hour session. And it gave a "camera shutdown" message twice and ended the session twice. The second time I had set it to take darks. The mount was parked. According to the software it took one dark and then the camera shut down. But here's what's weird. I always set it to save to both PC and camera. And all 18 darks were on the memory card this morning. So at least in that respect it's not the camera, and the camera clearly did not shut down. Could be a download issue, but brand new camera and brand new cable... We have eliminated power issues, since the camera was not on AC power as it usually is, and eliminated cable snags because it was parked. Another weird issue. If I try to go in and find you another log, the newest log in the folder is from January 2nd. Please tell me all this adds up to something you can help me with.  (PS: Also we have eliminated the possibility of my accidentally hitting disconnect, as I started the image session and went to bed.)

Edited by catherineryanhyde
Adding one thing.
Link to comment
Share on other sites

  • 0
12 hours ago, admin said:

Let's rule out the logfile mystery then, please send it again.

 

 
 
 

Unfortunately, as I stated in my reply above, for some reason the newer logs are not in the folder. And I see no purpose in resending the old one (unless you tell me otherwise) since it was a different camera and a different error.

Link to comment
Share on other sites

  • 0

Catherine,

I agree that it makes no sense to re-send a Canon log file when your issue is with the Nikon D810A. If the problem is persistent then you should be able to re-create it, even if you currently have no log files.

Are you sure that you are looking in the folder where BYN is storing its log files? The symptoms are that only older logs are in that folder. This could mean that somehow the location was changed and the newer logs are in a different folder. Or it could mean that you are looking in the BYE log files folder, not the BYN log files folder.

Link to comment
Share on other sites

  • 0
1 hour ago, astroman133 said:

Catherine,

I agree that it makes no sense to re-send a Canon log file when your issue is with the Nikon D810A. If the problem is persistent then you should be able to re-create it, even if you currently have no log files.

Are you sure that you are looking in the folder where BYN is storing its log files? The symptoms are that only older logs are in that folder. This could mean that somehow the location was changed and the newer logs are in a different folder. Or it could mean that you are looking in the BYE log files folder, not the BYN log files folder.

Okay, I'm really stuck now. I've even tried searching the whole hard drive for log files. The only ones connected to BYE or BYN end at 1/2/22. Can you please look at this image and tell me if I seem to be in the right place? (I really don't understand Windows well as I only use it for astro software.) Is there a chance that I really am having an issue with the BYN software and it's not saving logs? Should I try uninstalling and reinstalling? I just don't know what to do, and it's really messing with my ability to image.

Also, could you please read the other reply I posted today, where I give details about last night's imaging sessions? I ruled out a couple of things and discovered  that the camera goes on taking (and writing to the memory card) images long after BYN says it has shut down. BYN ends the imaging session but the camera doesn't seem to know it, and I feel like that adds info, but I don't understand it. Again I want to mention that this is not the older D810A I'm having trouble with. It' a brand new modified D850 with probably fewer than 100 images on its counter.

IMG_3037.jpeg

Edited by catherineryanhyde
Added info
Link to comment
Share on other sites

  • 0

So you use BYN with 3 cameras (old D810A, new D810A, brand new D850) and have the same issue with all of them. Is that correct? If so, I would test going forward with just one of the cameras. If we are able to solve the issue it may be easy to replicate the fix to the others.

BYN does not choose where to save the log files...You tell the software where you want your log files saved. BYE and BYN can be told to save their log files in different folders. Doing so makes it more difficult to confuse them.

Start BYN and click on the Settings button at the upper right. Below is what my Settings looks like. It is for BYE, but yours should look very similar. Look at the BackyardTEMP  folder location that I have circled in red. Your setting will likely be different from mine. Open a File Explorer window and browse to your BackyardTEMP folder. You should see log files in the Logs subfolder.

image.png.3df7f7bf53665fb5661f8ec3d907da63.png

The log files are readable text files so you should be able to double-click on a log file to display it in the Notepad app. Read the top of the file to see if it is for the correct camera.

I would also suggest configuring BYN to save your images only to the PC. In the past some users have reported issues when trying to save to both locations. It changes the timing since it takes a few seconds to save the image to the camera's SD card.

Also it seems strange that BYN would appear to lock up, but the camera continues to take images and save them to the memory card. BYN only takes one image at a time so it could not be both locked up and continuing to take, but not display, images. Something else must be happening.

Link to comment
Share on other sites

  • 0
48 minutes ago, astroman133 said:

So you use BYN with 3 cameras (old D810A, new D810A, brand new D850) and have the same issue with all of them. Is that correct? If so, I would test going forward with just one of the cameras. If we are able to solve the issue it may be easy to replicate the fix to the others.

BYN does not choose where to save the log files...You tell the software where you want your log files saved. BYE and BYN can be told to save their log files in different folders. Doing so makes it more difficult to confuse them.

Start BYN and click on the Settings button at the upper right. Below is what my Settings looks like. It is for BYE, but yours should look very similar. Look at the BackyardTEMP  folder location that I have circled in red. Your setting will likely be different from mine. Open a File Explorer window and browse to your BackyardTEMP folder. You should see log files in the Logs subfolder.

image.png.3df7f7bf53665fb5661f8ec3d907da63.png

The log files are readable text files so you should be able to double-click on a log file to display it in the Notepad app. Read the top of the file to see if it is for the correct camera.

I would also suggest configuring BYN to save your images only to the PC. In the past some users have reported issues when trying to save to both locations. It changes the timing since it takes a few seconds to save the image to the camera's SD card.

Also it seems strange that BYN would appear to lock up, but the camera continues to take images and save them to the memory card. BYN only takes one image at a time so it could not be both locked up and continuing to take, but not display, images. Something else must be happening.

That was helpful. Thanks. I was able to find the log file. I don't use all three of those cameras. I did use the old D810A but I replaced it because I thought it was the problem. Going forward I will use the D850 on this setup and the new D810A on a different one. I'll email the log file now. 

Link to comment
Share on other sites

  • 0

Hi Catherine,

The log file you sent is empty, it does not even have a single camera connect command. You basically started the app at 11:18 and left it running for about 2 hours without ever connecting the camera. There is nothing in there to troubleshoot.

 

2022-01-22 11:18:43,453 [Main] INFO  - BackyardNIKON 2.1.2.41690 started!

----

2022-01-22 13:04:14,566 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.

Link to comment
Share on other sites

  • 0
3 hours ago, admin said:

Hi Catherine,

The log file you sent is empty, it does not even have a single camera connect command. You basically started the app at 11:18 and left it running for about 2 hours without ever connecting the camera. There is nothing in there to troubleshoot.

 

2022-01-22 11:18:43,453 [Main] INFO  - BackyardNIKON 2.1.2.41690 started!

----

2022-01-22 13:04:14,566 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.

Okay, I must have sent you the wrong file. I'll try again tomorrow. Sorry.

Link to comment
Share on other sites

  • 0
18 hours ago, admin said:

Hi Catherine,

The log file you sent is empty, it does not even have a single camera connect command. You basically started the app at 11:18 and left it running for about 2 hours without ever connecting the camera. There is nothing in there to troubleshoot.

 

2022-01-22 11:18:43,453 [Main] INFO  - BackyardNIKON 2.1.2.41690 started!

----

2022-01-22 13:04:14,566 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.

Okay, my apologies for sending the wrong log. I just emailed you the log from last night, with a little additional information. It contains the word ERROR a lot.

Link to comment
Share on other sites

  • 0

Although not related, you should upgrade to BYN 2.1.3.RC2 in the download pre-release section, I cleaned up most of the "ERROR - Error converting False to int32" errors (which were falsely reported as errors) It will make the logfile easier to read.

From the log file the camera gets disconnected from the computer and shuts down at 22:04:25, is no longer available at 22:04:26, and when BYN sends the next command to end the BULB sequence to the now disconnected camera, BYN throws the error "Object reference not set to an instance of an object" at 22:08:56 because is can't find the camera.

The application is still running between 22:04:25 and 22:08:56 because it tries to log the ambient temperature every minute in between.  


2022-01-22 22:04:25,876 [Main] INFO  - Camera SHUTDOWN!
2022-01-22 22:04:26,267 [Main] INFO  - -----------------------------------
2022-01-22 22:04:26,267 [Main] INFO  - Application state changed: 'Disconnected'
2022-01-22 22:04:26,282 [31] INFO  - Camera  Type0022 is available
2022-01-22 22:04:26,813 [32] INFO  - Camera state changed: 'Disconnected'
2022-01-22 22:04:26,954 [Main] INFO  - -----------------------------------
2022-01-22 22:04:26,954 [Main] INFO  - Application state changed: 'Disconnected'
2022-01-22 22:04:26,954 [32] INFO  - Camera : 1 is no longer available
2022-01-22 22:04:38,423 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2022-01-22 22:05:39,047 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2022-01-22 22:06:39,766 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2022-01-22 22:07:40,469 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2022-01-22 22:08:41,156 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2022-01-22 22:08:56,609 [CameraTakePictureOnMessageRecieved] ERROR - Object reference not set to an instance of an object.

 

Then, at 22:10:06 you clicked "Connect" to reconnect the camera, and it connected. 

2022-01-22 22:10:06,624 [Main] DEBUG - ButtonPlus_MouseClick(btnConnect = 'Connect')
2022-01-22 22:10:06,859 [Main] INFO  - -----------------------------------
2022-01-22 22:10:06,859 [Main] INFO  - Application state changed: 'Connecting'
2022-01-22 22:10:09,359 [Main] DEBUG - ButtonPlus_MouseClick(btnCam1 = 'For most models generaly manufactured after 2016, or older models with recent 2016 firmware update (DEFAULT)')
2022-01-22 22:10:11,984 [Main] DEBUG - ButtonPlus_MouseClick(buttonD850 = 'D850')
2022-01-22 22:10:12,015 [Main] INFO  - Attempting to connect camera...
2022-01-22 22:10:12,015 [Main] INFO  - Camera action fired: 'MaestroChoose'
2022-01-22 22:10:12,031 [Main] DEBUG - Nikon drivers 'Type0022_D850/C:\Program Files (x86)\BackyardNIKONv2.1\Nikon\Type0022_D850\Type0022.md3' is loading...
2022-01-22 22:10:12,046 [Main] INFO  - Nikon drivers 'Type0022_D850/C:\Program Files (x86)\BackyardNIKONv2.1\Nikon\Type0022_D850\Type0022.md3' initialized.
2022-01-22 22:10:12,390 [Main] INFO  - Nikon/D850 drivers initialized.
2022-01-22 22:10:12,968 [23] INFO  - Camera state changed: 1 = 'CameraAdded'
2022-01-22 22:10:13,499 [Main] INFO  - Loaded devices...
2022-01-22 22:10:13,499 [Main] INFO  - +-- device(D850) Module(Type0022) loaded.
2022-01-22 22:10:13,499 [Main] INFO  - Device(D850) Module(Type0022) found!

 

This is a physical issue/connection issue.  Your camera got disconnected from the computer and from BYN as a result.  You need to figure out why it physically disconnected from the computer.  This could be because of an aging USB cable, a loose connection, a USB port going to sleep, and USB2 cable longer than 15 feet (of 9 feet for USB3), a poor/overloaded USB HUB, etc...

 

Link to comment
Share on other sites

  • 0
31 minutes ago, admin said:

Although not related, you should upgrade to BYN 2.1.3.RC2 in the download pre-release section, I cleaned up most of the "ERROR - Error converting False to int32" errors (which were falsely reported as errors) It will make the logfile easier to read.

From the log file the camera gets disconnected from the computer and shuts down at 22:04:25, is no longer available at 22:04:26, and when BYN sends the next command to end the BULB sequence to the now disconnected camera, BYN throws the error "Object reference not set to an instance of an object" at 22:08:56 because is can't find the camera.

The application is still running between 22:04:25 and 22:08:56 because it tries to log the ambient temperature every minute in between.  


2022-01-22 22:04:25,876 [Main] INFO  - Camera SHUTDOWN!
2022-01-22 22:04:26,267 [Main] INFO  - -----------------------------------
2022-01-22 22:04:26,267 [Main] INFO  - Application state changed: 'Disconnected'
2022-01-22 22:04:26,282 [31] INFO  - Camera  Type0022 is available
2022-01-22 22:04:26,813 [32] INFO  - Camera state changed: 'Disconnected'
2022-01-22 22:04:26,954 [Main] INFO  - -----------------------------------
2022-01-22 22:04:26,954 [Main] INFO  - Application state changed: 'Disconnected'
2022-01-22 22:04:26,954 [32] INFO  - Camera : 1 is no longer available
2022-01-22 22:04:38,423 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2022-01-22 22:05:39,047 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2022-01-22 22:06:39,766 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2022-01-22 22:07:40,469 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2022-01-22 22:08:41,156 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2022-01-22 22:08:56,609 [CameraTakePictureOnMessageRecieved] ERROR - Object reference not set to an instance of an object.

 

Then, at 22:10:06 you clicked "Connect" to reconnect the camera, and it connected. 

2022-01-22 22:10:06,624 [Main] DEBUG - ButtonPlus_MouseClick(btnConnect = 'Connect')
2022-01-22 22:10:06,859 [Main] INFO  - -----------------------------------
2022-01-22 22:10:06,859 [Main] INFO  - Application state changed: 'Connecting'
2022-01-22 22:10:09,359 [Main] DEBUG - ButtonPlus_MouseClick(btnCam1 = 'For most models generaly manufactured after 2016, or older models with recent 2016 firmware update (DEFAULT)')
2022-01-22 22:10:11,984 [Main] DEBUG - ButtonPlus_MouseClick(buttonD850 = 'D850')
2022-01-22 22:10:12,015 [Main] INFO  - Attempting to connect camera...
2022-01-22 22:10:12,015 [Main] INFO  - Camera action fired: 'MaestroChoose'
2022-01-22 22:10:12,031 [Main] DEBUG - Nikon drivers 'Type0022_D850/C:\Program Files (x86)\BackyardNIKONv2.1\Nikon\Type0022_D850\Type0022.md3' is loading...
2022-01-22 22:10:12,046 [Main] INFO  - Nikon drivers 'Type0022_D850/C:\Program Files (x86)\BackyardNIKONv2.1\Nikon\Type0022_D850\Type0022.md3' initialized.
2022-01-22 22:10:12,390 [Main] INFO  - Nikon/D850 drivers initialized.
2022-01-22 22:10:12,968 [23] INFO  - Camera state changed: 1 = 'CameraAdded'
2022-01-22 22:10:13,499 [Main] INFO  - Loaded devices...
2022-01-22 22:10:13,499 [Main] INFO  - +-- device(D850) Module(Type0022) loaded.
2022-01-22 22:10:13,499 [Main] INFO  - Device(D850) Module(Type0022) found!

 

This is a physical issue/connection issue.  Your camera got disconnected from the computer and from BYN as a result.  You need to figure out why it physically disconnected from the computer.  This could be because of an aging USB cable, a loose connection, a USB port going to sleep, and USB2 cable longer than 15 feet (of 9 feet for USB3), a poor/overloaded USB HUB, etc...

 

Brand new camera, brand new cable, not longer than 15 feet. No USB hub. It is connected directly to the computer. The only one of these I can't rule out is USB port going to sleep. I can try to research that, but is there any way you can help me know how one could prevent it?

Link to comment
Share on other sites

  • 0

Remember:

"New Cable" doesn't necessarily mean "Good Cable".  As it is the cheapest thing to try, start there.

Also:

Since Laptops are notorious for underpowering of USB Ports, try adding a Powered USB3 Hub (even though neither D810A nor D850 should be drawing much USB Power because of their Onboard Battery design).

Laptops may also have all USB Ports internally wired as Single Hub Device - are there any other USB Devices attached to Laptop at same time??  Another good reason for a Powered Hub.

Link to comment
Share on other sites

  • 0
2 hours ago, s3igell said:

Remember:

"New Cable" doesn't necessarily mean "Good Cable".  As it is the cheapest thing to try, start there.

Also:

Since Laptops are notorious for underpowering of USB Ports, try adding a Powered USB3 Hub (even though neither D810A nor D850 should be drawing much USB Power because of their Onboard Battery design).

Laptops may also have all USB Ports internally wired as Single Hub Device - are there any other USB Devices attached to Laptop at same time??  Another good reason for a Powered Hub.

I'm not using a laptop. I'm using a Kingdel mini computer. I've tried several new cables, just because that seemed like the most likely weak link. 

Link to comment
Share on other sites

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
Answer this question...

×   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.

 Share


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use