It sounds like Flowcode is correctly producing the HEX file, but the programmer being used (AvrDude) and/or the hardware connection tot he device is the problem. You could try loading the HEX file using an alternative programmer. As the problem does not appear to be due to Flowcode, there is not muc...

ATS-5S18F46K22.c:37:45: error: (1504) the PIC18 extended instruction set was enabled but is not supported by this compiler I have the license installed but still cant get the PIC18F46K22 to compile. I am getting the above error. The "Extended Instruction Set" bit is set in the config word for that ...

When the pin is entered and the car and laptop pair, it unpairs for no reason. Something seems odd about this. When a Bluetooth device is paired (e.g. by a PC), that pairing is remembered. It sound like something is actively unpairing the buggy on your PC. It might be worth trying a different PC or...

By "disconnect", do you mean "unpair"? And during this process, are you trying to connect tot he specific COM port being used by the buggy?

State Diagrams work fine in PC Developer apps. But there is no wat to convert between PC and Web Developer apps.

The instructions for pairing the buggy on a Windows PC are on p11 and p12 of this document.

Where exactly is the process failing for you? Presumably it's during step 2. If so, are you getting an opportunity to enter a pairing code and/or getting a pairing confirmation message?

My thoughts however were along the lines of a simple embedded flowcharting tool for inclusion within the Flowcode project source, enabling simple high-level charts to be created/presented/discussed potentially in advance of code development, particularly for collaborative discussions with non-FC us...

Thanks for pointing this out. To confirm - Web Developer does not support the use of State Diagrams. I will change Flowcode so that State Diagrams are not an option when designing web apps.

Really interesting info - thanks for doing that. When I looked at compatibility, I found it generally ok in most situations. Rendering differences mean that some components may look slightly different on some browsers, but I did not find any functionality problems like you have. That said, you have ...

I've had a quick look and there are others experiencing similar issues. For example this one says it could be a certificate issue or an issue with a browser extension.