@pipplo wrote:

I just got my new camera and since it's raining lately I decided to try out capturing some bias/dark frames for practice, but I'm running into 2 problems

System Config:
SGP version: v2.5.1.17
ASI Ascom Version 1.0.2.23
ASI camera drivers 1.3.12.28
USB Setting: 40
USB 3
Intel Compute Stick
I did not power or run the cooler for these experiments

First Problem: I set the sequence to take 10 bias frames at 0 second exposures, and I got some errors 'Error downloading file'. I was able to resolve this by injecting a delay of 4 seconds between each frame.

[1/4/2017 8:13:03 PM] [DEBUG] [Camera Thread] ASCOM Camera Error : CheckDotNetExceptions ASCOM.ASICamera2.Camera ImageArray Get System.OutOfMemoryException: Insufficient memory to continue the execution of the program. (See Inner Exception for details) (System.OutOfMemoryException: Insufficient memory to continue the execution of the program.)
at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in c:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
at ASCOM.DriverAccess.MemberFactory.GetTargetInvocationExceptionHandler(String memberName, Exception e) in c:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 664
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in c:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 288
at ASCOM.DriverAccess.Camera.get_ImageArray() in c:\ASCOM Build\Export\ASCOM.DriverAccess\Camera.cs:line 361
at fa.j(c8 A_0, hu& A_1)
[1/4/2017 8:13:03 PM] [DEBUG] [Camera Thread] Error while attempting to capture frame...
[1/4/2017 8:13:03 PM] [DEBUG] [Camera Thread] Adding sequence level notification: Error attempting to capture image (see logs for more information).

2nd Problem: After fixing #1 I set the sequence to take 100 frames and I got to about frame 62 before things appeared to be stuck on 'Downloading'. However when I looked at the file system I could see the file size growing for the current frame, but very very slowly. It took about 20 minutes for one frame to finish.

I rebooted and the speed looked fine so I started the 100 frames again. Again the same problem occured with very slow download speeds for later images. The first 10-20 which I watched manually worked fine.

Posts: 1

Participants: 1

Read full topic

@Marco_STRA wrote:

Hello everyone, I am a new user of SGP I can not figure out if there is a function to check the focus (manual operation) to make me see real-time dynamically HFR (number of graphics) of the stars, as present in all of the CCD software.

Posts: 5

Participants: 5

Read full topic

@Gunny01 wrote:

I was reading up on temperature compensation in SGP and hope I have this correct. Based on what I read my understanding of temperature compensation is that a refocus will only be initiated based on the compensation curve and at the END of the image currently being taken. If I am wrong on this feel free to correct me.

Since SGP can generate a log with curve as a session is progressing, is it possible to have SGP dynamically focus while an image is being taken? I Imagine this would be similar to IF ONAG' s Focus Sharp software. Unfortunately, that $100 software package requires the IF ONAG and in some cases you are limited by your available back focus. I have the IF ONAG on my AGO scope and it is a fantastic piece of equipment. Problem of it is the price: about $1300 plus adapters. I do not use the focusing software, as the AGO has a pretty stable focus throughout the evening. My Tak FSQ is another story. It frequently requires refocus and dynamic focus (DynaFocus) would be a nice feature for this and other refractors.

I'm not a script writer nor someone familiar with focus theory, so this may be pie in the sky thinking. Would it be possible to accomplish dynamic focus using something like a change in HFR (delta HFR) and delta time? There is a graph with the temperature compensation in SGP that I have seen.

I just starting looking into the Arduino boards and scripting using the Arduino IDE. I plan on building my own weather station for the wife's birthday and that is what turned on the light bulb in my brain for DynaFocus. Don't know if this would be a project that is both feasible and at the same time, something the developers would find interesting to pursue. Of course it would be an add on ($$)..........................Gunny

Posts: 2

Participants: 2

Read full topic

@hfjacinto wrote:

Hi all

I recently got a new mono camera the QHY 163 mono. Yesterday I tried to download images while using my old Windows XP acquisition laptop. Thedownload file hanged every time. Reached out to Qiu and they released a new ASCOM driver. I was able to test it on Frame and Focus and was able to download a lot of images. When I went to acquisition the download failed on the 2nd image. I also tried it on Maxim with the same ASCOM drivers and the download works fine. I have a newer laptop that has USB3 which works fine, but before I risk a new laptop to dew and frost I was hoping to see if you guys have any ideas?
The log files are here:

https://www.dropbox.com/sh/it58yj2qli8klp0/AABWGNsNEcG0dgvVikPuyUfxa?dl=0

I tried several things including various ports, and even uploaded the new QHY drivers and it still fails on image acquisition.

Thanks

Posts: 3

Participants: 1

Read full topic

@joelshort wrote:

Because I have different brands of filters (Optolong LRGB and Astrodon narrowband) there is quite a bit of difference in the focuser position for "in focus" bewteen the LRGB and narrowband filters, about 500 steps in my focuser. Although focus isn't critical for flats, I do feel that the discrepancy in my case is adversely affecting the flats and image calibration.

I can of course manually adjust the focuser to move the 500 steps, but it seems to me like if I have auto adjust focus per filter enabled that any time the filter changes the focuser should adjust, but this is not the case when taking flats.

Is there a way to enable auto adjust focus per filter for flats, is this a bug, or should this be a feature request?

Posts: 1

Participants: 1

Read full topic

@rodmichael wrote:

I couldn't find any other way to contact, so I'm using the Forum. I think I erred and got 3 licenses for "Mosaic and Framing Wizard." That would add up to $216. Can I get a refund of $78.

Posts: 2

Participants: 2

Read full topic

@Shawn wrote:

Using the previous version I was able to paste a solved link from astrobin into SGP and click check and it worked, setting the coords for the target. I have 2.5.2.8 installed and it is not accepting any astrobin links or DSO browser links. Yet they are solved links.

?

Thank you.

Posts: 2

Participants: 1

Read full topic

@toml wrote:

I there any way to save the camera temperature (%ct ##.#) to whole numbers with no decimal place, ie: %ct ## ?

Posts: 7

Participants: 2

Read full topic

@MarkW wrote:

HI Folks first of all I'm new to SGPro and I'm wanting to purchase this software but I've been trying to sort out a few problems first. I was having trouble plate solving but I think that's sorted but now I'm having problems with the images taken using SGpro.
I'm using a OSC QHY 10 and Astroart 6 to process them. However I've found for some strange reason I can't 'flat correct the images, I'm not sure if they are Bias and dark corrected either. I've gone through help on astroart forum but with no luck. Also I have been using Atroart for some years with no problem until now.
Anyway, I've looked at the Fits Header information on the images and the all say at the very top line "File does not conform to fits standard".......So I'm wondering if this is the cause of the problem and if so How do I correct it
Below are images of the fits header and I've highlighted in blue also the is an image that is supposed to be aligned stacked, bias, flat and dark corrected. Which you can plainly see has not been
Thanks for your help

2017-01-07 (1).png1440x900 107 KB

2017-01-07.png1440x900 690 KB

Posts: 5

Participants: 3

Read full topic

@jimsarge wrote:

There is more than one way to "attach" an equipment profile to a sequence and then the equipment profile name is displayed nest to the sequence name just above the target list. All good.

1) Request the capability be added to SGP to select user profile along with equipment profile in "New Sequence With Profile".

2) If not/also, request the user profile name be added to the sequence title bar alongside the equipment profile name.

The first would help mobile observers keep the observing site lat and lon correct.

The second would help all users keep a more positive control over what profiles are associated with sequences.

Thanks,
Jim Seargeant

Posts: 1

Participants: 1

Read full topic

@Steve1962 wrote:

SH2-157.jpg2722x2187 912 KB

This is a total of 12.5hours of 1800s subs in 3nm Ha and Oiii blended Ha, 70%Oiii + 30%Ha, Oiii
Kit list: Takahashi FSQ106ED @ f3.6, Atik 460exm, Chroma 3nm filters, 10 Micron GM1000HPS mount.

Acquired using SGPro (naturally!) (Beta 2.6.0.5 - which worked flawlessly for both nights I imaged this target) and PHD2, and processed in Pixinsight.

Hope you like it.

Posts: 4

Participants: 2

Read full topic

@Kinch wrote:

SGP 2.6.0.5

Tonight - doing some flats after a short run. The flats were the 2nd event in the sequence and commenced running without problem. However, I noticed that nothing showed up on the flat box module. Is this module only for manual control OR should it show actual status?
See the below screen shot and note the difference re the info displayed for the Flat Box (Alnitak Flip Flat) in the control panel and in the module:

Posts: 2

Participants: 2

Read full topic

@libraryman2 wrote:

Hi I'm installing my sgpro (full licence) on a new hard drive, it's asking for Microsoft.net framework 4.....fine...sgpro wants to install it but i gave it 10 hours last and it's still installing.....

Anyone got a work around for this? Research suggests it's a bit of a pain!

Ray

Posts: 2

Participants: 1

Read full topic

@David_Williams wrote:

Hi,

Hopefully this doesn't exist already (I looked).

I have two setups using different profiles (AT65EDQ and Edge8HD).

It would be nice if I could automatically use the profile name as the first filename key, so that I could automatically save files from each profile in their own directory, instead of getting files confused.

Thanks

David

Posts: 1

Participants: 1

Read full topic

@rubecula wrote:

I downloaded SGPro at the end of November and joined the forum at the same time. I didn't get chance to use it until now and of course the trial has expired. I decided to purchase anyway. I selected "Register" and am asked for a username and password. I have no recollection of ever giving a username amd password. I did make note of my username and password for the Forum but they don't work.
There is no forgotten password option and so I can get no further.
How can I pay for the app and start using it?
Thanks
Robin

Posts: 2

Participants: 2

Read full topic

@Andre wrote:

Where do I post a found bug ?

Posts: 2

Participants: 2

Read full topic

@barx1963 wrote:

I am attempting to get plate solving running. I am able to solve plates but when I utilise it, I get an error message "Runtime Error (6) Overflow" after the scope centreing routine takes an image an attempts to solve it.
I have saved the log file if that will help.
Any thoughts anyone one?

Malcolm

Posts: 2

Participants: 2

Read full topic

@UlteriorModem wrote:

This is really not SGP's fault but I though there might be a 'work around' available.

Last night while 'practicing' on M45 at some point a merdian flip was called for. Since the next frame was longer than the time to a flip the timer popped up.

I went ahead and clicked the 'flip now' button and the scope slewed over, that's when everything went bad.

Evidently I have like a mile and a half of backlash and the plate solve was failing. After glancing at the plate solve image it was obvious why. Star trails in the order of 6 or so arc minutes. Not only that I could see the stars moving in the PHD screen while looping. Almost as if sidereal tracking had been turned off.

I could see PHD sending pulse after pulse but the dec axis was way out like 7" or so and it wasent coming back. This required manual intervention to get back on track.

The only thing I can think of is since before the flip the weights were on the east side of the pier and balanced slightly east heavy. When it flipped it was taking a long time for the gears to mesh and work out that backlash.

What I was wondering is there any way to set a delay of a few minutes after a flip is done to let the backlash work out before attempting to solve and center?

Posts: 2

Participants: 2

Read full topic

@Ken wrote:

---

U P D A T E D   O N   J A N U A R Y   9 th,  2 0 1 7

---

Hi folks,

SGPro 2.6.0.6 is a beta release. While we love that many of our users are eager to help us test, make sure you are a fairly knowledgeable SGPro user before hopping onto the beta track.

If you would like to comment on colors or themes used in SGPro, please read and comment here:

http://www.mainsequencesoftware.com/Releases

2.6.0.6 Changes:

• Added target import functionality for DSO-Browser (including an early version of suggested target start and end times based on visibility information provided by DSO-Browser).
• The MFW is now more tolerant of corrupt cache files.
• Independent movement of the observatory shutter / roof or rotation now provides a warning if it is slaved to the telescope.
• Connecting to the camera no longer flags the sequence as needing to be saved.
• The plate solve API now honors the plate solver's chosen search method (in the control panel).
• Added PlateSolve2 search region increments 1000 through 3000 (was previously capped at 999).
• Added the user profile name to the sequencer title bar (after the equipment profile).
• Rounded camera temperature to a whole number for insertion into file names.
• Fixed a bug where the flat box module was not in sync with the control panel.
• Fixed a bug where a sequence failure due to lost guide star would not allow for end-sequence capture of calibration frames.
• Fixed a bug where several popup windows attached to the sequencing window would not close properly when the sequencer closed.
• Better Nikon logging.

2.6.0.5 Changes:

• The Mosaic and Framing Wizard now allows users to cancel fetch requests for the working canvas (a bunch of code was refactored in order to do this properly... may need some more testing, but it's certainly functional).
• Fixed a bug that would clear progress (visually only) when a profile was applied to an existing sequence.
• Fixed a bug that did not properly flag a sequence as needing to be saved when some properties were changed.
• Fixed a bug that did not properly flag a profile as needing to be saved when some properties were changed.
• Fixed a bug that prevented the Profile Manager's status text from displaying properly.
• Fixed a bug that would cause the Profile Manager to assume that the initial profile (on load) was in need of save and prompt the user when switching profiles.

2.6.0.4 Changes:

• SGPro will now show an error if the user attempts to rotate to a target position and the rotator does not have a sync.
• SGPro will now detect if a sync is required and automatically perform a solve and sync at the beginning of a sequence (one time).
• Added "slaved to telescope" indicator to the dome module.
• Added a warning dialog if the user attempts to open a new sequence while the camera is cooling or warming.
• Added a warning notification to let the user know if the camera was unable to attain the target temperature prior to starting the sequence.
• The delay sequence on camera temperature dialog now contains a better description of what the "Delay Start" option actually does.
• When attempting to start a sequence with the TEC temperature out of band, the warning dialog will now display the TEC's current temperature and state (Idle, cooling, warming).
• Fixed a bug where 2.6.0.3 could no longer open sequences.
• Fixed a bug where navigating image history would fail to update the HFR and star count metrics in the image stats module.

2.6.0.3 Changes:

• Fixed a bug that could affect post-meridian flip centering.

2.6.0.2 Changes:

• Added vertical sizing to the sequencing window. It's not smart... it doesn't attempt to auto adjust, it does not remember how it was set, but it does allow you to resize the event table for better visibility.
• Fixed a major bug where auto centering after a meridian flip would fail.
• Fixed a bug with dealing with odd frame counting behavior.
• Fixed a bug that would cause SGPro to crash if the Image History dialog was invoked while already visible.

2.6.0.1 Changes:

• Refactoring "Reverse Focuser" logic. Everything now resides in two places: the "Move" and the "GetCurrentPosition". Focuser position should almost never be called outside of these two places. This refactor effectively masks the real focuser position when Reversed. For instance if the focuser has 10,000 steps and is currently at position 2000 then when reversed SGP will report 8000 steps. Backlash compensation is in terms of "SGP Reported" steps not the actual steps of the focuser. So "IN" will always trigger backlash when the focuser moves from Low to High in SGP Reported Steps not Focuser Reported Steps. The main benefit of this is to have Auto Focus and backlash both work transparently when reversed. More info here: http://forum.mainsequencesoftware.com/t/rigel-sys-focuser-cant-reverse-direction-to-help-sgp-autofocus/4544/10
• SGPro now remembers your event suffixes and automatically populates the suffix drop down. There is no interface to create suffixes. If the suffix list becomes too long, you can clear it by using the new "clear" functionality in the SGPro options dialog.
• Added flip delay API calls (http://forum.mainsequencesoftware.com/t/2-6-0-0-meridian-flip-problem/4651/9).
• Fixed a bug where FLI cameras would immediately disconnect after connecting.
• Fixed a bug that might not allow some focusers to accept temperature override from the environment device.

2.6.0.0 Changes:

• The target centering routine will now skip the "pre-slew" solve and sync step. While this will make centering faster and compatible with a wider range of mounts, it will also place more onus on the user to ensure that the mount is properly synced prior to starting a sequence. This will also likely fix failure of the "Offset2" mount sync method.
• The meridian flip routine will now skip the "pre-flip" solve and sync step.
• Added an Observatory floating control module
• Added a Flat Box floating control module
• SGPro targets now remember any reference URL used to populate its location parameters.
• SGPro now remembers the last MFW FoV used to fetch the working canvas.
• SGPro now properly handles the PHD2 message indicating failure to settle
• More UI changes.
• Fixed a bug, that in rare circumstances, might "roll" the number of captured events from 9 back to 1. No loss of data occurs, but event frames would be recaptured.
• Fixed a bug that would automatically turn ASCOM focuser temp compensation off when it connects.

2.5.2.8 Changes:

• Major overhaul to the SGPro theme. An actual color theme, with new professional icons and imagery! No functional changes here, but it should make for a nicer experience.
• Image history now supports a fast star finding algorithm. You don't need to worry about this setting unless you are using an older (or slower) laptop with very large frames. This method essentially uses the older, but much faster star analysis routines. It can be found in the SGPro options dialog under "Find stars method". This is a beta feature and is not yet documented. Changing it does not affect the routine for auto focus.
• Adding sync behavior (Offset2) that utilizes slew position to calculate offset with sync data. Only usable for Auto Center and Center Here. Performing a Solve and Sync with "Offset2" will do nothing.
• Fixed a bug where aborting during target wait might force end of sequence options to execute.
• Fixed a bug where syncless center (offset) would behave oddly and sometimes not work properly after a sequence was opened initially.
• Fixed a bug where DSLR ISO settings did not work properly when using the SGPro REST API.

2.5.2.7 Changes:

• German help file! Select in SGPro options. Thanks to Hans-Eberhard! (Sorry, not sure which Forum handle is yours)
• User will now be prompted to unpark or start a mount tracking if, upon sequence start, the mount is not in a good state for imaging.
• ASCOM and QSI cameras now attempt to identify when a camera is downloading an image to support pause guider during download.
• Restored original auto stretch (this will break auto stetch for a very small number of cameras with very large overscan regions... we'll work on that shortly).
• Fixed a bug that could allow an end of sequence script to run between normal sequence end and the beginning of calibration-only frame capture.

2.5.2.6 Changes:

• Major update to Nikon DSLR support (Nikon 2016 drivers)
• Added support for Nikon D5 and D500 (Untested... we do not have these cameras avaiable for testing)
• Fixed a bug where the guider could sometimes fail to settle even though the error is well below the requested value.
• Changed some aspects of automatic meridian flips to help resolve this type of issue: http://forum.mainsequencesoftware.com/t/telescope-failed-to-perform-meridian-flip/4415
• Formally added SGPro API guider setup for users that want to use the SGPro connected camera with an auto-guider (like onboard SBIG guide chips)
• Fixed a bug where the new DSO-Browser location population was broken on official releases
• Fixed an issue where some FLI filter wheels would refuse to respond to commands despite being connected

2.5.2.5 Changes:

• SGPro now attempts to detect external device disconnections (and provide a notification to fix it)
• Added support for fetching target and MFW locations from DSO-Browser
• Better naming for AFPack images (debug feature)
• Auto adjust focus position per filter behavior fro flat frames has been returned to normal (2.5.1) behavior until we have proper time to dedicate to it.
• Rounding HFR metrics prior to AF validation out of tolerance check (prevents erroneous warning about AF out of tolerance in some cases)
• AF validation frame warning will now present itself if the HFR is greater than 15% above the low HFR value in the run (up from 10%).
• Fixed a bug where end of sequence scripts would disappear from the UI after being set
• Fixed an issue where images would always be analyzed for HFR, regardless of Image History status (on or off)
• Modified auto stretch to be more tolerant of overscan regions

2.5.2.4 Changes:

• Added an option to turn API logging on or off (developer setting in the Help menu). The default is off.
• Fixed an issue where the image capture API would not allow for high speed download (on supported cameras).
• Better user facing error messaging for target centering and many slew related errors.

2.5.2.3 Changes:

• Syncless centering is now available for testing (Control Panel->Telescope tab->Sync Behavior; Set this to "Offset")
• Fixed a bug that completely broke the SBIG guider
• Fixed a bug where API camera status no longer worked properly (affected PEMPro integration)
• Added API calls to enumerate, connect and disconnect devices to the public API
• Better error logging for epoch conversion errors
• Converting X,Y pixel locations to RA,DEC no longer allows values greater than 24 hrs (to be populated in the target's location)
• Fixed a bug that would prevent end of sequence options from running when conditions are unsafe.
• The MFW can now populate the canvas location using the mount's location (new menu option at top... Other->Fetch location from mount...)
• Better user feedback for mount park failures (more specific errors logged in the sequence alerts dialog box)

2.5.2.2 Changes:

• For users that experience an issue with SGPro not starting, we are now providing a much better recovery for SGPro when its settings file becomes corrupted (cmd: "sequence generator.exe " /recover). With this method you are even far less likely to lose old settings.
• Better trace code around force cal frame capture after sequence failure (to find why it appears to not happen sometimes)
• Image history detail now places most recent images at the top of the list.
• PHD2 "stop" call is now more robust (added a retry mechanism that will probably help with weird timing issues and using onboard SBIG guide chips)
• When call to set the override filter fails, but the user has requested to use one, SGPro will automatically try and find the LUM filter in order to continue with the sequence.
• Implemented foundation for smart dither decision engine
• Added some watchdog timers for certain aspects of SBIG camera operation timeout
• Added API documentation link to the "Help" menu
• Added much better logging around API requests (probably temporary)
• Better logging for equipment disconnect (in general)
• Fixed a bug that would cause SGPro to crash when Nikon bulb exposure failed
• Fixed a bug that would cause SGPro to crash if a file in image history was renamed outside of SGPro
• Fixed a bug that could cause rotator movement to never finish if the requested angle (not PA) was 0
• Fixed a bug where end of sequence options might run twice when shutting down due to unsafe conditions.
• Fixed a bug where the second fame might not dither when it supposed to
• Fixed a bug that could cause an error in SBIG cameras when the driver was "opened" multiple times
• Fixed a bug that, for certain types of flat boxes, the flat box light would not turn off properly when the sequence was done with flat frames.

2.5.2.1 Changes:

• Fixed a bug where some (probably most) old equipment profiles would not load correctly.
• Fixed an issue where some users could see erratic behavior with frame restarts when the telescope is on the east side of the pier.

2.5.2.0 Changes:

• Experimental: New behavior for the "Auto adjust focus per filter" option. When taking "light" frames, you can expect this to work as it always has in the past... no change here. When taking "flat" frames and this option is on, SGPro will automatically attempt to set your focuser to a suitable focus position. If you just finished imaging, you are already there... if you are taking flats on a different night, SGPro will set the focuser to focus position nearest your current temperature. If it can't find one, it will use the average focus position for that filter. If it can't find that, it will do nothing. Nobody asked for this (I don't think), but I wanted something like it so I added it in...
• Sync behavior: Added functionality to the telescope tab to define "sync behavior". This also affects the process by which SGPro centers on a target. Choosing "Sync" will cause SGPro to function like it normally does. This is what you should continue to use for this beta. Choosing "Offset" will use a sort of "Syncless" centering algorithm and should be used with mounts that really don't want external applications trying to sync the mount's position. This option is complete, but has not been tested AT ALL. Use at your own risk... DO NOT USE THIS OPTION UNATTENDED!
• MFW Image Fetching: MFW now queries from the DSS2 survey first (better quality images), then if that fails will default to the original DSS survey (current survey in use by MFW).
• Dither Every N Frames: Added option to auto guider to dither every N frames.
• Settling distance: Changed this from a drop down menu to a numeric control.
• Bug fix: Fixed an issue where centering (and meridian flips) might hang SGPro and report that the camera has timed out.
• Bug fix: Fixed a bug where the auto centering validation step could fail on camera rotation if the primary solver failed.
• Bug fix: Fixed an issue where SGPro could attempt to take an image without having sufficient time to finish before meridian flip.
• Misc: SGPro no longer performs a dither on the first frame (will still settle though)
• Misc: Added account management links to the help menu and registration dialog.

http://www.mainsequencesoftware.com/Releases

Posts: 1

Participants: 1

Read full topic

@headdown wrote:

I am going to be playing with the point modelling feature of APCC with my new Mach 1 mount. I would like to do some modelling runs of a few hundred points, just to see if they are worth doing if I decide to do some comet or asteroid imaging without guiding. I don't want to put the wear and tear on the shutter of my 6D as I do the modelling runs, and would rather use my Lodestar X2. I would then do a small modelling run after the large one, with the Canon 6D back in place. I don't see Starlight Xpress as a choice for imaging cameras. Am I out of luck? Thanks!

Dean

Posts: 2

Participants: 2

Read full topic