• Announcements

    • UnderDawg

      A Few Simple Rules   05/22/2017

      Sailing Anarchy is a very lightly moderated site. This is by design, to afford a more free atmosphere for discussion. There are plenty of sailing forums you can go to where swearing isn't allowed, confrontation is squelched and, and you can have a moderator finger-wag at you for your attitude. SA tries to avoid that and allow for more adult behavior without moderators editing your posts and whacking knuckles with rulers. We don't have a long list of published "thou shalt nots" either, and this is by design. Too many absolute rules paints us into too many corners. So check the Terms of Service - there IS language there about certain types of behavior that is not permitted. We interpret that lightly and permit a lot of latitude, but we DO reserve the right to take action when something is too extreme to tolerate (too racist, graphic, violent, misogynistic, etc.). Yes, that is subjective, but it allows us discretion. Avoiding a laundry list of rules allows for freedom; don't abuse it. However there ARE a few basic rules that will earn you a suspension, and apparently a brief refresher is in order. 1) Allegations of pedophilia - there is no tolerance for this. So if you make allegations, jokes, innuendo or suggestions about child molestation, child pornography, abuse or inappropriate behavior with minors etc. about someone on this board you will get a time out. This is pretty much automatic; this behavior can have real world effect and is not acceptable. Obviously the subject is not banned when discussion of it is apropos, e.g. talking about an item in the news for instance. But allegations or references directed at or about another poster is verboten. 2) Outing people - providing real world identifiable information about users on the forums who prefer to remain anonymous. Yes, some of us post with our real names - not a problem to use them. However many do NOT, and if you find out someone's name keep it to yourself, first or last. This also goes for other identifying information too - employer information etc. You don't need too many pieces of data to figure out who someone really is these days. Depending on severity you might get anything from a scolding to a suspension - so don't do it. I know it can be confusing sometimes for newcomers, as SA has been around almost twenty years and there are some people that throw their real names around and their current Display Name may not match the name they have out in the public. But if in doubt, you don't want to accidentally out some one so use caution, even if it's a personal friend of yours in real life. 3) Posting While Suspended - If you've earned a timeout (these are fairly rare and hard to get), please observe the suspension. If you create a new account (a "Sock Puppet") and return to the forums to post with it before your suspension is up you WILL get more time added to your original suspension and lose your Socks. This behavior may result a permanent ban, since it shows you have zero respect for the few rules we have and the moderating team that is tasked with supporting them. Check the Terms of Service you agreed to; they apply to the individual agreeing, not the account you created, so don't try to Sea Lawyer us if you get caught. Just don't do it. Those are the three that will almost certainly get you into some trouble. IF YOU SEE SOMEONE DO ONE OF THESE THINGS, please do the following: Refrain from quoting the offending text, it makes the thread cleanup a pain in the rear Press the Report button; it is by far the best way to notify Admins as we will get e-mails. Calling out for Admins in the middle of threads, sending us PM's, etc. - there is no guarantee we will get those in a timely fashion. There are multiple Moderators in multiple time zones around the world, and anyone one of us can handle the Report and all of us will be notified about it. But if you PM one Mod directly and he's off line, the problem will get dealt with much more slowly. Other behaviors that you might want to think twice before doing include: Intentionally disrupting threads and discussions repeatedly. Off topic/content free trolling in threads to disrupt dialog Stalking users around the forums with the intent to disrupt content and discussion Repeated posting of overly graphic or scatological porn content. There are plenty web sites for you to get your freak on, don't do it here. And a brief note to Newbies... No, we will not ban people or censor them for dropping F-bombs on you, using foul language, etc. so please don't report it when one of our members gives you a greeting you may find shocking. We do our best not to censor content here and playing swearword police is not in our job descriptions. Sailing Anarchy is more like a bar than a classroom, so handle it like you would meeting someone a little coarse - don't look for the teacher. Thanks.


  • Content count

  • Joined

  • Last visited

About gareth

  • Rank

Profile Information

  • Location
    New York, NY
  1. Thanks for the tips Allen. I am not issuing any commands to the Nexus server. By default, it starts publishing NMEA data at 4800 baud. All you have to do is read it. (If you want it to publish in its high-speed, proprietary binary format, called FDX, you have to issue a command to the server by writing a special string to the port). The commands I posted are issued on my Linux computer. The first one sets the baud rate of the port, and then I am reading the port using the normal Linux utility 'cat'. It's when I run the 'cat' command that the BTW display on my instrument immediately goes to "- - -". I may try writing my own program and do non-blocking reads as you suggest. I have never checked the CPU usage, but I don't believe it is pegged at 100%. If that does not work, I'll investigate getting rid of the 'write' pin on the cable. Will also check out StartLine. Thanks again... Gareth
  2. I have a strange issue with my Nexus instruments that I am hoping some sailor / computer person can help with. The setup is as follows: My instruments are the Nexus NX2 series. Nexus wind, depth, and compass sensors are connected to the Nexus NX2 server, which is in turn connected to a series of NX2 displays. GPS info comes from a Raymarine E-120 chart plotter, also connected to the Nexus server. My goal is to build my own NMEA mux, using a small Linux plug computer (a “GuruPlug”) so that I can log race data, and more importantly, re-broadcast the data on wifi, for use in apps like iRegatta. The GuruPlug is wired into boat’s power and connected to the serial port on the Nexus server via a USB-to-Serial cable. If I set a waypoint on the Raymarine, then I can see DTW and BTW on the chart plotter and also on the NX2 instruments, as one would expect. BUT, if I start dumping that data from the serial port on the server to the Guruplug, then all of the waypoint information disappears from the NX2 controls. BTW and DTW goes to “- - -“ and I don’t get those sentences in my log on the Guruplug. But BTW and DTW are still displayed on the chart plotter. The way I am dumping the data is as follows : stty -F /dev/ttyUSB0 4800 # sets the baud rate of the serial port to 4800 (I am not changing the server to FDX mode) cat < /dev/ttyUSB0 > log-file.txt # reads data from the serial port and writes to a file The data reads just fine and I see a bunch of NMEA ASCII sentences. But the second I start dumping the data, the BTW/DTW display on the NX2 multi-displays goes from what it should be to “- - -“. This is totally repeatable and happens immediately. And as I said, none of the sentences in the log has the waypoint information. I do get GPS lat/lon information, and also SOG/COG, so I know some of the GPS info is making it from the chart plotter. I can’t for the life of me figure out how dumping data from the Nexus race server effects what data the server is sending to the other instruments over the FDX protocol. But somehow it is. Has anyone seen this behavior or have any guess as to what might be going on? Many Thanks, Gareth