Date   

Re: error message In motor encoder limit Actual solution- For loss of a sign the mount went haywire!

Don W
 

I am glad to hear you have it solved.  I never played with those limits, but I can see that a wrong sign would certainly cause problems.  I hope all goes well with your system, and have a Happy New Year.
Don W


Re: USB dongle

Don W
 

Hi Mike,
OK you were using a Prolific dongle, but you don't know if it was a legitimate Prolific or a pirate.  Microsoft some years ago put into windows a way to determine if the prolific chip was legitimate or not, and then Windows would refuse to operate with a bad chip.  That might be what is happening to you.  As far as I know, all the FTDI dongles are good.
Don W


Re: error message In motor encoder limit Actual solution- For loss of a sign the mount went haywire!

andoverobservatory <SJamiem16@...>
 

    Hello all. I sit here with egg on my face and would prefer to hide but I think its always best if you get the real facts. On Christmas eve I though I had found my motor direction problem as explained above. Right after sending out that message it was back. Since then I have gone through the motor waveforms to make sure there wasn't a hardware problem and tried to imagine any setting that should manifest that way.
     As is common in this type of issue, it was operator failure. When I was updating the parameters from my old telescope configuration years ago , I decided to increase the limits for the movement of RA both clockwise and counterclockwise. While editing I selected the first two digits to change to the new value but didn't realize that I also selected the negative sign. As a result both the limits were made positive and the same , 200000000 Since one was clockwise and the other was counterclockwise I guess I assumed the sign was built in when I checked the numbers. 
     This caused the limit message that I got but I didn't understand the connection well enough because I was so rapped up in the strange behavior of the RA axis.. I had no idea that they were related, but the old brain isn't as nimble at 73. I only found it because I went through every number asking if I really knew what it did and realize that it could be one counter and therefore probably had a sign.
   So finally , everything is really working so I can proceed with the rest of the project.
BTW, Dan's message went directly to those two numbers but the image was just blurry enough that I didn't notice  the negative sign!. I could have saved myself about 10 hours of headaches if I had been more careful.
Thanks for everything Don and Dan !! You guys are the best.


Re: USB dongle

Mike Colyar
 

Don,

I just ordered one with an FTDI chip just in case that solves the problem. $10. Whoop de doo! Big spender.

So I can stop pestering you for a week or so. Enjoy your new years eve in peace.

Mike


On Dec 31, 2020, at 4:13 PM, Mike Colyar <mike@...> wrote:

Windos 10.

I didn’t know that SiTech sets the communications parameters. Eases my mind (I think).

I had a friend plug one of mine into his LINUX machine and sent me what it said. Here it is:

Bus 001 Device 007: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port

[4823487.580558] usb 1-5: New USB device found, idVendor=067b, idProduct=2303
[4823487.580563] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[4823487.580567] usb 1-5: Product: USB 2.0 To COM Device
[4823487.580570] usb 1-5: Manufacturer: Prolific Technology Inc.
[4823487.664811] usbcore: registered new interface driver usbserial_generic
[4823487.664839] usbserial: USB Serial support registered for generic
[4823487.669606] usbcore: registered new interface driver pl2303
[4823487.669633] usbserial: USB Serial support registered for pl2303
[4823487.670841] usb 1-5: pl2303 converter now attached to ttyUSB0

T:  Bus=01 Lev=01 Prnt=01 Port=04 Cnt=05 Dev#=  7 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=067b ProdID=2303 Rev=03.00
S:  Manufacturer=Prolific Technology Inc.
S:  Product=USB 2.0 To COM Device
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=pl2303

Hope this is informative,

Mike


On Dec 31, 2020, at 4:01 PM, Don W <westergren@...> wrote:

Hi Mike,

OK, I need a bit of information from you.
What version of Windows?
Do you know the brand of dongle and it's age?  Dongles with FTDI chips work, dongles with pirated Prolic ships often don't work.  Older Prolific dongles made for WinXP may not work with Win10.

SiTech automatically sets the settings of the dongle bit rate if you leave the windows settings at their default settings (960 baud).

Don W



Re: USB dongle

Mike Colyar
 

Windos 10.

I didn’t know that SiTech sets the communications parameters. Eases my mind (I think).

I had a friend plug one of mine into his LINUX machine and sent me what it said. Here it is:

Bus 001 Device 007: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port

[4823487.580558] usb 1-5: New USB device found, idVendor=067b, idProduct=2303
[4823487.580563] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[4823487.580567] usb 1-5: Product: USB 2.0 To COM Device
[4823487.580570] usb 1-5: Manufacturer: Prolific Technology Inc.
[4823487.664811] usbcore: registered new interface driver usbserial_generic
[4823487.664839] usbserial: USB Serial support registered for generic
[4823487.669606] usbcore: registered new interface driver pl2303
[4823487.669633] usbserial: USB Serial support registered for pl2303
[4823487.670841] usb 1-5: pl2303 converter now attached to ttyUSB0

T:  Bus=01 Lev=01 Prnt=01 Port=04 Cnt=05 Dev#=  7 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=067b ProdID=2303 Rev=03.00
S:  Manufacturer=Prolific Technology Inc.
S:  Product=USB 2.0 To COM Device
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=pl2303

Hope this is informative,

Mike


On Dec 31, 2020, at 4:01 PM, Don W <westergren@...> wrote:

Hi Mike,

OK, I need a bit of information from you.
What version of Windows?
Do you know the brand of dongle and it's age?  Dongles with FTDI chips work, dongles with pirated Prolic ships often don't work.  Older Prolific dongles made for WinXP may not work with Win10.

SiTech automatically sets the settings of the dongle bit rate if you leave the windows settings at their default settings (960 baud).

Don W


Re: USB dongle

Don W
 

Hi Mike,

OK, I need a bit of information from you.
What version of Windows?
Do you know the brand of dongle and it's age?  Dongles with FTDI chips work, dongles with pirated Prolic ships often don't work.  Older Prolific dongles made for WinXP may not work with Win10.

SiTech automatically sets the settings of the dongle bit rate if you leave the windows settings at their default settings (960 baud).

Don W


USB dongle

Mike Colyar
 

I can't seem to get this borrowed Windows 10 laptop to talk to my Servo 1 controller. When I hook things up it continues to give me a message (in Servo Config) that it is unable to communicate on Port N. N depends on which physical port I plug my dongle in to. Com3, 4 or 5. I have tried using the communications set up button in Servo Config to make sure that the Com port numbers are the same. I have found my way into the Windows machine to look at the Com port and the members agree with those in Servo Config. What I haven't done is experiment with the baud rate beyond the 9600 that it came up with and one wild fling at 19200. 8 none 1. These setting in the computer.

And clues? I am an extreme novice at Windows so be explicit. Not about my ancestry please!

Thanks,

Mike


Re: Conversion of Orion Skyquest XX scope #poll- Motor runs no stop #poll-

Don W
 

Hi Raphael,

The encoders A and B voltages normally flip between 0 and 5 volts.  They are staggered, so they rarely both read 5 volts.  When they are moving, they should read about 2.5 volts (averaging the 0 to 5 volts).  Do these encoders still work with your old controller?  If they do work, then they are OK.  Since they all measure alike, I think the way you are measuring the voltages is the problem.  They are probably all OK.  You must verify the A and B wires, although it doesn't matter which is the A or B signal to SiTech.  The order of A and B can be easily reversed in ServoConfig.

You can not get new encoders from SiTech - the SiTech servos are made by Pittman company, and the encoders are built on to the servo motors.  SiTech only sells the complete servos with the encoders installed.
Don W


Re: Conversion of Orion Skyquest XX scope #poll- Motor runs no stop #poll-

Raphael T Vilardi
 

Hi Don  Happy Holidays!


I'm not knowledgeable in electronics, to star with, so I'm sorry if I say something silly. I rechecked the wiring.: there are two 4-way flat cables; one for the motor encoder the other for the scope encoder. The same goes for altitude and azimuth systems. I've measured the four terminals of each.  Gnd is easy to find. 5V too. The other two with 4.89V each got to be the A&B, right? The motor and scope encoders have the same arrangement. They are connected to the 8-way controller according to the wiring diagram.

There are 4 encoders. Could it be the all 4 are bad?  They were working fine with the original controller.

Should I order the encoders from Sideral Tech? I don't know whether they would fit the existing motors. I would like to order the motors too but checking their size, at 3.92 inches length it seems they wouldn't fit the existing housing and the gearbox/worm/gear without a major surgery.

 


Re: error message In motor encoder limit

andoverobservatory <SJamiem16@...>
 

Hello , Found the problem!  Decided to download Sitech094N  again and the direction issue went away!
The laptop was connected to the controller when I had the bad power supply and apparently the software got corrupted.


Leason learned!!
   Good night and Merry Christmas to all


Scott


Re: error message In motor encoder limit

andoverobservatory <SJamiem16@...>
 

Hi again!
Now that i have the motors working great in config , i set up the mount to do testing and tweeking and immediately realized I had a problem i cant explain.
In Sitech 94N i have discovered that when I try to move the telescope East it goes West. If I try to move it West, it also moves West. This is true if I iniialize on Skymap and select a star East to GOTO or if I use the virtual handpad to move the scope. This makes it impossible to do an alignment. Going back to Config the telescope moves normally and the handpad selections are properly matched on Configs virtual handpad.. I'm found a link to more current software for Sitech version 95 but cant get the link to work. I am also using version 3.7 for the controller even though I understand that somewhere there is 3.9.
not sure this is a version issue and cant see any explanation other than the telescope is not really in German Equatorial mode , but that should not cause this.
I did confirm that the directions are proper  in Config. I specialize in finding strange issues, seems to be my greatest talent
Oh ,one other symptom, In siteck the Pan speed left button is orange, which seems to be stuck there . No idea what that means but though maybe it was overiding the direction bit for moves , but it seems like its the wrong direction for moving West.
Scott


Re: Restarting tracking after a meridian flip

old_eyes
 

On Mon, Dec 21, 2020 at 08:29 AM, Don W wrote:
Hi Old_Eyes,
Uncheck the settings in SiTech for reversing guiding.  Let PHD2 do the reversing.  Normally only DEC changes direction for a GEM after the flip.
Don W
Hi Don,

That seemed to fix the problem - at least on the first trial.

It was made slightly difficult by clouds rolling over just as the meridian flip was made, but they were moving fast and PHD2 quickly picked up a guide star again and once things settled down, the guiding was good.

No sign of any instability or 'heading to the horizon'. I will have to wait for another clear spell to prove it works repeatedly, but encouraging.

Thanks for the suggestion.


Re: Conversion of Orion Skyquest XX scope #poll- Motor runs no stop #poll-

Don W
 

Hi Raphael,
The encoder signals must flop between near zero and +5 volts - it is a square wave signal.  Since you are always measuring near 5 volts that means your encoders are NOT sending a signal to the SiTech controller so the controller can not control the4 servo properly.

Either your wiring is incorrect or the encoders are burned out and bad.
Don W


Re: Conversion of Orion Skyquest XX scope #poll- Motor runs no stop #poll-

Raphael T Vilardi
 

I've just repeated he test and measured the A and B on the connector on the controller: They read 4.98 volts, the same as when the motors are fully stoped


Re: Conversion of Orion Skyquest XX scope #poll- Motor runs no stop #poll-

Raphael T Vilardi
 

Hi Dan
Merry Christmas and Happy New Year!
It is a Servo Controller II.
Reviewing your instructions: Second step:  “uncheck both of the “Man” checkboxes”. To do so one must check the “Auto” checkboxes but, if you do so the altitude and azimuth sliders stay locked. So I checked the “Man” instead.  Did I get something wrong up to this point?
After moving the altitude slider to the righ, the motor starts to run slowly clockwise. The output box reads 118, both Mot[    ]Loc reads 0. I don´t see any voltage boxes but the Amps [   ] reads 0.30.average

As I mentioned, I don´t have the full scope with me now, only the altitude set: motor, motor encoders, main gear and the scope encoders installed beneath the main gear, all these attached to one leg of the mount. Is this an issue? I  

Wiring. On the original Orion wiring: one 4-way  flat cable comes from the motor encoder and a seconf 4-way flat cable comes from another encoder linked to a smaller gear beneath the main gear which, I assume, would be scope encoder. Both 4-way flat cables connect to the Orion controller.

I measured both with a multimeter several  times: the two 4-way wires read the same: 5V, Gnd, 4.98V, 4.98V. I assume the last two to be the A & B motor encoders wires and I connected the two 4-way cables plus the motor + and – according to the Servo II wiring Diagram.

Turning on the Servo II, I measured the current, first at the Servo II  8-way  ALT/DEC connector  head screws and then at the end of the cables terminals connected to the motor encoder connectors. The reading was the same: 5V, Gnd, 4.98V, 4.98V. So, the current is flowing from the Servo II to the encoders.

What should I do now?

Best regards
 


Re: Another question about encoders!

Don W
 

Hi Stefan,
If you can't install a compatible encoder with your BISS on the Dec Axis, it really is not a disaster.  You have a Renishaw on your RA axis and that is the important axis for tracking accurately.  When tracking a target, the Dec hardly moves and guiding with the servo encoder gives you high resolution (for guiding).  The 10K encoder on DEC would only resolve to about 2 arc-min, so set the DEC to use Polite Mode with your 10K encoder on DEC.

Dan can confirm if you can use the BISS on RA and the 10K encoder on DEC.
Don W


Re: Conversion of Orion Skyquest XX scope #poll- Motor runs no stop #poll-

Dan Gray
 

Did you look at the other Mot[        ]Loc in case the encoders were wired to the wrong inputs (alt to az)?
Also, do the experiment again.  WHen you have the motor moving slowly, both the A and the B should be reading average of 2.5 volts (as they go high and low).
I can't remember if you have a servoI or ||, but check the A and B right ON the connector on the controller, they should be 2.5 volts when moving slowly too.
I would be really surprised if it's the controller itself, other than lightning strikes, we've had maybe one time it was the controller, not the wiring or connector.
If it's a servoI, carefully look at the modular connector.  If a plastic separator gets bent over, it will prevent the wire contact from seating in the connector.
let us know, and merry christmas everybody!
Dan


On Wed, Dec 23, 2020 at 6:26 PM Raphael T Vilardi <rtvilardi@...> wrote:
Hi Dan, I just followed the steps prescribed and yes, I got the altitude gear moving slowly clockwise and it would speed up as I moved the slider as you said it would. I had for the first time total control on speed and direction but the Mot[     ]Loc reads zero and does not change.
 
I don’t   have the full scope with me now but just the altitude system disconnected from the OTA. Could it be that I have to have both altitude and azimuth system connected to the servo controller for the thing to work?

Just for the record: I checked  the wiring over and over again both at the controller connector and at end connectors linking to the encoder terminals and scope encoders. The  5v  is there for both motor and scope encoders, and the motor encoders and scope encoders  A and B read 4.98v each.  So the energy is reaching the encoders.
 


Re: Another question about encoders!

Stefan Shelander
 

The BiSS C interface only being able to talk with 26 bit encoders creates a real problem for us. What we have is a modified JMI NGT 18 telescope. This is a split ring equatorial Newtonian telescope. The difficulty is finding the space for the encoder on the declination axis. The existing encoder (10,000 tics) required gears to couple it to the declination axis. There simply isn't enough space to fit a Renishaw encoder into this setup. This might not be a realistic question, would it be possible to alter the interface box on the declination channel to work with a 22 bit encoder? Or is there another BiSS C interface out there that will work with a 22 bit encoder and talk with the Servo II drive? Any help with problem would be greatly appreciated. Happy Holidays to everyone out there!


Re: Conversion of Orion Skyquest XX scope #poll- Motor runs no stop #poll-

Raphael T Vilardi
 

Hi Dan, I just followed the steps prescribed and yes, I got the altitude gear moving slowly clockwise and it would speed up as I moved the slider as you said it would. I had for the first time total control on speed and direction but the Mot[     ]Loc reads zero and does not change.
 
I don’t   have the full scope with me now but just the altitude system disconnected from the OTA. Could it be that I have to have both altitude and azimuth system connected to the servo controller for the thing to work?

Just for the record: I checked  the wiring over and over again both at the controller connector and at end connectors linking to the encoder terminals and scope encoders. The  5v  is there for both motor and scope encoders, and the motor encoders and scope encoders  A and B read 4.98v each.  So the energy is reaching the encoders.
 


Re: Conversion of Orion Skyquest XX scope #poll- Motor runs no stop #poll-

Raphael T Vilardi
 

Hi Dan Sorry for the delay. I had no access to the telescope until now.

Thanks for the advice. Let me try the steps right now and I'll let you know. 

2441 - 2460 of 34819