The meaning of "Es'hail"
Recently we see many postings about the new satellite called "Es'hail 2". Maybe you also wondered what the meaning is of "Es'hail". I asked two 'friendly Arabic speaking colleagues' to fill me in.
It appears the satellite is named after a star, that we know as Canopus. https://en.wikipedia.org/wiki/Canopus In Arabic, Canopus is Sohail. But in the section 'Middle East' on the Wiki page you see that there are many variants for this name, including Sohayl, Soheil, Suhayl, Suheyl, etc.
Actually the name of our satellite is 'The Canopus', or in Arabic 'El Sohail'. In Arabic they tend to merge the two words, so it would become 'ElSohail'. Since Arabs find it hard to pronounce the combination of l and s, they drop the l. So it becomes 'ESohail'. An apostrophe is added to emphasize the S: 'ES'ohail'. And since the o (or u) will be pronounced anyway, almost 'automatically', it may be dropped. So that is how we get 'ES'hail', or even 'Es'hail'.
As for the pronunciation of this satellite's name, probably 'eSohayl' is best, with a short and soft e at the beginning.
So now at least we know what we are talking about :-)
73, Nico PA0DLO
Thanks Nico for the nice explanation, well done!
Yes, the company Es'hailSat and there satellite fleet are named after Canopus.
Es'hail 2 will be launched in first quarter 2017.
73s Peter DB2OS
Am 11. Juni 2016 17:17:51 MESZ, schrieb Nico Janssen [email protected]:
Recently we see many postings about the new satellite called "Es'hail 2". Maybe you also wondered what the meaning is of "Es'hail". I asked two 'friendly Arabic speaking colleagues' to fill me in.
It appears the satellite is named after a star, that we know as Canopus. https://en.wikipedia.org/wiki/Canopus In Arabic, Canopus is Sohail. But in the section 'Middle East' on the Wiki page you see that there are many variants for this name, including Sohayl, Soheil, Suhayl, Suheyl, etc.
Actually the name of our satellite is 'The Canopus', or in Arabic 'El Sohail'. In Arabic they tend to merge the two words, so it would become 'ElSohail'. Since Arabs find it hard to pronounce the combination of l and s, they drop the l. So it becomes 'ESohail'. An apostrophe is added to emphasize the S: 'ES'ohail'. And since the o (or u) will be pronounced anyway, almost 'automatically', it may be dropped. So that is how we get 'ES'hail', or even 'Es'hail'.
As for the pronunciation of this satellite's name, probably 'eSohayl' is best, with a short and soft e at the beginning.
So now at least we know what we are talking about :-)
73, Nico PA0DLO
Sent via [email protected]. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
I have been troubleshooting CAT control problems of my 847 ahead of Field Day, and the oddest situation has come to light and wondered if anyone has seen this situation.
I used to run Gpredict on my Mac, and on a Linux netbook with the 847, and both worked fine. In testing the setup in portable operation over Memorial Day weekend (on one of the XA birds), CAT control stopped working with the Netbook. Flatly refused to work. Before I started transmitting, however it had been running all day prior to moving to the portable setup.
I moved to the Mac, and it too wasn't working. Puzzled, I tried a reset of the CPU in the radio. Nothing changed. Tried a different Prolific and FTDI USB adapter. Nothing.
The shack computer, a desktop, works fine both Linux and Ham Radio Deluxe under Windows 10, with all three USB adapters. I also dragged out an ancient Sony laptop with a real RS-232 port. That works. I made some test scripts on the desktop Linux machine to initiate CAT commands, they worked at all possible port speeds. Tried the scripts on the netbook and Mac, they do not work. Hamlib reports a communication error.
I also have a 5 year old i5 Windows machine, never ran HRD and that does not work either.
I am not sure if the radio is on its way out, or if there is just some strange incompatibility between the USB serial adapters, but the desktop box works very reliably where the others do not. And the last thing I want to do is drag that beast out to FD.
Any input welcome.
I had this same problem with an 847 that I had loaned out to another ham. This person somehow pushed in one of the pins in the RS-232 DB9 connector just enough that it would sometime's work. I was taking the 847 apart to prepare to replace the 232 chip when I noticed the pushed in pin. I simply pushed the pin back out and problem went away. I hope your problem resolution is as simple...
73 Jeff kb2m
-----Original Message----- From: AMSAT-BB [mailto:[email protected]] On Behalf Of Jeff Breitner Sent: Saturday, June 11, 2016 3:15 PM To: [email protected] Subject: [amsat-bb] FT-847 CAT
I have been troubleshooting CAT control problems of my 847 ahead of Field Day, and the oddest situation has come to light and wondered if anyone has seen this situation.
I used to run Gpredict on my Mac, and on a Linux netbook with the 847, and both worked fine. In testing the setup in portable operation over Memorial Day weekend (on one of the XA birds), CAT control stopped working with the Netbook. Flatly refused to work. Before I started transmitting, however it had been running all day prior to moving to the portable setup.
I moved to the Mac, and it too wasn't working. Puzzled, I tried a reset of the CPU in the radio. Nothing changed. Tried a different Prolific and FTDI USB adapter. Nothing.
The shack computer, a desktop, works fine both Linux and Ham Radio Deluxe under Windows 10, with all three USB adapters. I also dragged out an ancient Sony laptop with a real RS-232 port. That works. I made some test scripts on the desktop Linux machine to initiate CAT commands, they worked at all possible port speeds. Tried the scripts on the netbook and Mac, they do not work. Hamlib reports a communication error.
I also have a 5 year old i5 Windows machine, never ran HRD and that does not work either.
I am not sure if the radio is on its way out, or if there is just some strange incompatibility between the USB serial adapters, but the desktop box works very reliably where the others do not. And the last thing I want to do is drag that beast out to FD.
Any input welcome. _______________________________________________ Sent via [email protected]. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
Whenever I use Gpredict with my 847, I need to set the refresh rate to about 5 seconds (5,000 ms). Never understood why, but updating too often quickly ends up with a hang. This is on a Linux system with a real serial port (not USB). I'm using "rigctld -m 101 -r /dev/ttyS0 -t 4532 -v -s 57600" as the run string for the rig control process.
Good luck,
Greg KO6TH
Jeff Breitner wrote:
I have been troubleshooting CAT control problems of my 847 ahead of Field Day, and the oddest situation has come to light and wondered if anyone has seen this situation.
I used to run Gpredict on my Mac, and on a Linux netbook with the 847, and both worked fine. In testing the setup in portable operation over Memorial Day weekend (on one of the XA birds), CAT control stopped working with the Netbook. Flatly refused to work. Before I started transmitting, however it had been running all day prior to moving to the portable setup.
I moved to the Mac, and it too wasn't working. Puzzled, I tried a reset of the CPU in the radio. Nothing changed. Tried a different Prolific and FTDI USB adapter. Nothing.
The shack computer, a desktop, works fine both Linux and Ham Radio Deluxe under Windows 10, with all three USB adapters. I also dragged out an ancient Sony laptop with a real RS-232 port. That works. I made some test scripts on the desktop Linux machine to initiate CAT commands, they worked at all possible port speeds. Tried the scripts on the netbook and Mac, they do not work. Hamlib reports a communication error.
I also have a 5 year old i5 Windows machine, never ran HRD and that does not work either.
I am not sure if the radio is on its way out, or if there is just some strange incompatibility between the USB serial adapters, but the desktop box works very reliably where the others do not. And the last thing I want to do is drag that beast out to FD.
Any input welcome. _______________________________________________ Sent via [email protected]. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
On 6/12/16 2:10 PM, Greg D wrote:
Whenever I use Gpredict with my 847, I need to set the refresh rate to about 5 seconds (5,000 ms). Never understood why, but updating too often quickly ends up with a hang. This is on a Linux system with a real serial port (not USB). I'm using "rigctld -m 101 -r /dev/ttyS0 -t 4532 -v -s 57600" as the run string for the rig control process.
Good luck,
Greg KO6TH
Yeah, I have to set it to no more than 2000ms or it causes Gpredict to cough and gasp. Gpredict has multithreading, but the writes to the rig control appear to be blocking. I don't think it matters much, the radio can only take the data so fast anyway.
The radio works fine with any of the desktops I use, it just won't work with any of my portable computers. Confirmed exact drivers in Windows, sniffed the ports in Linux and hooked up a 'scope to watch the waveforms. Created test programs to try to look for buffering issues. Nothing is a smoking gun...'cept maybe that these USB->Serial converters are just good enough to work with (maybe) better chipsets that are on these desktop motherboards. Dunno.
I have a GearMo adapter showing up this week. If it works, great, if not this smaller desktop will be what I use.
What is so puzzling is that, it worked with everything up until a few weeks ago.
Thanks,
Jeff
Jeff Breitner wrote:
On 6/12/16 2:10 PM, Greg D wrote:
Whenever I use Gpredict with my 847, I need to set the refresh rate to about 5 seconds (5,000 ms). Never understood why, but updating too often quickly ends up with a hang. This is on a Linux system with a real serial port (not USB). I'm using "rigctld -m 101 -r /dev/ttyS0 -t 4532 -v -s 57600" as the run string for the rig control process.
Good luck,
Greg KO6TH
Yeah, I have to set it to no more than 2000ms or it causes Gpredict to cough and gasp. Gpredict has multithreading, but the writes to the rig control appear to be blocking. I don't think it matters much, the radio can only take the data so fast anyway.
The radio works fine with any of the desktops I use, it just won't work with any of my portable computers. Confirmed exact drivers in Windows, sniffed the ports in Linux and hooked up a 'scope to watch the waveforms. Created test programs to try to look for buffering issues. Nothing is a smoking gun...'cept maybe that these USB->Serial converters are just good enough to work with (maybe) better chipsets that are on these desktop motherboards. Dunno.
I have a GearMo adapter showing up this week. If it works, great, if not this smaller desktop will be what I use.
What is so puzzling is that, it worked with everything up until a few weeks ago.
Thanks,
Jeff _______________________________________________
Grounding?
Just a wild thought. What else could be different?
Greg KO6TH
Grounding?
Just a wild thought. What else could be different?
Greg KO6TH
*ding*
This afternoon I hooked up the null modem cable to the desktop, hit one end with cold spray and nothing happened. Hit the other end and *poof*, it quit working.
Not content, I went and hit the ends with a heat gun while hooked up to the Mac. You'll never guess what happened...just before I made a new one.
Thanks for pulling me off the primrose path. After years of working in software, of course it was a dev's fault, right?
Jeff
Hey, no problem. As a software engineer I always blame the hardware first. Just a reflex... :)
Good luck on Field Day,
Greg KO6TH (will be W6EK 5-AB SV on field day)
Jeff Breitner wrote:
Grounding?
Just a wild thought. What else could be different?
Greg KO6TH
*ding*
This afternoon I hooked up the null modem cable to the desktop, hit one end with cold spray and nothing happened. Hit the other end and *poof*, it quit working.
Not content, I went and hit the ends with a heat gun while hooked up to the Mac. You'll never guess what happened...just before I made a new one.
Thanks for pulling me off the primrose path. After years of working in software, of course it was a dev's fault, right?
Jeff
participants (5)
-
Greg D -
Jeff Breitner -
Jeff Griffin -
Nico Janssen -
Peter Gülzow