YAPP Crew Watcher - Test results

AngusMcDoon

Well-Known Member
Joined
20 Oct 2004
Messages
9,052
Location
Up some Hebridean loch
Visit site
For those following this project, and maybe wondering what's happening, here's an update. Here's the original thread...

http://www.ybw.com/forums/showthread.php?381831

Last month I requested for 2 testers to have a go with the first 2 complete prototype systems to be made, and 2 complete systems were sent out. Here's the feedback from the testers...

1) There should be a confirm step when cancelling an alarm as it's too easy to choose cancel when meaning to choose silence. Choosing cancel by mistake means that the MOB position is lost.

2) After an alarm has been cancelled no further alarms will be raised for 90 seconds, a design feature. It is not indicated on the display when this 90 second period is in effect so it looks like the system is not working.

3) The radio range between the victim unit and the central unit is sometimes insufficient leading to false alarms, for example if someone goes behind a closed door on a boat.

4) There should be a power switch, or at least an options for one.

5) The board and battery holder in the victim unit come loose and start rattling around in their case.

These are all valid points and I will attend to them all. Here's what's to be done...

1) Easy software change to make. Now there's a confirm cancel alarm on the display with a YES or NO button press. Pressing cancel then NO silences the alarm (as that was probably what you intended) but doesn't cancel it.

2) Another easy software change. When in this 90 second period it is shown on the display along with a count down to re-activation.

3) This is the biggest problem, and requires a new PCB. I've described it with pictures at the end of this list.

4) A power switch is easy to add but there was no provision on the PCB to wire it in. However, because of 3) requiring a new PCB I'll add a couple of pads just after the power connector. If a switch is required it can be taken off from these pads. If not required, then a solder link across the gap between the pads will be used instead.

5) The items in the victim unit were attached using sticky foam pads. I don't want to have to drill any holes in the victim unit because my drilling is not very good. The sticky pads seem to come unstuck after a few weeks. I have bought a glue gun and will use that instead. First tests seem fine.


The radio distance problem...

For the radio circuitry I use pre-assembled RF modules which have all the radio circuitry and an aerial on the board, like this...

bLLvj65.jpg


This is fine in the victim unit which transmits, but the aerial is a bit puny to use in the central unit that receives. The alternative is in the central unit to use a receiver with an external aerial and a signal amplifier like this...

6oOPnIJ.jpg


There are 2 problems with this - firstly it costs about £4 more which will blow my minimum-configuration budget of £20 for the central unit (so maybe I'll offer a small boat version with the original module and a big boat version with the alternative module), but a bigger problem is that the alternative RF module does not fit on the current PCB. Here's the original module in place...

uLA4tzQ.jpg


and here's the alternative, which is bigger. It fouls one of the connectors...

XYqqtI6.jpg


So it's yet another PCB design needed - the third, all the previous PCB's end up as inadequate beer coasters and table leg shims...

TlGPlkj.jpg


The RF module in the bottom right is rotated by 90 degrees to fit within the board boundary and not clunk into any connectors. I've added the power switch option while I'm at it, and rotated a transistor outline the right way up as well, although that's not a functional change. I'll send it off to the factory today, but that will be another 3 week delay.
 
My immediate thought on the cancel / silence issue is why show a cancel button at all to begin with?

The first thing anybody's going to want to do when it goes off is shut the distracting noise up. In the case of a unit with physical buttons, I would make the initial press on any of them do this. If yours is touchscreen, perhaps a touch anywhere on the display? Or at least a large and obvious button, and no other potentially-confusing buttons displayed at the same time.

Once it's silenced, you can then show the buttons for the likely next steps, including cancelling a false alarm.

Pete
 
An external antenna will be necessary on a metal boat to prevent false alarms when the crew goes onto the for deck. a second antenna may also be needed below deck for the same reason.
 
My findings as one of the testers - the range on deck with the base unit in the wheelhouse was excellent, no issue with false alarms. As soon as the crew units bent below - all sorts of issues with false alarms but to be honest - so what? We thought of the units like lifeline straps, you put one on before going on deck. Psychologically we didn't want a unit that meant we switched off in any way from being utterly, totally paranoid about the children falling overboard. The odd false alarm makes you check the base unit is working fine! Our rule will be that children going on deck clip one on.

For adults we've long been worried about being on deck with the engine running or a bit of wind in the sails, the other adult wouldn't hear your scream when you went over the side, autopilot on (usual for us) and it could be 10 miles before anyone knew. The crew watcher unit again will be a clip on, kept hanging in a waterproof pouch by the wheelhouse door. For this and the yonkers the power of the unit is no issue.

Overall top marks to Angus for a cracking bit of kit. When I persuade work to let me load the software update app I'll get that on and retest.

It all works seamlessly with Seatalk and NMEA and let's face it, it's about 90% less than the Raymarine kit which in any case won't work with my Pathfinder chartplotter.
 
Would it be possible to mount that connector on the bottom of the board and save the re-layout ?

Boo2

Possible, but would still need a new PCB. Rotating the RF module connector by 90 degrees wasn't difficult to do in the layout as there's plenty of spare space around that part of the board anywat.
 
My immediate thought on the cancel / silence issue is why show a cancel button at all to begin with?

That's a good idea. It's not a touch screen, just 2 hardware buttons with labels next to them on the display. I could change the software so that when an alarm goes off there's just one option to silence, and when that's pressed the single option changes to cancel. Less to read on the screen.
 
But please used the other button not the silence button to cancel so as to prevent an in advert double press cancelling the alarm when the intention was just to silence the alarm.
 
What is the weight of the tag? I'm looking for something like this to put on my cat's collar to warn me if he wanders off from the boat in the marina - but a commercial MOB tag is too heavy really.
 
What is the weight of the tag? I'm looking for something like this to put on my cat's collar to warn me if he wanders off from the boat in the marina - but a commercial MOB tag is too heavy really.

55 grammes. I tried attaching one to Cat's collar, but he got in a huff and skulked behind the sofa fighting it.
 
55 grammes. I tried attaching one to Cat's collar, but he got in a huff and skulked behind the sofa fighting it.

Hmmm, 55 grammes is a bit heavy. We use a Loc8tor tag for our cat - around 5 grammes, he doesn't notice it - trouble is that the alarm box is a small, battery powered thing and eats batteries if you leave it running in boundary monitoring mode.
 
It needs to be a bit difficult to cancel an alarm, if it's just a double press then it's too easy to do that and to get into the habit of it. I like the press to silence then a long press to cancel. The interface with the seatalk MOB is brilliant but when you can the alarm it immeiately removes the MOB waypoint - fine but if you accidentaly cancel then you've lost your waypoint.
 
With my Aluminium boat it looks like I need an external antena - so be it. Does this mean that I'll be further away from the boat when it triggers?
(Don't make the crew unit too small otherwise SWMBO will have ideas of slipping one in my pocket to keep me in the kitchen cooking and washing up). Andrew
 
It needs to be a bit difficult to cancel an alarm, if it's just a double press then it's too easy to do that and to get into the habit of it. I like the press to silence then a long press to cancel. The interface with the seatalk MOB is brilliant but when you can the alarm it immeiately removes the MOB waypoint - fine but if you accidentaly cancel then you've lost your waypoint.

This is what I was going to suggest. A short press to silence, a long press to cancel.
 
A suggestion, which may not be practical.

The problem seems to be that once a MOB alarm is cancelled, the MOB position etc. are all lost. Could not the MOB data be stored in a small buffer until the next MOB comes in, and that a "Recover MOB" procedure be provided? The buffer only needs to store one position; if stored in ASCII, that would only be about 20 or so bytes. Ideally the buffer would be non-volatile, but that isn't essential.
 
Or as recommended in post #8. use one button to silence and the other button to cancel.

A couple of other suggestions would be to have a n/c reed relay in the supply from the battery or the crew unit so that it could be stored in a rack with a magnet positioned to disconnect the power when not in use like the rack of EPIRB's have.

The storage rack could also have charging connections so when the crew unit is not in use the battery's could be kept charged like some hand held radios have.

The storage rack could also have a way of telling the base unit that the crew unit is not in use thus disabling the alarm for that crew unit.

I would not expect Angus to design all this but could make provision on the circuit boards and in the software to allow for this.
 
Why would you cancel the MOB alarm until the MOB was recovered. Silencing the alarm could also prevent a repeat alarm for that crew unit until the cancel button was pressed once the MOB was recovered.
 
A suggestion, which may not be practical.

The problem seems to be that once a MOB alarm is cancelled, the MOB position etc. are all lost. Could not the MOB data be stored in a small buffer until the next MOB comes in, and that a "Recover MOB" procedure be provided? The buffer only needs to store one position; if stored in ASCII, that would only be about 20 or so bytes. Ideally the buffer would be non-volatile, but that isn't essential.

All that can be done easily is software. The processor has 256 bytes of NV storage of which only a little is used to store the settings. However, I am down to the last few 100's of bytes of program flash space on the processor. I could go to the next size up, but that adds another £2 to the cost which I am trying to avoid.
 
All that can be done easily is software. The processor has 256 bytes of NV storage of which only a little is used to store the settings. However, I am down to the last few 100's of bytes of program flash space on the processor. I could go to the next size up, but that adds another £2 to the cost which I am trying to avoid.

Program memory constraints are a familar problem to me - back in the 80s , I worked on Z80 based "single card computers". 2k ROM, no operating system and the development system was a CP/M micro( an Osborne 1!) with asm and link!
 
Top