Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - rvdvoort

Pages: 1 [2]
16
mc-Studio / Re: Mc Studio chrashing on Win 10 proffesional
« on: June 30, 2016, 01:47:54 pm »
I didn't attached the first error message so here is the first one...

[ Guests cannot view attachments ]

17
mc-Studio / Mc Studio chrashing on Win 10 proffesional
« on: June 30, 2016, 01:46:03 pm »
Everytime when I start-up Mcstudio I get the error message as attached (error 1). Mcstudio than start-ups fine but when I press ok to acknowledge the first error McStudio is crashing while displaying the second error message (eeror 2).

On another win 10 laptop (home version) McStudio start-ups fine without the error messages. Contentwise the McStudio folders seem to be exactly the same. Wat is strange that the first error message is related to loading FTD2XX.DLL (in the McStudio folder I only see a file FTD2XX_NET.DLL, on both laptops).

Any explanation what is wrong?

Thx,
Rob

[ Guests cannot view attachments ]

18
That fixed it  :D

Thx,
Rob

19
I have tried the following:
First test:
1) Using a dummy User Name / Password hitting save.
2) Disconnect/connect
3) Tried if this would work --> answer No

Second test
1) Using a dummy User Name / Password hitting save.
2) Disconnect/Connect
3) Delete dummy user name/passw hit save
4) Disconnect/connect
5) Tried if this would work --> answer No

Andy other suggestions?






20
I was using the "test broker" of HiveMQ to test a simple MQTT project. Settings in Gateway via McStudio
* MQTT Broker:  broker.hivemq.com
* MQTT port:  1883

No other settings

This was all working fine with the test project and gateway sw 06-354. After upgrading the gateway sw to the latest version 06-357 (including the modules to 07-356 and the host on gateway to 07-404) nothing is being published to the broker.

Downgrading only the gateway sw to 06-354 it works again. After upgrading the gateway again to 06-357 it stops working.

Is there a need to add some other configuration settings in the gateway for the broker to get this working on 06-357 or is there something else what is wrong?

Thanks,
Rob

Pages: 1 [2]