-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Apologies - this is now working fine. I did not realise that I had another process still running that was in contention for the port. I stopped it and the tio console to MicronettoNMEA seems to be working without any obvious data errors. I need to investigate the port speed settings a bit more as well. Thanks for your patience! |
Beta Was this translation helpful? Give feedback.
-
Sorry for not answering earlier. |
Beta Was this translation helpful? Give feedback.
-
Hello, It has been a year since I looked back at this after a few tries. Thanks for your great work on Micronet To NMEA: I have ALMOST :-) got it working, but I am still a little stuck, this time with the Micronet protocol. As before, all compiles well on the Arduino IDE and it seems to run well and connect to our MN100-2 display. I had hoped to be able to send some test NMEA data to this display over serial USB for the Teensy to forward to Micronet and be read on the display, but I see nothing, only dashes - - - - for the depth and speed data …..and no other data. The test data works fine when connected to AvNav via a USB serial port or a socket over wifi, so I think MicronetToNMEA should be able to convert and forward the NMEA for Micronet. For example: I don't understand Micronet very well, so I could be doing something stupid. Using the console over the USB serial I seem to be able to connect the Teensy and observe traffic that the display puts out, but I don't have any Micronet tools to observe what, if anything, is arriving in Micronet while my test host (simulated depth sounder) is sending the Teensy data over the USB Serial. Maybe the MN100-2 has to have another 'proper' device connected to make this work? Example from the console: *** MicronetToNMEA *** 0 - Print this menu Choice : 2 Scanning Micronet networks for 5 seconds ... done List of scanned networks : Network 0 - 810372D2 (very strong) Choice : 3 Enter Network ID to attach to : 810372D2 Choice : 5 Starting Micronet traffic scanning. Network ID : 0x810372D2 810372D2 810372D2 01 09 00 9A 23 23 -- 81 03 72 D2 17 03 12 34 58 1E 03 12 34 57 1F 03 12 34 56 1D 00 00 19 (-67, -7512) Network ID : 0x810372D2 810372D2 810372D2 01 09 00 9A 23 23 -- 81 03 72 D2 17 03 12 34 58 1E 03 12 34 57 1F 03 12 34 56 1D 00 00 19 (-67, -7512) Note that the number of devices seems quite variable… I have seen values from 3 down to 0, but there are only two devices on test here - the MN100-2 display and the MicronetToNMEA Teensy. See below for the Boardconfig file I am using. Note that I have changed /***************************************************************************
*/ #ifndef BOARDCONFIG_H_ // // // Select EU (868MHz) or not-EU (915MHz) Micronet frequency // Selects on which I2C bus is connected compass as per Wiring library definition // CC1101/SPI pins // NMEA GNSS UART pins // USB UART params // Wired UART params // The console to use for menu and NMEA output // Defines which data comes from which link // Navigation softwares can send a wrong RMB sentence and invert "FROM" and "TO" fields // In case your displays would have difficulties to receive data from the Tacktick wind // In case your Micronet system would not have SPD data (speed on water), you can set this // Define which compass axis will be compared to magnetic north // // #endif /* BOARDCONFIG_H_ */ I would be really grateful if you could have a look at this and maybe suggest what else I could try. Happy New Year, Nick |
Beta Was this translation helpful? Give feedback.
Apologies - this is now working fine. I did not realise that I had another process still running that was in contention for the port. I stopped it and the tio console to MicronettoNMEA seems to be working without any obvious data errors. I need to investigate the port speed settings a bit more as well. Thanks for your patience!