Another approach is to configure 8 radio channels in the Multitech gateway rather than the default activated ones ch0 and ch1.
↧
Reply To: RN2483 can't join to Conduit
↧
Reply To: RN2483 can't join to Conduit
Hi Lorawan2016,
Thank you.
I am using GUI of Conduit to configured it running in public mode, there is only a “Channel plan” and “Additional Channels”, there is no option to enable and review all channels to enable or disable, how I can to do that, any suggestion?
also, I used “curl -m 5 -s “127.0.0.1/api/loraNetwork”" can get following what is Conduit Lora configured
“lora” : {
“ADRStep” : 30,
“antennaGain” : 3,
“channelPlan” : “EU868″,
“dutyCyclePeriod” : 60,
“enabled” : true,
“frequencyBand” : 868,
“frequencyEU” : 869500000,
“frequencySubBand” : 1,
“maxDatarate” : 4,
“maxTxPower” : 26,
“minDatarate” : 0,
“netID” : “000000″,
“nodeQueueSize” : 16,
“packetForwarderConfig” : “{\n\t\”SX1301_conf\”: {\n\t\t\”radio_0\”: {\n\t\t\t\”enable\”: true,\n\t\t\t\”freq\”: 867500000\n\t\t},\n\t\t\”radio_1\”: {\n\t\t\t\”enable\”: true,\n\t\t\t\”freq\”: 868500000\n\t\t},\n\t\t\”chan_multiSF_0\”: {\n\t\t\t\”enable\”: true,\n\t\t\t\”radio\”: 1,\n\t\t\t\”if\”: -400000\n\t\t},\n\t\t\”chan_multiSF_1\”: {\n\t\t\t\”enable\”: true,\n\t\t\t\”radio\”: 1,\n\t\t\t\”if\”: -200000\n\t\t},\n\t\t\”chan_multiSF_2\”: {\n\t\t\t\”enable\”: true,\n\t\t\t\”radio\”: 1,\n\t\t\t\”if\”: 0\n\t\t},\n\t\t\”chan_multiSF_3\”: {\n\t\t\t\”enable\”: false,\n\t\t\t\”radio\”: 0,\n\t\t\t\”if\”: -400000\n\t\t},\n\t\t\”chan_multiSF_4\”: {\n\t\t\t\”enable\”: false,\n\t\t\t\”radio\”: 0,\n\t\t\t\”if\”: -200000\n\t\t},\n\t\t\”chan_multiSF_5\”: {\n\t\t\t\”enable\”: false,\n\t\t\t\”radio\”: 0,\n\t\t\t\”if\”: 0\n\t\t},\n\t\t\”chan_multiSF_6\”: {\n\t\t\t\”enable\”: false,\n\t\t\t\”radio\”: 0,\n\t\t\t\”if\”: 200000\n\t\t},\n\t\t\”chan_multiSF_7\”: {\n\t\t\t\”enable\”: false,\n\t\t\t\”radio\”: 0,\n\t\t\t\”if\”: 400000\n\t\t},\n\t\t\”chan_Lora_std\”: {\n\t\t\t\”enable\”: true,\n\t\t\t\”radio\”: 1,\n\t\t\t\”if\”: -200000,\n\t\t\t\”bandwidth\”: 250000,\n\t\t\t\”spread_factor\”: 7\n\t\t},\n\t\t\”chan_FSK\”: {\n\t\t\t\”enable\”: true,\n\t\t\t\”radio\”: 1,\n\t\t\t\”if\”: 300000,\n\t\t\t\”datarate\”: 50000,\n\t\t\t\”freq_deviation\”: 25000\n\t\t}\n\t},\n\t\”gateway_conf\”: {\n\t\t\”synch_word\”: 52,\n\t\t\”forward_crc_disabled\”: false,\n\t\t\”forward_crc_error\”: true,\n\t\t\”forward_crc_valid\”: true,\n\t\t\”gateway_ID\” : \”<008000000000C4EB>\”,\n\t\t\”keepalive_interval\”: 12,\n\t\t\”push_timeout_ms\”: 600,\n\t\t\”serv_port_down\”: 1700,\n\t\t\”serv_port_up\”: 1700,\n\t\t\”server_address\”: \”eur1.iothub.ca\”,\n\t\t\”stat_interval\”: 20\n\t}\n}”,
“packetForwarderMode” : false,
“rx1DatarateOffset” : 2,
“rx2Datarate” : 12
},
↧
↧
Reply To: RN2483 can't join to Conduit
Hi Yuqian,
Check if this is the correct path to edit the file.
/var/config/lora/lora-network-server.conf
or find its location in your gateway, there should be similar one.
↧
Reply To: RN2483 can't join to Conduit
Hi Loranwan2016,
It is same what I got from “curl -m 5 -s “127.0.0.1/api/loraNetwork”” just a “frequencySubBand” in there.
also I found this link http://openlora.com/forum/viewtopic.php?t=1252, they all talking about the subBand definition.
↧
No RS-485 communication
I have installed the RS-485 DCE accessory card in AP2 slot of Multitech.
My slave device has address 2 and baud as 38400.
I ran below commands from serial debug console of Multitech to enable 485 communication:
root@mtcdt:~# mts-io-sysfs store ap2/serial-mode rs485-half
root@mtcdt:~# set-rs485 /dev/ttyAP2 1
When I am trying to communicate with the slave device from python interpreter using minimalmodbus, I am getting no communication error:
>>> inst = minimalmodbus.Instrument(‘/dev/ttyAP2′, 2, minimalmodbus.MODE_ASCII)
>>> inst.serial.baudrate = 38400
>>> hp_in_value = inst.read_register(40605, 4)
Traceback (most recent call last):
File “<stdin>”, line 1, in <module>
File “/usr/lib/python2.7/site-packages/minimalmodbus.py”, line 258, in read_register
return self._genericCommand(functioncode, registeraddress, numberOfDecimals=numberOfDecimals, signed=signed)
File “/usr/lib/python2.7/site-packages/minimalmodbus.py”, line 697, in _genericCommand
payloadFromSlave = self._performCommand(functioncode, payloadToSlave)
File “/usr/lib/python2.7/site-packages/minimalmodbus.py”, line 795, in _performCommand
response = self._communicate(request, number_of_bytes_to_read)
File “/usr/lib/python2.7/site-packages/minimalmodbus.py”, line 930, in _communicate
raise IOError(‘No communication with the instrument (no answer)’)
IOError: No communication with the instrument (no answer)
I tried swapping the communication lines on RS-485 bus but still getting same error. Any suggestions would help me to move on.
Thanks,
Prakash
↧
↧
Reply To: No RS-485 communication
Prakash,
The setup commands look correct for setting up rs485-half duplex mode on accessory card port 2.
I don’t know a lot about python minimalmodbus, but when you create the instrument object “inst” I’m assuming that you have the correct slave address. Also, when you call read_register you are asking for four decimals. Is that correct? Another note is that 40605 is a pretty high register number, is that correct?
Jeff
↧
Reply To: Problem with curl in network server startup.
Are you running mLinux or AEP? The API service is the major difference between mLinux and AEP. The API is not available on mLinux images.
-
This reply was modified 19 hours, 40 minutes ago by
Peter Ferland.
↧
Reply To: No RS-485 communication
Hi Prakash,
Can you try putting the set-rs485 call inside the python script after you open the tty like this:
import minimalmodbus
import os
instrument = minimalmodbus.Instrument('/dev/ttyAP2', 1)
os.system('set-rs485 /dev/ttyAP2 1')
reading = instrument.read_register(40605, 4)
↧
Reply To: Modbus TCP with node-red
Thank you,
I start to implement my solution.
About set up, you said :
pip install pyModbusTCP
It’s only a modbus client, so i replaced pyModbusTCP package with pymodbus package because i need to implement a modbus server on Conduit.
Do you think there will be a problem running if I install the pymodbus package ? Can the Conduit gateway support a modbus server ?
↧
↧
Reply To: Modbus TCP with node-red
Michael when you install using npm it takes the latest npm package.
node-red-contrib-modbus has been completely re-written and has a number of discrepancies which means it won’t run on AEP.
I think I used version 0.7.0 which only does modbus TCP you wan’t get RTU working on AEP.
To install old npm versions use the following
npm install node-red-contrib-modbus@0.7.0
To see a list of all versions
npm view node-red-contrib-modbus versions
I have friend that is running 3 or more AEP’s using node-red-contrib-modbus I will ask what version they got working.
Lawrence
↧
Reply To: Modbus TCP with node-red
pymodbus can be installed on the conduit however its not quite as simple as using minimalmodbus or pymodbustcp because it depends on the compiled python extension “twisted” for threading.
An ipk is not provided on the default package feed so you’ll have to cross compile it yourself using the bitbake environment documented on this page: http://www.multitech.net/developer/software/mlinux/mlinux-building-images/building-a-custom-linux-image/
The recipe name is python-twisted. You do not need to build an image, you can scp over the python-twisted-core ipk to the Conduit and install using opkg. After that you can use pip to install pymodbus.
↧
Reply To: Modbus TCP with node-red
@Lawrence
I checked the following site : https://libraries.io/npm/node-red-contrib-modbus/0.4.8
I don’t know if I can trust it, but from the version 0.4.8 the nodejs requirement was 0.13.4.
Comments above show that we have limitations, because our nodejs version of Conduit gateway is 0.11.1 and can’t be updated :
However, it is not possible to upgrade nodejs beyond 0.10.x due to the Conduit being restricted to the armV5tej instruction set.
In your case, do you remember the version of nodejs and npm that you have used before ? It is nice of you to ask your friends about their versions.
@Peter
I tried to install pymodbus two hours ago. I had some compilation errors but the package pymodbus seems to run.
With your advice i’m going to reinstall pymodbus
↧
Reply To: Modbus TCP with node-red
@Lawrence
Sorry, i made a mistake:
because our nodejs version of Conduit gateway is 0.11.1 and can’t be updated
it’s nodejs 0.10.40 not 0.11.1. The 0.11.1 is the version of node-red. Do you know the nodejs requirement for node-red@0.14.1 (the required version for node-modbus package)
-
This reply was modified 15 hours, 55 minutes ago by
Michael Hance.
↧
↧
Reply To: Modbus TCP with node-red
The limiting factor is that google V8 dropped support for armv5 after V8 version 3.17. This means that versions of node.js that require later versions of V8 cannot be compiled for the Conduit.
-
This reply was modified 15 hours, 38 minutes ago by
Peter Ferland.
↧
Reply To: RN2483 can't join to Conduit
really appreciate if some MultiTech tech guys can help out 
, as this is very important for us, thank you.
↧
Reply To: RN2483 can't join to Conduit
Hi Yuqian,
I am trying to investigate this problem but I need some information from you.
Do you know which Microchip firmware version in your RN2483 module? … you can use Tera term and the version will be printed on the screen upon starting the module.
Have you investigated if it works with earlier firmware versions of the Multi-tech gateway?
↧
Reply To: RN2483 can't join to Conduit
I am quite sure that last year I connected RN2483 with MultiTech gateway and it worked without any problem but I’m unsure from which firmware version this problem has been introduced.
Another approach is to investigate this problem if you have another LoRaWAN module from ARM mBed i.e. SX1272 or similar one from Murata and try to connect it to the same Multitech gateway and check if it works. If it works then it’s compatibility problem and Microchip or MultiTech has to find a solution for it.
I don’t know why there’s no official response on this track yet !!
↧
↧
Reply To: RN2483 can't join to Conduit
Hi Lorawan2016,
Thanks for your suggestion, i am using the 1.0.1 of RN2483 firmware, Conduit AEP 1.3.3.
No idea why there is no MultiTech guy in here 
↧
Reply To: Multitech Conduit Gateway 8 Radio Channels Configuration
Hello,
Thanks again Mike.
Though this is not exactly answering my questions, I appreciate the time you spent answering my question. Simply, I can’t find the 8 radio channel configurations in any of the given links and in the TTN link there’s mLinux not AEP configuration.
In Conduit AEP configuration as packet forwarder, is the MQTT client/broker needs to be configured and enabled so that the packets forward to the server in two directions?…. I am asking this because I have AWS MQTT to subscribe/publish from/to the gateway.
Do you have any idea?
↧
Reply To: RN2483 can't join to Conduit
Hi Yuqian,
Since the 1.0.1 is old firmware version, just for testing, try to downgrade the firmware on your gateway to either
Firmware version 1.0.33 (Released 09/25/2015)
OR
Firmware version 1.1.2 (Released 02/02/2016)
You can do this easily by registering your gateway in MultiTech DeviceHQ https://www.devicehq.com
Before doing the downgrade it’s important to save your configuration and then let DeviceHQ do the job for you after scheduling the downgrade to be done on next restart of the gateway. It will take a couple of hours or less depending on your internet connection.
Then test it with RN2483 firmware version 1.0.1 to check if it works better.
Later on, you may upgrade your gateway easily to any firmware version as all of them are available on DeviceHQ.
Another alternative is to do the firmware downgrade/upgrade for your gateway manually if you have the firmware file available on your system.
↧