Video Tutorial Help

[Simon Dreyer]

Hi Folks, I'm new to 61499 and Holobloc, but definitely not new to control systems :-). I have downloaded the latest FBDK8 and am working my way through understanding everything. I am currently trying to get the FLASHER_TESTR running. I have a Rpi 4 as the remote device and a Win10 laptop as the CONTROL side. I have got as far as the FLASHER launching on the remote machine and the CONTROL launching on the local machine, but when I try to launch the configuration I get the TIMED OUT error. I have updated the timeout to 10 sec.

This is my command for launching the FLASHER:

java -jar device.jar FLASHER RMT_FRAME MGR_ID 192.168.102.42:61499

And the CONTROL:

c:\fbdk>java -jar device.jar CONTROL RMT_FRAME MGR_ID 192.168.102.52:61499

When I try to launch the configuration with this:

c:\fbdk>java -jar device.jar FLASHER_TESTR

I get the following error:

Exception in thread "main" fb.datatype.FBDataTypeException: UNDERFLOW

        at fb.datatype.FBDataTypeException.<clinit>(FBDataTypeException.java:40)

        at fb.rt.Device.main(Device.java:110)

When I launch the config from within the app I get the timeout error:

The network is good between the machines, I can ping either way.

Are there any video tutorials that I can watch to step through the entire process and see what I am doing wrong please?

Regards Simon

[James Christensen]

• If you are running both FLASHER and CONTROL on the same RPi, they must have the same TCPv4 address, which must be the same as the RPi's assigned TCPv4 address, which you can see by hovering over the icon for the active comms link (Ethernet or WiFi) on the taskbar. To distinguish between the two comms channels, use different socket addresses, e.g., "192.168.102.42:61499" and "192.168.102.42:61500" (I recommend the quotes around the MGR_ID values in the command line to avoid confusing the command line interpreter with the colon character). These must also be assigned to the MGR_ID inputs of the corresponding Devices in the FLASHER_TESTR System diagram.
• You must also save the modified FLASHER_TESTR diagram before attempting to run it.
• FLASHER_TESTR is a System configuration, so the command line should be "java -jar system.jar FLASHER_TESTR"
• When in doubt, consult https://www.holobloc.com/doc/fbdk3/systest.htm (accessible via the "Systems==>Testing" link sequence at https://www.holobloc.com/doc/fbdk8/howto.htm).
• One caveat: Since the underlying protocol for the TAGIN and TAGOUT blocks is UDP, it may not work on a WiFi mesh network like Google WiFi. As long as the sender and receiver are on the same router (WiFi or Ethernet), it should work. 

--
Best regards,
Jim Christensen

--
You received this message because you are subscribed to the Google Groups "FBDK" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fbdk+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fbdk/6c06a19a-37df-452e-b1fd-d1e4aadbdb26n%40googlegroups.com.

[James Christensen]

Oops, I meant "IPv4", not "TCPv4"!

--
Best regards,
Jim Christensen

[Simon Dreyer]

Thanks Jim

I managed to get it up and running fine between two RPI's :-).

So far I am pretty impressed with the system and can see a lot of potential. One thing I have not seen yet are any file management controls for loading or saving machine/plant/recipe data, do such controls exist yet?

Regards Simon

[James Christensen]

Hmm... how about a link to Google Sheets? Other ideas?

To view this discussion on the web visit https://groups.google.com/d/msgid/fbdk/269a479c-19df-420f-b22b-64fce28eb683n%40googlegroups.com.

--