Communication failure

benng · 2017-01-13 02:21:48

Hi there
After failed download to target, I can not connect to the target anymore, it says: "connect to Rex// admin@192.168.1.252: 43981/ failed", Error: Network communication failure (code-400).
I try to reboot the raspberry pi, still the same, the only way I can do is format the SD card, reinstall everything all again. Is there anything else I can do other then have to reinstall again? Please help.

Regards Ben

jaroslav_sobota · 2017-01-13 08:07:14

Hi Ben,
it might be your project which is causing RexCore to crash. Upon reboot, RexCore tries to start your algorithm and it immediately crashes again. That's why you cannot connect even after reboot.

Please try deleting the /rex/rexcore/exec.rex file on your Raspberry Pi. RexCore will have no project to load on startup and therefore it will not crash and you will be able to connect.

Let me know if this helps. It is a very serious problem so we will definitely investigate this into more detail.

Kind regards
Jaroslav

benng · 2017-01-14 10:00:43

Hi Jaroslav

Thank you for your advice, it all work now.

Regards Ben

Last edited by benng (2017-01-14 10:01:13)

jaroslav_sobota · 2017-01-14 15:56:48

Hi Ben, glad I could help. Is there any chance you could upload the source files of the problematic project? That would help us in hunting this bug. You can also send it to support(at)rexcontrols.com if you prefer. Thank you.

Jaroslav

benng · 2017-01-15 21:58:20

Hi Jaroslav,

Sorry for the delay reply, I re-created what I did to caused the raspberry pi to crash,
First I copied working project file I used for UnipiA, rename it to UnipiB for this project.
It had MtmDrv, RpiDrv and OwsDrv, changed all the parameters where necessary
Create a new cfg file to the MtmDrv, add all the new Modbus address.
Create a new cfg file to the OwsDrv, set local host to 127.0.0.1:4304, no ow device in the device list.
Download to project to unipiB, it crashed!
Compare both Unipis, the only difference is unipiB has no devices in the cfg file, to confirm this , I delete the crash exec.rex file, reboot the pi, and wire couple temperature sensors to the unipiB, add the tags /addresses in the cfg file. Then it all work.
In my opinion, I don't think it should be crash like this, what do you think?
Hope this report will help your investigation.

I am away at the moment, not with my pc, if you still need the files I will email to you on my return.

Regards
Ben

Last edited by benng (2017-01-16 08:14:16)

jaroslav_sobota · 2017-01-16 14:46:48

Hi Ben,
very precise and very helpful. I am able to replicate the bug. Thanks for reporting and investigating this bug!

Adding an I/O driver without any I/O signal is quite uncommon scenario, but you are absolutely right, RexCore should not crash like this.

Kind regards,
Jaroslav

REXYGEN Community Forum

Announcement

REXYGEN forum has been moved. This one is closed.
Head over to the new REXYGEN Community Forum at https://forum.rexygen.com.

Looking forward to meeting you there!

#1 2017-01-13 02:21:48