Go Back   IceInSpace > Equipment > Equipment Discussions
Register FAQ Calendar Today's Posts Search

Reply
 
Thread Tools Rate Thread
  #1  
Old 26-07-2013, 07:45 PM
Paul Haese's Avatar
Paul Haese
Registered User

Paul Haese is offline
 
Join Date: Jan 2009
Location: Adelaide
Posts: 9,991
USB dropping out when roll off roof opens and closes

I have discovered a unique problem that I cannot seem to nut out myself. I have sought help from a couple of guys I know that a handy with electronics and electrics and it has stumped them too. I did get plenty of good suggestions from them but I thought I would put this out for people who might know how to sort this.

The problem:

When I connect up CCDautopilot which connects my mount (the sky6), maxim (controls the camera and guiding), Focusmax (focusing), pinpoint (plate solving), AAG cloud sensor (weather), rotator (Pyxis) and the scope dome driver (the roll off roof), everything is fine. Then when I open the roof via run imaging session; about 15 seconds into the roof opening the main camera (QSI) disconnects and makes Maxim hang, that caused all sorts of havoc. I need to reboot the entire system to get everything working again.

Now just to let you know the cameras (both guide camera and QSI), Focus (robofocus), dew heater and rotator run off the mount hub pro, which is powered by a 20amp 13.8v regulated power supply sold at Jaycar.

The roof is powered by a power cable coming out of the power point into the hardware USB card.

Scope dome do say to use heavily shielded USB cables as the system can produce some problems with cheap USB cables. I have good cables but not perhaps heavy shielded ones.

To test things out I have left the roof off the connect with CCDautopilot and opened that separately. It still did the same thing. I have even totally disconnected the USB cable that connects the roof hardware to the computer (removed the USB cable altogether) and when I open the roof or close it the camera disconnects and hangs maxim (no matter whether it is connected to CCDautopilot, or not).

I have not yet powered the Mount hub pro on a separate power system, from say the house or a battery. That would tell me whether the regulated power supply is at fault.

I have bought heavy duty double shielded cables from Lindy.com.au which should arrive next week. That may stop the problem although I doubt it.

I have opened the roof first then started the computer and all the appliances and things seemed ok, although I cannot tell about a full run yet.

The roof has an inverter than converts the 240 power to 0.9kw for a three phase motor. I have used a wiring loom that was supplied by the manufacturer of the scope dome gear and it acts exactly like the loom I had done myself before they sent me the plug and play one. So I don't think that is the problem.

To me this seems like a voltage spike or drop but I know there might be some other explanation. Feel free to ask me any questions you may have and I will answer those as best as possible. I really need to have the whole system connected.

Officially stumped????
Reply With Quote
  #2  
Old 26-07-2013, 08:16 PM
h0ughy's Avatar
h0ughy (David)
Moderator

h0ughy is offline
 
Join Date: Apr 2005
Location: NEWCASTLE NSW Australia
Posts: 33,425
well if plugged into a hub you have only a couple of amps available and everything adds up if powered by the hub? I have found that externally powered devices even though connected to the hub suffer similar Bermuda triangle effect - and things in a certain order. it only takes a few half amps inputs to add up to hub fully saturated then you just need that final push over and the serial chain is broken. in the end I had two completely different systems, dome and guide camera on one and then the imaging camera on the other. just my thoughts. you could even get a voltage drop, though how you would be able to measure that would be interesting? the longer the usb cable the tighter the power requirements as it drops down significantly
Reply With Quote
  #3  
Old 26-07-2013, 08:27 PM
mithrandir's Avatar
mithrandir (Andrew)
Registered User

mithrandir is offline
 
Join Date: Jan 2009
Location: Glenhaven
Posts: 4,161
Paul, a couple of thoughts.
Does the motor cause a brownout that would upset the power supply and the stuff hung off it? You'd need something like an oscilloscope to pick up the transients.
Can you shield the motor and its cables? Why blame the USB if it's the motor's fault.

Your load on the power supply should be OK.

Running the motor from another power point might work, but off a different circuit would be better. If you have more than one phase, putting them on different ones would be even better.
Reply With Quote
  #4  
Old 26-07-2013, 09:35 PM
jase (Jason)
Registered User

jase is offline
 
Join Date: Sep 2006
Location: Melbourne, Victoria
Posts: 3,916
What happens when you change the main imaging camera (QSI) to the ASCOM camera simulator. Do you still get Maxim hanging when you try reproduce the problem?
Reply With Quote
  #5  
Old 26-07-2013, 10:51 PM
Paul Haese's Avatar
Paul Haese
Registered User

Paul Haese is offline
 
Join Date: Jan 2009
Location: Adelaide
Posts: 9,991
Quote:
Originally Posted by h0ughy View Post
well if plugged into a hub you have only a couple of amps available and everything adds up if powered by the hub? I have found that externally powered devices even though connected to the hub suffer similar Bermuda triangle effect - and things in a certain order. it only takes a few half amps inputs to add up to hub fully saturated then you just need that final push over and the serial chain is broken. in the end I had two completely different systems, dome and guide camera on one and then the imaging camera on the other. just my thoughts. you could even get a voltage drop, though how you would be able to measure that would be interesting? the longer the usb cable the tighter the power requirements as it drops down significantly
I also forgot to mention I powered the camera with its native power supply too and got the same results. So it is unlikely to be the hub, those hubs are made for this sort of work.


Quote:
Originally Posted by mithrandir View Post
Paul, a couple of thoughts.
Does the motor cause a brownout that would upset the power supply and the stuff hung off it? You'd need something like an oscilloscope to pick up the transients.
Can you shield the motor and its cables? Why blame the USB if it's the motor's fault.

Your load on the power supply should be OK.

Running the motor from another power point might work, but off a different circuit would be better. If you have more than one phase, putting them on different ones would be even better.
Yes this is my main leaning at this stage. I will test the system by powering from another circuit and then if that prevents the problem, then I will be digging another trench and that was hard the first time.

I had thought that getting heavier USB would do the shielding I need. Perhaps I am wrong here.


Quote:
Originally Posted by jase View Post
What happens when you change the main imaging camera (QSI) to the ASCOM camera simulator. Do you still get Maxim hanging when you try reproduce the problem?

Not tried this but I suspect it is not going to help. I have noted that if I pull the USB cable I can disconnect the camera in Maxim and then reconnect. If I try to disconnect the camera without physically pulling the USB then it just hangs further. Worth a try though.
Reply With Quote
  #6  
Old 27-07-2013, 12:20 AM
Joshua Bunn's Avatar
Joshua Bunn (Joshua)
Registered User

Joshua Bunn is offline
 
Join Date: Oct 2011
Location: Albany, Western Australia
Posts: 1,486
Paul,
I connect all my gear to a powered usb hub and i found that when my SBIG camera was powered up (which i purposely restricted the power to), it initiated my mirror heaters to stop writing to my usb port. I then supplied the correct power to the camera and then connecting the camera had no effect on the mirror heaters.

my point... maybe its a power issue, but your gear sounds pretty good.

Also make sure you don't exceed the usb cable length or if so, use active repeaters, but im sure you know this.

Try going back to real basics and getting one thing to work at a time to issolate components, then adding one thing after another to try and find the issue.

Josh
Reply With Quote
  #7  
Old 27-07-2013, 12:51 AM
DannyV (Danny)
Registered User

DannyV is offline
 
Join Date: Oct 2012
Location: Adelaide
Posts: 43
I powered my hubs via 12v to 5v converters powered from my 12v battery supply, rather than the 240v supply. This stopped a lot of hangups.
Reply With Quote
  #8  
Old 27-07-2013, 12:57 AM
DannyV (Danny)
Registered User

DannyV is offline
 
Join Date: Oct 2012
Location: Adelaide
Posts: 43
Paul,
Have you seen these:
http://www.keterex.com/kxusb150.php
http://electronics-shop.dk/galvanica...m?currency=EUR

They might help
Reply With Quote
  #9  
Old 27-07-2013, 03:21 AM
Tandum's Avatar
Tandum (Robin)
Registered User

Tandum is offline
 
Join Date: Apr 2008
Location: Wynnum West, Brisbane.
Posts: 4,166
Quote:
Originally Posted by Paul Haese View Post
To me this seems like a voltage spike or drop
I agree. Something is getting back into the usb and hanging the camera which freezes maxim and screws the goose. It's a pig of a thing to find. If usb devices disconnect they will not automagically reconnect when they reappear, you have to physically unplug and replug it so it cames back to the fold. Bring back serial I recon.

I had sort of similar issues which ended up being the qhy5L2 camera didn't like my usb card in the PC. Works fine when plugged into a usb port on the PC motherboard but would randomly disconnect from the usb card? The SX wheel will not work unless cabled directly to a PC. It just will not work through any hub.

You need to find these idiosyncrasies in your setup.

Good Luck.
Reply With Quote
  #10  
Old 27-07-2013, 09:56 AM
Bassnut's Avatar
Bassnut (Fred)
Narrowfield rules!

Bassnut is offline
 
Join Date: Nov 2006
Location: Torquay
Posts: 5,065
Get a USB to USB opto isolator. You should do this anyway, asking for trouble if you dont.

Last edited by Bassnut; 27-07-2013 at 10:12 AM.
Reply With Quote
  #11  
Old 27-07-2013, 11:52 AM
gary
Registered User

gary is offline
 
Join Date: Apr 2005
Location: Mt. Kuring-Gai
Posts: 5,999
Paul, is the frame of the motor happened to be attached to the steel frame of the observatory?

Best Regards

Gary

Last edited by gary; 27-07-2013 at 12:03 PM.
Reply With Quote
  #12  
Old 27-07-2013, 12:00 PM
rally
Registered User

rally is offline
 
Join Date: Sep 2007
Location: Australia
Posts: 896
I fear the title of this thread might be confusing the diagnosis issue.

It may or may not have anything to do with USB - that hasnt been established yet.

It may well be software Driver problems, ASCOM problems, OS systems, Hardware problems

There are a lot of issues at hand here - its a complex system - hardware, firmware, many different circuits, many different devices all talking with one another, power supplies, motors, inverters, wireless systems, communications systems and protocols etc etc

This problem is occurring when the ScopeDome USB cable is not plugged in at all and there i sno connection to it and the PC or the rest of the system !
Therefore it has nothing to do with a direct USB problem - at least on the part of the ScopeDome controller, but may have something to do with an indirect consequence on the QSI USB side or elsewhere in the USB hubs and or their power supplies.

The wireless Scopedome controller is communicating to itself
(two halves - one on the controller side and one on the motor side) wirelessly when the Shutter is opening or closing and also when the limit switches open and close. The motor is a 3 phase inverter frequency controlled motor so we can't discount RF or electrical interference - although I would think this to be unlikely - something is causing the problem !

He has blown up one single phase to 3 phase inverter on the low voltage control side, so an electrical problem that is on the controller side cannot be eliminated.
And its unknown if there was any further damage when this occurred or from my perspective how and why it occurred, given it was tested beforehand.

So that leaves the possibility of a power supply or supply interference problem as well as a potential electronics circuit problem.

Paul says the error occurs when he uses the controller manually - 100% of the time, so its a very reproducible problem.
So the manually operated hand controller for motor control (without any connection of the ScopeDome controller via USB to the system) causes this problem in another electronic system entirely that is not connected except via the mains power. Note - this is still making use of the wireless comms link.

Paul is using CCDAutopilot, TheSky, MaxIm, QSI, FocusMax, etc etc and these are all talking via ASCOM and their various drivers.
So its also possible that there is an ASCOM Hub or driver related problem (that may or may not have its cause rooted in the USB system), but that would still need to be triggered off by the roof opening or closing activation - either motors or sensors or control circuit or frequency 1~ to 3~inverter.

I have suggested a few things for him to try to see if he can get a change :
Swap his imaging/camera system over to a 12v battery to eliminate the possibility of a main power or mains cabling interference between the roof automation system and his normal imaging system
To manually hold the limit switches in their same position initially so as not to trigger any further sensor activity and see if it still occurs - to isolate if its a wireless (or electrical) control problem related to the position sensors.
To shield the inverter output cables with some foil to see if that makes any difference
To avoid any looped cables - eg USB cables bundled up
To remove the USB hub (MountHubPro) out of the equation to see if that makes any difference - eg it could be resetting itself or doping something unusual when the motors are activated
Disable any other WiFi devices he may be using - that would include Bluetooth devices, USB wifi dongles etc - who knows a Blutooth Keyboard or mouse might be misbehaving !


I would add to those now -
Manually trigger the Inverter input for Forward and Reverse operation by manually Jumpering P1 and then separately P2 to Common (while holding the sensor limit switch in its same position as the roof moves)
To see if that triggers the errors - this eliminates the wireless communications system from the system and would imply an inverter/motor problem if it still remained - that ought to be overcome by most modern power supplies in the rest of his system.

If this didn't resolve things then as suggested I would be putting an Oscilloscope with event triggering - on the mains, the control circuit wiring, all USB wiring and all the power supply outputs of all devices to see if there are an obvious problems.

The fact that the problem is so absolute and repeatable and is not intermittent should make it a relatively easy problem to resolve or at least isolate further.

Hope that helps

Cheers

Rally
Reply With Quote
  #13  
Old 27-07-2013, 12:10 PM
gary
Registered User

gary is offline
 
Join Date: Apr 2005
Location: Mt. Kuring-Gai
Posts: 5,999
Quote:
Originally Posted by rally View Post
Paul says the error occurs when he uses the controller manually - 100% of the time, so its a very reproducible problem.
So the manually operated hand controller for motor control (without any connection of the ScopeDome controller via USB to the system) causes this problem in another electronic system entirely that is not connected except via the mains power. Note - this is still making use of the wireless comms link.
Hi Rally,

These particular sentences are an important clue. Do you happen to know if the
frame of the motor is attached to the metal frame of the observatory?

Best regards

Gary
Reply With Quote
  #14  
Old 27-07-2013, 03:38 PM
rally
Registered User

rally is offline
 
Join Date: Sep 2007
Location: Australia
Posts: 896
Gary,

I dont know the answer to that question.

Whilst I have seen it superficially, I haven't inspected it as I wasn't aware of these problems then.
The motor is 3 phase, so none of the phases should be connected to earth and Neutral isn't required.
All of the three phases ought to be fully isolated from everything else electrically too via the single phase to 3 phase inverter.

But checking for stray leakage/loops is definitely warranted given the problem.

Cheers

Rally
Reply With Quote
  #15  
Old 27-07-2013, 04:07 PM
coldlegs's Avatar
coldlegs (Stephen)
Chopped its rear end off!

coldlegs is offline
 
Join Date: Jul 2009
Location: adelaide, sth aust
Posts: 331
Paul
My money is on earth loops between your PC and everything else. Have similar usb dropouts myself depending on the wiring configuration. Wire a few earths together and see what happens.
Cheers
Stephen
Reply With Quote
  #16  
Old 27-07-2013, 04:23 PM
gary
Registered User

gary is offline
 
Join Date: Apr 2005
Location: Mt. Kuring-Gai
Posts: 5,999
Quote:
Originally Posted by rally View Post
Gary,

I dont know the answer to that question.

Whilst I have seen it superficially, I haven't inspected it as I wasn't aware of these problems then.
The motor is 3 phase, so none of the phases should be connected to earth and Neutral isn't required.
All of the three phases ought to be fully isolated from everything else electrically too via the single phase to 3 phase inverter.

But checking for stray leakage/loops is definitely warranted given the problem.

Cheers

Rally
Hi Rally,

Parasitic capacitance between the rotor and stator will allow for common-mode
currents to pass into the motor frame and if that is mounted on some other
metal structure into that too.

As the inverter will have high frequency spectral components, they will
be transferred via common-mode too.

Those noise currents will certainly play havoc with other electronic equipment within
the observatory and it is not surprising that something like a USB connection
would drop out.

So based on the description, none of this surprises or puzzles me.

Though one might potentially solve the particular problem at hand by opto-isolation
on all the other victim USB links, that tends to be the "Little Dutch Boy" approach
to the problem. The best prescription would be to solve it at the source by
installing common-mode chokes on the motor drive cables.

As few of these problems tend to fit into the realm of lumped circuit theory,
multimeters and oscilloscopes tend to be of little help. Instead, they are often
best diagnosed in the frequency domain and a spectrum analyzer and current
probe would be the first tools to reach for. However, hopefully none of that
heavy artillery will be called for and simply instaling the common-mode chokes will
solve the problem.

Best regards

Gary Kopff
Mount Kuring-Gai
02 9457-9049
Reply With Quote
  #17  
Old 27-07-2013, 04:24 PM
gary
Registered User

gary is offline
 
Join Date: Apr 2005
Location: Mt. Kuring-Gai
Posts: 5,999
Quote:
Originally Posted by coldlegs View Post
Paul
My money is on earth loops between your PC and everything else. Have similar usb dropouts myself depending on the wiring configuration. Wire a few earths together and see what happens.
Cheers
Stephen
Hi Stephen,

That is the last thing you want to do!

All the best

Gary
Reply With Quote
  #18  
Old 27-07-2013, 06:43 PM
Paul Haese's Avatar
Paul Haese
Registered User

Paul Haese is offline
 
Join Date: Jan 2009
Location: Adelaide
Posts: 9,991
Hey thanks guys for the questions and detailed responses.

Good thinking Rally, I will see if that makes any difference although if I hard wire to the wireless unit this should sort the problem out. The previous inverter might have been checked but I doubt having an earth leakage problem would cause the inverter to be blown by me. To that end though I know have the scope dome plug and play kit installed and all seems to work until we go with full automation. Anyway, some more things to sort. Appreciate the advice.

Gary to answer your question re the steel frame work. Definitely not screwed to frame, but I will check just in case. I am pretty certain it is not but will do that anyway. When I screwed the motor on I took special care not to screw to the frame. That being the case though each wall frame is isolated by a timber post in the corners and the timber floor on which it is fixed. I wonder though could this be like a faraday cage?

The USB suppressors are a good idea anyway and I will pick some up. Is this what you mean by current choke?

I can say with absolute certainty though that I have all the earths sorted in the wiring of the observatory and all actives and neutrals are going to the correct places.

Really appreciate the advice and will do some testing with the ideas suggested so far. I will get back to you with further developments.
Reply With Quote
  #19  
Old 27-07-2013, 08:04 PM
gary
Registered User

gary is offline
 
Join Date: Apr 2005
Location: Mt. Kuring-Gai
Posts: 5,999
Quote:
Originally Posted by Paul Haese View Post

Gary to answer your question re the steel frame work. Definitely not screwed to frame, but I will check just in case. I am pretty certain it is not but will do that anyway. When I screwed the motor on I took special care not to screw to the frame. That being the case though each wall frame is isolated by a timber post in the corners and the timber floor on which it is fixed. I wonder though could this be like a faraday cage?

The USB suppressors are a good idea anyway and I will pick some up. Is this what you mean by current choke?
Hi Paul,

With regards the motor frame not being attached to the steel frame, very good.

Nevertheless, it still has a very strong possibility of being noise related and
the cables from the inverter to the motor are likely to be the major source of it.

What are termed "stray" capacitances which cause leakage currents can
come from a variety of sources, including from the cables themselves,
the inverter, the rectifier within the inverter and so on.

To make this concrete, these stray capacitances are created whenever two
conductors are at different potentials and are separated by a, typically thin,
insulator. That dielectric might be, for example, just plastic or even just air.

As the voltages in the motor drive cables change very rapidly, these capacitances
allow tiny currents to pass through them and their paths back to their
the source may take some large physical loop area. A conductor having a large
loop area with alternating currents, even small ones, will generate electromagnetic
noise.

In order to improve the quality of the current waveforms in motor drive systems,
high frequency switching tends to be used these days. It is the very short
rise time of the pulses of this fast switching that is one major noise culprit and
not just the pulse frequency itself. These fast rise times are harmonically rich
which means lots of noise over a wide spectrum. This multiplies the probability that
some other circuit will be susceptible to noise at one of those frequencies.

There are sources of noise and then there are victim circuits. If the ends justifies
the means, one can attempt to filter the victims. The suggestion of isolators on
your USB connections is one approach to this in that if there are common-mode
currents passing back through these cables that had originated from the motor
drive system, then isolators block this return current path.

However, my suggestion is that if indeed the problem turns out to be noise
from the motor drive, then it can be wiser to cure it at the source. This then
minimizes the chance of the problem manifesting itself in some other way,
say noise artifacts on your images.

So the common mode choke, which is a form of transformer, goes on the three
cables from your inverter to the three-phase motor. Hopefully it will "choke"
one of the largest noise contributors.


Here is an example of a class of commercial three phase filters -
http://www.digikey.com/product-highl...e-filters/1955
Here is a datasheet for one -
http://www.schaffner.com/en/products...lications.html

For belts and braces, one could add current mode choke/filter to the source and
an USB isolator on the USB cable but I would start with the choke first.

As we just discussed on the telephone, also make sure any cables running
large switching currents are not in close physical proximity to, for example, the
USB cables. Even when run at right angles to each other, there may be sufficient
coupling between them to induce noise. The USB cables should be shielded
and the design of the shield and the equipment should be such that the shields
are fully connected to the chassis at both ends, 360 degrees around.

It seems telling that when you manually switch on the motor that the problem
manifests itself. Electromagnetic interference (EMI) problems
related to inverters controlling three phase motors are common
enough that they appear in the standard texts and in the literature.

It is important to appreciate that the path of interference can be both through
conducted noise and through antenna mode radiation. In both cases, the
choke/filter can assist.

Having said all of the above, it might be a power integrity issue with the
motor/inverter drawing large currents particularly when they first switch, but
I'd still try the common mode choke/filter first.

Best Regards

Gary Kopff
02 9457 9049

Last edited by gary; 27-07-2013 at 08:42 PM.
Reply With Quote
  #20  
Old 28-07-2013, 02:57 PM
gary
Registered User

gary is offline
 
Join Date: Apr 2005
Location: Mt. Kuring-Gai
Posts: 5,999
Hi Paul,

With regards the inverter used to control the motor on the shutter, does it happen to be
SV008iC5-1F manufactured by LS or is it a SV iE5 or some other make/model number?

Best Regards

Gary
Reply With Quote
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +10. The time is now 05:01 PM.

Powered by vBulletin Version 3.8.7 | Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Advertisement
Bintel
Advertisement