I was using netPI CORE 3 , I can access to control panel all settings but now I am not able to login into Docker
It shows as attached." session has expired ",
I restarted Docker service again, but same issue.
I m trying with edge gateway Connect for image " hilschernetpi/netpi-codesys-basis"
Container running successfuly.
I am using Codesys version 3.5.14.0 .Then I upgraded to Codesys control rasoberry PI package & tryinng to start runtime , but when I cllick on " install "it shows me error ; as No connection could be made to target. I have connected to fixed IP to Connect 192.168.253.1
in June 2019 we started a Node-RED container project that is embedding all Node-RED nodes (invididually containerized before) we ever have developed and published for netPI.
From today we abandon all those individual containers and announce the immediate availability of the single Node-RED container for a better user-friendliness. Consider to load the correct tag depending on your netPI model in use.
The following container projects are no more published and maintained on Docker Hub while their source code remains on GitHub:
Posted by: Armin@netPI - September-15th-2019, 10:32 AM - Forum: News
- No Replies
Wanna control a netPI desktop from remote over the internet?
No problem since the latest release of netPI's Desktop container featuring AnyDesk.
All you need to do is to install AnyDesk on your remote machine, enter the ID shown on netPI's desktop and the screen is right there.
For private and non-commercial use AnyDesk is for free. With a license for just 16,99€/month (september 2019) you can logon to an unlimited number of devices.
Products like TeamViewer in comparison would cost you 57,90€/month (september 2019) for the very same offer while REALVNC is about 36€/year (september 2019) for a single device.
Regading prices and license models pls visit the 3rd parties' websites in any case.
What HAT (Hardware Attached on Top) modules are for the Raspberry Pi the NPIX modules are for netPI. They are add-on boards extending basic devices with physical hardware to add more connectivity to them.
HAT modules are attached onto RPi3B 40W GPIO headers whereas NPIX module are shifted into a slot at netPI's bottom. The good thing is that NPIXs' connecting host signals (not all supported) are the same as those known from HAT. So in the end only the modules' form factor is different. This means that the official HAT introduction on Raspberry HATs applies for NPIX as well.
There is a set of Hilscher netPI NPIX extension modules already released. The manual for those can be obtained from the download section here.
But how about designing own NPIX modules?
For designing own NPIX modules you should consider the following questions:
Will I be using the standard netPI with preinstalled software or do I use a netPI version without SD card for using my own system software?
Reason for this question: An NPIX respectively HAT module has an EEPROM needed for automatic Linux onboarding using overlay/device-tree techniques. The content of the EEPROM must match to the used OS. If you are using the original Raspbian system software the HAT's git hub project applies to compile your own EEPROM file. If you are using the standard netPI only Hilscher is able to provide you an EEPROM file based on the settings you need to tell us.
Is it possible for me to design an NPIX module that reuses one of the existing mounting brackets or do I need a new bracket with a new front?
Reason for this question: NPIX modules need brackets for proper mounting. For Hilscher's NPIX we have a set of brackets already in stock ready to be offered to you for sale at a price of 7EUR/piece at 100pcs. The following brackets are available through us
In any case it is possible to receive our brackets directly from our manufacturer in Taiwan. This will lower the price for you. In such case we would inform the manufacturer for your subscription of an order permission for those.
For new brackets it is possible to deal with the manufacturer directly. In this case Hilscher is in the loop no more and delivers best price ratio. The manufacturer just needs a drawing of the new bracket's front and he will provide you an offer. Usually he will not charge you with an initial tooling fee until it is only the
bracket's front that is different to existing brackets.
Will all signals provided by the NPIX mPCIe connector cover my NPIX hardware setup in mind?
Reason for this question: The standard 40W PIN header of RPi3B provides a lot of signals and features the design of full featured HAT module. On the NPIX connector a subset of all those singals is available. On netPI some are already in use like the SPI0 for the netX industrial network controller so it doesn't make sense to offer them in NPIX. So study the NPIX documentation and the connector's pinout well before starting a design.
Have I evaluated my design in mind with a mock-up using an NPIX-EVA evaluation board before?
Reason for this question: We offer a board that routes the inner NPIX mPCIe connector signals on a pin header. This allows you to make a design study with ease and avoids unwanted surprises if you have started directly with the PCBA design and are recognizing them with the first prototypes.
I have a docker container with a Python application that connects to a USB (infrared) camera.
The docker container runs fine on the Raspberry Pi 3 B, but not on the netPI.
On the netPI, additionally to running in privileged mode, I have added following devices:
/dev/gpiomem (for digital IO),
/dev/bus (for usb; I also tried with just /dev/bus/usb),
/dev/video0, and
/dev/hidraw0.
The camera library complains about data corruption and "select error". Since, the problem does not appear on the Raspberry Pi and happens inside code I do not own, I see no way how to debug this.
Any idea what other docker container configuration could be missing? Or any ideas on how to investigate this?
I have a docker that runs a Python application which uses GPIOs (via the Python RPi.GPIO library).
This docker runs fine on the Raspberry Pi 3B, but not on the netPI. I get:
Code:
RuntimeError: No access to /dev/mem. Try running as root!
Further information:
- I do start the docker container with the `--priviliged` option.
- I have not yet attached a DI DO extension the netPI. I assume the module is "just" extending the GPIOs to the outside.
- On the Raspberry Pi, I don't use portainer.
- I've upgraded the firmware of the netPI to the latest version on September 5.
Are there any differences between the netPI and Raspberry Pi concerning the GPIOs or am I doing something wrong?
I'm trying to test a Ethernet IP communication with netPI on NodeRED.
I managed to deploy NodeRed on docker (it needed upgrade, so I have firmware version V1.2.0.0). However, when I try to configure the Fieldbus node, I can choose the EIP adapter, but I cannot enter the configurator. Web browser is trying to open new tab (https://DeviceIP:9000/webConfigurator/fieldbus?Config_Filename=Hil~cifX0~Ch_2~CC_5~PC_10.json) and then halts with ERR_CONNECTION_CLOSED (chrome).
Is there something missing in the nodeRED package?NIOT-E-NPI3-51-EN-RE | V1.2.0.0
