[dormani]

I am having trouble setting up CumulusMX and WeatherDuino via a Raspberry PI. I have CumulusMX running on the Raspberry using Mono.
Unfortunately Cumulus is not displaying any results when connected via usb to the receiver. Actually when I connect to the receiver Weatherduino freezes. I also have a Scientific Oregon WMR200 unit and in a similar situation with this with no data being displayed.
It seems that the issue related to setup of the usb ports. Details of ports listed below. Device 009 I believe is the Arduino. I know little/nothing about Linux. Any assistance would be appreciated.

Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 009: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 005: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 006: ID 413c:1002 Dell Computer Corp. Keyboard Hub
Bus 001 Device 007: ID 413c:2002 Dell Computer Corp. SK-8125 Keyboard

[werk_ag]

Hello, dormani

Normally the Arduino USB port in the raspberry is /dev/ttyUBS0
In the terminal window, you can issue this command to make sure the device exists:
ls -l /dev/ttyUSB*

Try to add or change this lines in your Cumumus.ini file:

Code:

[Station]
Type=0
Model=WeatherDuinoPro2
Port=/dev/ttyUSB0
UseDavisLoop2=0

Also don't forget to keep the WeatherDuino Pro2 VP1 switch in close position, when it is connected by USB to the Raspberry (or PC)

Nice to hear from you.
Regards

[dormani]

Hi Caneira

Unfortunately still not receiving any data when I run CumulusMX. Confirmed that VP1 is closed. When I connect the USB cable to WeatherDuino the receiver stops re transmitting.

I ran the terminal command to confirm that the device is there. No other USB were attached apart from connection to receiver. Result was;

pi@raspberrypi ~ $ ls -l /dev/ttyUSB*
crw-rw---T 1 root dialout 188, 0 Sep 20 11:10 /dev/ttyUSB0


Made the changes to the CumulusMX.ini file that were suggested. Error highlighted below when starting CumulusMX.

pi@raspberrypi ~/CumulusMX $ mono CumulusMX.exe
Current culture: English (United Kingdom)
Serial: 74FECEABEB2DA94ECB5EBA0CD11A7137
Cumulus MX v.3.0.0 build 3030
This is pre-release beta software
Today.ini = data/today.ini
Last update=2015-09-20T11:27:28
Unable to connect to station
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
20/09/2015 11:27:29
Type Ctrl-C to terminate

I have a Synology NAS which unfortunately can not use Mono due to chip constraints, hence reliance on Raspberry to FTP to the NAS which runs 24/7 for my weather station to go live. I don't want a PC running to do FTP.

So close yet so far.

Great project. I have learned heaps putting all this together. Thank you so much.

Best regards
Ian

Cumulus.txt Size: 15,36 KB  Downloads: 306

Hello, dormani

Normally the Arduino USB port in the raspberry is /dev/ttyUBS0
In the terminal window, you can issue this command to make sure the device exists:
ls -l /dev/ttyUSB*

Try to add or change this lines in your Cumumus.ini file:

Code:

[Station]
Type=0
Model=WeatherDuinoPro2
Port=/dev/ttyUSB0
UseDavisLoop2=0

Also don't forget to keep the WeatherDuino Pro2 VP1 switch in close position, when it is connected by USB to the Raspberry (or PC)

Nice to hear from you.
Regards

[werk_ag]

Actually when I connect to the receiver Weatherduino freezes.

Unfortunately still not receiving any data when I run CumulusMX. Confirmed that VP1 is closed. When I connect the USB cable to WeatherDuino the receiver stops re transmitting.

Hi dormani

We should concentrate in this issue. If the RX units freezes, it will not be able to communicate.

It freezes only when you connect it to the PI, or it also freezes when you connect it to your PC?

Some time ago, one user (vk2kzo) has reported a similar problem, and why it happens remains a mystery. He has sent their RX board back to me, and I sent him a fully tested RX board. The result: The board he sent to me is working perfectly, and the one I sent to him, also freezes as soon as he connects it by USB.

Edited 20-09-2015: Regarding the info above, today I received an PM from vk2kzo tell me that their RX unit is now working perfectely.

I hope that is not what is happening with you. If possible, test the RX unit with different PC's, and with different power supplies, check if it freezes or when it freezes, and please report back.
My suspect is that this issue is somewhat related to the power supplies, but so far I've never been able to reproduce this behaviour.

In your Cumulus.ini, you should also change the ComportName

[Station]
Type=0
Model=WeatherDuinoPro2
Port=/dev/ttyUSB0
UseDavisLoop2=0
ComportName=/dev/ttyUSB0

[dormani]

I am now up and running.

Firstly the bit I was missing was defining the Com port which I changed after your post. This allowed the station to connect to the pi. The second piece, data not being received/processed when connected via usb took a bit more time to clear up. After trying different power options, changing cables and trying different arduino modules to no affect, I stumbled over the issue. I was about to give up when I decided to move the unit a little closer to the tx unit (500mm). Transmission LED flashed immediately and LCD data changed. It appears that the unit must have been on the boundries of reliable reception. It was ok without usb but adding the cable introduced some hash that looks to have affected receipt/process of the transmitted signal.

Thanks for your help, once again. I hope to send through a url shortly linking my station to the outside world.

Rgds
Ian

Actually when I connect to the receiver Weatherduino freezes.

Unfortunately still not receiving any data when I run CumulusMX. Confirmed that VP1 is closed. When I connect the USB cable to WeatherDuino the receiver stops re transmitting.

Hi dormani

We should concentrate in this issue. If the RX units freezes, it will not be able to communicate.

It freezes only when you connect it to the PI, or it also freezes when you connect it to your PC?

Some time ago, one user (vk2kzo) has reported a similar problem, and why it happens remains a mystery. He has sent their RX board back to me, and I sent him a fully tested RX board. The result: The board he sent to me is working perfectly, and the one I sent to him, also freezes as soon as he connects it by USB.

Edited 20-09-2015: Regarding the info above, today I received an PM from vk2kzo tell me that their RX unit is now working perfectely.

I hope that is not what is happening with you. If possible, test the RX unit with different PC's, and with different power supplies, check if it freezes or when it freezes, and please report back.
My suspect is that this issue is somewhat related to the power supplies, but so far I've never been able to reproduce this behaviour.

In your Cumulus.ini, you should also change the ComportName

[Station]
Type=0
Model=WeatherDuinoPro2
Port=/dev/ttyUSB0
UseDavisLoop2=0
ComportName=/dev/ttyUSB0

[werk_ag]

Hi, Ian

I'm really glad that you have managed to put the system to work.
Your efforts may have given some light about those strange freezes.

After trying different power options, changing cables and trying different arduino modules to no affect, I stumbled over the issue. I was about to give up when I decided to move the unit a little closer to the tx unit (500mm). Transmission LED flashed immediately and LCD data changed. It appears that the unit must have been on the boundries of reliable reception. It was ok without usb but adding the cable introduced some hash that looks to have affected receipt/process of the transmitted signal.

Your experience, has some similarities with what vk2kzo has reported to me. For him, putting the two units away from each other, also solved the problem.
To be honest I never tested an RX unit working very close to a TX unit, I always put them at least 10 meters away from each other. The TX unit is very powerful, it's possible that when they are very close, the USB cable acts like an antenna, and somehow causes a freeze in the RX.
As soon as I can, I will try to recreate this condition.
Thank you very much for you persistence, you may have helped a lot with this strange freeze problem.

Apparently, I think we can conclude that is best don't try to test the system, with the two units very close to each other.

I hope to send through a url shortly linking my station to the outside world.

Will be a pleasure visit the site. One more WeatherDuino Pro2 online in AU
Thank you Ian

[GreggWardNZ]

After my old Windows XP running Cumulus 1, finally gave up the ghost last week, I have tried to move across to Cumulus MX, running on a Raspberry Pi.

I have had no luck with either Cumulus MX or weewx. Cumulus MX does not even connect to the WeatherDuino:

pi@raspberrypi:/usr/local/CumulusMX $ sudo mono CumulusMX.exe
Current culture: English (New Zealand)
Serial: 74FECEABEB2DA94ECB5EBA0CD11A7137
Cumulus MX v.3.0.0 build 3038
Today.ini = data/today.ini
Last update=2016-07-17T17:39:44
Unable to connect to station
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
17/07/2016 5:40:16 PM
Type Ctrl-C to terminate

Whereas weewx comes up with the following error:

Traceback (most recent call last):
File "/usr/bin/wee_device", line 54, in <module>
main()
File "/usr/bin/wee_device", line 51, in main
device.configure(config_dict)
File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
self.do_options(options, parser, config_dict, prompt)
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1830, in do_options
self.show_info(station)
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1992, in show_info
Outside Humidity: %(outHumid)+.0f%%""" % calibration_dict
TypeError: format requires a mapping

I have attached logs for both of these.

I have looked through the forum and can see similar reports to what I am seeing, but they seem to be around issues with the RTC module that was using a different address i.e. 0x56 as opposed to 0x57. My RTC uses 0x57, as per the i2c_scanner program that I ran on the Rx unit.

Also my Nano has FTDI chipset on it:

Bus 001 Device 005: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have also upgraded my WeatherDuino Tx and Rx units to use the latest v2.0 software, but I still cannot get it to connect.

Any help with this would be much appreciated.

Thanks


Gregg

[hornychz]

After my old Windows XP running Cumulus 1, finally gave up the ghost last week, I have tried to move across to Cumulus MX, running on a Raspberry Pi.

I have had no luck with either Cumulus MX or weewx. Cumulus MX does not even connect to the WeatherDuino:
Gregg

Hi Gregg,

Look if you have the special device in your Raspbian ttyUSB0. You can find it in the folder /dev:



I had had this problem too until Werk_AG helped me. From this time I have to have USB hub with its own power source between Raspberry Pi and RX unit. This problem is because there is only a small power to USB port from Raspberry.

Good luck

[werk_ag]

I have also upgraded my WeatherDuino Tx and Rx units to use the latest v2.0 software, but I still cannot get it to connect.

Any help with this would be much appreciated.

Please check / try this:

- Check if after having programed your RX unit, you have put the VP1 switch at close position, otherwise the unit always reboot as soon as you try to start Cumulus (1 or MX)

- Check if your RX unit is powered by the external power supply (A powered USB hub is not required)

- In the PI terminal window:
Do a "ls /dev/tty*", with the RX unit unplugged. Then plug the RX unit in and repeat the ls command. The difference in the two lists should be your device. Usually shows up as ttyUSB0

- Edit Cumulus.ini file and check the com port name in use. Usually it is: ComportName=/dev/ttyUSB0

- Revise all [Station] section in Cumulus.ini, and check if the above statement is not duplicate somewhere.

[GreggWardNZ]

After my old Windows XP running Cumulus 1, finally gave up the ghost last week, I have tried to move across to Cumulus MX, running on a Raspberry Pi.

I have had no luck with either Cumulus MX or weewx. Cumulus MX does not even connect to the WeatherDuino:
Gregg

Hi Gregg,

Look if you have the special device in your Raspbian ttyUSB0. You can find it in the folder /dev:



I had had this problem too until Werk_AG helped me. From this time I have to have USB hub with its own power source between Raspberry Pi and RX unit. This problem is because there is only a small power to USB port from Raspberry.

Good luck

Thanks hornychz, but my Rx unit is powered by an external power supply.

---

I have also upgraded my WeatherDuino Tx and Rx units to use the latest v2.0 software, but I still cannot get it to connect.

Any help with this would be much appreciated.

Please check / try this:

- Check if after having programed your RX unit, you have put the VP1 switch at close position, otherwise the unit always reboot as soon as you try to start Cumulus (1 or MX)

- Check if your RX unit is powered by the external power supply (A powered USB hub is not required)

- In the PI terminal window:
Do a "ls /dev/tty*", with the RX unit unplugged. Then plug the RX unit in and repeat the ls command. The difference in the two lists should be your device. Usually shows up as ttyUSB0

- Edit Cumulus.ini file and check the com port name in use. Usually it is: ComportName=/dev/ttyUSB0

- Revise all [Station] section in Cumulus.ini, and check if the above statement is not duplicate somewhere.

Thanks Werk_AG for the reply.

The VP1 switch is closed, the Rx unit is being run off an external power supply, the port name in use is /dev/ttyUSB0, which is what I had updated it to in my Cumulus.ini. One thing I cannot confirm, until I get home, is whether the "ComportName=/dev/ttyUSB0" line is duplicated in the Cumulus.ini file. Are you saying that is shouldn't be duplicated in there?