RBLHG-5HPnD-XL-US Not updating .bin file

30 posts / 0 new

Sat, 09/19/2020 - 10:02

KE0BCQ

Hey all,

Not sure if this is the correct forum location about this issue but here it goes. I am currently working on getting two MikroTik RBLHG-5HPnD-XL-US up and running. I am using the install instructions from https://www.arednmesh.org/content/installation-instructions-mikrotik-devices via Linux and I get to step 11 uploading the .bin file and rebooting. From what I can tell it does not write the file to the flash it just reboots the hardware. I know this because it changes the IP from 192.168.1.1 back to 192.168.88.1 after the reboot. It does say it is unsupported hardware when i do access http://192.168.1.1:8080/cgi-bin/admin. I checked the hardware is saying it is RBLHG-5HPnD-XL-US for the ID on the back and is listed on the supported hardware page https://www.arednmesh.org/content/supported-platform-matrix. Any ideas on what I could be doing wrong or any tips?

node: NOCALL-74-110-225

model: MikroTik RouterBOARD RBLHG-5HPnD

!!!! UNSUPPORTED DEVICE !!!!

boardid: MikroTik RouterBOARD RBLHG-5HPnD

Device has not been tested. Please file a ticket with your experiences.

br-lan 48:8F:5A:4B:6E:E1

eth0 48:8F:5A:4B:6E:E1

eth0.1 48:8F:5A:4B:6E:E1

eth0.2 48:8F:5A:4B:6E:E1

tunl0 00-00-00-00-00-00-00-44-00-00-00-00-00-00-00-00

wlan0 48:8F:5A:4A:6E:E1

/proc/cpuinfo

system type : Atheros AR9344 rev 3

machine : MikroTik RouterBOARD RBLHG-5HPnD

processor : 0

cpu model : MIPS 74Kc V4.12

BogoMIPS : 299.82

wait instruction : yes

microsecond timers : yes

tlb_entries : 32

extra interrupt vector : yes

hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]

isa : mips1 mips2 mips32r1 mips32r2

ASEs implemented : mips16 dsp dsp2

Options implemented : tlb 4kex 4k_cache prefetch mcheck ejtag llsc dc_aliases perf_cntr_intr_bit nan_legacy nan_2008 perf

shadow register sets : 1

kscratch registers : 0

package : 0

core : 0

VCED exceptions : not available

VCEI exceptions : not available

nvram

hsmmmesh.settings=settings

hsmmmesh.settings.wifimac='48:8f:5a:4a:6e:e1'

hsmmmesh.settings.mac2='74.110.225'

hsmmmesh.settings.node='NOCALL-74-110-225'

hsmmmesh.settings.dtdmac='74.110.224'

Thanks,
Adam
KE0BCQ Iowa

Sat, 09/19/2020 - 22:54

AE6XE

KE0BCQ, Mikrotik keeps

KE0BCQ, Mikrotik keeps changing the string used to recognize the specific model. It appears this has occurred, again:

before: "MikroTik RouterBOARD LHG 5HPnD"
after: "MikroTik RouterBOARD RBLHG-5HPnD"

AREDN knows about the following LHG 5GHz models to date:

MikroTik RouterBOARD LHG 5HPnD-XL
MikroTik RouterBOARD LHG 5HPnD
MikroTik RouterBOARD RBLHG-5nD
MikroTik RouterBOARD LHG 5nD

You would be able to install or flash the firmware with the manual command "sysupgrade -F" using the force option. However, after flashing AREDN, there will be some issues in basic setup. AREDN firmware also needs an update.

I can prepare an image to test and we'll get this in the nightly build -- will post a link to download test images shortly.

The label on the device has "XL", but it appears the model string no longer has "XL"? The error reported, not recognizing the device, ""boardid: MikroTik RouterBOARD RBLHG-5HPnD", which does not have XL in it. This is interesting as the firmware may not be able to detect or know that the antenna gain is much higher for XL--identical mother board used in 2 devices with different gains. Not an issue for AREDN, but an issue for using under part 15 unlicensed wifi -- the device with the higher antenna gain would somehow need to be restricted as the max power is lower, to stay within part 15 unlicensed compliance.

Joe AE6XE

Sat, 09/19/2020 - 23:32

KE0BCQ

Hey AE6XE,

Hey AE6XE,

I had a feeling they changed the name from reading an older post by you with someone having a similar issue. I would be interested in getting a test image and test it out from the nightly build. I also downloaded the support data but not sure what would be useful to upload. If you need anything from me just let me know. Thanks for all the help!

-Adam KE0BCQ

Sun, 09/20/2020 - 01:32

(Reply to #3) #4

AE6XE

Test these images. Be sure

Test these images. Be sure to use the .elf provided here:

https://drive.google.com/drive/folders/1PhjMYoOBv1t-_OFGC6HS3BEdDR77NWqE...

Joe AE6XE

Sun, 09/20/2020 - 15:24

(Reply to #4) #5

KE0BCQ

Hey AE6XE,

Hey AE6XE,

Thanks for the test images. I downloaded the files and changed them out. I am getting stuck now at loading the .elf image. It is showing the file was sent but I am unable to access 192.168.1.1:8080/cgi-bin/admin. I checked my cables and tested it out on my other AP and still the same issue, i am unable to ping or port scan 192.168.1.1.

Thanks,
Adam KE0BCQ

Thu, 10/01/2020 - 17:53

(Reply to #5) #6

KE0BCQ

Hey Joe AE6XE,

Hey Joe AE6XE,

So I been doing some more testing. I was able to boot into the .elf without any issues or warnings. But I think found a bigger issue I am unable to flash the .bin file hardware. I tried flashing both of my APs with the new firmware but no luck I checked to make sure i was doing everything correctly acording to the flash directions. Any ideas on what I could try next.

Thanks,
Adam KE0BCQ

Thu, 10/01/2020 - 19:45

(Reply to #6) #7

KO8V

I too have one of these new

I too have one of these new nodes that won't work. It's an LHG HP5 XL. I purchased it using the amazon link on the supported hardware page.

I tried the images at this link. I can get the ELF file to load via PXE and it no longer complains about unsupported hardware. I tried loading the BIN file via the browser, but that did not work. So I tried the sysupdate command via an SSH session. With out the force option, it would not load - again complaining that the device is unsupported. After using the force option, the node would not boot up completely. Just like with the normal nightly build.

This is what is reported by the browser: MikroTik RouterBOARD RBLHG-5HPnD.

I also popped the board out of the node. The sticker on it has tthe ID: RBLHG-5HPnD. That matches what the browser reported.

Sat, 10/03/2020 - 20:46

K6CCC

Another LHG with Untested Hardware

KI6GRC - Jon has a new LHG radio that is getting the Untested Hardware error. He has attempted the alpha code posted in post 6 of this thread with the same issue. He has attempted to join this forum, but it is apparently awaiting approval. So I am posting this for him. He sent me a support file that I am uploading with this message.

Support File Attachments:

From KI6GRC on a new LHG radio

Sun, 10/04/2020 - 10:05

(Reply to #8) #9

AE6XE

Sorry, I've not had time to

Sorry, I've not had time to look at this, but just now arrived back to QTH1. I'll have time to investigate from Monday. It appears the problem is with a firstboot script that creates /etc/board.json file. It is not correctly setting up the model.id info. If you compare this file on a working device, it may be a work around to manually edit this file to enter the correct contents, until this is resolved.

Joe AE6XE

Sun, 10/04/2020 - 11:28

(Reply to #9) #10

KI6GRC

Thanks, I'm Jon, the one

Thanks, I'm Jon, the one having the issues. Good to be here:)

Sun, 10/04/2020 - 13:47

(Reply to #10) #11

K6CCC

Welcome, Welcome, Welcome

Welcome back to QTH #1 Joe. And Jon, nice to see that you were able to get onto the forum...

Mon, 10/05/2020 - 23:23

(Reply to #11) #12

KI6GRC

What's the best way to edit

What's the best way to edit the json file? I tried to telnet into the LHG using Putty on my WiIn 10 machine, but couldn't edit the file. Honestly my command line skills are little league at best but I do have a Mac and a machine running Ubuntu if that if a better format to play on;)

Tue, 10/06/2020 - 00:02

#13

KO8V

I assume we are editing the

I assume we are editing the file after the PXE boot of the elf file and before we flash the bin image. I used ssh on port 2222 to login into the board. What I could not figure out is the value I need for model.id field. It says unknown when I open it.

i don't have a file to compare to since I don't know anyone with an XL version of the device.

Tue, 10/06/2020 - 00:16

(Reply to #13) #14

KI6GRC

OK, That makes sense. I'm

OK, That makes sense. I'm more versed in SSH than telnet.

I think the thing to do is change "Unknown" into the description that closest resembles yours.

MikroTik RouterBOARD LHG 5HPnD-XL
MikroTik RouterBOARD LHG 5HPnD
MikroTik RouterBOARD RBLHG-5nD
MikroTik RouterBOARD LHG 5nD

Mine was showing up as...
MikroTik RouterBOARD RBLHG-5HPnD
So I'm going to change "unknown" to
MikroTik RouterBOARD LHG 5HPnD

Tue, 10/06/2020 - 02:56

(Reply to #14) #15

nc8q

change 'unknown' to

LHGs:
root@NC8Q-MVHS-PP:~# cat sysinfo/board_name
rb-lhg-5hpnd
root@NC8Q-MVHS-PP:~#
root@NC8Q-M5-Kett:~# cat sysinfo/board_name
rb-lhg-5hpnd-xl
root@NC8Q-M5-Kett:~#
root@NC8Q-M5-MVHS:~# cat sysinfo/board_name
rb-lhg-5hpnd-xl
root@NC8Q-M5-MVHS:~#
root@NC8Q-MVHS-BT:~# cat sysinfo/board_name
rb-lhg-5hpnd-xl
root@NC8Q-MVHS-BT:~#

newLHG:
root@NC8Q-newLHG-38:~# cat sysinfo/board_name
unknown
root@NC8Q-newLHG-38:~#

SXTs:
root@NC8Q-PP-MVHS:~# cat sysinfo/board_name
rb-lhg-5nd
root@NC8Q-PP-MVHS:~#
root@NC8Q-PP-Yankee:~# cat sysinfo/board_name
rb-lhg-5hpnd
root@NC8Q-PP-Yankee:~#

It seems that the new LHGs and SXTs have 'RB' added to the boardid.
Unique model IDs:
MikroTik RouterBOARD LHG 5HPnD
MikroTik RouterBOARD LHG 5HPnD-XL
MikroTik RouterBOARD LHG 5nD
MikroTik RouterBOARD RBLHG-5HPnD
MikroTik RouterBOARD RBSXTsq5HPnD
MikroTik RouterBOARD SXT 5HPnD
MikroTik RouterBOARD SXTsq 5HPnD
MikroTik RouterBOARD SXTsq 5nD

Tue, 10/06/2020 - 10:48

#16

AE6XE

On an older hardware LHG XL,

On an older hardware LHG XL, the board.json file is created and looks like this:

"model": {

"id": "rb-lhg-5hpnd-xl",

"name": "MikroTik RouterBOARD LHG 5HPnD-XL"

The id is an internal openwrt designation. The same id may be used by many different models, e.g. some of the SXT and LHG have the same id. This means the mother board is the same, but the different models may have different power settings, etc.

The problem we have with this new board, is the 'name' does not have "XL" in the string. Thus, we can no longer tell if it is the small gain or larger gain antenna model. Probably not an issue as both models are "HP" or high power and all the settings are the same anyway. the id should be "rbi-lhg-5hpnd" and the code in my test images says to make it this string. but alas something isn't right and still coming up with unknown. I may need someone with one of these devices to run some test code to see what is amiss.

Our necessary end state:

"model": {

"id": "rb-lhg-5hpnd",

"name": "MikroTik RouterBOARD RBLHG-5HPnD"

Joe

Tue, 10/06/2020 - 11:34

(Reply to #16) #17

K6CCC

Fortunately for our purposes,

Fortunately for our purposes, the antenna gain does not matter - unlike some other services where ERP is the regulated power level, not RF output. Obviously antenna gain is important, but we don't need to back off RF level to meet an ERP requirement.

Tue, 10/06/2020 - 14:03

(Reply to #17) #18

nc8q

someone with one of these devices to run some test code

Hi, Joe:

I volunteer.
I am willing to set up a tunnel to you and share the root password of a new LHG-HP5nD-XL-INTL.
I have 2 newLHG-HP5nD with the XL omitted from the 'boardid'.

Chuck

Tue, 10/06/2020 - 14:26

(Reply to #18) #19

AE6XE

Thanks Chuck. I may be able

Thanks Chuck. I may be able to resolve without direct access. I'm looking at it now and for some reason the intended code is not getting into the test images. I may have new images shortly to give another test.

Joe AE6XE

Tue, 10/06/2020 - 18:04

(Reply to #19) #20

KI6GRC

It would make sense if the

It would make sense if the 5HPnD and 5HPnD-XL have the same radios with the XL simply having the larger dish to give it more gain.

I'm going to try and play around with the json file later tonight.

Tue, 10/06/2020 - 18:14

(Reply to #20) #21

AE6XE

Try the updated images, just

Try the updated images, just posted a couple hours ago at same link, all seems to be working now. images have same name as before, so caution to not mix them up.

Joe AE6XE

Tue, 10/06/2020 - 19:31

(Reply to #21) #22

KI6GRC

The ones you posted around

The ones you posted around noon? I'll try them out when I get home. I'll delete the old ones off my computer first.

Just to double check, mine is a 5HP, non XL version.

Tue, 10/06/2020 - 15:36

#23

AE6XE

test images are updated. I

test images are updated. I fixed an issue and the code is in the images now. Please try on the LHG 5HPnD XL device. Best to do clean start with the .elf boot, then install the .bin to flash, to avoid any carry over.

https://drive.google.com/drive/folders/1PhjMYoOBv1t-_OFGC6HS3BEdDR77NWqE...

Joe AE6XE

Tue, 10/06/2020 - 17:34

(Reply to #23) #24

nc8q

identical file names>

Joe:
Those have the same file names as #4.
https://www.arednmesh.org/comment/16021#comment-16021
Trying anyway. ;-)
Did not balk on the .bin upload. :-)

Image Attachments:

Tue, 10/06/2020 - 18:04

(Reply to #24) #25

AE6XE

Everything looks good on the

Everything looks good on the basic setup page -- channel options, power selection?

Tue, 10/06/2020 - 21:55

(Reply to #25) #26

nc8q

basic setup page -- channel options, power selection?Hi, Joe:

Hi, Joe:

Yes, Channel 131<>184, 20, 10, 5 MHz bandwidth, 1 to 28 dBm.
Lookin' good in the neighborhood.

Thanks,
Chuck

Tue, 10/06/2020 - 21:56

(Reply to #26) #27

KI6GRC

I think its working...

Tue, 10/06/2020 - 23:05

(Reply to #27) #28

KO8V

I'll give them a try in the

I'll give them a try in the morning.

Joe

Wed, 10/07/2020 - 09:04

(Reply to #28) #29

KO8V

Progress

I used the new files and the load went smoothly. Good progress.

After I assigned the node a name/password and rebooted, the node pulled a DHCP address from my network (it gets 192.168.1.51 - I can see the lease in my home network router). But I can't connect to it. It doesn't respond to a ping, ssh or web browser. I probably messed up something since this is my very first AREDN node. I'll redo the process this evening after work.

But we do have progress, which is good news.

Joe

Wed, 10/07/2020 - 10:47

(Reply to #29) #30

KO8V

I'm in

OK, I'm in. The radio is doing WiFi scans correctly. Now I just need to try to connect to our mesh system here in central Virginia.

Thanks for the work.

Joe, KO8V

Amateur Radio Emergency Data Network

Menu SF

You are here

RBLHG-5HPnD-XL-US Not updating .bin file

Amateur Radio Emergency Data Network

Search form

Menu SF

You are here

RBLHG-5HPnD-XL-US Not updating .bin file