Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transfer PLC failed #3

Open
Felipeasg opened this issue Apr 6, 2018 · 4 comments
Open

Transfer PLC failed #3

Felipeasg opened this issue Apr 6, 2018 · 4 comments

Comments

@Felipeasg
Copy link

How is the correct way to transfer application to the PLC?

After I have download the YAPLC/IDE beremiz matiec in the same folder, put the src of RTE in the home directory and set de PATH with arm-gcc I can build the project in the beremiz using the target - yaplc.

I also built and tested the stm32flash and put it in the same folder of the beremiz ide.

Therefore I can't deploy the application in the plc.

The procedure that I followed after build was:

  • Click in the Connect to the target PLC ( This open an connection with PYRO)
  • Click in Transfer PLC

but I got this error:

Transfer failed
PLCobject : Traceback (most recent call last):
File "/home/felipe/tests/beremiz/runtime/PLCObject.py", line 433, in NewPLC
'wb').write(data)
TypeError: argument 1 must be string or buffer, not list

I opened the file PLCObject.py in the line 433 and print the argument 1 that is:

['/home/felipe/nucleron/IDE/yaplctargets/../../stm32flash/stm32flash', '-w', u'/home/felipe/yaplcide-projects/test1/build/test1.elf.hex', '-v', '-g', '0x0', '-S', '0x08008000', '%(serial_port)s']

@nucleron
Copy link
Owner

nucleron commented Apr 6, 2018

The connector should be YAPLC, Not PYRO.

Try YAPLC:///dev/ttyUSB0 instead.

@Felipeasg
Copy link
Author

Great this configuration works fine. I read this later in the nucleron manual.

Why when I using QX1.0 I receive critical error but this option to use this pin is available in yaplcconfig?

@nucleron
Copy link
Owner

nucleron commented Apr 9, 2018

This error means that you should use QX1.x where x may be 1,2,3,4.

F4 board was a prototype, and we have changed IO ennumeration later, there is also a copy-paste mistake in yaplc target description.

I think I'll push a commit, fixing it.

@nucleron
Copy link
Owner

Dear @Felipeasg, can I close the issue or you need some help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants