chicken

Members
  • Content count

    882
  • Joined

  • Last visited

  • Days Won

    78

chicken last won the day on August 3

chicken had the most liked content!

1 Follower

About chicken

  • Rank
    Level 4

Profile Information

  • Gender
    Not Telling
  • Location
    Redmond, WA
  • Github
    https://github.com/astuder
  1. Yes, message type 24 is supported. dAISy itself is not really aware of the AIS message contents. It will forward all valid AIS messages it receives. You may see fewer Class B messages than expected because: Class B transponders are much weaker than Class A, and therefore more prone to noise interference. Especially for long messages like static data. Class B messages are typically sent less frequently than Class A
  2. Happy to hear that, and thank you for the review on Tindie! I had to lookup how a Jon boat looks like With that low height, I'm surprised of the 7 miles range.
  3. Here's something new in the "I would like to play with that" category: A pico-projector in the form factor of a BeagleBone Black cape. At $99, the price isn't too bad either. http://www.ti.com/tool/dlpdlcr2000evm#0
  4. @nazmibojan your radio IC may be toast by now, so you may have to replace it. @longjohn119 thank you for the detailed report. My own knowledge about antennas is very basic. It's definitely much noisier around here in suburban Seattle. Also always interested how the receivers compare to SDRs, as basically it's a very specialized SDR. For a fairer comparison, you could try to add a bandpass filter in front of the SDRs. My 1-channel dAISy has a discrete LC filter built from SMT components, and it holds up surprisingly well to the SAW filter used on other models. In real world tests the advantage of the SAW was maybe 10% more messages. An external filtered preamp can help. I observed better range when adding this one in front of the HAT: https://store.uputronics.com/index.php?route=product/product&product_id=93 Adding a preamp on-board is still on my to-do list. I did early experiments which resulted in worse reception. However by now I know that the small dAISy is limited by noise from the USB side. I may give it a try with the HAT, which despite the integrated splitter performs as good as the single-channel dAISy, i.e. the design likely has a lower noise floor.
  5. I usually have the check for the CCA condition turned off as well. It only did make sense for single-channel receivers where RSSI level can be used for more intelligent channel hopping (didn't make much of a difference). I still suspect noise to be your main issue.
  6. Excessive power would be my guess if the receiver doesn't work anymore. The radio IC is only rated to an absolute max of 10 dBm, equivalent to 10mW. You can somewhat protect the radio with two parallel PIN diodes from RF to ground. One with cathode to GND and the other the opposite way. This clamps the signal to a maximum of less than +/- 0.7V, the equivalent of 10dBm. Though not sure how long that would help when directly connecting the receiver to an AIS transponder.
  7. Hi Rian, Is this repeatable? I.e., when you reboot dAISy it works again for a few minutes?
  8. Regarding your range problem: I program the firmware on my HATs with the debugger on the MSP430F5529 launchpad. If I don't power cycle (unplug and reconnect USB) after programming and before testing, I see elevated noise levels. I don't know the exact reason, but suspect that the JTAG traffic on USB introduces noise. Maybe there's a similar issue with the Discovery boards.
  9. Hmm, it's a while since I looked at it in detail. Channel spacing is 50KHz. If I remember correctly, bandpass was set to 20 or 15KHz. I stay away from building a transponder as there's a real risk of disrupting AIS traffic if done wrong. But if you want to go down that avenue, check out this project: https://github.com/peterantypas/ais_transponder
  10. I apologize for the slow response. Besides configuration, severely limited range can be a noise issue. You may introduce noise to the radios with the wires connecting over to the STM32. The radio_config.h for the Si4362 should be a good starting point as the EzRadioPRO chips are compatible. You can generate the radio_config files for the Si4467 with the WDS tool from Silabs: https://www.silabs.com/products/development-tools/software/wireless-development-suite Seems like they changed the file format since the last time I used it. The attached project file can be loaded with the latest version of WDS. I also attached a radio_config.h for the Si4467 that I created with this project file. I haven't tested the results though. WDS3211_si4362_revb1_direct_rx.xml radio_config_Si4467.h
  11. Hi John, Quite an impressive setup you have here. I will have to dig through your blog when I have more time. As for your questions: You are correct, the HAT can be run standalone and connected to a PC with a FTDI cable. You also can power the HAT over USB by connecting the respective wire to a 5V pad on the HAT. Serial 1 duplicates the connection that goes to the Raspberry Pi and you can connect it to any other "host" device, including an Arduino. The baud rate of Serial 1 is fixed to 38400 baud. And you are also correct regarding the I2C header. It's a straight breakout of the Pi's I2C port, without any connections to the rest of the HAT. I expected that some people want to hook up sensors, as this seems to be supported by projects like OpenPlotter. Regards, Adrian
  12. Look at the pinout in the datasheet. With the G2553, TAxCLK is only available on P1.0. I compiled a table for a few MSP430s for my CounterLib here: https://github.com/astuder/CounterLib-Energia/blob/master/README.md
  13. Good progress and tidy prototyping. Interesting observation about the beam being too narrow. I wouldn't have expected that problem with bare LEDs. Angling will be tricky without visual verification.
  14. That's a nice mock-up. Took me a while to realize that the keypad and display just sit on top of a tin box.
  15. Hi Jens, The breakout while primitive will work as well as the Si446x modules from Ebay/AliExpress. Both will get you started if in line of sight of AIS targets. But I should publish the BoosterPack sometime and update the Github project accordingly. The bandpass filter increases the number of messages received. Range can be better or slightly worse depending on your RF environment. The Si4467 does perform better than the older gen chips (e.g. Si4362-B1B). In real world scenarios the difference can be minor to significant, depending on how marginal AIS reception is. I recently started toying with the EFM32 MCUs. I hope to create a small, inexpensive and easy to integrate AIS module. I really like the dev environment and peripheral libraries. Too early yet to assess RF performance compared to the standalone radios. Regards, Adrian