Let's talk marine computers
#12
I'm in touch with http://www.chersoft.co.uk. They offer a COM server that comes close. From the looks of it, it is the basis of certain commercial packages on the market.
More as it develops.
More as it develops.
#13
Here's my nickels worth.
While running "hard",
I don't think you will end up needing to do anything other than changing views and info pages:
*Pan right 1/2 screen
*Pan left 1/2 screen
*Pan up 1/2 screen
*Pan down 1/2 screen
*Zoom In 1 step
*Zoom Out 1 step
*Center Screen to current position
*Next page (to scroll thru nav and data pages)
*Back to chart page
All other data entry and functionality should be left to the touchscreen form of entry.
My guess on one way to get close to the above is as follows:
One 4-way joystick paddle for 4-way pan function (a fast double-stroke any direction centers to current position).
One 4-way joystick paddle for Zoom (Up/Dn) and Scroll (Rt/Lt for nxt pg, last pg - a fast double-stroke any direction goes to Chart page).
Nothing as large as a bow-thruster stick, nor as small as a Guest remote spotlight stick. Probably somewhere around an old Bennett single stick tab switch. Could put both of em above your throttles..
Should be easy enough to modify a 8-or-12-button CAD keypad guts to work with the paddle switches. Then a matter of assigning functions to the "buttons" via standard included software for the button pad. (assuming that you can assign hotkeys to the necessary functions in the native charting software you plan to use..).
I like your idea and don't think it sucks.
I DO think you should avoid trying to do anything more than the above-mentioned functionality to the remote pad.
While running "hard",
I don't think you will end up needing to do anything other than changing views and info pages:
*Pan right 1/2 screen
*Pan left 1/2 screen
*Pan up 1/2 screen
*Pan down 1/2 screen
*Zoom In 1 step
*Zoom Out 1 step
*Center Screen to current position
*Next page (to scroll thru nav and data pages)
*Back to chart page
All other data entry and functionality should be left to the touchscreen form of entry.
My guess on one way to get close to the above is as follows:
One 4-way joystick paddle for 4-way pan function (a fast double-stroke any direction centers to current position).
One 4-way joystick paddle for Zoom (Up/Dn) and Scroll (Rt/Lt for nxt pg, last pg - a fast double-stroke any direction goes to Chart page).
Nothing as large as a bow-thruster stick, nor as small as a Guest remote spotlight stick. Probably somewhere around an old Bennett single stick tab switch. Could put both of em above your throttles..
Should be easy enough to modify a 8-or-12-button CAD keypad guts to work with the paddle switches. Then a matter of assigning functions to the "buttons" via standard included software for the button pad. (assuming that you can assign hotkeys to the necessary functions in the native charting software you plan to use..).
I like your idea and don't think it sucks.
I DO think you should avoid trying to do anything more than the above-mentioned functionality to the remote pad.
#14
Phd: Your list about covers what I have in mind as the "fingertip subset." The joystick idea is interesting, I'll look into it. As for keyboard macros, I want to avoid them like the plague. Very unreliable. What I have in mind is a daemon that either interrogates dedicated switches (via parallel port, for instance), or it hooks into the keyboard queue. With the proper inputs, it will call the respective functions directly.
#15
We've run 12-and 16-button digitizers for nigh on 20 years in our engineering department. We've found that Virtual Tablet driver/software has performed admirably for us. Some of our engineers only assign button events to F- and ALT- combinations while others assign full macros. You are correct in the macros are questionable, but nobody has ever had any issues with assigning something like (two fast clicks of button #10 returns an ALT-F9 to the system).
You obviously have the I/O translation capabilities to build your own "driver" for the input device. I am still not fully understanding how the charting software will recognize these inputs unless you send them in a hotkey format...
You obviously have the I/O translation capabilities to build your own "driver" for the input device. I am still not fully understanding how the charting software will recognize these inputs unless you send them in a hotkey format...
#16
All: I talked more w/ Chersoft), and they say: "We have been involved in developing systems for the RNLI (UK Life Boats). The operators are strapped in and operate the computer using dedicated controls built into the armrest. The design of the hardware is very shock resilient: no fans, no spinning hard-discs, etc. I guess you would set up charts, routes, etc. using a normal mouse & keyboard. Then you would want to put the system into a mode where it displayed the information required by the helmsman with virtually no manual input. The display would need to show the best chart data, the vessel, the route, the next waypoint, distance & CTS, that sort of thing."
That pretty much covers what I had in mind. I'll stay in touch with them.
Here is what I don't like about dedicated chartplotters and how a PC-based system could help.
Too many buttons to fumble with. Keys in front of the throttle would take care of it.
- At high speed and during hard maneuvering, sometimes I lose track of the route. I'd love to have clear steering cues (such as a big yellow arrow) .
- On many chartplotters, redraw rate is anemic. No problem for a fast Pentium.
- The larger the display, the easier to read, especially at high speed.
- A PC is powerful enough to do several things at one. For instance, I plan to monitor and log all parameters of the HP525 that are made available on the CAN-Bus.
And there's always room for other winter projects.... Any requests?
Phd: Hotkeys (as oppsoed to keyboard macros) do work, but the app has to support assignable hotkeys (most use fixed hotkeys .. what the programmer thought to be hot). Also, the app needs to have the focus for keys to work. I'm indeed planning to use a driver (Win 2000 service) that monitors the keyboard and that talks to the app via the COM (Computer Object Model ... not serial port) interface.
That pretty much covers what I had in mind. I'll stay in touch with them.
Here is what I don't like about dedicated chartplotters and how a PC-based system could help.
Too many buttons to fumble with. Keys in front of the throttle would take care of it.
- At high speed and during hard maneuvering, sometimes I lose track of the route. I'd love to have clear steering cues (such as a big yellow arrow) .
- On many chartplotters, redraw rate is anemic. No problem for a fast Pentium.
- The larger the display, the easier to read, especially at high speed.
- A PC is powerful enough to do several things at one. For instance, I plan to monitor and log all parameters of the HP525 that are made available on the CAN-Bus.
And there's always room for other winter projects.... Any requests?
Phd: Hotkeys (as oppsoed to keyboard macros) do work, but the app has to support assignable hotkeys (most use fixed hotkeys .. what the programmer thought to be hot). Also, the app needs to have the focus for keys to work. I'm indeed planning to use a driver (Win 2000 service) that monitors the keyboard and that talks to the app via the COM (Computer Object Model ... not serial port) interface.
#17
I think (hope) I’ve found the solution. It’s the X-keys switch interface from PI Engineering http://www.ymouse.com . This thing translates a switch closure to one or more (programmable) keyboard codes which are then sent to the computer. No software or custom programming required.
I have looked at all the PC compatible navigation packages. Most accept hotkeys. They usually are what the programmer thought are intuitive hotkeys. I found no software packages that allow for definable hotkeys. It would be possible to use a keyboard macro program, or write a dedicated one, but they usually are not reliable.
Writing a custom application, even one that is based on commercial components such as the ones from Chersoft, looks like a bad investment of time if the only problem is the keyboard interface.
With a switch-closure-to-keyboard-code interface, I can map dedicated switches to keys, even key combinations. I can use the same type of switches which are used on my dash (in my case, Contura type), which makes for a sano look.
The PI Engineering units are not marinized of course, will need some work and a dry place. I don’t see major problems there. If the project doesn’t pan out, then I can always use the switch panel for something else.
Also, I won’t have a dorky trackball or a numerical keyboard on my dash. This way, the boat doesn’t look like a cash register.
It’s enough that the boat sometimes feels like a cash register.
I have looked at all the PC compatible navigation packages. Most accept hotkeys. They usually are what the programmer thought are intuitive hotkeys. I found no software packages that allow for definable hotkeys. It would be possible to use a keyboard macro program, or write a dedicated one, but they usually are not reliable.
Writing a custom application, even one that is based on commercial components such as the ones from Chersoft, looks like a bad investment of time if the only problem is the keyboard interface.
With a switch-closure-to-keyboard-code interface, I can map dedicated switches to keys, even key combinations. I can use the same type of switches which are used on my dash (in my case, Contura type), which makes for a sano look.
The PI Engineering units are not marinized of course, will need some work and a dry place. I don’t see major problems there. If the project doesn’t pan out, then I can always use the switch panel for something else.
Also, I won’t have a dorky trackball or a numerical keyboard on my dash. This way, the boat doesn’t look like a cash register.
It’s enough that the boat sometimes feels like a cash register.
Thread
Thread Starter
Forum
Replies
Last Post
TalkOffshore
General Boating Discussion
3
07-13-2004 01:06 AM
TalkOffshore
General Racing Discussion
0
07-12-2004 03:02 PM





