Forum Replies Created
Glad you have found a work around, but I will discuss the results you have found with our developers and see if we can track down what is happening.
I’ll post some more feedback on here ASAP.
I think the difference between Position and other Signal K values, is that position had three fields; Latitude, Longitude and Altitude which are all under the same schema key, where as Course Over Ground, Speed Over Ground, etc. all have a single unique key and value.
In theory the Signal K developers could have separated the three fields in to three separate keys, but then you would need to have a way to link them, as you would not want a Latitude from one source to be mixed with the Longitude of another source. I had assumed that this was a normal way for positions to be stored in a JSON schema but your post did make me question this decision.
Do you belong to the Signal K Slack group? I would strongly recommend joining as you will then be able to chat directly to the core Signal K development team and gain from their knowledge and expertise…. http://slack-invite.signalk.org/
If you have any further questions please let me know.
We have no known issues with web socket stability. Have you tried running either of the hosted web apps that use web sockets (Instrument Panel, iKompass or the Websocket Logger) for long periods?
It would be good to prove if it is specific to your NodeJS implementation.
We do not use a Ping/Pong type procedure on iKommunicate, just another thing to create incompatibility. I have been told that some firewalls can cut idle WS connections, but never experienced it myself.
However when a web app opens a web socket with iKommunicate, it will send a hello message and then even if there is no NMEA0183 or NMEA2000 data being received and therefore no Signal K Delta messages, iKommunicate will send a Signal K “heartbeat” Delta message every second…
Hope this answers your question and please come back with anymore questions or feedback on your testing.
We replaced the PCB as the Atmel processor refused to run the bootloader and so we could not reflash it. We have had a small number of this type of failure and it is really frustrating as we just have to scrap the PCBs. We contacted Atmel but nothing useful was gleaned and replacing the processor is really difficult and risky even with the right tools.
So I don’t think it is something you have done.
Hi Red Herring,
Sorry to hear of your problem.
The good news is that you have LED activity, so we should be able to recover the situation (remotely).
I note that you have also emailed me directly, so I will reply to you via email.
You place the IP address of your iKommunicate in the “IP_Address” part of the URL i.e. http://192.168.1.80/stats/v1/
Yes next week I am around and you can give me a call.
The first URL I gave you is one that you can use with iKommunicate to make it return its internal statistics. When connected to iKommunicate, just type the URL that I gave… http://IP_Address/stats/v1/ in to your browser, remembering to put in whatever your iKommunicate’s IP address is on your network and after a second or so your browser should return a load of JSON text. Raw JSON text is difficult to read as it has no structure, so the second URL I gave you was for a public website that has a JSON structuring tool, which lets you copy and paste the RAW JSON data in to a box and then in another box you see the nicely formatted and easy to read JSON.
Sorry to hear that you are still having problems. I thought when you got it to power up previously that everything would be OK, but perhaps there is an intermittent fault somewhere.
Please return your iKommunicate with a short note explaining the nature of the fault and that you have been in communication with me.
It is important that you include a daytime contact number and of course the return address where you would like us to send it back to. If you need to have the unit back within a certain time frame please highlight this and we will do our best to achieve it, but we cannot guarantee to meet all requested deadlines.
The address to return the equipment to is…
Digital Yacht Limited
6 Farleigh Court,
Old Weston Rd,
Tel: + 44 (0) 117 955 4474
IMPORTANT – if you are returning equipment from outside the European Union, please mark on the Shipping paperwork that this is “Faulty Yacht Equipment, returned to UK manufacturer for repair” and state a low value of $25 USD to avoid any delays in customs and additional import charges.
I don’t think this is true, you should be able to copy the Kindle App manually in to the same folder as the Instrument Panel App and it will be served up just like any webpage. It is not a Node App, but a simple HTML5/CSS/JS app.
If you copy the Kindle files on to your PC’s desktop and then double click the HTML file, it will open and run on your PC’s browser without Node.
Sorry for the delay in response, as you might have seen from some of my other recent replies, I had a problem with WordPress notifications not happening.
Please could you create a log file of your NMEA networks by following this procedure….
I can then replay this on my demo iKommunicate and confirm what PGNs are available and why they are not being converted.
As discussed via email, I will be investigating this and your other issues tomorrow. I had hoped to work on it today but ran out of time.
Perhaps a call on Thursday would be best to review my findings. In the meantime if you could generate a Statistics report by typing in this URL to your browser it might shine some light on what is happening with the slow responses/performance in the browser…
This will return a JSON formatted list of statistics so you might want to install the Chrome JSON Formatter extension or copy and paste the output in to this website…
Which will create nicely formatted and easy to read JSON output.
Not re-transmitting RMC was an oversight and I will try and get this added on the next release.
Hi apologies to everyone but something must have broken on our WordPress bbPress Forum plugin as I stopped receiving notifications of posts and it was only when Editwiz59 contacted me directly that I became aware of the issue.
By adding an extra plugin specifically designed to create notifications, I seem to have fixed things, so I will endeavour to provide more timely replies from now on.
If you create a sub-folder in the Signalk folder on your Openplotter system and then unzip the files in to this sub-folder, renaming the iKommunicate-API-Kindle.html file to index.html, then when you go to 10.10.10.1:3000/signalk/kindle it should run the Kindle app. You might have to fiddle around with the URL the App tries to use to get the Signal K data, but it should be doable even by a non-developer (which also describes me).
I am sure there are developers on the OpenPlotter project that could help.
No iKommunicate does not currently convert NMEA2000 data to NMEA0183, except for the TCP/UDP network output.
More conversions maybe added in the future but our original goal was not to make iKommunicate convert anything to anything, more to convert NMEA0183/2000 to Signal K and TCP/UDP.